@arthurfranca
Software dev + graphic designer + Nostr enthusiast
https://github.com/arthurfranca
Relays (2)
- wss://relay.44billion.net – read & write
- wss://nos.lol – read & write
Recent Notes
Updated our website to get rid of all the BS: https://amethyst.social/
Straight to the point. Very good!
Nostream 3.3.0 supports the proposed NIP: https://github.com/cameri/nostream/releases/tag/v3.3.0
Let me know if we’ll need to make changes
Nice! I'm about to add support for it too on my relay.
I see you added the `params` value to `OK` messages but not to the `CLOSED` ones yet.
I see you added the `params` value to `OK` messages but not to the `CLOSED` ones yet.
1
I also noticed that relays in general have no way to inform for how long should clients backoff.
I've just submitted a PR to address that problem: https://github.com/nostr-protocol/nips/pull/2498
Pi...
Thanks for the feedback, all of you. Edited the PR.
I see that @Vitor Pamplona and @jex0 seem to prefer miliseconds granurality. I'll change that too.
I see that @Vitor Pamplona and @jex0 seem to prefer miliseconds granurality. I'll change that too.
2
This is the main reason I like the web, a permissionless multi-platform app runtime. Caveat: API bloating that makes it hard to have new players build competing browsers.
2❤️1😡1
Email is the only completely reliable thing, in my experience. I urge you to email your friends. It’s very fun and feels cool
nostr:nevent1qqs936zuy4kkuhl26auml0ernddap89vldtv5ktjust26jrrdzn39fszyq...
regular email is plaintext, i.e. email servers can read the message content
Zillion is in a stable state now after many fixes. Please try it again as back then it wasn't really ready.
I need to create a nym to talk trash while AI outputs tokens.
Nostr was never about being fully open for everybody, only that there is no single central authority deciding on behalf of users.
What about all the interop effort on the NIPs repo? It is impossible to interoperate with closed apis.
You thought about one very niche use case that I had never considered, then you proceed to proclaim that it is the only valid use case.
You could perhaps have some humility to imagine that other peop...
I'm making bold claims trying to become an influencer
I hereby elect this one-liner https://github.com/nostr-protocol/nips/pull/2310/changes as the most important addition to the NIPs repo of year 2026.
I was referring to read activities, auth yourself for writing is fine, it has near zero overload.
Imo even for writing it isn't fine (except for what I mentioned) because the signature already proves who's the author of the event.
Requiring auth for reading would be similar to what X/Reddit do when asking for money to access their closed apis, which goes against Nostr selling point. It may also be interpreted as the relay inability to stop spam by other frictionless means.
Requiring auth for reading would be similar to what X/Reddit do when asking for money to access their closed apis, which goes against Nostr selling point. It may also be interpreted as the relay inability to stop spam by other frictionless means.
1