go-mtree VS HedgeDoc

go-mtree can take care about it. It calculates files hashes and you can use it to compare it later.

There is old unix utility called 'mtree' (there also is fully binary static compatible with mtree version on github go-mtree ) to check integrity of files. Another solution is - ZFS that do it dynamically

There is FreeBSD utility called mtree that also ported to Linux systems, that walk specified filesystem and creates hashes for all found content which later can be used to check integrity against corruption/modification. If your distribution of choice doesn't have ported version of mtree, you can use multiplatform version go-mtree that replicate the same workflow

go-mtree # Integrity

go-mtree: portable implementation of well known utility mtree) that can be used to save/test file's integrity as well directory structures. Open source, portable across most popular operation systems, no dependencies, single executable file.

There is standard utility for integrity testing mtree) that ported to linux too. Also there is multi platform version of upstream written in Go (read works everywhere from one single file) that called go-mtree

SHA1 is dead, and there is a better dedicated tool mtree(8) for such tasks (which by the way exists as implementation in Go as go-mtree ) but I believe OP wants to check versions (like fzf --version) not an integrity of files

Nice and simple. I feel the only lacking feature for a basic blog is having unlisted blog posts, which is very handy when you want to share it to proof-readers. This can be done on google doc/hedgedoc [0] for sure, but then when porting there are very often typos creeping in.

[0] https://hedgedoc.org/

Maybe Hedgedoc will fit these needs? You can use markdown to format. https://hedgedoc.org/

If self-hosting is an option for you I would recommend that you go with HedgeDoc. Completely open source, you get all the features you asked for including real time collaboration.

You can give HedgeDoc (https://hedgedoc.org/) a try as a replacement for Google Docs.

It is the one that works best for concurrent editing IMO (but it is markdown which can be a problem for some)

I use one singular HedgeDoc document for that purpose. It's not exactly the same intent as Google Keep, but it's an awesome project I use anyway and fills the role perfectly for me personally.

HedgeDoc is a web-based, self-hosted, collaborative markdown editor. This open-source option allows a team to easily share ideas on notes, graphs and presentations in real-time. troubleshootmertr finds it a good option "for knowledgebase."

HedgeDoc [0] allows you to collaborate in markdown, and also create slides.

[0] https://hedgedoc.org/ and https://demo.hedgedoc.org/slide-example?both

For writing Markdown documents I use Hedgedoc.