Subnostr

Nobody can version like git, after all. Could git-version all of your high-signal events.

I actually do that, already, for all of my long-form stuff, like 30041, 30023, and 30818.

Could also do lists. Would give you a local version of every list, to use as recovery. Could even look at versions of the list.

MichaelJ 6mo ago

IMO the best use of git for Nostr events is for long-form content. Being able to, for instance, do version control on a full publication before it is broken down into 30040 and 30041 events and pushed off to relays could have a use case.

Smaller content, such as text notes or comments, are generally one-shot and don't really need versioning.

That said, git could be useful if one wanted to do version control on a local archive copy of one's Nostr profile and associated events. Dump everything into .jsonl files, perhaps.

Reply to this note

Please Login to reply.

Discussion

Silberengel 6mo ago

Yeah, let's think of a smart git integration for the Tauri client.

ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 6mo ago

yeah, that is precisely the use case i see it being for. the idea i see is that you store the document as unsigned collection of these events, that originates in an asciidoc master version. there needs to be a bidirectional codec between the master and storage format, and the rest is handled by standard git commits, and because the document is already segmented neatly, there should be very few chances of several people working on different paths having a merge conflict issue, but it can be fixed i guess. probably just to poll the log in case a user is editing a section of the document that has been updated in the repo.

git itself, for actual signed nostr events tho. so simple. everything is already atomic, there can't be conflicts, although there might be a problem with forks.