Make sure the user “bind” and whatever the owner of that folder outside of the container is, have the same user number.

If the postgres container doesn’t start properly, then something’s wrong with the config. Most likely you are trying to expose port 5432 to the host network, but you have postgres already installed there, so the ports conflict.

You can check for those errors with journalctl.

Seems pretty neat. Does it also support location based reviews?

Probably the taste of dissolved gasses differs. Normally that is the main difference in taste between water of different temperatures thus we take it as a taste proxy for temperature.

The realest answer: baby bear. Because the mother is right around the corner.

The well tended sidewalks make me guess Singapore, but not sure they allow cats running around like that.

No, I claimed that they are legally required to do so, should a court ask them to and would very likely also be hit with a gag order to not tell anybody about it.

They can easy claim in retrospect that they can’t access data, but this says nothing about them being forced to change this for future updates. And besides that, for sure they have a clause in their end-user contract that exempts necessary legal compliance.

Thus saying that you should always update because upstream always has your best interest in mind is certainly false in the case of Apple.

This has nothing to do with what I wrote.

Apple is a US based company. They are legally required to comply and not openly speak about it when a court asks them to do so.

Same for Google obviously, but since their software on end-devices is much more diverse, it is much harder to do.

This assumes the official upstream is not compromised. Apple absolutely will push new vulnerabilities in updates when requested so by higher level law enforcement and/or the NSA etc. The FBI is also known to have placed moles in app vendor teams.

Why would you start with such a complex and advanced tool when you are new to self-hosting?

Yeah, that was my first thought.

Probably driven by: then I can put that on my CV. But just playing around with that self-hosted is not going to give you any actionable skills.

Alternative explanation: Lemmy is big enough now for astroturfing 😑

Here on our instance with image proxy enabled it works as expected, your images are proxied and only show the IP of our server. This is true for both posts and comments.

Are you sure? Because it looks like lemmy.ml has the new image proxy enabled. Maybe you tested lemmy.world, which is still on Lemmy version 0.19.3?

This is fixed with Lemmy 0.19.4/5 on instances that have the new image proxy enabled.

This is a good guide: https://wiki.tnonline.net/w/Btrfs/Replacing_a_disk

Usually you want to replace drives before they fail (SMART monitoring will give you ample warning in most cases). The it is better to have an additional free SATA port to turn the failing raid temporarily into a three-way raid and use the btrfs built-in function to replace the disk in situ.

Mirror (raid1) btrfs raids are fine and are more convenient anyways.

…except email 😑

Since it is Google Docs, the data is already on Google servers. But yeah, it doesn’t exactly instill confidence into the confidentiality of documents on Google Docs.

If you only use it so rarely, why not just connect a USB drive to your network router? Most have an option to serve files from that over the network.

A RasberryPi uses so little power when idleing that turning it on and off on demand makes not a whole lot of a difference. It is different though with OP’s x86 with spinning rust drives.