Exactly. Your KVM switch need to support it, or your clients will always act like you unplugged the screen when you switch between them.

Check the manual of the switch if it simulates a connected monitor for the client.

Some clients are picky when it comes to unplugging monitors or booting without one.

Wayland also seems to do something weird when the monitor is off (I have some applications where the window becomes tiny when turning off the screen).

Operating systems and porn.

Smith & Wesson

If I know the information isn’t available anywhere else and I really need it, I use a temporary unrestricted browser profile.

Otherwise, Ctrl+w it is.

Authentication with NPM is pretty straightforward. You basically just configure an ACL, add your users, and configure the proxy host to use that ACL.

I found this video explaining it: https://youtu.be/0CSvMUJEXIw?t=62

NPM unfortunately has a long-term bug since 2020, that needs you to add a specific configuration when setting up the ACL as shown in the video.

At the point where he is on the “Access” tab with all the allow and deny entries, you need to add an allow entry with 0.0.0.0/0 as IP address.

Other than that, the setup shown in the video works in the most recent version.

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 🙂

Exactly this. If you buy quality products and be considerably careful with them, they figuratively last forever.

Mmh, maybe around 20-30 years.

What is this scam and why is it still here?

This versioning is just moronic.

Dumbing things down is a sign of respectlessness towards the audience. So no. I am not doing this. I sometimes write things in a shorter way due to the nature of the medium, though.

But my Mastodon instance is configured to allow up to 5000 character per message, so there is plenty of space if I feel like.

I think Mozilla should focus on that. Yes. But instead they sink money in AI bullshit and other so-called “social” projects that have nothing to do with web browsers or their standards.

Focussing on the browser means focussing on web standards, too.

Since basically forever I use DejaVu Sans for UI elements and DejaVu Mono for the terminal.

Yeah, don’t let us be too nitpicky here. They intentionally make it not run on Linux because of their spyware. So it’s entirely their fault.

Maybe I’m a bit stupid, but where the fuck is the code in that repo? All files seem to be just some sort of structured meta data and stuff.

that’s not the developers fault.

Forcing Ring0 spyware on the users IS the developers fault by 100%.

That poor IT support person:

I think the reason is stupid and it is contrary to what I expect from dockerized applications.

lolwhat

Did you miss the part where Mozilla spends most of their money for not the browser?