Microsoft has 18 months to convince folks to upgrade.

They’ll be lucky if I boot my Windows 10 partition between now and 18 months.

I write a ton of SQL. I never use my CapsLock key.

SQL doesn’t need to be upper case, in fact I loathe upper case SQL.

Yeah that’s a common one. If you’re into mechanical keyboards, there are a lot of keycap sets that offer an alternative Control key for the CapsLock position.

Personally I rebind it to Super (Winkey). I have a couple of keyboards without Windows keys, so I can still have a Super key and don’t miss out on some handy shortcuts.

COBOL is not a current program language anymore.

I use all of these except ScrollLock.

What about the CapsLock key? Windows menu key?

Pixel phone which doesn’t let you install CA certs any more

Is that something new? I can still install CA certs on my Pixel 6. It does give a scary warning, but you can just click through it.

The only way I’ve found to reliably delete a huge amount of comments and posts is to do a GDPR request for your data, extract the resulting zip file and then use the free shreddit utility to delete your data. The utility has an option where you can point it to the extracted GDPR data, and it will handle everything.

You can use the wildcard domain

Yeah the problem was more that this machine is running on a network where I don’t really control the DNS. That is to say, there’s a shitty ISP router with DHCP and automatic dynamic DNS baked in, but no way to add additional manual entries for vhosts.

I thought about screwing with the /etc/hosts file to get around it but what I ended up doing instead is installing a pihole docker for DNS (something I had been contemplating anyway), pointing it to the router’s DNS, so every local DNS name still resolves, and then added manual entries for the vhosts.

Another issue I didn’t really want to deal with was regenerating the TLS certificate for the nginx server to make it valid for every vhost, but I just bit through that bullet.

I was afraid it was going to come down to that. I have been looking into configuration options for the apps, but they’re 3rd party nodejs apps and I know jack shit about nodejs so I’ve had no luck with it so far.

Going with vhosts anyway (despite the pains it will create on this setup) seems to be the preferred way forward then.

Thanks for the insight, and for confirming what I already suspected.

No worries, your input was helpful and informative anyway, so thanks.

Going with vhosts anyway seems to be the least cumbersome route at this point.

WEI is a proposed modification to Chrome/Chromium that doesn’t even exist yet, and that would have the side effect of blocking adblockers on every site that implements WEI.

This here is an already existing change to the YouTube service that blocks adblockers on YouTube, across all browsers, Firefox included. It does not use or need WEI to do this.

Hmm no, that’s not really it… that’s more so that you don’t pass URLs starting with /app1/ onwards to the application, which would not be aware of that subpath.

I think I need something that intercepts the content being served to the client, and inserts /app1/ into all hardcoded absolute paths.

For example, let’s say on app1’s root I have an index.html that contains:

...
src="/static/image.jpg"
...

It should be dynamically served as:

...
src="/app1/static/image.jpg"
...

But the point is, for the cost of a single CD per month I was able to listen to any CD from any band whenever I wanted. It was an extremely easy decision to sign up.

Yeah but my point is, you pay but you don’t actually get those albums. So if after some years Spotify turns to shit you don’t have anything to show for when you cancel the service, and even though you have paid the equivalent of dozens of albums your music collection is gone.

Also, I don’t buy anyting near an album per month, so even on that level it doesn’t make sense to me. I do have a large collection, but I’m not really digging much current music anymore so if I buy two albums per year, it’s a lot.

This has nothing to do with WEI. Google can do more than one shitty thing at once you know.

Never understood why anyone would want to rent their music in the first place. As good as the service may be when you sign up for it, you know it will eventually turn to shit as they’re trying to monetize every last cent out of it, and then your only choices are to endure the shit or to quit the service and be left with nothing.

If you really want to get anal about it, yes I know there things like CNAME, PTR and MX records too but that’s outside of the scope of this discussion.

DNS doesn’t deal with ports, there’s no way to say: homelab.example.com should point to IP address 1.2.3.4 and port 12400.

Sure, but the point is not so much about which one to use but that the terminating point listening on 443 should sit outside of his network.

So he will either need a cloud service, or accept that he will have to add :12400 to his URLs.

DNS doesn’t deal with ports, it resolves hostnames to IP addresses and that’s it.

What you probably need is some kind of reverse proxy that sits outside of your network, listens on port 443 and then directs it to your home IP address on port 12400.

Oh… I definitely misread that.

Of course it is. It’s fun to rebuild the computer of your youth, and run old games on periodically correct hardware.