Ditto looks amazing and the idea of smaller communities loosely coupled is much more appealing than a social monolith.
The data architecture is confusing though.
Notes created by an npub still propagate across all relays in a user’s profile and they are just filtered by the Ditto relay? nostr:npub1q3sle0kvfsehgsuexttt3ugjd8xdklxfwwkh559wxckmzddywnws6cd26p
Ditto is like a mini Primal. It does not read data from relays at request time. It works in the background to gather data from relays, then at request time it reads from its own database. When you publish it does publish to the relays in your relay list.
Ah ok, so “membership” is handled by the background process on the local instance to only include approved npubs etc etc?
If it’s a moderated community it does seem counterintuitive to blast the note to every relay in my profile as there will be many out of context notes floating around. It’s an interesting problem.
Which relays does it gather data from? Which data?
+1
Been reading the docs and it looks like you specify them in the server config.
https://docs.soapbox.pub/ditto/install#add-relays
Kudos to Alex on the documentation as well. It's very clear and easy to follow.
Ditto appears to be following a pattern in which a user's relays are simply the relays of the Ditto communities they are in. This makes sense, it's just a change in mindset because currently there are 3-4 major relays which we all connect to in hopes that they have everything (every note, like, zap, profile, etc....)
This model embraces the fact that relay consensus at a network level is not only difficult, it’s not necessary.
