have you noticed nostr got a lot quieter in the last weeks? if you did, its probably because your notes are being rejected by naieve throttling on ALL the big relays. you wont notice it when you post because clients dont surface this info to you, for all you know just nobody liked your post, but the reality is it did not post. πŸ„

Replies (99)

frphank's avatar
frphank 1 year ago
Meanwhile on nostr:
cloud fodder's avatar cloud fodder
have you noticed nostr got a lot quieter in the last weeks? if you did, its probably because your notes are being rejected by naieve throttling on ALL the big relays. you wont notice it when you post because clients dont surface this info to you, for all you know just nobody liked your post, but the reality is it did not post. πŸ„
View quoted note →
frphank's avatar
frphank 1 year ago
Exhibit A: Distributed systems made by 5 year olds.
cloud fodder's avatar cloud fodder
have you noticed nostr got a lot quieter in the last weeks? if you did, its probably because your notes are being rejected by naieve throttling on ALL the big relays. you wont notice it when you post because clients dont surface this info to you, for all you know just nobody liked your post, but the reality is it did not post. πŸ„
View quoted note →
clients usually cover up the failure.. but most relays will respond back and say why its not currently accepting a particular note so that you would know to retry.
Zaelus's avatar
Zaelus 1 year ago
I just made a post about this a couple days ago: Using noStrudel, it will show you the status of every event generated from your account. I've started noticing that with any event whether it be a reaction, zap, note, etc. just as you mentioned, there's always at least a few relays that don't accept it for one vague reason or another. The thing that really bothers me about it is that with most of them you can't go and see what rule you broke or what the specific cause was if they don't include it in the 5-6 word error.
Zaelus's avatar Zaelus
What can or should be done about these failures to post to relays? I assume I wrote something that broke a rule, but I have no way to find out. I tried to find some kind of list of policies or rules or something for each relay but wasn't able to find anything useful. Unless I missed it, they don't have actual websites with stuff like that listed. Just wondering if anyone has advice. How would you find out what policy you violated or why you were blocked? Is it even worth worrying about, or should you just add more relays to your publish list and move on? #asknostr image
View quoted note →
Zaelus's avatar
Zaelus 1 year ago
Both noStrudel and Gossip give feedback on the status of every event generated from your key.
nostrudel did a great job showing how simple it can be to show the status, now it needs outbox model for reading notes from follows and similar award winning UI for that also. relays can easily have as many words or landing pages as possible, thats just a matter of giving them a reason to.. (eg, that their users can see the messages)
Zaelus's avatar
Zaelus 1 year ago
Agreed, it's UI/UX is still definitely rough and awkward in a few places. I like to actually swap between it and Gossip. Gossip feels even more weird, kind of like an application from the 90s or something, but I appreciate the amount of lower-level info it provides. Thanks for the info... I guess in these specific cases it's probably like you said, they haven't really had a reason.
Damus appears to be the only one rejecting my events right now. That might be because noStrudel doing something fancy like pushing the latest version of replaceable events if it detects damus serving older versions of my follows profiles for example. image
P2P broadcast... nothing except propagation conditions to bottleneck anything. lol.
What? If I post your old events to relay, relay will reject your new events? I don't think so. Rate limiting should apply to the connection and not to the author.
It is time for the ecash nut πŸ₯œ per note relay implementation
cloud fodder's avatar cloud fodder
have you noticed nostr got a lot quieter in the last weeks? if you did, its probably because your notes are being rejected by naieve throttling on ALL the big relays. you wont notice it when you post because clients dont surface this info to you, for all you know just nobody liked your post, but the reality is it did not post. πŸ„
View quoted note →
I wonder if I'd even notice tbh, I'm here to talk to myself lol
cloud fodder's avatar cloud fodder
have you noticed nostr got a lot quieter in the last weeks? if you did, its probably because your notes are being rejected by naieve throttling on ALL the big relays. you wont notice it when you post because clients dont surface this info to you, for all you know just nobody liked your post, but the reality is it did not post. πŸ„
View quoted note →
so are most major relays censoring now?
cloud fodder's avatar cloud fodder
have you noticed nostr got a lot quieter in the last weeks? if you did, its probably because your notes are being rejected by naieve throttling on ALL the big relays. you wont notice it when you post because clients dont surface this info to you, for all you know just nobody liked your post, but the reality is it did not post. πŸ„
View quoted note →
Damus broadcasts automatically with geometric backoff if it fails to write to the relay, you don’t need to do it manually. If clients don’t do this then notes are easily lost during connection issues
yeah nostrudel and coracle have both had this since i first used the beginning of this year... the client should keep a queue and a checklist of which relays it has got to and some sort of scheme for backing off one of the differences with web clients though is that queue is nixed when you refresh the page, and sometimes the page scripts are broken and make this refresh happen on clicks unintentionally
Default avatar
Rand 1 year ago
t-y Will for participating!
On the relay, I mean. Some of us are relay customers, more than client customers. We're sort of client nomads, but we use the same relays everywhere. And we'd be more-inclined to use a client, if it offered us controls for a relay, like relay.tools does.
Default avatar
Rand 1 year ago
true cost ^ i'm obliged to pay just not efficient(here) yet but getting there v4v
Perhaps you may not have noticed that the progression between real spaces & virtual ones are similar, you have the wild west days when it's pretty good, then the "civilised people" invade & everything starts going downhill...
I don't think "they" are worried about this as much as some think, they'll pressure the relays holders one way or another & they'll get what they want eventually.
that's the thing, because nostr can partition we can ultimately isolate ourselves from that bullshit but it takes a lot of extra tools, like paid relays and spam filters and all the necessary support in clients and relays to allow us to build these walls they can have their own spammy free relays, we will move to our paid relays where spam is not tolerated and expensive to do
nostr has a problem with spam, everything does they haven't been hit with much yet so we will have to see what they dev to solve it
↑