Having multiple sufficiently-powered virtual machines makes OS development really low friction. Though I’d personally go for a blade subrack instead.

weekend = day_of_week in (“sat”, “sun”)

As a bonus this completely sidesteps the issue of what day is 0 or 1.

If there’s water between the membranes an alternative is to wait a long time for it to dry out (months).

Yeah, hobbit-serial architectures lack performance.

So the Fellowship of the Ring was made up of an elf, a dwarf, two humans, a maia and one hobnibble?

Interesting. I have the classic FSSK on order. How’s the keyfeel compared to, say, a model M?

As I’m saying, I don’t think you need to: manually subscribing to each trusted instance via ActivityPub should suffice. The pass/fail determination can be done when querying for known images.

How about a federated system for sharing “known safe” image attestations? That way, the trust list is something managed locally by each participating instance.

Edit: thinking about it some more, a federated image classification system would allow some instances to be more strict than others.

Yes: it prevents things like death threats mods have been known to receive on the centralised Lemmy precursor.

I’m sure your colleagues will want one too when they see you using one :)

With instances already disappearing (eg. vlemmy), content is being lost. Are you considering a lemmy archive?

In my opinion this runs counter to the idea of federation

The rest of the internet runs counter to the idea of federation, yet Lemmy must work with it.

You mean like lmmy.to?

Like lmmy.to?

Not very. If it boots it boots. Although the ACPI implementation may be a little less buggy (plus you can fix it yourself if needed), so if you’re having power management issues it may help.

They’ve set a separate display name that’s show instead of the name that also appears in the URL.

Well, irdc stands for “I really don’t care”, and I guess “derp” and “foo” speak for themselves…in the long run it doesn’t really matter.

willemijn@derp:~/lemmy/volumes$ sudo du -hs postgres/
3.0G	postgres/

This is the PostgreSQL database on a freshly-rebuilt server (that is, one with a small WAL) which has been running for nearly 3 weeks now.

Compressed pg_dump rsync’ed to off-site server.

However, these relative links unfortunately don’t work on non-lemmy activitypub sites like mastodon and kbin.

And that’s exactly the reason why I created lmmy.to.