Oddbean new post about login | logout Some fundamentals of Nostr and where exactly we should strive for most decentralization and why were never very clear to me, as well as how should we go about dealing with microapps and "other stuff" that isn't microblogging, but today I got this better understood (although the article might not be as clear to readers): nostr:naddr1qqyxxepcvdjnyc3hqyghwumn8ghj7enfv96x5ctx9e3k7mgzyqalp33lewf5vdq847t6te0wvnags0gs0mu72kz8938tn24wlfze6qcyqqq823cwf295e
Hopefully this will be helpful to the podcast-on-Nostr crowd @merryoscar, and after reading nostr:naddr1qvzqqqr4gupzq3svyhng9ld8sv44950j957j9vchdktj7cxumsep9mvvjthc2pjuqyghwumn8ghj7mn0wd68ytnhd9hx2tcppemhxue69uhkummn9ekx7mp0qywhwumn8ghj7mn0wd68ytnzd96xxmmfdejhytnnda3kjctv9uq3wamnwvaz7tmjv4kxz7fwxpuxx6rpwshxxmmd9uq3zamnwvaz7tmwdaehgu3wwa5kuef0qqxnzdej8q6rswphxuunvdfnm0s0ut I am hoping that even @Vitor Pamplona will. @PABLOF7z is the one that won't like it since he is a solution-b maximalist.
Ha-ha. 😒 Not a maximalist; a hopefullist.
Magical Other Stuff Hopefullist has a nice ring to it
Meh, aren't you now assuming that if I follow you as a microblogger, then I also want to know about all other stuff you do, which is not necessarily the case?
All the 3 solutions in the post assume this. And I agree it's not the case all the time, that's why solution-c at least gives the microblogger the option to not talk about his other stuff in his microblog, if he is aware of the fact that the people following him might not be interested. Not all people who have podcasts also send a note on X.com about their latest podcast episode every time.
Developers are still thinking in terms of NIPs, Relays and Zaps instead of focusing on use cases. They focus on tools and adding more complexity to the ecosystem instead of bringing real use cases that creators can use. Apart from zaps, nearly no work is done to develop the tools needed by musicians, artists, podcasters and teachers.
You need the Kind 01 reference, like this, to ensure that people can respond to your article. Replies to OtherStuff events are extremely buggy and flaky. If I open this up in Habla.News, I can't post a reply to a reply. Just get errors. Or, I post a reply and it doesn't show up in the list. Just floats around in Nostrspace, wherever. Or I post a reply there, but I can't see that reply in a different long-form client. Also, content discovery tends to be extremely difficult, for everything except Kind 01. I often can't see articles, from people who are writing to my own relays, or I need to toggle back-n-forth between four clients, to see the article and all replies, and to post a reply.
All of that sounds more like an argument for apps that are excellent at: 1️⃣ Replies on [ANY CONTENT TYPE] (without them having to actually display the content properly, let alone let users interact with it) 2️⃣ Aggregrating [ANY CONTENT TYPE] around the niche communities that are interested in them. Making discovery something that organically happens, instead of something you have to start iNfLuEnCoRing around for in the kind 1's you're blasting out to god-knows-where.
Well actually I guess you are back to problem 2 that Fiatjaf outlined namely that many microblogging clients would then ignore your other stuff keys. This would be a problem with my solution as well. In Fiat's solution c, spamming other stuff into type 1 gives the advantage that microblogger apps would appear to suck, if they don't handle these signals in a pretty way (implementing or NIP31 & NIP89 help).
Which is exactly what keeps most users/builders in this Twitter-clone feedback loop. The answer to "But most people only use Twitter-clones, so how will they ______?" isn't more Twitter-cloning 🤦♂️ . Endless discussions about how to match Nostr's inherent multi-content type nature with a kind-1 feed 🆚 Building apps :110percent: based on the premise that Nostr has a multi-content type nature (that said, it's time to take my advice and stop discussing and start building, lol 🙈 )