𝘋𝘪𝘳𝘬

tldr:

“Small, itchy, blister-like bumps caused by the varicella-zoster virus,” the dish description from Sikar’s Royal Roll Express restaurant reads. “Common in childhood.”

A misreading of the dish name in question — “Chicken Pops” — could well explain why an AI may have spat out a description for what sounds an awful lot like chicken pox, a common childhood virus that causes the exact kind of nasty “blister-like bumps” detailed on the menu.

The IPv6 range is barely even used.

Yet.

Also I imagine that there will be a secondary market for IPv6 at some point.

Like there already is one for IPv4 addresses?

I stand by my point:

No-one will ever need a /48 range.

The ranges will become larger over time because “we have it”, and companies will get thousands of sections with figuratively unlimited IP addresses in them each.

With this huge ranges we’ll have the same problem with IPv6 in a few years that we already have with IPv4.

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

Spicy Pillow!

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.)

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?

They do it since quite some time now, right?

but I’d like to give Nginx Proxy Manager a try, it seems easier to manage stuff not in docker.

NPM is pretty agnostic. If it receives a request for a specific address and port combination it just forwards the traffic to another specific address and port combination. This can be a docker container, but also can be a physical machine or any random URL.

It also has Let’s Encrypt included (but that should be a no-brainer).

I run my website as static site from within a Docker container, I wonder how I would get the information about the other containers into that site.

Do you directly serve that site from the host or do you run the script and write something in a volume the site has read access to or bind a file?

Do you guys have any suggestions?

Because I don’t like software getting in my way I just cobbled together some HTML and CSS and call it a day.

Usually you just see LibreOffice and nothing else, so it’s fine, I guess. Not a web-based editor, but usable.

Ah, I see. Not as native web application, though.

They’re using Alpine Linux, install X and Openbox and Xvnc and serve KasmVNC via Nginx and connect via KasmVNC to that X instance. LibreOffice is started in fullscreen and looks like a slightly blurry web application.

But in reality it is just a regular desktop installation with some extra things.

@fikran@lemm.ee, maybe this is a solution? I wouldn’t recommend it because it’s not really a web-based document editor.

So, LibreOffice can be used over the Internet in a web browser?

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 🙂