⚠️ The following is important mainly to the people who have written applications against api.6529.io or plan to do so.
**All waves and drops related GET API's now have a v2 version and we've deprecated the old versions**
If you have any plans to code something that uses our API's brain part (waves, drops etc) then **I strongly discourage** you from using GET API's like. /drops, /waves, /waves-overview, /feed, /boosted-drops, /curated-profile-wave-drops, /notifications.
**Instead you should use the alternatives starting with /v2/ in URL.** (/v2/drops, /v2/waves etc).
https://api.6529.io/docs/#/DropsV2
https://api.6529.io/docs/#/NotificationsV2
https://api.6529.io/docs/#/WavesV2
These are leaner, more performant and guaranteed to be fully maintained in the future.
All the old ones are deprecated in documentation.
**What if I already have something built against the old ones?**
If possible then I suggest you change it to use v2 endpoints. Then you'll be guaranteed to benefit from future features also. But if you can't then don't worry. We are not planning to disconnect the endpoints any time soon. There are a lot of external integrations depending on them.
**Are you planning to migrate more API's in the future?**
Might be yes. There's no concrete "next up" but at some point some other API's might be worth tackling. I'll keep you posted then.
**Why did you even do a V2 API?**
We've developing the brain part of this app for something like 2 years now. Most of this time has been spent experimenting and assuming stuff. But like we all know the assumption is the mother of all f***ups. And so the API has been growing and growing to be a pile of ideas and pieces laid on top of each other and by now it's kind of a mess. Much of the stuff there doesn't make sense knowing what we know now. Dragging this mess back-and forth between API and FE wasted a lot of useless bandwith. It was not easy to remove/restructure stuff, because we don't control the external integrations. So we decided for a v2 API set. 50-80% smaller payloads and still has all of the info.
Our own UI is already using it since today. And you might notice some small changes here and there visually also. Biggest one is that you can't see top contributors identities overview in leaderboard without actually opening a concrete drop.
If you do see anything weird in the UI or something misbehaves somewhere or you have any API related questions then tag me in #[6529 Tech Feedback]
Wave
Announcements
Generate Summary
Choose a timeframe to see summary coverage.
Drops
-
-
Seems that the new "Profile Waves Feed" has caused some confusion so let me clear things up. P.S.: Following only applies to desktop and is not released to mobile users yet. On left in the waves list on top of the Announcements wave there is a new item "Profile Waves Feed". When you click on it, you see a stream of drops from different peoples profile waves. **How do you get your own stuff there?** Create a profile wave and profile curation, add your work to this curation and it pops up there. **Whats the point of this whole thing?** To give artists a way to be seen and to give all the rest a way to see what people are up to. **Shouldn't we add some filters to it (REP/TDH)? Wont it otherwise just be an endless stream of spam?** Maybe in the future when we do in deed see that it becomes too spammy. But for now, it's a way for new community members to be discovered. Once you already have some TDH, some REP, etc, people have probably noticed your work. In Main Stage or elsewhere. But when you are totally new, it can be hard to get anyone to see your stuff. So this might help. Lets see. Second thing is, that it will hopefully lessen the thing where people silently do their stuff and no one ever notices because they aren't that much of shillers. To sum up - lets see how it goes and if it turns out to not work as we expected then we'll adjust.
-
@all As you see we now have the possibility to tag all wave joiners at once :) 1. You have to be wave admin to do it. 2. Only people joined to the wave you do it get notified it. 3. You as a joiner can opt out of "all" notifications in a concrete wave if wave admins get too spammy (see the attached screenshot 1) WAVE ADMINS! USE YOUR NEW POWERS RESPONSIBLY! P.S. - We plan to add other tags in the future in addition to all. @developers, @artists, etc... Also some other news: You can now select a wave to be your official wave. You have to be the creator of the wave and the wave has to be fully public. Then go to the wave, open right pane, click the three dots, click "Set as profile wave" (to undo it, click "Clear profile wave") (see screenshot 2) What does this do? If you create a curation to this wave then things curated to this curation will wind up in your profile under section "Curation" (see screenshot 3). Point is that you can treat your profile waves curation as your profile extension. Excuse us, this is beta, so the UX of it all is kinda shitty still. We are working on making it better. Some things to know until that: 1. You can only have one profile wave at a time. If you already have one, and pick another, the old will be replaced with new 2. If you have multiple curations in profile wave then only the drops in the first one will end up in the curation. (We will change that soon, so you could choose the curation you want streaming to your profile) 3. We backfilled some of your waves to be "the profile waves". This applies to anyone who had exactly one public wave created by them at the time of backfilling. Rest of you have to do it manually. Any questions/feedback about all this? Send to #[6529 Tech Feedback]
-
I would like to congratulate @[maybe] and @[HugoFaz] for their election to their term as Network Museum Vault Signers and @[david] and @[blocknoob] to their election as alternates. It is heartening and encouraging that once again the candidates and the voters did the right thing. I would have been thrilled with any of the candidates so I did not vote, but I think the outcome is great.
-
Chat for announcements
Loading more drops...