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.

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 →

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.

This is so stupid.

New #pyramid release

GitHub

GitHub - fiatjaf/pyramid: a wondrous furnace of communityzenship backed by a dynamic ladder of socialhood

a wondrous furnace of communityzenship backed by a dynamic ladder of socialhood - fiatjaf/pyramid

with new stuff: Paywall (or exclusive content) support (following

GitHub

Build software better, together

GitHub is where people build software. More than 150 million people use GitHub to discover, fork, and contribute to over 420 million projects.

Global or per-level configurable Blossom upload limits for members: Marking someone other than yourself as a root user with full powers in the relay: LiveKit support for NIP-29 audio/video rooms (as per

GitHub

Build software better, together

GitHub is where people build software. More than 150 million people use GitHub to discover, fork, and contribute to over 420 million projects.

System stats and a manual restart button: Please try and let me know what is broken.

Hey @Azzamo what do you think about running a one-click #pyramid relay setup hosting charging some monthly bucks? I can try to help with whatever I can. Let me know. Join the NIP-29 group at pyramid.fiatjaf.com'Tnq7x2ZTgrPZWFrC if you want to chat. The expected revenue is between zero and a thousand millions.

Make Nostr that app no one likes but everybody is forced to use: View quoted note →

@Anjhc can you create a NIP-29 group that we can join to complain about

Nostrord

Maybe the way Nostr can get more people is by making it a good choice for semi-closed hyperlocal mini-social-networks, like a low-effort impromptu social network for a neighborhood, a church, a school, a company, I don't know. People could join this just because they have to if they want to get news about their community and stuff like that. They won't regard it as a global social network, they will keep using X, Instagram etc, this will just be an annoying app they're forced to use. How to make it work: Some conscientious member of such community would set things up, spin up a #pyramid relay or something like that that would provide an exclusive space for this community. Then he would use a client that supported such mode of operation to send invites to other members. Upon receiving the invite (the invite can just be specific for that client, no need for a standard here) new users would have an account created for them and be thrown into a prepared environment in which the only feed would be that relay's feed, search would be scoped to that relay, replies and mentions would only be sourced from that relay. There will be no spam, no Bitcoin, no bots. Luckily it's easy to turn an existing kind 1 client into a client that supports this mode of operation (some are already almost there), so if you're a developer reading this here are some ideas to consider implementing: - making relay usage highly configurable (allow users to be set up to only read mentions from their "read" relays ever, only publish to "write", only search for specially designated "search" relays etc -- this could be optional); - supporting relay feeds alongside the classic "following" feed; - hiding the "following" feed entirely if the user doesn't follow anyone (or having an option to hide that regardless); - maybe allowing other customizations, like changing the UI colors and whatnot; - supporting an invite flow that allows some community leader to prepare the invites and then sets up all of this stuff automatically for people who get the invite.

DNS is a scam. View quoted note → Is anyone keeping a database of all the many many cases of domain names taken from their supposed "owners" for whatever reason?