Censorship in all the dictionaries I see don’t require it to be a government that is censoring for it to be called “censorship”.

Someone attempting to hinder someone else’s ability to reach certain information is engaging in censorship.

Security is much more effective and adopted when it is simple. My understanding is that SELinux is not.

This means not only will fewer people use it and more people turn it off if something doesn’t work, it means more people are at risk of misconfiguring their system to allow something they didn’t intend to.

This is somewhat mitigated from the fact that, from my experience, Linux Security Modules cant ever make you less secure than without it. But it still can provide a false sense of security if you misconfigure it.

Here is a good article showing what I am referring to, and providing a solid security tool: BSD pledge/unveil on Linux.

Depends on the environment surrounding the door, as well as the environment surrounding the computer.

Some people simply care less about their computer security. The debate stops there. Security operates on a foundation of what you want to secure.

By comparing two environments of someone’s life you know little about, you are commenting from ignorance.

If you’re going to censor something, use an opaque black shape. These half-ass censorship attempts are ridiculous.

True.

Though, you are probably going to have a much easier time implementing a change to your code that is present in a company’s published code, than you would trying to reverse-engineer a binary.

Sharing of the code I would consider “giving back” in it of itself.

It can be done if you mess with the initramfs.

The kernel starts everything else by unpacking an archive containing a minimal environment to set stuff up for later. Such as loading needed kernel modules, decrypting your drive, etc. It then launches, by default, the /init program (mines a shell script).

That program is PID 1. If it dies, your kernel will panic.

After it finishes setup, it execs your actual /sbin/init. These means it dies, and that program (systemd, openrc, dinit, runit, etc) becomes PID 1. If an issue happens, both could fail to execute and the kernel will loop forever.

These applications likely know they can get away with it, as people classify them as “too important” to uninstall.

The solution is to make them wrong: To uninstall. Who woulda thunk.

Very simple actually: don’t use 100% transparency.

Just use something like 80-90% opaque (10-20% transparent) and use the background color as black so it just dims whatever us behind it.

You can have both function and form.

The Gnome Gitlab link is locked up for me. Stuck here:

I need to see body camera footage, but their claim is that she had a butcher knife and approached an officer who was backed into a closet, all while carrying the infant.

This doesn’t seem like a simple “bad cop” moment.

Its possible: Link

I’ll take a program that isn’t getting updates anymore or simply wasnt working in my modified environment using slightly more ram and storage over it not working at all.

I have firsthand experience with videogames made for one flavor of Linux not working on my machine due to dependency hell.

This is a good reason for static linking. All the dependencies are built into the binary, meaning it is more portable and future proof.

We don’t need flatpak for this!

Yes. Using kexec.

Though this is irrelevant for majority of users: I’ve never seen it as the default.

That +

WARNING: Use with caution! Kernel crashes, spontaneous reboots, and data loss may occur!

gives me the idea that its likely safer to just do a proper reboot, if your alternative is kernel patching or loading a completely different kernel.

Plus, its likely that not every single bit of firmware running on your devices support live patching. Thus you will be rebooting eventually, unless you are fine with avoiding the updates.

Generally no. There are some parts of your system that you will have to reboot for (like the kernel). But apps? Installing a new service?

No.

Most systems you just install the app you want, and run it.

There are some immutable distros the require things that are installed as part of the base system to only be available after a reboot, but they provide ways to install things without making it a part of the base system. Thus no reboot required.

Is what necessary?

I had to update a Chromebook-like machine that was running Windows not to long ago. It was excruciating. The restart progress bar on one update after reboot took ~30 minutes to reach 3%.

Keep in mind that the computer is unusable during this time, and all it takes is one poweroff to brick the machine. Ask me how I know :) . I had to leave it plugged in overnight to finish.

If this comment is referring to Windows reboots after update, I will call it confidently incorrect.

Discord servers are just groups. Lemmy “instances” are actual separate instances of Lemmy communicating.