Thread

I feel the same. I think we've all finally realized Nostr sucks and no one is coming, really. We built all this giant piece of something that turns out no one really understands or cares, not even most Nostr developers.

I feel the same. I think we've all finally realized Nostr sucks and no one is coming, really. We built all this giant piece of something that turns out no one really understands or cares, not even most Nostr developers.

I feel the same. I think we've all finally realized Nostr sucks and no one is coming, really. We built all this giant piece of something that turns out no one really understands or cares, not even most Nostr developers.

I feel the same. I think we've all finally realized Nostr sucks and no one is coming, really. We built all this giant piece of something that turns out no one really understands or cares, not even most Nostr developers.

Since @fiatjaf has everyone posting their ideas for what nostr needs to get out of its stall, here are 3 simple suggestions: ¶ We need a JavaScript-free self-hostable publicly-accessible Onion service frontend. I'm pretty sure Snowden basically suggested it should be top priority. Basically njump but with posting. ¶ We could use nostr-native visual design tools for making printouts, fliers, etc. with QR codes linking to npubs and posts in various nostr apps. Maybe it could be more multi-purpose than this, but I'm thinking every time a nostrich stays at a hotel with a free printer, they could be printing fliers/newsletters with their best nostr posts to leave out somewhere. ¶ We need to fix Tor on Android and get Amethyst back on F-droid. @Vitor Pamplona has talked about this ¶ All nostr clients should add P2P data integrity verification ASAP - when you interact with someone's post while they're online, your clients could automatically audit your relays by talking directly to each other client-to-client to cross-reference each other's local databases. ¶ We need to improve NIP-13 PoW support across the board to improve spam filter accuracy. People do not like inaccurate spam filters where a lot of bot posts get through and a lot of human posts don't. ¶ I think it also might be good to have a PoW "ticket" relay where an npub just generates sufficient PoW for 1 nevent and they're whitelisted for a certain number of additional nevents to be published from that npub within a certain timeframe, or maybe from that npub+network address combined. ¶ We need doggie coin and Monero tipping ASAP - I will keep working on this point myself. ¶ We need a new nevent format which doesn't use JavaScript or any English-centric code, and which is designed with P2P communication in mind, ASAP. This is another point I'm personally working way too slowly on (almost not at all). ¶ Later, if implementations based on the new js-free nevent format still don't support BitTorrent very well, we need to improve the BitTorrent integration with the js-free branch of the protocol and its implementations. Basically: nostr for indexing and storing small chunks of text, BitTorrent for storing and transferring big data. ¶ We need a tagging system for everything, not just posts, and it should be figured out alongside the nevent format and P2P network. This is why I work so slowly it's almost not at all. It's hard to make choices in one area without impacting another area. The tagging system should help the P2P network deal with manipulation at the technical level and also help the community keep track of stuff at the human level. Some tags would be human-managed, like "this npub has been helpful before." Some tags would be managed automatically, like "this npub is known to have replied before" (so even if a reply isn't in your database of posts, your tags database might still remember everyone you've talked to). ¶ We need a proper Wikipedia clone that doesn't use English-centric formatting unless it's wikitext for compatibility (fiatjaf is very tired of me saying this but it's true). ¶ A proper Wikipedia clone will end up requiring seriously advanced web of trust models once it has a bit of growth. ¶ We need systemic key backups / key rotation. At least 1 client needs to have a profile metadata field for a backup key, and a profile metadata field for a key the profile is a backup for, and NIP-03 timestamps for that metadata field. Is that good enough for people who say they don't join nostr because it has no key rotation built in, or do they need an overly complex spec that talks about derivation paths and stuff? I don't know. ¶ We need a blockchain-based DNS alternative that supports the backup keys / key rotation. I've posted a pretty good outline of a design for this, we would just need to decide collectively on formatting details and make sure to consider key rotation before finalizing the design. ¶ We need git over nostr. I do not have the skills to help with that, @npub1l5sg...gx9z and others are trying ¶ We need something like the old @primal "my tribe" feed to come back and be more well-known this time. A feed that shows posts from all followers could bring some of the most beloved people and millions of their fans to nostr. It would be a big selling point to be able to say "come with me to nostr because I can actually fucking hear you there" ¶ We need w3.do the nostr-native DNS URL shortener, which we've already had the whole time I was typing this. There must be a cunning dev behind that. ¶ We need more people running nostr.

circular economy Düsseldorf style 🍺 Am Mittwoch 26.03.2025 19:00 ist wieder Stammtisch. Wir sprechen dort über Kreislaufwirtschaft, Bitcoin, #Nostr und weitere Themen mit gutem Vibe und Zukunftsaussichten. Brauerei Ausschank am Zoo, Graf-Recke-Straße 103 40239 Düsseldorf https://portal.einundzwanzig.space/de/meetup/meetup-events/l/2150?l=de #Bitcoin #Meetup

I feel the same. I think we've all finally realized Nostr sucks and no one is coming, really. We built all this giant piece of something that turns out no one really understands or cares, not even most Nostr developers.