Oceans of Wisdom

@[simo] totally minor but for consistency, I think I would make this breadcrumb now "My Stream" To match what it looks like when it is expanded 

testing a quotedrop squared https://seize.io/waves/0849642f-1770-4de2-9cbc-70aae59c17ff?drop=e8a2d536-9927-406c-b5ae-6abfc571ddbf

I am going wild in my own head because I keep thinking of new ways we can use waves to decentralize things that today are centralized even in crypto. patience 6529, patience 6529, need to wait for us to get the basics done, but I am going wild inside my head. I will try to work some easy examples into our development pipeline the coming months just to make the point

Nice looking updating visual improvement @[prxt0]!

@[prxt0] auto-update on 6529 Core Windows 11 threw this error Error: Command failed: set "PSModulePath="; chcp 65001 >NUL & powershell.exe -NoProfile -NonInteractive -InputFormat None -Command "Get-AuthenticodeSignature -LiteralPath 'C:\Users[username]\AppData\Local\6529-core-updater\pending\temp-6529-CORE-win-0.0.4.exe' | ConvertTo-Json -Compress" ``` at genericNodeError (node:internal/errors:984:15) at wrappedFn (node:internal/errors:538:14) at ChildProcess.exithandler (node:child_process:422:12) at ChildProcess.emit (node:events:519:28) at maybeClose (node:internal/child_process:1105:16) at ChildProcess._handle.onexit (node:internal/child_process:305:5) at Process.callbackTrampoline (node:internal/async_hooks:130:17) ``` Path, permissions or encoding issue I guess

@[ragne] @[simo] I think when you are in the wave, having the wave name in every drop and reply is unneeded. This is needed in my stream bc there you do not know which wave it is from but in a situation like the below it is not needed IMHO 

@[ragne] @[simo] I think there is no way to get to "my stream" from here (see screenshot) other than main menu which is slow and annoying way to do it. Can we consider replacing "waves" in the breadcrumb with "my stream" 

@[simo] after the first time you break into a storm, I think the message for the 3rd, 4th, etc part of the storm should not be "Break into storm" as we are already in a storm. Maybe "Continue storm"

@[GelatoGenesis] not an immediate priority but when you can can you add to the endpoint for waves sort/paginate by: a) total number of drops in the wave (all-time, last month, last 7, last day) b) when a certain user has last dropped in there As people follow more waves, having some type of intelligent sorting algo will be relevant 

@[GelatoGenesis] @[simo] I don't know if it is backend or front-end issue (probably back-end?) but individual drop screens (when you click on a drop to get just the page with the drop) are a bit slower to load than they should be. We should make them snappy ;)

@[simo] in replies embedded links lose their link and show this error message "invalid link" 

FYI If you download the iphone app via testflight **via our public link**, we don't get any information about you! Details below its anonymous when downloaded using the public link i shared we get only get 3 things: status (version installed and when it was installed), device info and number of sessions and that's it 

Time to test @[simo]'s new release

@[simo] 1. See the below 2. When I click on the quoted drop, my expected behavior is that I would go to the quoted drop as in twitter (the one by 6529) 3. instead it opens up the one by ghostpepper 4. Even then, I think you cannot get to the original drop 5. I think the behavior here should be just like twitter 

yes, ok that could be it also since we are talking about emojis, we need an emoji bar including with cool emojis

feeling left out!!!! I have not yet tried the app lololol

OK EVERYONE IMPORTANT DEVELOPMENT WE NEED TESTERS FOR THE IPHONE APP. WE HAVE ROOM FOR 50 TO START. SEE NOTES BELOW

@[simo] Here I just posted in my tweet with a normal-sized emoji and while this mega-emoji looks cool in this specific case so I dropped it anyway, I think the emojis should be normal sized lololol 

1. Things doable this fall. 2. Publish NFTs through 6529 Core 3. Mint NFTs through 6529 Core 4. In both cases above, Ethereum is the database 5. So once the functionality is all built into the app 6. You have an end-to-end system that is decentralized 7. Brain/Rep/CIC will need a bit more work to decentralized 8. It is going to be soooo coool


Economics Professor: How should you catch up vs your strategic competitors in tech? the EU (eager): I will regulate tech more than they do!!! Prof: Umm, well, I'm not sure about that the EU: OK, OK, I WILL **ARREST THE CEOs** Prof: 

The Telegram news is shocking. EU is going to burn itself big-time in tech.

**Some Thoughts On Where We Are** I would like to share a general idea of how I see the pace of progress on software development. 1. Current focus: Clean up UX on "chatting" - there are all types of obvious improvements that we need to make and are working through and, in aggregate, once they are all done, the quality of life of seize chatting should get to an acceptable modern level 2. Along with #1, we should hopefully get out mobile apps for Apple and Android in September 3. Remember that "chat" is not strategic to what we are doing, but I could not figure out how to do what we are going to do without having native chat. In my mind, it is a helper function and it has to exist first because if we are going to vote on what Stream NFT to mint (as an example), we need the ability to have a discussion about it. So to reiterate, I do not think we are building a chat app or that the world needs a chat app or a social network. I am overwhelmed with chat apps already. We just need to be able to communicate with each other 'on site" or "on network" in service of a "decision network" 4. I am forcing myself to use web and desktop so I can feel the pain points which are still there. I think by mid-Sept, the ability to have a conversation will reach non-painful, no worse (and no better on average) than Discord or Twitter GC or TG. 5. Once we get to "acceptable user experience on chatting" we will have the decision-making infrastructure start to roll out. This, to me, is the important part. This will have its own set of interesting challenges and here we will need people trying to use it. Unlike with chat where we all have 20 years experience on what that feels like, there is no obvious parallel so we will be inventing the UX as we go along 6. Once #5 is in place, we then roll out the tools to implement (some subset of decisions) on-chain. There are a series of smart contracts we have ready (we are twiddling our thumbs waiting for the front-end to catch up) but they need #5 done first to be deployed. The TDH oracle is part but not all of this. 7. Let's say all of this takes us into October and is stable and working acceptably across web/desktop/mobile 8. At this point, I think there is a divergence between: a) people using it to actually do things, make decisions, etc (e.g. curate Stream) which at this point can start working. So basically a longwinded way of saying I see Stream ERC-721 contract as being live in Q4 2024 contract b) and final boss work on decentralization which will be a long surgical effort of removing dependencies on the centralized APIs in the desktop app. In other words, everything will either work peer to peer or Ethereum to node when 8(b) is done fingers crossed, etc etc, there will be unexpected problems for sure here. We *think* this will work but it is the last frontier part. 8(a) is ok as an outcome tbh; centralized decision-making and decentralized implementation of the decision, but I hope we can get going all the way to no single dependency on anyone which needs 8(b). I would say end of Q1/Q2 2025 is feasible here. 9. To make 8(b) more clear, I want to see if we can get to world where if all of 6529 team gets teleported by space aliens to AOS land, are never seen again, the website disappears, the AWS account disappears, everything can run normally, from the desktop apps If we get this to work, we have made something very special, very new, very non-existent, a decentralized decision-making layer, with no external dependencies on any normal web infrastructure. I think it is doable and if we have this, this is the actual beginning of a network state. it is the ground floor. I spoke to (famous network state promoter) last week and said "but all current network states are 100% dependent on centralized infrastructure. Once 6529 gets to where we want to get to, then you can actually build on a decentralized stack on top of what we are doing. 10. I don't think any quite like this has been done before and there are various concepts that I need to write up formally once we have it 11. I think I am willing to take down the Levels gate at point 8(a) 12. I think this alpha period is proving to be correct and valuable as expected. There is no reason in my mind to let 1,000 or 5,000 people in to have a crappy UX experience on web, not have mobile, to be discovering along the way what things are doing wrong 13. What can you do to help? Use the system please. Use web, desktop, mobile (when it comes out). Tell us where it sucks. The more we can fix now, the better the experience will be for new people. Also, anyone with software development expertise who wants to hop into the repositories and take anything on, we are happy to have more help! 14. OK, going AFK for a while. Will be back later in the day. Hope this all makes sense. Overall, I am happy with the pace. Early August was a bit slower as people took some well deserved vacations but we are cooking now.

life at 6529 Capital with @[BatSoupYum] 

Replies in notifications are kindof odd in that: 1. You see your whole drop (which you presumably already know since you wrote it) 2. You see very little of the reply (which you want to read) 3. The reply is on top of the message 4. I think all of the above should be opposite: a) excerpt of your drop (you know it) b) full expansion of the reply c) reply below the drop it is replying to @[ragne] @[simo] 

lol required metadata is not workable @[prxt0] @[simo] @[ragne] 1. you don't see where you have to put it unless you expand the text box 2. you have to manually type in the key value label 3. if a wave has required metadata: a) it should auto-fillin the label b) auto show the needed labels (no expansion needed) 

1. I minted on core / windows 2. minting worked 3. minting page kept showing ... (see below) 4. then "unknown RPC failure" 5. but it actually minted 

In terms of easy improvements that are not voting and not speed, my suggestions for @[simo] @[ragne] @[GelatoGenesis] as the most important immediate improvements are the following: They are individually not crazy hard, but the aggregate set of them will be a big quality of life improvement and I would focus next week on them and get those done before we do Rank and Approve because it will make it much more plausible to use this as our main communication platform 1. Make wave title clickable 2. Make Wave | Wave into the name of the wave 3. On My Stream add two more categories in right side: a) My Waves (Waves I have made) b) Followed Waves (Wave I have followed) c) I would move Popular waves to 3rd place 4. If you combine #3 with: https://seize.io/waves/0849642f-1770-4de2-9cbc-70aae59c17ff?drop=077bf7f9-b5cf-4b74-8630-c5091c6c41ab you can make "My Stream" the command center 5. In Waves change the color of "My Waves" to not make it grayed out 6. In Groups make "Add me to a group I made" independent of way to create a group and very visible 7. Add internal 6529 NFTs as easy-to-make groups "holders of meme card 69" 8. Allow for private groups (I might want a private wave but right now the wave membership leaks through the group 9. Every time I make a wave with similar memberships, do not create another group 10. Allow deletion of drops 11. Allow deletion of waves 12. Allow edit of waves 13. Allow edit of drops but only for a short period of time 14. Allow more than 1 media asset uploaded to a wave (at least 4 as a next step) 15. HIGH QUALITY ASSETS. Allow expansion at much better than twitter quality of photos and videos. a key stakeholder are artists and an easy way to differentiate is allowing people to share their art in its full glory and resolution. 16. When a link is placed in a drop (of another drop) convert it to a quote drop (expand it) 17. Support OpenGraph and Twitter card for drops (e.g. if someone shares a link of a drop return both OpenGraph and Twitter card data 18. When someone shares an external link, expand based on OpenGraph and Twitter Card data 19. Move pinned drop in a wave to the left somewhere (this is the quick and dirty solution but it is annoying seeing it in the way all the time) 20. The long-term solution for #19 is to have another tab in a wave for popular drops ranked by how much TDH they have but since this needs endpoints, etc I would deal with #19 first 21. When writing a long drop like this give us a drop button at the bottom too I have other ideas too but the first 21 I think are a good start ;)

@[simo] @[ragne] so something for you to consider. 1. I find "my stream" to be an incredible experience. far better than the discord experience of all my discord chats being disaggregated and I have to go into each channel to find what I want 2. I do all my replying from there 3. the only weak point is that when I want to drop, I need to come into an specific wave and it is a bit of a hinderance 4. I think my stream should also have a drop text box with the most popular waves you follow as buttons below and a select to see all. I think it might need some fine tuning but I think it will be a very interesting experience to be able to operate across all your waves in one place

 check out font got mixed up on reply

1. OK I think release is quite fast for basic dropping. 2. good job @[simo] and @[GelatoGenesis] on this 3. From my perspective, I would move on on web to: 1. A variety of other UX improvements (smaller ones) we can easily knock out 2. And get on with Rank and Approval which is the real thing 4. What does everyone else think?

testing something

has anyone tested the Mac desktop app?

we did another speed improvement today. testing to see if real

what a boss card

So dropping posts should be meaningfully faster. time to appear should be down from 4-5 seconds to 1.75 to 2.00 seconds. Still work to do but a good step forward. I had to reboot my computer before I saw the performance increase. Currently only on web; will get this to Core soon. Give a shot and let me know what you think.

seeing this in console 

@[simo] I think this "show more" is totally unnecessary just to show that simo is mentioned in this text. show more implies that there is more substantive text then I click and just find out "simo" which I can already see. option 1: do not hide the identities mentioned option 2: get rid of the identities mentioned section altogether But in any case hiding them beyond a "show more" is unneeded 

trying another new drop to see what @[simo] has done

On Not Buying A Dali Tonight https://x.com/punk6529/status/1826358529554612560

@[simo] I think tomorrow we can drop the level gate to 10

good tweet https://x.com/StartupArchive_/status/1826225251103162483

omg that was nuts. who made this?

Wave title should be clickable to return to stream if you are at the level of a drop 

Centralized Verification, Part 69 The latest in the saga of getting our Apple Developer signing keys for the Core on Mac. This is the nth annoying thing in the process. Every time we think we are "done", we are not. Imagine thinking that all this is not going to get swept aside by self-sovereign crypto From the Apple Forums. "There’s been a recent spate of issues where notary requests get stuck in progress for a long time. This seems to primary affect folks who are notarising for the first time, but I’ve also seen it affect other folks. The first thing to do here is to wait. The blockage usually clears itself in a day or two. And once it’s clear, my experience is that new requests run quickly again.'

I think quote drop window when typing it should go above quoted drop since that is how it is displayed in Stream. this makes it look like you are writing a reply

@[simo] @[prxt0] @[GelatoGenesis] @[000] We need to start putting scope on releases Web Core etc

ok missed the announcement by @[simo] so we have been fighting / struggling with how to best handle replies. we just released last night the first batch of improvements: a) references and markdown available b) they appear in a different order (this still needs some work to see chatting style; also, separately we are optimizing the speed but that is not live yet) c) I think we need to add upload media to the drops d) also need to add to Core

1. @[simo] did you release drops as replies? 2. you need to announce in releases and meme-chat if you did and what you did 3. don't we need to allow the media upload and expand icon too? 4. also it does not feel like they are drops. i dunno if the box needs to be bigger 5. @[prxt0] we need to get to core too noting the above

 @[prxt0] - I think: a) beta label off on mint on seize b) swap order c) Add a "backup" label on mint on manifold