semi-related: would it count as piracy, if you reconstruct the 3d model from the 2d promo-images?

.azw3

didn’t they switch to epub last year?

so… netflix with extra storage?

multiple processes?!

full-spectrum lighting

this doesn’t sound true.

iirc full spectrum means “every wavelength” (like sunlight) and not just “3 wavelengths that add up to white”.

You vote with your wallets. Each time you buy a phone without SD cart, you are submitting a ballot.

Seriously. phones are 99% identical anyways. It’s not so hard to filter for the 2-3 criteria you actually care about.

oh nice. If this trend continues, they will be by 4 million tommorrow and 20 million next week and by summer every human on earth will have an account.

It’s cute how they blame Rowan Atkinson, when we all know who’s fault this really is… https://www.youtube.com/watch?v=bkrcxLgHn-w

raspi with vlc, mulvad and qbittorrent installed.

haptics of a button means that you can keep your focus on the street while pressing a button.

As opposed to Threads stealing all brands companies and users anyway?

The extend-phase is when people migrate to threads, who would have stayed otherwise.

the general strategie is called “embrace, extend, extinguish”. This strat is the reason, why everyone uses MS Office today

https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguish

I recommend to use relevativ paths in the compose files. e.g.

  - '/home/${USER}/server/configs/heimdall:/config'

becomes

  - './configs/heimdall:/config'

you may want to add “:ro” to configs while you are at it.

also I like to put my service in /srv/ instead of home.

also I don’t see anything about https/ssl. I recommend adding a section for letsencrypt.

when services rely on each other, it’s a good idea to put them into the same compose file. (on 2nd thought: I am not sure if you already do that? To me it is not clear, if you use 1 big compose file for everything or many small ones. I would prefer to have 1 big one)

you can use “depends_on” to link services together.

you should be consistent with conventions between configurations. And you should remove config-properties that serve no purpose.:

• you don’t need to specifiy “container_name”, when it would be same name as the service
• PUID=1000 and PGID=1000 shouldn’t be needed, I think.
• sometimes you add explicit “:latest” to the version, and sometimes you don’t

while you are at it, you may want to consider using an .env file where you could move everything that would differ between different deployment. e.g.

• PUID
• TZ
• exposed ports, maybe

consider using podman instead of docker. The configuration is pretty much identical to docker-syntax. The main difference is, that it doesn’t require a deamon with root privileges.

you may want to consider to pin version for the containers.

pro version pinning:

• no unexpected changes, when you restart the container (e.g. because you accidentally pulled)

con version pinning:

• when you DO want to make an update, you have to spent 2 minutes to go to docker hub to find out which version you want.