prevents cheating.

lol

I use podman, and the standalone tool “buildah” can build images from dockerfiles, and the tool “skopeo” can upload it to an image repository.

I’m a fan of beancount and it’s corresponding web interface fava.

Since the underlying format is human readable text, it’s easy to edit by hand, and you can send the raw file to your accountant as-is and they should have no issues understanding it.

TiddlyWiki might interest you. It’s an entire wiki stored in a single HTML file. You can even use it without a web server if you want (although a web server makes editing more convenient)

vim ~/.ssh/config

Is smallstep free to self host? Looking at their pricing page it’s kind of unclear, and their saas is pretty pricey.

This is the same as assuming anything written in Rust is secure. (i.e. it’s very wrong)

That looks like a cool setup, but I would never trust important data to some crypto shit (Storj) no matter what kind of track record they have.

Yeah rsync.net has always been pricey.

Mxroute is great. It just works, and there’s no sneaky fees, upsells, or any other bullshit.

I thought about doing something like this, but came to the conclusion that ActivityPub doesn’t make too much sense for a traditional blog. A static site generator with RSS is cheaper, easier to host, more reliable, and a better experience for users.

If I want it on the fediverse, I can just post a link on my mastodon account/lemmy communities. If I’m extra lazy, I can automate that part.

The main issue with the AP protocol is that there’s no way to see old posts. If a new user wants to see your blog content, their server might not have recorded older articles. It’s simply not a good protocol choice for publishing that type of content (IMO)

Wordpress+AP would solve that problem, but only because wordpress remains accessible as a regular website. Unless you want to integrate e.g. a comments/like system using AP identities, I don’t think it’s worth the hassle of maintaining a stack like that.

Plus, if you are publishing content directly to the fediverse, you need to worry about how your article’s formatting will render in the various fediverse clients out there. You’ll also need to worry about actually federating with other servers, and potentially being blocked for arbitrary/technical reasons you need to debug.

…those are just my initial thoughts on this idea. I’m interested to hear opinions from others who disagree and/or are running their own AP blog. SSG + RSS still feels like the winning combo to me.