Nostr Web Client

Why?

they unnecessarily silo content, chat and twitter are just ui decisions that can work on the same content

there is a work around tho as a client could mix kind1 and kind40 kind42 together, and the ultimate goal would be to eliminate kind 40 and 42

#amethyst btw mixes kind40 kind42 with the kind1 feeds

seems we are also getting the same problem with communities where #tags already cover #topics and moderation should be via #filters with #lists

#tags, #channels, subreddits, etc are just generally topics...

#nostr general philosophy should and is remove silos, censorship is pro silos

Reply to this note

Please Login to reply.

Discussion

captain ☦️ 2y ago

How could you create a UI for channels using kind 1 events?

StephanGuy 2y ago

with tags, so #tags, or for a thread ie the parent note , #chat #channels are already threads as the channel is set by a note like a thread does

the things is we are duplicating the same data structures across the #nostr protocol, at some point i think it will be good to rewrite parts of it, remove excess, stay simple, good engineering is removing things making it simpler

when nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s started #damus he implement chat on a #tag, he agreed chat should be like that, point is your kind1 chat then automatically fills other kind1 using apps, ie everything, ie not siloed, nostr has been amazing how it can leverage all these different apps by keeping the social protocol the same between them, the same not different