Developers has long been discussing the problem of data inconsistency among relays.

For example, your follow-list might be different in various relays. Your profiles might be different.

At the beginning, I, just like many other developers, thought it's a design shortcome of Nostr, if not a flaw and we spent much time solving it.

But, what if, we fully embrace the inconsistency? Then it's a design advantage.

Imaging that you can have different subscription/follow/block list in different relays.

How client developers design the product will vastly change how users experience Nostr.

Reply to this note

Please Login to reply.

Discussion

I wish we could specify an authoritative relay for our lists

It really depends on how client developers treat relays.

The real question is: Should a user has a unified view of data over the Nostr network or just over separate relays?

I dont need a unified view over everything, but do want to avoid having contact lists wiped out.

For this reason I dont use primal and manage all follow/unfollow from a single client