Yes but it’s unregulated and like most unregulated TLDs it has become a cesspool of malware and dark dealings. I don’t think anybody would never if that were to happen to .io.

Normally that would have been the preferred solution, but since IANA has experienced all kinds of shenanigans on similar occasions they have decided to not allow ccTLD’s to survive their former country anymore.

The dev has not made available any means to donate to him directly. He asks that people donate to the maintainers of the block lists instead.

Linux printing is very complex. Before Foomatic came along you got to experience it in all it’s glory and setting up a working printing chain was a pain. The Foomatic Wikipedia page has a diagram that will make your head spin.

override the auto driving

I must be tired right now but I don’t see how a remote operator could have driven better in this situation.

You can’t get away from someone blocking your car in traffic without risk.of hitting them or other people or vehicles.

You probably meant they ought to drive away regardless of what they hit, if it helps the passenger escape a.dire.situation? But I have to wonder if a remote operator would agree to be put on the spot like that.

If you end up with resizing /var as the only solution, please post your partition layout first and ask, don’t rush into it. A screenshot from an app like Disk Manager or Gparted should do it, and we’ll explain the steps and the risks.

When you’re ready to resize, you MUST use a bootable stick, not resize from inside the running system. You have to make a stick using something like Ventoy, and drop the ISO for the live version of GParted on the stick, then boot with it and pick the Gparted live. You’ll have to write down the instructions and be careful what you do, and also hope that there’s no power outage during.

The safest method, if your /home has enough space, is to use it instead of /var for (some) Flatpak installs. You can force any Flatpak install to go to /home by adding --user to the command.

If you look at the output of flatpak list it will tell you which package is installed in user home dir and which in system (/var). You can also show the size of each package with flatpak list --columns=name,application,version,size,installation.

I don’t think you can move installed apps directly between system/user like Steam can (Flatpak is REALLY overdue for a good package manager) but you can uninstall apps from system, then run flatpak remove --unused, then install them again with --user.

Please note that apps installed with --user are only seen by the user that installed them. Also you’ll have to cleanup separately for system and user(s) in the future (flatpak remove --unused for system, then flatpak remove --unused --user for each user).

Interesting, I’ll keep it in mind.

Still not sure it would help in all cases. Particularly when 3rd party repos have to override core packages because they need to be patched to support whatever they’re installing. Which is another very bad practice in the Ubuntu/Debian world, granted.

I’m not sure how that would help. First of all, it would still end up blocking proper updates. Secondly, it’s hard to figure out what exactly you’re supposed to pin.

Third party package mechanism is fundamentally broken in Ubuntu (and in Debian).

Third party repos should never be allowed to use package names from the core repos. But they are, so they pretend they’re core packages, but use different version names, and at upgrade time the updater doesn’t know what to do with those version and how to solve dependencies.

That leaves you with a broken system where you can’t upgrade and can’t do anything entirely l eventually except a clean reinstall.

After this happened several times while using Ubuntu I resorted to leaving more and more time between major upgrades, running old versions on extended support or even unsupported.

Eventually I figured that if I’m gonna reinstall from scratch I might as well install a different distro.

I should note I still run Debian on my server, because that’s a basic install with just core packages and everything else runs in Docker.

So if you delegate your package management to a completely different tool, like Flatpak, I guess you can continue to use Ubuntu. But it seems dumb to be required to resort to Flatpak to make Ubuntu usable.

You should not have to open such a permissive rule. Like you’ve seen, docker will set firewall rules as needed if you have services that actually need to listen on the public interface.

If you’ve run that permissive input command on the VPS it’s most likely not a good idea.

What exactly are you trying to do? If you’re trying to use curl from inside a docker container that is not the correct way to achieve that. In fact you should not need to do anything like that, outside connections should be allowed (OUTPUT), and incoming collections (INPUT) should be allowed only if they’re related to an already ongoing connection (look up the ESTABLISHED flag).

Any extra flag you can offer that would narrow things down would also be welcome. When you write firewall rules you should be as restrictive as possible. For example since this is curl you’re probably going to connect to ports 80 and 443 so you can add --dport to restrict the ports to the OUTPUT rule. And you should specify the interface (in this case docker0) in almost all cases.

What does “old network” and “new network” mean? What are they, LAN setup? Docker setup? Describe them better (netmasks, routing etc.)

Claws-Mail is still alive and well and works great. Lots of plugins, you can write your own post processing actions, custom powerful filters, customizable interface etc.

Bold of you to assume Ubuntu was a recent version.

You can’t do machine learning without tons of data and processing power.

Commercial “AI” has been built on fucking over everything that moves, on both counts. They suck power at alarming rates, especially given the state of the climate, and they blatantly ignore copyright and privacy.

FOSS tends to be based on a philosophy that’s strongly opposed to at least some of these methods. To start with, FOSS is build around respecting copyright and Microsoft is currently stealing GitHub code, anonymizing it, and offering it under their Copilot product, while explicitly promising companies who buy Copilot that they will insulate them from any legal downfall.

So yeah, some people in the “Linux space” are a bit annoyed about these things, to put it mildly.

Edit: but, to address your concerns, there’s nothing to be gained by rushing head-first into new technology. FOSS stands to gain nothing from early adoption. FOSS is a cultural movement not a commercial entity. When and if the technology will be practical and widely available it will be incorporated into FOSS. If it won’t be practical or will be proprietary, it won’t. There’s nothing personal about that.

The IRC bots that run these sharing channels will crap themselves if hit with any kind of automation. Many/most have limited bandwidth and use a queueing system that only serves one or two downloads at a time and a small queue (it varies, some may have a 10 slot queue, some may have 50 or 100).

It’s GPL, they have to also provide the source. And you benefit from all the rights they do.

“Business” licenses try to prevent competition while still benefiting from free contributions, and pass it as “fairness”. But how is it fair for anybody except that particular company? What about the contributors? If OBS used such a license and reaped all the benefits would you still contribute to them?

I love that website. Now I have an easy way to find all the licenses and projects and companies I need to stay away from.

A self-hosting server does not necessarily crunch data and it doesn’t have to have loud fans or use lots of power. It can idle in the 15-20W range with an Intel CPU and if you put the HDDs on standby when idle.

Seafile is a file platform that’s more in line with what you mean. It can do sync but also sharing and collaborative editing.