Subnostr

One example…

The challenge of “linking” posts together to extend conversations, connecting ideas and people that may otherwise be missing each other.

This morning alone… we have a great example (linked here for reference alone, and NOT to extent a conversation… which is its own use case)

nostr:npub149p5act9a5qm9p47elp8w8h3wpwn2d7s2xecw2ygnrxqp4wgsklq9g722q posted a question.

https://damus.io/note1xnu7xcn7unhxx3apt8n97l883glkgrkzxser0hwp48dltspeywwqp3y7j5

nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z posted a “stand alone” reply without mentioning niel

https://damus.io/note17zrsu0thhpjvsfk45tzmjlegrcchncwftkt727d7dangc4uewepqkj7tpp

Meanwhile… niel is back on his timeline posting his own follow up.

https://damus.io/note15xvvscasa0egfj0hh72g4fg3neh553zwmsws06qm4r6lcfrt6f2q4e7yj0

This is a simple example of what I see every day! Broken snippets of conversation, that might or might not find each other. We’ve all seen this…

Maybe we “frame” it as OK “because it’s social media”. Maybe social is not responsible for being actually productive. But an open protocol like nostr has the opportunity to break this mold.

How do we make social more productive? First use case: how do we “cross link” posts, people and good ideas?

ManiMe 2y ago

What I was JUST considering as you posted this reply (@⁣⁤karnage ⁤we are all psyc-linked) is the reality that (at lest two) clients I use have multiple means of sharing a post, but none have an (obvious “share @“) option to simply output a nostr: uri … for sharing posts WITHIN a client.

Why is this? … maybe because client rendering of nostr: URIs is inconsistent? I don’t know.

But as long as “share post” buttons output an http URI by default, then …

1: end users will be sent out of the client to continue reading… bad design

2: clients cannot verify when a post is “back-linked” to another. (Which would be bonus)

And as a result… cross linking of good ideas and people will be hampered.

https://nostrcheck.me/media/public/f8c60f6231f27b751174315722093d0c0f09de22193b9268ed69fa9bc74b67c0.webp

https://nostrcheck.me/media/public/266dd24c071789089d9f295295c8ced3ae1aa809f50db0f87afedb52d2d140b1.webp

Reply to this note

Please Login to reply.

Discussion

Vitor Pamplona 2y ago

We have ways to cross-link (replies and quoted posts, for instance). But in those cases, the author (me) did not choose to do so on purpose. Maybe we need a new way to link stories that is not author-based. Something similar to Communities, but for Curator-assembled threads.

Who knows...

ManiMe 2y ago

Right. More author tools are great. But…

Tools for “self organizing” conversations and communities is where it’s at. This particular example I identified highlights this use case of ME trying to cross link multiple posts and finding it hard. (Because the links point out rather than stay within the client).

This is only one example and use case of our BIGFER challenge to build tools that allow content to be discovered and shared in a productive manner thats facilitates communities and conversations to self organize.

(Forgive my informal chicken scratch, as I wake up and frantically type ideas on my phone) M

ManiMe 2y ago

Doesn’t this NIP already outline the solution, for cross linking existing posts?

https://github.com/nostr-protocol/nips/blob/master/27.md