An experimental capability being kicked out of the kernel, so that it has to settle for being a kernel module or custom forks of the kernel, is absolutely a minor matter

This is a non-issue, being over-reported by people looking for clicks. A minor technical matter being handled by the person ultimately responsible for handling such things

In principle, yes. It depends on your Linux distribution though, I’m not familiar with the one you’re using

It’s asking for the ability to take screenshots, which is definitely suspicious unless there’s an in-app screenshot feature, and for the ability to launch discord and interact with it. The thing is it’ll be interacting using your discord account, I expect. That means it’ll be able to see your conversations and all the servers you’re in. It’ll also be able to post as you. Again, that’s the sort of thing which is very suspicious unless there’s some way in the app to have conversations over discord for some reason (maybe a bug report button, or a social feature).

Basically, I’d consider both of these alarming but not necessarily evidence that they’re spying on you to collect personal data or training data for an AI

That’s going to be a problem whatever solution you come up with, because of the federated nature of the lemmy system.

There’s no central authority to hand out usernames, so if two people sign up to different instances with the same username, any design which didn’t attach instance name to each username would fail. The only way around it would be for each instance to contact every other instance which exists, including the ones which haven’t federated yet, and negotiate ownership of the new username, and that’s just not possible

While that sort of analysis probably isn’t impossible, it is computationally unrealistic to do in realtime on a language which wasn’t designed for it.

It’s the sort of thing which is simple in 99% of cases, but the last 1% might well be impossible. Sadly it’s the last 1% you need to worry about, because anyone trying to defeat your system is going to find them

Also, it’s probably possible to fix the partition so that it’s as big as it used to be. It’s likely that some of your data is corrupted already, but the repartitioning won’t have erased the old data except here or there where it’s written things like new file tables in space it now considers unused

What they’re suggesting is to back up the whole disk, rather than any single partition. Anything you do to the partition to try and recover it has the potential to make a rescuable situation hopeless. If you have a copy of the exact state of every single bit on the drive, then you can try and fix it safe in the knowledge that you can always get back to exactly where you are now if you make it worse

I find it makes my life easier, personally, because I can set up and tear down environments I’m playing with easily.

As for your user & permissions concern, are you aware that docker these days can be configured to map “root” in the container to a different user? Personally I prefer to use podman though, which doesn’t have that problem to begin with

Podman supports docker compose just fine. You have to run it as a service, so that it can expose a socket like docker does, but it supports doing exactly that

Because a container is only as isolated from the host as you want it to be.

Suppose you run a container and mount the entire filesystem into it. If that container is running as root, it can then read and write anything it likes (including password databases and /etc/sudo)