Go on wss://subnet.relays.land/. What number do you get? Mine is 177.

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.

Fevela

A Nostr social client that give you back full control of your attention and time with an innovative interface

now has per-relay reply and reaction fetching: Can you think of a concrete use case for this that doesn't involve Marlon Brando?

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 →

Thank you for coming to my stream:

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 🧑‍💻 @Kieran @Vitor Pamplona @Sirius @Cody

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:

I did an Android local relay app, it is called Topaz and you can download it here:

GitHub

Release v0.0.1 · fiatjaf/topaz

a nostr relay for android. Contribute to fiatjaf/topaz development by creating an account on GitHub.

Citrine is great, but we needed at least one other implementation, and Topaz is running Khatru underneath, which is cool.

The NIP-29 groups ecosystem is getting pretty good. View quoted note →

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 →

If you are a bored ex-programmer in this sunday evening here's something for you to look at:

GitHub

NIP-5C: Scrolls (WASM programs) by fiatjaf · Pull Request #2281 · nostr-protocol/nips

Instead of writing a description for this PR I recorded a lengthy video: https://nostr.media/50da90a24726067baaa3e1285b0b8e1a098114f08d2ba859271dc3...

Please send feedback and suggestions if you have any.

I just realized people talk about "Android". They know that many different phones and even other types of devices all speak this same "protocol" called "Android". They know that there are many different apps that can be used in Android but not on iPhones. They know that there are many flavors of Android, but that there is something that is the same underlying all of them. It's not a perfect analogy with Nostr, but regardless of that UX specialists would have led us to believe that no one would be able to understand or care about such technical details, and that these technical details should be hidden at all costs, but they're proven wrong again. Are there other examples of this phenomenon? I guess there are also email, podcasts, SMS messages, web browsers and HTML (although this is a bad example it's still valid).

YouTube has a subscriptions page that used to show me just videos from channels I've subscribed to in chronological order. It was great. Now most of the screen is filled with some recommended content "for me" (or "most relevant", who knows, they're still tweaking things apparently), which is basically just reordering the same few videos I have in my subscription, such that I can never get a clear picture of what is new and what isn't or what I have already watched or skipped and what I should take a look at.