𝘋𝘪𝘳𝘬

Well—that is certainly a meticulous observation! 🔍

The URLs mentioned in their blog article all have a wrong certificate (different host name).

I am sure if they fix it Google’s system would reclassify the sites as safe.

• Mail with all the bells and whistles (been there, done that – but I just want this to work and not care about details).
• Dynamic DNS because I just need to tell someone my non-static IP so they can connect that with my domain name.

They would lose likely 98% of their player base.

I’m going to voluntarily read other people’s AI slop.

They not only force their user to buy their crap, they also intentionally and maliciously frame the AGPL in a certain way.

I did not, but of course you can. Either by using an adapter (maybe a printable one?), or – if it is an SSD – by just placing the drive there and hld it in place with one screw.

If there already is a drive installed you want to removed and there is no spare cover, you can also print one.

(You can of course buy the parts instead of printing them. Those adapters and covers are fully standardized and widely available.)

It’s annoyingly complex and causes massive amounts of traffic and high load on the server to run a Lemmy instance that federates with larger instances. So most people prefer having someone else doing it.

Why are people still accepting this?

Okay, bye!

Always has been like that.

Not one single corporation is your friend or wants to be. All they want is your money. No exceptions.

Except those who aren’t.

Can’t watch right now, but is there a list of affected devices?

How do you handle SSL certs and internet access in your setup?

I have NPM running as “gateway” between my LAN and the Internet and let handle it all of my vertificates using the built-in Let’s Encrypt features. None of my hosted applications know anything about certificates in their Docker containers.

As for your questions:

1. You can and should – it makes managing the applications much easier. You should use some containerization. Subdomains and correct routing will be done by the reverse proxy. You basically tell the proxy “when a request for foo.example.com comes in, forward it to myserver.local, port 12345” where 12345 is the port the container communicates over.
2. 100% depends on your use case. I purchased a domain because I host stuff for external access, too. I just have my setup to report it’s external IP address to my domain provider. It basically is some dynamic DNS service but with a “real domain”. If you plan to just host for yourself and your friends, some generic subdomain from a dynamic DNS service would do the trick. (Using NPMs Let’s Encrypt configuration will work with that, too.)
3. You can’t. Every georestricting can be circumvented. If you want to restrict access, use HTTP basic auth. You can set that up using NPM, too. So users authenticate against NPM and only when it was successful,m the routing to the actual content will be done.
4. You might want to look into Cloudflare Tunnel to hide your real IP address and protect against DDoS attacks.
5. No 🙂

Have a look at Forgejo which is a soft fork run by a nonprofit organization of Gitea which is owned by a for-profit company.

https://forgejo.org/

It need very little system resources and still gives you all the common features you know from commercial Git hosting providers.

And yes, you can mirror existing Git repos using a web UI.