as a dev, I take a look at bluesky's spec and feels overwhelmingly bloated and confusing
as a dev, I take a look at nostr's NIP-01, realize I don't need to read anything else, and build something 10 minutes later
not quite the same
Discussion
I mean, the mere fact that you need an invite code to try an "open protocol" it's like the most idiotic thing ever
Spoke to #[2] about this recently. Fascinating how any dev can simply read a few paragraphs to grokk the concept and start building.
I’m not familiar with the technical details of Bluesky, but I’ve seen that the AT protocol allows data portability. So you have control over your data.
Is there anything similar in Nostr, where you can download your data, and upload it into your relay, something unified.
Yeah, ofc, that’s baked right into the protocol. There’s a ton of tools to do this 😊😊😊
the pattern for this would be to run your own personal relay and make that your “primary” relay. think of other relays as secondary broadcast tools
i believe that At Protocol allows for verification in the sense that your data will only be accessible from the server that you have specified.
NOSTR allows for copying and pasting your data all over.
At Protocol = more user control but less broadcasting / availability theoretically