Sure. I'm not recommending anything, just stating what has worked for me. For simple use cases, I think most of the DDNS services are pretty much the same anyway and it's easy to switch to an another one if one stops working for some reason.

I've been using No-IP free plan for years without issues. Inputted the credentials to my routers DDNS client and then basically forgot about it. Free users need to confirm their account once a month via email but that's just one click.

If your domain registrar happens to have an API to update DNS entries, you could implement DDNS yourself by writing a simple automated script to check the external IP (e.g. via ipify.org) and if it's changed from the last check then call the API to update the DNS entries.

I've been working through my backlog on Steam

I finished Twin Mirror last night and today I started Kona II. I'm couple of hours in and so far it's been a little meh. Graphics are great and all but it just doesn't have the same atmosphere than the first Kona had

My main issue with CVEs nowadays is that it seems one gets generated even when 99% of the use cases for the software in question are not vulnerable as the vulnerability requires a very specific configuration/circumstances/etc. to be exploitable. In large projects with lots of dependencies this adds a lot of noice and there's a risk that actual important CVEs go unnoticed.

That or live cd (well, most likely live usb nowadays)

I was going to give the example of the Carnival cruise ship that sank in the 2010s (I think) largely due to the captain’s incompetence[...]

That's Costa Concordia. It received extra media attention and is mostly known due to the awful behavior of the captain who first directly caused the accident and then fled the ship before most of his passengers.

Well, just by looking at responses in this thread, the controversy most definitely still exists. Some seem to like it and others hate it fiercely.

Cool, thanks for the explanation.

a single application that gets bundled with all necessary dependencies including versioning

Does that mean that if I were to install Application A and Application B that both have dependency to package C version 1.2.3 I then would have package C (and all of its possible sub dependencies) twice on my disk? I don't know how much external dependencies applications on Linux usually have but doesn't that have the potential to waste huge amounts of disk space?

Sorry to ask, I'm not really familiar with Linux desktop nowadays: I've seen Flatpak and Flathub talked about a lot lately and it seems to be kinda a controversial topic. Anyone wanna fill me in what's all the noice about? It's some kind of cross-distro "app store" thingy?

I think it would be useful with updates when setting up a new phone or after a factory reset when basically every app needs an update

Google Tasks. Does not have all the features of other apps but does everything I need and was preinstalled

Telegram has a builtin support for proxies and the authorities probably won't be able to block all of them