Collect page: https://6529.io/collect
Wave
Announcements
Generate Summary
Choose a timeframe to see summary coverage.
Drops
-
-
**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...