‘Bricked’ in this sense meaning not that you’d just trash your OS and need a reinstall, but that it could actually stop your computer from booting at all. So the system32 analogy doesn’t exactly fit.

It’s because some motherboards implement UEFI in a way that allows important variables to be overwritten by I/O processes. Executing sudo rm -rf /* would recursively go into the EFI parameters folder where the kernel mounts EFI variables and attempt to delete things. Some motherboards allowed these delete operations to remove things in the motherboard’s firmware it needs to complete POST, thus rendering the motherboard useless.

But that’s a problem with the motherboard, not with Linux or Windows. The same damage can be caused by Windows.

‘Brigading’ would be if pro-Linux communities were organizing to specifically target another community.

The fediverse is likely to attract the kinds of people interested in Linux in the first place, and all the negative attention that community attracts comes organically.

I talked with the user a bit in Linux_vs_Windows before they were booted from the community, and it’s my opinion that they just have a hate-boner going for Linux. It’s possible to have valid criticism of Linux, but they go way past legitimate and straight into obsession territory. They tend to post in that community daily. So their points aren’t exactly great (though sometimes they hit on a good meme) and they get the points they get naturally.

It’s not a conspiracy, their arguments just tend to be shit.

This is what I think is most likely as well. The capacity on the drive makes me think it’s a SSD and they can just spontaneously fail.

This is why you always need backups. It’s never a question of if, but rather when a drive will fail.

An inbound only DNS forwarding rule would be pointless. All DNS queries should be originating from within the network.

EDIT

I think I see what you’re getting at. Assuming that the firewall is running on the NAS vs on the router.

The OP doesn’t specify, but I would assume the firewall rule would be on the router, as that makes the most sense to force all DNS requests on the network to go through the pihole.

I agree.

So the solution, OP, is to set the DNS settings on your NAS to your router’s internal IP so the firewall can redirect the traffic to your new port.

Never ask a company to pick between the right thing and profit.

It’s fundamentally impossible for a publicly traded company not to choose profit over ‘The Right Thing’, fullstop. Shareholders feel that have a fundamental right to growth, and if Google’s CEO were to choose ‘The Right Thing’ over profit, the shareholders can oust them in favor of a CEO willing to choose profits.

Enshittification is where every public company ends up, because the line MUST go up, no other alternative is acceptable.

Even if law enforcement can get a warrant, unless there’s a backdoor in the encryption then the data stays private. That’s the whole point of encryption.

The fundamental problem is law enforcement feeling entitled to snoop on private communications with a warrant vs the inherent security flaw with making a backdoor in encrypted communications. The backdoor will eventually get exploited, either by reverse engineering/tinkering or someone leaking keys, and then encryption becomes useless. The only way encryption works is if the data can only be decrypted by one key.

Anyone else remember when TSA published a picture of the master key set for TSA approved luggage locks and people had modeled and printed replicas within hours?

I think my favorite part of swapping has been forgetting how Windows does things. I’m so embedded in Linux and how it works every day that I don’t remember where to go for certain things in Windows without having to search.

I remember some power user shortcuts like run prompt shortcuts (appwiz.cpl or control userpasswords2) but I used to be able to walk people through how to get certain pages in the Windows UI, and I couldn’t do it today.

I made the swap after they forced Windows 7 update behavior to change. You used to be able to download updates but you got to choose when to install them. Then they changed it to either they’re on and fully automatic, or fully off.

At the time, I was running a computer repair company, and my work computer running Win7 was running a data recovery on an accidentally formatted drive for almost two days. After I had left and the program finished, Windows was all “Oh, the computer is idle now. Let me give you a 15 minute warning that I’m going to install updates and reboot if you don’t cancel”.

After the second time, I formatted my work computer. Shortly after, I did the same to my gaming PC. Haven’t looked back once.

Some of us manage to break the cycle, but despite how much I love Linux (ups and downs) I understand that it isn’t for everyone currently.

What most people want is a stable system they can just use without understanding much if anything about how the underlying systems work. They don’t care that wifi drivers can be fixed through a few terminal commands, they rail against the fact they have to do much of anything at all besides click [Next >]. And I can’t blame them; that’s what Microsoft has trained them for.

So many people with random toolbars and junk extensions in their browsers because the [Next >] button is how they get past whatever problem they have. The average user isn’t very tech savvy, and it takes someone with a desire to learn to truly thrive in a Linux environment.

I’ve converted my mom to Kubuntu, and she does well, but she’s also an outlier (she has an expired CCNA certification).

Linux suffers from a catch 22: there’s not enough users because there’s not a lot of commercial support because there’s not enough users because… And the people who are donating their time to make it better are saints as far as I’m concerned, but there’s only so much people can do for free. Things truly have gotten better, but until more typical user types can adopt Linux with little to no fuss, not much will change.

And that fact hurts my soul.

AFAIK, the unilateral nature of TOS/EULA agreements in the day of Software as a Service hasn’t been litigated. Which means there isn’t a court’s opinion on the scope or limits of a TOS/EULA and what changes can be made.

Currently, Adobe has the full force of contract law to initiate this change without any input from consumers because a case about this has never made it to the courts.

It’ll be interesting to see where this goes, but Adobe will likely backpedal on their language in the TOS before any case gets to a Judge because the last thing any company wants is for a TOS/EULA agreement to be fundamentally undermined by a court.