TheHolm

Check their contribution rules. https://github.com/versity/versitygw/wiki/Contributing-Changes
quoting
All new files in the change should have the versitygw copyright and license headers.

Versity S3 Gateway is Apache‑licensed, backed by a commercial entity. Their contribution agreement forces you to give up copyright to them. It will follow the same path as Minio over time.

you are mistaken about it. There is a lots of other use for ipfs.

Ollama has long history of exploits. PLease do not feed anything which come from outside to it.

I got some Matrox G400 on PCIx1 for this from ebay. (Yes they still making them) Really cheap. native linux support, very low power consumption.

With AI search engines hosting public repo is very expensive.

If you happy with 16g , nothing can beat in speed/cost of AMD RX 9070 XT.

Some standalone WAPs for WiFi and PC based router. Depends on what you are getting you can get it dirt cheap. WAP also need firmware upgrades, but it is less a problem.

Then read my post again. Contributing and writing opens source is no longer about how much time one willing to spend on it, it is about how much money someone willing to spend on LLMs which will write code. And all these money will go to AI overlords.

Yes, but in each joke there is bit of truth. Open Source have to change. Open Source code written by LLMs is still open source, but it drastically different from current one.
Instead of spending time to “scratch the itch and help others in the process” - now people should give money to corps to use LLM to to do same.

This is one good article. I guess humans are now mostly redundant in open source. Bots can do everything themself, write code, submit PR, merge them and even blog about it. Time to book a place for myself in a graveyard.

for start private keys should never leave the system which uses them. Wildcards are even worse, as if one host got compromised, all others can be spoofed.

Just do not use wildcard, very bad security practice. Getting individual cert for each service is easy these days.

you can’t going wrong with squid. It was around forever, and still in development.

Why? Why anyone needs online version?

IMHO Jellyfin is processing everything it sent to clients. So I do not think it possible to put it behind SDN( may be it possible if server side transcoding is off) Please define slow. Slow on what part? It should be like 250ms RRT to your server which is not much for web-based apps.

Yes. Always. Unless you prefer FreeBSD

It just REST API, use restic for example.

Imho not worth the risk. Nothing except ECC is protecting system from memory corruption. And consequences of flipped bit can be huge. Unless it is in a system you do not care about, just do not use it.

If you using bind mounts - you are using dockers in wrong way. Use named volumes.