provoost on Nostr: Where things really get confusing is that nostr users are identified by pubkey, ...
Where things really get confusing is that nostr users are identified by pubkey, fediverse users by URL. When there's multiple bridges you get an infinite number of permutations, e.g. bridge1.com/npubabc, bridge2.com/npubabc are the same nostr user, and each fediverse user has one npub per bridge. And all can follow and interact:-)
Published at
2024-10-11 09:30:53Event JSON
{
"id": "1bfcc4d05884c094788aae7a4793b12d3a7a380ea4fb837ff8696d4c6add8137",
"pubkey": "8685ebef665338dd6931e2ccdf3c19d9f0e5a1067c918f22e7081c2558f8faf8",
"created_at": 1728639053,
"kind": 1,
"tags": [
[
"e",
"5f59749e387ed944be4379bc8bca9c89169295a552fefc0514f30989ba9d9b87",
"",
"root"
],
[
"e",
"2492088f8bef15470c2225aa6cd2ecfb535ca3564ccfc4b817cdcfc32d892814",
"",
"reply"
],
[
"p",
"4fda8b10d2d955b1f85f1e65bbb624dfc46575d70982e86462fd18a77bbee962"
]
],
"content": "Where things really get confusing is that nostr users are identified by pubkey, fediverse users by URL. When there's multiple bridges you get an infinite number of permutations, e.g. bridge1.com/npubabc, bridge2.com/npubabc are the same nostr user, and each fediverse user has one npub per bridge. And all can follow and interact:-)",
"sig": "3e5df26af6ac65ca0220b9fd42cc25aaeb7dd3863d2f459360ce5d8df43f33b321c58cbccc6b1a519fde24262633449f0dc2c168da2e67b51fb9c33e74a5a06f"
}
