I think you can use Immich external libraries for this, also to be extra safe you can just mount your external images folder as read only by adding :ro to the docker volume mount so that the container won’t be able to modify anything as a precaution.

We’re seeing this at work too - our public git frontend is constantly getting scraped as well as our self hosted issue tracker. We had to spend days working on fail2ban and other kinds of tools to mitigate all the traffic that’s adding tons of load to our instances, which otherwise would easily be able to handle the handful of employees who actually use these systems.

Nowhere did they say that those statements mean immutable to them. Just that your claims that OP “literally said they didn’t want immutable” is not based in reality.

I once had someone open an issue in my side project repo who asked about a major release bump and whether it meant there were any breaking changes or major changes and I was just like idk I just thought I added enough and felt like bumping the major version ¯⁠\⁠_⁠(⁠ツ⁠)⁠_⁠/⁠¯

Not sure about Facebook since authenticating for private videos is a hurdle, but for my partner who uses a mac I downloaded open video downloader which is just a foss GUI for ytdl, it also keeps ytdl up to date which is a requirement for me since I don’t want to be called when it stops working. I think on windows you have to manually install msvc2010redist but besides that it seems to just work out of the box.

Somebody should make an api shim that proxies openapi compatible requests to this. And since Microsoft is forcing copilot on windows 10 they’re on the shit list too. Load balance all the AI workloads onto both of them through API adapters.

The screenshot doesn’t show any version change to signal - the version number is the same, so I was just answering why you might see an update like that since I thought that was part of your question.

Those might be flatpak “refreshes”, which show up as “updating to the same version”. As described by a flatpak maintainer, sometimes an app or runtime gets updated without changing the user-facing version number. I assume that’s what you’re seeing here.