Not your responsibility what others do with information.
If it was about building a nuclear bomb, sureā¦ this?
Oh also it breaks clients that use any form of caching service like Primal.
Unfortunately, local or remote caches are one of the few ways Nostr will stop using gigabytes of mobile data.
A better version of the moderated communities NIP.
Admins can keep a local backup of notes.
Again, with that NIP, groups are single relay, and thereās no transparent migration path. A group should be defined by its owner, not by the relay it is on.
Also, all of these approaches are horrible for clients like nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s's Damus as they maintain a local DB. There is no way to sync event deletions by admins, and local caches lose all benefit as they need to make round trips to the centralized community relay to get the latest state of everything.
Relays were designed as data stores, a subset of all events. The construction of views on top of these relays were and always have been the responsibility of a client on top.
A deletion for example, it should still function in clients even when relays donāt give a shit and do the bare minimum of storing events.
Relays support it because thereās no reason for them to store deleted events.
Uhā¦ can you read? Thanks.
Iām saying that one community = one relay.
they arenāt in communities
thereās 1 community relay and thatās it
it makes things easier, because itās centralized, but good things are never easy
An average user would need to figure out:
- how to do port forwarding
- getting a static IP
- getting a domain name
- configuring a reverse proxy
- installing and compiling strfry
- writing their own relay policy scripts
Pretty easy isnāt it? š
Donāt see how relays fix anything. Except it allows developers to be lazier by going back to the centralized model.
The average person will be the main source of new communities though.
Only if there is a tangible benefit that they can see and care about. āWhat ifās donāt matter until they happen to a user.
You forgot the part where you get the average person having interest in running a server and learning how to do that.
But why dedicated relays?
Except if you want to make anyone that wants to start a 5-person community pay for overpriced relay hosting
why does it have to be a relay and not something like moderated communities?
but also, to the average person, that doesnāt have much value to them really
I figured, I'm drawn towards the DIY devices for those reasons. The attacks required to exploit seem extremely advanced
I thought the Crypto guide fork with a Satochip plugin was an interesting twist.
Iām intending to be transparent with what my device can and canāt do, unlike most vendors out there.
Also, using a proper SE, same as the ones in a lot of servers + security keys + ID cards etc.
ājust one killer app bro. trust meā nostr:note1m263xj0w3mq2awxxn3ett56a3gpvl0emfkdwtjk3jnl9vnqafecsg5appm
Most HWWs are developed using cheap IoT SEs, some with poor track records. These only provide protections against basic attacks and anyone that stole a few HWWs holding 1BTC can easily make a good return on investment.
They also are not developed with security by design: itās literally āthrow shit at a wall until it worksā
look outside the bitcoin space for VCs.
unless you want to be bought out by the same people that sell insecure and overpriced gimmick HWWs and use podcasts/influencers to exploit bitcoiners
and the people that made primal, which is falling apart on a technical level as they struggle to scale (they had to last-minute change to PostgreSQL, for example)
