Replying to Avatar Sjors Provoost

One hack could be to agree on a (totally unsafe) deterministic nsec key generation to represent any given URI. That solves the duplication issue: no matter the bridge, it will always generate the same npub for the same person in the Fediverse.

But it means anyone can fake messages from anyone in the Fediverse, with no way to know what to filter.

Perhaps this could be fixed by making the bridge add their private key to the deterministic key. This would require adding a meta-data field to the Nostr post ("orig-URI"). That way all clients can de-deduplicate by subtracting the URI from the npub. And then they can keep a list of which bridges they trust and ignore the spam.
Avatar
Sjors Provoost 2y ago

This doesn't solve duplication in the other direction. Each bridge creates a unique Fediverse user for each Nostrich. That may be less of a problem though. If you have your preferred bridge, just give that to your Fediverse friends.

Reply to this note

Please Login to reply.

Discussion

Avatar
Sjors Provoost 2y ago

Oh and now you created a feedback loop where each npub gets replicated into N (bridges) identities in the Fediverse which N - 1 bridges may not recognise as such and turn into N * (N-1) npubs, etc… but that seems solvable.