fiatjaf's avatar
fiatjaf
_@fiatjaf.com
npub180cv...h6w6
~
fiatjaf's avatar
fiatjaf 2 months ago
Go on wss://subnet.relays.land/. What number do you get? Mine is 177.
fiatjaf's avatar
fiatjaf 2 months ago
Seeing how people add all sorts of URLs to their Damus relay lists I wonder if the best Nostr app UX isn't just a single big list of stuff. Do you want to write to a relay? Add it to your list. You want to read from a relay? Add it to your list. Do you want to browse a niche relay every now and them? Add it to your list. Want to upload stuff to a Blossom server? Add it to your list. Wanna bookmark a note? Add it to your list. Wanna join a NIP-29 group? Add it to your list. You're interested a hashtag? Add it to your list. Follow someone? Add to your list. Do you want to run custom spell or scroll? Add it to your list. Then the app understands everything you want from that and displays all the UI views you need.
fiatjaf's avatar
fiatjaf 2 months ago
I like that these guys are holding a sign that says "this is not AT". A clear message that they have evaluated the Bluesky protocol and decided, correctly, that Nostr is the real deal. View quoted note โ†’
fiatjaf's avatar
fiatjaf 2 months ago
Has every client stopped offering an option to use imgproxy for autoresizing images? I remember users could configure their own imgproxy on Snort, Iris and Coracle. Was that a bad idea because no one was using the option and if anyone used they would have a sitting duck imgproxy that anyone else could abuse? View quoted note โ†’ We could think of some solutions for community-hosted imgproxy servers that can be secure by having the client compute the required HMACs locally, or is this too ambitious? @hodlbod @utxo the webmaster ๐Ÿง‘โ€๐Ÿ’ป @npub1v0lx...qj49 @Vitor Pamplona @Sirius @Cody
fiatjaf's avatar
fiatjaf 3 months ago
Every part of Nostr that relies on hardcoded "big relays" is a bug and a gate to spamland waiting to be used. Spam gets to everything, whether it's malicious, automated spam or just someone handwriting something in the wrong place because they were confused. Even the relay reviews section isn't exempt: image
fiatjaf's avatar
fiatjaf 3 months ago
If we had infrastructure for curating entries, allowing groups to vote on proposed additions and deletions and simple UIs for viewing the list of all items in a list then it would be easy to get rid of the NIPs repository. It's sad that after so many years all we have are "feed" views. And GitHub continues to be a better platform for browsing and updating text lists of things. Notice that I'm not asking for much. We would also have to get rid of the NIP numbers, but we could just say "the longform NIP", "the badges NIP" etc and it wouldn't be hard to know what were people talking about. But if you're reading this and thinking about a complicated system with events being published with votes, proposals, lists of replaceable events with other lists inside or whatever absurdity, please stop. Just use a relay and normal events inside, add and delete. Custom write policies, standard Nostr read API. #pyramid has a moderated subrelay that is probably 25% there already. If you disagree please let me know. View quoted note โ†’
fiatjaf's avatar
fiatjaf 3 months ago
fiatjaf's avatar
fiatjaf 3 months ago
Do we need a standard to tell clients to not render our links as rich previews?
โ†‘