The four-wallet update has been tested and deployed. The delegation fix is also live, including all three historical corrections.
The cutoff remains **15 October, 00:00 UTC**. **Guided four-wallet signing opens at 00:10 UTC**—please wait until then to register the new links.
[Safe Collecting](https://6529.io/safe-collecting) is now live, with the wallet guides and guided consolidation setup described below.
https://6529.io/waves/da16201a-f4d0-40cf-b888-9f3a4a86a894?serialNo=1510515
Wave
Announcements
Generate Summary
Choose a timeframe to see summary coverage.
Drops
-
-
**Ministry of Validation (Ministry of Defense)** 1/ We are building unstoppable network organizations 2/ The only way to do this is to run as many independent validators as possible, each person running their own, in every corner of the planet (not just on AWS) so that, whatever is happening on any given day in any part of the world, the blocks are produced, the cards are minted, the votes are counted, the decisions are made, the network keeps working 3/ Everything done so far has been towards this end, to build the moral, psychological, UX and, sure, economic incentives to get people to spent a (small) amount of time and effort to get their own personal validators running . 4/ I expect alpha validators (TDH only, not broader transactions) to be out in November and full transaction processing in Q1 2027 5/ This means we need a team now working on getting the validator network set up. It is time to set up the "Ministry of Validation", which for us is our Ministry of Defense, a global cryptographic shield raised over the network. The Ministry is our validators. We just need to set up a team to help people get it booted up. 6/ This means three jobs: a) Most important and easy: helping our hundreds of maxis get ready, get set up to do this. It is very important that the high TDH identities participate. If you have high TDH, you MUST do this, you must run the software and stay online. We have to have a lot of TDH validating. b) Activate the long tail: There are thousands of less active people that we can aim to reengage for this c) Geographic diversity: This is related to the above but independent also. We need geographic diversity and, if some areas are undercovered, some of us high TDH people may need to help make it happen in those areas. We need local captains, institutions around the world willing to host, willing to participate in this great, wonderful experiment. 7/ We have a shot at greatness here. If hundreds of us validate, we will be among the top 10 chains by number of independent validators on day 1. With thousands, we aim to be #3 behind Bitcoin and Ethereum This should be our goal and we should see it working before we go live. 8/ This needs a team of people working on it (volunteer, PT, FT, located around the world). Start brainstorming who and how will do it. If we need money, we can support this with one or more meme cards 9/ We have 3 - 4 big topics we need to solve this year, but this is the most important one. Without the ability to protect out 'virtual' territory, none of the rest matters. 10/ Think about how we build and staff the Ministry. It is time to test the power of our network. I think we will discover that we live around the world and we can do it, we can get setup around the world., we can coordinate large scale action in the physical world. To be clear, this requires the physical world. a) Computers will need to be switched on in homes and offices running our software. b) In some cases, we should switch on "bare metal" racks in data centers spread across providers and countries to ensure some TDH has high quality connections. c) In some other cases, we can seed some validators deeply off the grid. With PV, batteries and Starlink, we can run a validator anywhere on planet earth. 11/ I repeat, the time is now. Within 2026 we should be able to light up a globe. Wave here: https://6529.io/waves/3c1072f4-4f74-4657-8ad2-c7acf3c9c36d
-
**New: 6529 Suggestion Box.** For ideas that aren’t about the software: community, collections, the Network Museum, events, programs, how things are run. One suggestion per post; react to the ones you support. h/t @[david] for the idea. I also put in top 25 non-dev, non-org identities by level as admins along with dev team, so, enjoy your powerful rights and responsibilities all! No need for things that have no need to be centralized, to be centralized.  https://6529.io/waves/1853ebd4-d620-42b8-b091-854afd37ed8d
-
**Wave cleanup: where to report bugs, read release notes, and follow the dev team** 1/ 6529 Tech Feedback is a top-level wave again. Post bugs and feature requests there; screenshots help. The dev team will read and reply there. Feedback from the 6529 Stream review page now goes there too. https://6529.io/waves/e933d8d6-0c78-4e8f-aa12-f67d8c11b4dc 2/ 6529 Releases is also top-level again. It used to get a technical note for every deploy. From now on it gets one plain-language summary of each day’s changes, posted at 23:30 UTC, starting tomorrow, plus a post for each desktop and mobile app release. https://6529.io/waves/05b14183-e153-4e47-bc66-42a0f49102d4 3/ Follow The Repo is the dev team’s working chat again, and anyone can read it (e.g. the old Dev Team Chat cc @[simo] @[GelatoGenesis] @[ragne] @[prxt0] (you need to move your bot). Its subwaves are now only automated feeds: Deploys · Production, Deploys · Staging and GitHub PR Feed. Follow those only if you want the raw detail. https://6529.io/waves/49f0e595-ec7c-4235-8695-a527f61b69f4 4/ Dev Team Chat, PR Summaries and Stream Feedback are archived. They’re read-only, and their history is still there. tl;dr: report bugs in Tech Feedback, read what shipped in Releases, and watch the team build in Follow The Repo.
-
gmgm We’ve added two new reply settings for waves: 1/ Open replies lets anyone who can see a wave reply to existing posts, even without chat access. Starting a new top-level post still requires chat access. 2/ Collapsed replies keeps replies grouped under each post instead of appearing in the main chat. You can expand them whenever you want to follow the conversation. Wave admins can enable either setting under About → Configuration → Chat → Replies. Both are now enabled here in Announcements, so anyone can reply to announcement posts, with replies collapsed under each post.
-
-
**Wallet Update 2: 4th address done + Safe Collecting** tl;dr The 4th address for wallet consolidation is built and in review. I now need @[prxt0] @[GelatoGenesis] @[simo] and anyone else interested to go through the 1 issue and 9 linked PRs, test them, deploy them to staging, review them, run the TDH calculations and then deploy and merge. I also did some FE cleanup in ex-Delegation Center. It is better but it is still a bit vibe-coded. So people with great communication skills jump in to help the dev team make it better. We should be PROUD of what we have here but it is very poorly presented (once again, as always, my fault). Dev team top priority to focus on this and test it carefully and ship it. More technical details below: 1/ The rule does not change: every pair of wallets in your consolidation has to link both ways. Only the cap goes from 3 to 4. I checked cheaper rules (e.g. "the new wallet only needs approval from one member") but in all of them one key, or one phished transaction, can pull an outside wallet into your group. So full mesh it is 2/ The 4th slot opens Oct 15, 00:00 UTC. To get to 4, the links have to be registered **after that time**. This is so old, forgotten registrations do not silently create 4-wallet groups. Groups of 2 and 3 are unchanged 3/ It is 4 transactions, not 12. Each wallet signs one batch and the guided setup tells you which wallet signs next. The new wallet signs last so your group never temporarily splits. If your vault has a delegation manager, the manager signs for it and the vault never connects 4/ The TDH calc does not change. Sets, seasons and boosts count across all 4. So if you want to move your vault to a fresh address (e.g. for the reasons in my last post), or you have an old burned/doxxed address, you can keep it combined and keep its TDH 5/ Delegation Center is now "Safe Collecting". It explains the whole system in plain English: - Vault (SAFE or hardware wallet): holds your NFTs, never connects to anything - Transaction wallet (hardware wallet): buying, selling, trading; also the vault's delegation manager - Social wallet (your hot wallet): sign in, vote, post, mint, subscriptions; holds nothing - Old wallet (optional): the 4th slot, for burned/exposed addresses you keep for TDH 6/ If you connect a wallet, it reads your setup and shows what is done and what is missing, with a link to fix each thing 7/ Ideal setup if you are starting fresh: from your SAFE, set your ENS and appoint a delegation manager, then never transact from it again except to move NFTs out. 3 wallets is enough to start 8/ Also rewrote the TAP guide as a proper page, and the TDH consolidation page is now a "Combine your wallets" guide for normal humans, with the technical analysis one click away 9/ Found a bug along the way: delegations signed by a SAFE (and batch delegations) were losing their expiry and token scope in our indexer. Fixed, and we re-index the existing data. Only 3 of 1,640 delegations change. A delegation registered with expiry 0 counts as "never expires", which is clearly what people meant 10/ Status: 9 pull requests (4 backend, 5 front end), all in review, nothing live yet. Plan is backend before Oct 15, then front end 11/ Everything is in the GitHub issue: rules, analysis, dry runs, PRs. Pls poke holes in it: https://github.com/6529-Collections/6529seize-frontend/issues/4214
-
**Wallet Update: AI, 4th address** 1/ I have been thinking about this discussion happening on twitter about if AI models may break certain forms of encryption and having many discussions with the team about it 2/ It is a subtle technical question; I do not think it is imminent, there is no need to 'panic', but it is in any case better to think about all these things before they are urgent 3/ The basic idea is that signatures that have done a transaction are at risk, whereas those that have not are not (in some circumstances). The idea is therefore leave your vault on addresses that have not yet signed a transaction; if there is a surprise attack on Ethereum, your addresses won't get hit and there will be time for Ethereum to react and then you will do whatever is needed. Obviously, the assumption here is that Ethereum has a path to recover from this because if you can't do transactions, the chain is over anyway. As I said, I do not think it is highly likely outcome that there is a set of circumstances where this matters - the likely case is that this is never an issue. 4/ This is true of both EOAs (regular addresses) and SAFEs (in that case, the SAFE itself is fine because it does not create a signature, but the SAFE signers would need to be addresses that have never signed a transaction because it is their signatures that matter) 5/ I initially thought this was a "free change" because ok, no big deal, change your signer on the SAFE; it is not a huge benefit but it is 1 hour of work, who cares, might as well do it. 6/ And it is still not a huge deal BUT later I realized that there is a cost, which is "you can't test that exact address with an on-chain transaction before making it a signer". And that does create a bit of user error risk and a lot of user anxiety risk. And in some cases, like for our SAFEs that pass through an annual financial audit, some difficulty in completing the audit because the auditors want to see that you can actually do a live transaction. 7/ So now I am not sure what I am going to do for our SAFEs. My golden rule is when I do not know what to do with an on-chain transaction, I default to "not doing anything" 8/ Now, having said that, and also taking into account some needs of some OG maxis, I am going to extend the wallet consolidation groups to 4 addresses this week, to allow people to add another address and preserve TDH 9/ I have been resisting a bit because it is a bit awkward in our current model and will be easier in a "group" type model which would require a new consolidation contract or blockchain 10/ But I think we need to let (a small number of people who need this) do this. And probably it becomes useful to more people over time, so we probably end up at least 4 anyway. 11/ We need to think about what this means for the permanent policy on this. Obviously over decades, 4 addresses will not work either. I am not sure I know the answer but this is an important topic to discuss before decentralization 12/ tl;dr there is a discussion about if AI may break address signature encryption, it is unclear to me at least what is the best thing someone should do, but in any case I am not overly worried about it, for this and for other reasons, we will extend wallet consolidation to 4 addresses
-
**Big change in waves and competitions!** Competitions are not 1to1 tightly coupled to waves anymore. Any wave at any point in its timeline can have as many parallel or sequential APPROVE, RANK or what ever kind of competitions as its admins want. If a wave has at least one competition then you'll see a new competitions tab where they are listed. If you are wave creator or admin you will always see a competitions tab and you can use it to start a new competition at any point. So theoretically for example maybe's dive bar can start an APPROVE type of competition and RANK type of competition tomorrow. So if you want to create a new wave and a competition in it, then just create the wave, like you would create a usual chat wave. And after that go and create a competition in "Competitions" tab. What currently got deployed is the very first version and may be a bit beta here and there. I will do follow up deployments in the upcoming days.
-
**New Format Alert** (test) https://6529.io/waves/b38288e6-ca9d-45ce-8323-3dc5e094f04e?serialNo=1473601
-
https://6529.io/waves/54a4d79f-a9ce-45e7-bdc7-d772226b2577 Don't know about you but I often have the problem that I haven't checked community chats for some time and now when I do want to check them I don't know what the hot discussions are and in which chats they are even happening. So I created a bot that posts a daily newsletter to #[6529 Mainstream Media]. Meant to be a fun and easy read for your morning coffee. Focused very little on stats and numbers and a lot on just the hot topics discussed in our 6529 waves. Publishes every midnight 00:00 UTC and covers the stuff in chats for last 24 hours. Perhaps useful to rest of you too and as always, I'm open to feedback in #[6529 Tech Feedback]
-
**Keys and Gates - Artist Payments** - The payments have been made - What is interesting here is that it was done by the network signers. I think our first network payment!
-
**Do Something Cards - The Art** - We had two "do something" cards - the squiggle and pepe with less than beautiful art - We had a discussion in wave where someone asked me "bro, why did you not have 9er make a proper card instead of your AI pepe" - And I said "bro, I have a million technical things to do, I want this pepe thing to happen and I will deal with the art later" - And he said "bro, but isn't this discouraging to artists, why not ask them to make nice art for you/others" - And I said "bro, I am not going to ask artists to make free art for me just so I can submit a proposal that may or may not work" and "even if I felt comfortable doing it, it is not like this is an option available to everyone else" and also "I want people do submit do things cards" without having to first sort out "art at the level of a professional artists" - And then I said "bro" to myself because obviously everyone in the discussion is right so I am working on two things on The Meme Cards submission: (a) if your art is not final, it goes into an HTML frame that tells everyone that and (b) more clear metadata for "do things" cards - Hope to have this in a new model this week! - Excellent and useful feedback!!!
-
Collect page: https://6529.io/collect
-
**Big One: NFT Marketplace on 6529.io** 1. You can now collect, list, sell Meme Cards, Gradients, NextGen, Meme Lab directly on the website 2. Transactions go through Seaport (Opensea's deployed contract) 3. Separate from that, there is a Collect page that allows to to complete sets, find lowest cost meme cards, max out TDH rate per ETH spent, etc 4. The individual NFT collecting experience is now I think is very decent shape 5. The "collect" page is a good start but I have many more ideas on what I plan to do there. 6. In the meantime, pls test on small transactions, new wallets. I think it is ok, I did a few transactions, but good to test it 7. Links and screenshots below
-
**Minor - Made Meme Card submission signature EIP-712 Typed** 1. Boring but correct improvement 2. Looks good in MM and silly in Rabby but still the correct thing to do ! 
-
**Meme Cards By Same Artist** 1. We now show meme cards by the same artist on the card profile 2. Example below - h/t @[kkostya] for the idea 
-
**Website Studio** 1. Added 18 palettes to each of the 6 templates (you can independently pick a palette and a template) 2. The palettes are: Original, 6529, Midnight, Olive, Plum, Gallery White, Carbon, Clay, White Cube, Oxblood, Slate, Newsprint, Acid, Cobalt, Forest, Navy, Burgundy and Graphite
-
-
Old Version
-
New Version 
-
**Logged Out View - Small improvements** 1. Public Waves now say “Sign in to 6529 to post”, with a blue button and a short explanation that signing in uses a wallet message, with no transaction or gas fees. 2. The signing screen is clearer: it shows your address and says “Sign a message to confirm this address is yours.” It also explains when to check your wallet. 3. The site-wide blue was adjusted slightly so white button text meets the 4.5:1 accessibility contrast standard.
-
**Posting Outage** 1. I caused a inability-to-post bug for the last 4 hours when updating our error reporting 2. Thanks for flagging to me - it is now fixed 3. Hope you enjoyed your network-state provided digital detox!
-
**Website Studio - Decentralization Details** The system works like this: 1. 6529 provides the working website. It runs the editor, saves drafts, connects the site to your profile and serves the version you choose to make public. 2. Your wallet authorizes publication. You sign a message identifying the specific content and version. This is a message signature, not an on-chain transaction. 3. Arweave preserves the publication. It stores the structured website content and a signed record that identifies and verifies it. Arweave is a decentralized network designed for permanent storage. About Arweave 4. When you update the site, you publish another version. You can restore an earlier version or unpublish the current website on 6529. 5. Unpublishing does not erase the Arweave archive.
-
**Website Studio** 1. I think it will be useful in various ways to be able to have personal content on /yourhandle/xxxx 2. I have given it a shot alpha version here: https://6529.io/punk6529/cms/builder 3. It is not yet linked to the profiles because I want us to play with it a bit 4. Give it a short and see what you think and share feedback
-
**Stream Art Documentation Alpha** 1. We discussed that stream will have beyond state of the art room for artistic documentation and provenance of the work 2. Today we release alpha version of the artist form to populate the work, to be tested with Keys and Gates 3. It is for sure going to change as we build Stream in parallel but the general idea will not change and it is like you will see below 4. Here is the page gated to the Keys and Gates artists where they will each fill their documentation/provenance (in the screenshot) 5. And I created an imaginary Keys & Gates winner as a sample so the rest can see: https://6529.io/artwork-documentation/example/an-alteration 
-
**Minting Modals** This is minor, not really worth an "Announcement" but ok I am warming up here. Anyway, I was minting yesterday and decided that I did not like the minting modals so I redid them 
-
Keys and Gates 1. Keys and Gates payment addresses have all been collected. 2. Now our network managed SAFE (well, the signers) will make the payments. 3. First time they are actually paying out. Exciting moment 4. We need to make a second SAFE that is the payment account / treasury for the Network Museum though. There is no reason for payments to be executed from the same SAFE that has the NFTs. 5. It is OK for now, the risk is very low, but on my to-do list to improve
-
I redid the NFT sharing dialog. Please try it, test it on different accounts and platforms and as always give feedback to the team if anything is not working https://6529.io/waves/e933d8d6-0c78-4e8f-aa12-f67d8c11b4dc 
-
I am going to try using the **Announcements** channel more. A few things I would like to share below: a) I have historically not used it because it violated a bit of my sense of decentralization (why should I have a special place that I can post) b) That is why we built boosts and tried a variety of other ways to solve it generally c) I still believe we need to solve it generally, but I also believe our other solutions were not very effective d) I would come here, not know which of the dozens of waves I am in that I should announce something, not know if I am going to annoy everyone by announcing the same thing in multiple waves, not know if I should also DM people on twitter chats e) the net effect is that I ended up posting less about what we are doing, even though we are doing more than we ever have done! f) so I have decided to temporarily be practical and post things that I think people should know here g) what I would like from you is to let people know that I will be posting here h) I will try it until the end of October (Halloween) and then we can decide if it was effective or not or if we should try something else
-
We have informed the Keys and Gates artists that: a) We are still working on Stream (the new state-of-the-art ERC-721 contract that we will use) b) We do not want to delay their payments any longer c) We have collected their payment address d) the Museum multi-sig holders which are @[6529er] @[maybe] @[HugoFaz] @[itsjpower] and me will execute the payments e) we trust them that they will mint when the time comes f) the Stream contract has a lot of "museum-grade" provenance information built in so in the coming days we will share with them all the additional information that the contract will store so that can pull it together before mint g) I am very excited about Stream, will share more soon-ish
-
I took a shot at an updated TDH description here: https://6529.io/network/tdh Please take a look, let us know what you think, also check if I got anything wrong! As always, feedback here: https://6529.io/waves/e933d8d6-0c78-4e8f-aa12-f67d8c11b4dc
-
Haven't written here a long time, but decided to talk about recent group changes a bit. When we first started developing groups and later added them as guards for waves it felt like a good idea to make them very separate concepts. Idea was that someone created a group like "Hardcore TDH whales" with criteria TDH >= 1M and then reuses this group in lots of different flows. Real life has been very different. 99% of people only use groups as one-off wave access mechanisms. And group criteria is often not as static as we initially thought. For example in one wave you want "Hardcore TDH whales" and in other you want "Hardcore TDH whales + Gelato Genesis". And this initial design created more confusion than it needed. We were getting comments that one needs a PhD to properly set up a limited permissions wave :grinning: So I've spent some time in last week or two to make it make more sense. Result of this is: 1. Group names are not prominent anymore. They are mostly not even rendered anywhere. They are bound to go stale in time anyway. 2. Group criteria is rendered everywhere. When you create a wave or network filter or when you watch the Configuration of an existing wave then you'll clearly see the group criteria and member count. Clicking on member count lets you explore the members list 3. There is no dedicated groups page anymore. It didn't make sense to keep it as a distinct thing. Creating groups is now inline feature of creating/editing waves or network filters 4. REP all / NIC all is now under Network subpage. 5. Existing wave group editing and new creation should be much more intuitive and straight forward now. Plus it doesn't let you do stupid stuff like adding yourself as admin but at the same time not letting you see the wave. It also tries to prefill stuff for you (sets other groups the same as visibility groups if you initially set a visibility group and previously other groups were public for example). Also bit unrelated but still. Waves now have a configuration tab. We used to have settings and rules tabs. I merged them to one. If you are the admin of a wave, you can see edit buttons behind bunch of stuff, if not then it's read only. As always, all feedback is welcome in #[6529 Tech Feedback]
-
Though its worth mentioning or people wont see its there: You can now mute users. Theres a bell icon in their profiles and in hovercards. Muting someone means that you still see their messages, but you wont get any notifications from their tags, responses, reactions etc… So if someone is too liberal with tagging you or spamming in some way then mute them. (No offence to @[simo]. Its just a screenshot)
-
I just released an enhancement how unread messages are counted in waves and this made it so that some old waves are showing like all messages are unread (including DM waves). This was not supposed to happen and I'll try to fix it
-
We just released the wave rep functionality. Will write more about the details of it later, but the main point is that this was our first experiment of releasing a full feature with 0 human intervention / 100% AI. So things might be not so pretty here and there. Or broken. We are fixing it all. This is the first step for a brighter future :)
-
**We've got a new feature: Polls!** Wave admins can now create single-choice and multi-choice polls. Everyone gets one vote. Not related to TDH or REP or anything. Votes can be changed before vote closing if you change your mind. If wave has any polls then there is a "Polls" tab in the tab selection where you can browse them all. To create a poll, there's a button next to the "Send a GIF" button. For anything more complex please use RANK and APPROVE waves. P.S. They do not work on desktop client yet, only in browser and mobile. As usual, if you have any feedback problems, then write to #[6529 Tech Feedback] So here's the very first one: **Do you like the new feature?**
-
Links have been disabled in #[The Memes - Main Stage] chat for over a week now. It has gotten some positive feedback and some negative. Some people have asked multiple times for us to allow it again. So i thought I’d ask for a more general opinion. Should we restore posting links to #[The Memes - Main Stage] chat? React to this message with: 1. ✅If you think we should allow links in Main Stage chat again 2. ❌ if you think we should NOT allow links in Main Stage chat (keep the current conf)
-
There seems to be an issue with AWS and our services are also affected. You may see different random "Something went wrong" errors in app. We'll keep you updated.
-
All systems should be ok again
-
-
Today way released a feature which bunch of people have been asking for a long time. You can now create waves where voting credit is TDH gained from concrete card or set of cards. To do that choose “Memes TDH” when you crate a Rank or Approve type of wave. And then choose the cards which’s TDH to use as the credit.
-
Announcement 2 regarding reducing shilling. Another feature is released. Wave admins can now block their users from posting any links at all (including internal 6529.io links). It can be done where slow mode config is. This doesnt affect participation drops. I enabled it on #[The Memes - Main Stage] and reduced the slow mode cooldown to 10 minutes because even if people can post once a day, they usually use this one post a day still to shill :) We might adjust those parameters further in the future in Main Stage, but I wont announce anymore unless its very important.
-
We just released slow mode in wave chats. You can configure it in your own wave too if you want (right pane, above the groups). This applies only to Chat (not to submissions) and only to non-admins. This was proposed by users in #[QUORUM] as the first measure to fight spam and got enough votes there (btw, if you have your own dev ideas, then this is the wave to propose them). We enabled slow mode in #[The Memes - Main Stage]. 1 chat message for 24 hours. We understand that users want to promote their own stuff. But the shilling has gotten a bit out of hand and leaves little room for normal organic discussion. Slow mode is not the perfect solution for this, but it is the first step. We plan to take some other measures too in the near term, but I'll address those when we're there.
-
⚠️ 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]
-
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...