Iirc the openXML standard was open sourced due to some anti trust stuff brewing. They then expanded on the standard with proprietary addons that give LibreOffice/Google Docs trouble.

Technically, according to the GPLv3 you don’t need to make the source code publically available. If you sell software with binaries then their source code must be included with it. If you’re Red Hat you can also add an additional ToS to the website that states if you buy the software you can’t freely distribute the source code you download from the website or you will be sued to oblivion.

Didn’t the new CEO just start?

Don’t understand how this isn’t criminal in America.

A public S3 bucket? Whoever used the app should start a class action lawsuit, this is beyond misconduct.

They’re about to turn AI into a scapegoat for why kids are stupid and blame everything on it, as if before AI our education system was perfect.

Sure, but you can’t be tracked via css so it’s okay in my book. Have fun with your whacky css sites.

I can get behind no JS club, I can’t get behind no CSS club.

CSS is 🆒

This 240TB JBOD full of books? Oh heavens forbid, we didn’t pirate it. It uhh… fell of a truck, yes, fell off a truck.

Some TVs will sneakily connect to open APs to try and phone home. It is nasty but it does happen. You can only be worry free if you yank out the radio module. Some TVs make it easier than others (My LG TV made it as easy as opening the back of the TV and disconnecting, YMMV)

https://trash-guides.info/

0.0.0.0 means listen on all IPs

1. I don’t think this is a problem with tailscale but you should check. Also you don’t have to pipe all the traffic through your tunnel. In the allowed IPs you can specify only your subnet so that everything else leaves via the default gateway.
2. in the DNS server field in your WireGuard config you can specify anything, doesn’t have to be RFC1918 compliant. 1.1.1.1 will work too
3. At the end of the day, a threat model is always gonna be security vs. convenience. Plex was used as an attack vector in the past as most most people don’t rush to patch it (and rightfully so, there are countless horror stories of PMS updates breaking the whole thing entirely). If you trust that you know what you’re doing, and trust the applications you’re running to treat security seriously (hint: Plex doesn’t) then go ahead, set up your reverse proxy server of choice (easiest would be Traefik, but if you need more robustness then nginx is still king) and open 443 to the internet.

For the license to be changed every team member needs to submit a written agreement that he agrees to the change, otherwise their contributions must be removed as they were written under a different license, the only exception is usually permissive licenses such as MIT/BSD 3 clause.

Usually, to rugpull FOSS contributors, companies who maintain FOSS software ask contributors to sign a CLA which waives their rights and lets the control their contributions. Immich isn’t doing any of that, and it will likely remain AGPL forever because changing the license will be a big hassle for them with the amount of contributors.

Hi, I recommend you read the book “Run Your Own Mail Server”. The fact that a book exists for this topic is all the proof you need to not do this decision. But if you absolutely must, this is the way.

Only I rely on my services and if they break I’ll fix them myself.

I don’t run Immich specifically but all other software I run is on :latest tags and unattended-upgrades on Debian. It works so, why bother?

Docker Engine is open source. They could’ve easily contributed patches to it which just further proves that it is a NIH syndrome response.

I use Docker exclusively. Podman is the NIH syndrome response to an industry standard. It has its benefits but Docker just works.

I remember researching the topic a while back. SimpleMDM seems to do it, but it requires paying Apple $300 a year. Luckily, Mosyle allows up to 30 devices for free.