Open snarfed opened 1 year ago
Data points to help determine priority:
365k vs 1.13M is a big spread, not sure why that is.
I think they differ because of when they started collecting stats, maybe also the relays they are using. Here are two more:
Talking to a nostr friend @gzuuus, he told me that https://stats.nostr.band/ is the most reliable source.
Thank you!
ActivityPub <=> Nostr bridge! https://soapbox.pub/blog/mostr-fediverse-nostr-bridge/
Is there something to test already ?
@sven-hash not here yet, no, but PRs are welcome!
Thanks @snarfed for the quick answer, good to know that PRs are welcome ! Will check on it with other Nostr people
I reread https://github.com/nostr-protocol and https://github.com/nostr-protocol/nips/blob/master/01.md and have a few questions about the protocol:
Here are the relevant NIPS I've found so far:
cc @manton
To relay, or not to relay? Reasons:
Relay:
Not relay:
Same either way:
Interestingly Nostr user growth and posts seem to be way down over the last month or so. Either that or maybe some big relay change happened and stats.nostr.band missed it. But it's "the most reliable source" ^ so 🤷
...ah, ok, the earlier high new user growth was evidently accounts with no profile or other info, so they likely weren't human, so the drop in posts may have just been a big wave of spam ending.
Still, active "trusted" users is slowly dropping too.
List of relays: https://nostr.info/relays/
I'm currently testing with https://relayable.org/
Curious what relays you settle on. I'm currently using nos.lol, relay.snort.social, relay.damus.io, and relay.nostrgraph.net because they seemed popular and didn't sound terrible. But I'd like to put some more thought into this. There's a performance trade-off to supporting "all" the relays.
Definitely. Right now I'm just learning, but I suspect Bridgy Fed will actually need to be a relay itself: https://github.com/snarfed/bridgy-fed/issues/446#issuecomment-1563618821 . Not sure yet though, and obviously it's pretty different from micro.blog.
I like the idea of Bridgy being a relay itself, although I'm not sure that's required. If I do more with Nostr, I will probably have a relay too. Mostly because it feels like the right thing to do to fully participate in the Nostr ecosystem, more than a technical requirement. (But I might be missing something!)
I recently finished enough Nostr data conversion and relay protocol support to launch it in granary:
Current obstacle: from NIP-01:
Each user has a keypair. Signatures, public key, and encodings are done according to the Schnorr signatures standard for the curve secp256k1.
I'm having trouble finding a production-appropriate Python implementation of BIP340 Schnorr signatures.
Production-ready candidates:
secp256k1-py looks like the winner.
To try: https://www.nos.social/
I should do a survey of relay info metadata, specifically the limitation
field, for a handful of the bigger relays. nostr.law (?), nostr.mom, relayable.org, etc. I'm curious what their limits on the various filter fields are, esp if I need to subscribe for all Bridgy Fed users on a given relay.
Started a todo list in the description
Active user counts are still low, but trending up again. Last 6 mos:
Simple, key-centric, UX is still rough, community is heavily Bitcoin/crypto people right now, but could be promising.
https://github.com/nostr-protocol/nostr
Protocol
/.well-known/nostr.json
path. Translate@user@instance
touser.instance@ap.brid.gy