I can't explain it.
Do you want a lot of traffic?
Thanks for bringing this up, here is a chart that's long overdue. Events/pubkeys per relay in the last 7 days.
https://stats.nostr.band/#relay_writers
I can't measure their read-load obviously, but can tell how much events are written. As I expected, the list of top relays by number of events is materially different from list of top relays by contact list. Does this tell you anything new/interesting?
Whoa, I had not seen these stats, they are amazing.
Um brasileiro que fala inglês e russo aleatoriamente.
Your right to speech doesn't include a right to have others listening to you if they don't want to, just that.
#[0] what client(s) are you using?
It's already over, the anime people are here.
cargo install nostcat
✅Nostrid v1.26.1 is out! Check out release notes in GitHub.
Android/Windows/MacOS/Linux: https://github.com/lapulpeta/Nostrid/releases/tag/v1.26.1
Web/PWA: https://web.nostrid.app/
#nostr #nostrid
People must stop making names that have "nostr" or "str" or "nos" in them, this is starting to get confusing.
When https://pinboard.in/ on Nostr? #[0]
If you really think that why are you here?
This is ridiculous.
I guess along with rate-limiting and other measures free and open relays must have a very strict event deletion policy -- i.e. delete everything that is 7 days old.
Is it correct to say that the most famous 25 relays are being basically DDoSed all the time while the other 900 relays are seeing very little traffic?
One advantage of https://github.com/nostr-protocol/nips/pull/158 over NIP-26 for key security is that it only requires a single app to monitor key invalidations and update your list of followed keys for a key to be invalidated/rotated mostly successfully.
While NIP-26 requires all apps and relays to support it for it to work.
However, NIP-26 could work with much less than 100% if it was only used for sporadic delegations for niche use cases, or for grandfathering keys in custodial services.
This could be very interesting: #[0]
Please join https://t.me/gossipclient
How can that be done technically?
The kind 3 relay lists were a mistake from me made in name of getting things working, but that was never specified in any NIP.
The meaning of "read" and "write" in NIP-65 is different though (where is that diagram, #[0]?), although I agree it is confusing. It would have been better to call it "inbox" and "outbox" or something like that as #[1] suggested.
The difference is that other people can follow you directly.
You require private relays (or a set of "safe" relays) for either showing a global feed or for seeing replies to your own posts, which is a kind of mini-global feed.
Please watch https://mikedilger.com/gossip-relay-model.mp4 and listen to the Mike Dilger episode on https://nostrovia.org/ and let me know if that fixes the issues you're seeing.
https://github.com/mikedilger/gossip and https://coracle.social/ are trying to make that work.
#[0] #[2] #[1]
Maybe read this too: https://fiatjaf.com/3f106d31.html
See, #[0]? We have another confusion here.
Where on the NIPs is the idea that clients are supposed to use static relay lists? To me NIPs 2, 10, 19, 65 all hint to the fact that clients need to be smarter than just using static relay lists.
Clients (and users) must do a better job helping each other find people and notes on Nostr.
For example, someone just sent me a link like this: https://snort.social/e/note1g459tq3ucft6jz5s7zhhswjtz7h8qlfyf43vmrsu7tfpw800hkesq543gg -- but when I click on it it doesn't show anything. Why? Because Snort has no way to know in which relay this note is. It also doesn't show on https://nostr.guru/note1g459tq3ucft6jz5s7zhhswjtz7h8qlfyf43vmrsu7tfpw800hkesq543gg
But if I convert that to nevent format with the Mostr relay encoded inside then it suddenly works: https://nostr.guru/nevent1qqsy26z4sg7vy4afp2g0ptmc8f930tns05jy6ckd3cw095shrhhmmvcpz4mhxue69uhhyetvv9ujumt0wd68ytnsw43qe2wps6
It also works on https://coracle.social/nevent1qqsy26z4sg7vy4afp2g0ptmc8f930tns05jy6ckd3cw095shrhhmmvcpz4mhxue69uhhyetvv9ujumt0wd68ytnsw43qe2wps6
Markdown syntax for links, footnotes and images is definitely not plaintext. The rest is tolerable. Please don't break it for all other clients or force everybody to support a cumbersome and heavy syntax with all the garbage that comes with parsers, plus the indeterminism as there are multiple flavors or Markdown, it's an endless shithole.
Did you know Twitter doesn't have Markdown support?
Also https://zbd.gg/
Why?
Next time I show Nostr to someone I'll try Coracle: #[0]
Since there is no global feed there is no risk of accidental porn or worse things.
Did you take the kids out of school?
In which sense is https://coracle.social/ "behind"? I don't think it is behind anything, it used to be slow but now works like a charm. And has a bunch of interesting features other clients don't. Is it just because it doesn't implement zaps?


