Yasssd
Discussion
Imagine if stacker.news used nostr to login and every post and comment was a nostr event, then those comments and posts could be individually zapped, shared, etc
(That’s not what I’m building btw, just an example of a non-nostr site using nostr)
Right on. I’m pretty sure #[3] and team are deep into nostr.
We are working on it building a nostr native site outer.space but making SN that kind of hybrid would be cool.
Neat! I wanna be friends :)
I’m wondering about general design philosophy for these kinds of apps. The prototypical example would be a stacker.news app but posts and comments are nostr events.
Is it fair to think of apps like these as a nostr client but for only a small subset of notes?
What is the best way to keep track that a note is a “stacker.news” note? Would hashtags be fine? We don’t want a special stacker.news “kind” number do we? And I assume we don’t want a special stacker.news nip either. Is this what a “tag” is for?
Must we run our own relay to be practical? I see you’re planning one for outer.space , curious if you think it’s always necessary for these kinds of apps.
Tagging #[4] #[5] #[6] in case they want to chime in.
If these questions have all been answered somewhere, please share - I’m still a noob on the nostr protocol side of things and want to build in a helpful way to the whole ecosystem.