Semisol 👨💻 on Nostr: Again, with that NIP, groups are single relay, and there’s no transparent migration ...
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 jb55 (npub1xts…kk5s)'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.
Also, all of these approaches are horrible for clients like jb55 (npub1xts…kk5s)'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.