i don't get what you mean by that
the logic is all inside the client, it just grabs events of users relay lists and uses them as a starting point to searching for events that aren't found on your own relay lists and associated configuration.
if you aren't a nerd then what are you doing writing client software for a decentralised post-office/pubsub protocol?
Login to reply
Replies (1)
The assumption is that a user:
- wants to publish all his publications to the same set of relays (as if he's a nerd with only 1 interest / community he interacts with)
- has time to figure out what relays are, compare them and pick and pay for some that suit him (to then have zero solution yet for his media, the more expensive hosting need he has).
- takes responsibility for the moderation of all his publications, with that moderation being applied by the same relays for all of his stuff
That's all nerd stuff imo.
Most people just want to post in the Communities / Apps they're involved in and let them take care of the moderation, hosting, etc...
And the have the option to backup whatever is relevant or important to them on their own (cloud) server solution. Ideally, that server also lets' them share specific stuff with specific profiles, for the private (non private group- side of things too.