nostr:note1g2qhjxe3z9hma8ahvt6hv0y2dpd6myvws3tn98sxw46t864hjvrsnq0u9q
Discussion
What is your main client? Damus?
My diagnosis is Damus is the problem. I don't have this issue at all and I've used everything except an iOS device or Windows.
I’m guessing other clients use a fallback set of relays then. Damus is pretty strict when it comes to following your relay set. Damus could do this too but it would only hide the problem
Well, there's the problem right there.
Nobody else is having this problem, apart from Damus users.
IMO, the real problem is Nostr has no countermeasures against spam, or relay failure. Damus' strategy is very brittle. Do you think Bitcoin would work if you only had like 10 peers and it didn't run off on its own looking for more?
its brittle because it is strict and is detecting bad stuff. Other clients accepting silent data corruption isn’t very good either.
dont use it then 🙂
It would be nice if freedom tech people would recognise how utterly unfree their iChains are.
For spam we have mute, and for relay failure..you can easily run your own relay.
Personally, I like it. This is how we educate people to take care of their own shit.
I like the fact that it can fall offline, also.
I always imagined in the future a p2p social network system where eventually people would charge for access to their fat cache. There is uses for this in the context of dispute resolution too, in that these archives could have a system that mutually certifies each other's set and distributes everything between them, acting like a backbone does for the internet.
I think that Crapple users are a special kind of brainwashed, extra double plus than the rest of the population. They are used to highly reliable everything that they don't realise is why they pay so much more. It's to fund their surveillance.
This is very evident to me.
The problem I anticipate in the future is not being able to delete content. There should also be an expiry date field on notes so compliant relays purge it. This also saves on complexity for cache culling.
I’ve been looking at how clients manage user relay preferences and I see a lot of “common public relay” constants being used as a fall back if they can’t find a kind 3 contact list with relays on it.
I think clients unifying on publishing and using kind 10002 relay lists for users would help. But as you already know that requires everyone being more strict and folks tend to not do that.
By tomorrow I’m going to make it so that on https://relay.guide you can create, publish, and manage relay lists for all the clients that respect it. Hopefully more clients move towards using it.
Correct