Holla

They’re writing whole paragraphs in their commit messages. What dev would even write that much documentation at all? And then into the git message? https://codeberg.org/vitali87/croft/commits/branch/main?page=2

aiming to

ftfy

I think with the current architecture of the fediverse it’s already quite hard for government actors and such to have arbitrary content be taken down, as any content gets federated to all the followers’ instances, where it will be stored afaik pretty much indefinitely. An exception to this would be media and external links, so an archive instance could focus on storing those as well.

uncensorable, undeletable

Perhaps I don’t understand what you mean with private, but this seems like an awful idea. Hosting unmoderated content will lead to trouble as soon as csam, doxxing, or any other illegal content appears and making everything undeletable might seem like the entire point of an archive, but it’s also woefully disrespectful to the original authors to keep their content online after they have expressed to remove it (not to mention gdpr stuff).

The only thing better than perfect is standardised. Supporting two vcs-systems would mean that a lot of tooling would need to be duplicated for it

They are the same; both refer to https://github.com/helix-editor/helix