![](/static/66c60d9f/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/8286e071-7449-4413-a084-1eb5242e2cf4.png)
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.
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.
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.
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.
I use syncthing to synchronise my collection of important stuff between my laptop, local server and VPS. My laptop then gets backed-up to an USB SSD using Time Machine. Granted, it’s not a proper backup, but it’s better than nothing.
For my photo collection I burned it to a BluRay (M-disc) and asked my SO to store it at work.
Having multiple sufficiently-powered virtual machines makes OS development really low friction. Though I’d personally go for a blade subrack instead.