It feels like Nostr is struggling in two major areas:
1) The discussion isn't what the everyman gives a fuck about
2) The UI of the platforms using it assume too much of a user, only making sense for those who want to "be a part of the project"
The protocol has so much going for it and the platforms utilising it are functional, but lacking in UX. I believe fixing 2 helps improve 1. xoxo
I want to build a system on top of Nostr for all platforms to access and plug into. Think like "kind:0" on steroids.
Anyone got any sweet examples of the entire journey other parties have gone through building upon Nostr? Interested to see the approach and the pitfalls.
at protocol & nostr are quite different both in architecture and aspiration
The best thing to do is go through the documentation
Read the overviews here
NOSTR:
https://github.com/nostr-protocol/nostr
AT PROTO:
https://atproto.com/guides/overview
And then I would recommend comparing the first 5 implication possibilities (NIPs) on nostr:
https://github.com/nostr-protocol/nips
To the identity / repo / lexicon / app sections of the docs on at proto:
Appreciate what is likely the most legitimate form of help; docs. But if anything it's made me feel like even more of an imposter - I'm a hundred levels more simplistic than the docs are going to be. The phrase ELI5 has always felt lazy to me until this moment.
Not sure why I'm able to "like" here - is that an artificial addition by Amethyst or an actual part of the Nostr protocol? #onlyzaps
Unfortunately they went a bit too hard on focusing on a Twitter product and not developer community.
Are Bluesky and Nostr different? Searching tells me Jack's a major force behind both, but which is worth committing time and attention to? Are they the same thing and I'm dumb? Help a non-technical normie!