Thread

Zero-JS Hypermedia Browser

Relays: 5
Replies: 10
Generated: 21:09:51
avatar
laoc42 laoc42@getalby.com npub1r30l...t9ma
What are current approaches of collaborative nostr notes? Is this already solved on a technical level? If we would have collaborative markdown editor like https://hedgedoc.org/, how would we sent and find the event? I guess it would have a `d`-tag to identify the document, but how would we identify allowed collaborators? Or think of community-curated collections of content. How would I follow and edit a list that could be edited by multiple pubkeys? Query by `d`-tag, kind and then just take the most recent event? cc nostr:npub1l5sga6xg72phsz5422ykujprejwud075ggrr3z2hwyrfgr7eylqstegx9z nostr:npub1m3xdppkd0njmrqe2ma8a6ys39zvgp5k8u22mev8xsnqp4nh80srqhqa5sf nostr:npub149p5act9a5qm9p47elp8w8h3wpwn2d7s2xecw2ygnrxqp4wgsklq9g722q
2025-05-22 12:16:27 from 1 relay(s) 3 replies ↓
Login to reply

Replies (10)

avatar
Silberengel silberengel@gitcitadel.com npub1l5sg...gx9z
Addressable events have a kind in the 30000-39999 range and a d-tag and an a tag that looks like ["a", "<kind>:<pubkey>:<d-tag>", "<relay hint>"] Indexes allow you to determine the order in which the content appears, but you also just show most-recent first. I don't know, if that answers your question. Simpler and cleaner than key delegation is to have a shared key, like we have for nostr:nprofile1qys8wumn8ghj7mn0wd68ytn9d9h82mny0fmkzmn6d9njuumsv93k2tcprdmhxue69uhhg6r9vehhyetnwshxummnw3erztnrdakj7qpqs3ht77dq4zqnya8vjun5jp3p44pr794ru36d0ltxu65chljw8xjqxqf9se , and use that for the index.
2025-05-22 13:15:02 from 1 relay(s) ↑ Parent 1 replies ↓ Reply
avatar
Silberengel silberengel@gitcitadel.com npub1l5sg...gx9z
If you want to collaborate on one article d-tag, just have the client take the fork with the newest created_at, from within some community/relay or set a list of collaborators. Everyone has their own version, and you think up a scheme for which version is primary. Or you can have collaborators recommend their favorites. Which ever receives the most defers is listed first. What you're describing is more wiki than longform article. You can include wikis in an index, like I did for https://next-alexandria.gitcitadel.eu/publication?d=gitcitadel-project-documentation-by-stella-v-1 (those are all 300818 wiki pages with Asciidoc markup, not 30041 articles). https://github.com/nostr-protocol/nips/blob/master/54.md
2025-05-22 13:22:32 from 1 relay(s) ↑ Parent 1 replies ↓ Reply
avatar
mleku me@mleku.dev npub1fjqq...leku
they also call them "parameterized replaceable" and they make sense in that they create a secondary link between them to decide whether to allow replacing and deleting the old version i haven't thought about it much but i also haven't thought of a better way to implement such a thing, it makes sense
2025-05-22 14:13:39 from 1 relay(s) ↑ Parent Reply