Thanks.

See my comments bellow.

I’m simply addressing the fact that nostr IS breaking the “traditional” and arbitrary bounds of what is “social media”, simply BY being the ever-growing decentralized protocol that it is. As this protocol grows, we should keep this in mind ad facilitate end users to pollinate content across threads, users, clients, relays, and event kinds. Keep these tools forefront, as the protocol develops.

Forgive my abstractions. Big picture is difficult to explain without examples (as you posted) but examples inevitably lead away from the big picture. That’s OK also, but (this will be my recurring theme, so watch out) I will always attempt to bring attention (back) to the bigger picture. Not to define, but to realign. That’s what is important to me, in a decentralized dev environment. So thanks for your patience.

Reply to this note

Please Login to reply.

Discussion

Ty. Keep beating that drum 🥁!

It’s hard for me to translates peoples ideas into practice designs sometimes so it helps to understand what people mean. Thus the questions.

Nostr is naturally interoperable and I think we’ll see a lot of that unfold in the coming days. I’m very excited for it!

ICYMI

By “comments bellow” I simply mean another branch of this thread, in which I address your points above.

(See if this works to make a link … here’s me PASTING a note ID and prefacing it with “nostr:” ala NIP-27 specs)

nostr:note1zjtzt45jp37n7df336ggktt8kzulxe4s6pegd946rtvrgvyaevrs98rcll