https://www.pcmag.com/news/brave-browser-caught-redirecting-users-through-affiliate-links

I’m not going to defend Mozilla by any means, but if you care about privacy, you wouldn’t use a browser based on Chrome anyway.

You could replace “Brave Browser” with Firefox and the statement would still be true.

At least Firefox wasn’t caught hijacking affiliate links.

If you want to fully wipe the disks of any data to start with, you can use a tool like dd to zero the disks. First you need to figure out what your dive is enumerated as, then you wipe it like so:

sudo dd if=/dev/zero of=/dev/sdX

From there, you need to decide if you’re going to use them individually or as a pool.

!< s

I’m not disagreeing with anything you’ve said?

I’m saying that just adding Mozilla’s PPA to your sources won’t change apt’s behavior when installing Firefox unless you tell apt to prefer the package offered by the Mozilla PPA.

As someone who uses Kubuntu as a daily driver, I’m well aware of the snap drama and have worked around it using the method I pasted above.

Even though it’s an underhanded move by Cannonical, I’m still glad the OS is open source since it makes the workaround so trivial.

It takes a little more than just adding a different repository to your package manager, you have to tell apt which to prefer:

echo ’
Package: *
Pin: origin packages.mozilla.org
Pin-Priority: 1000

Package: firefox*
Pin: release o=Ubuntu
Pin-Priority: -1’ | sudo tee /etc/apt/preferences.d/mozilla

‘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.

Windows is way more documented. Not necessarily by Microsoft but by the absolute waste community.

If I had a nickle for every BSOD error code I researched only to find “have you tried running sfc /scannow? What about a refresh? You tried both and nothing worked? Just reinstall!”

More documented my ass. Linux at least tells me what’s wrong. “No space left on device” or “missing dependency” is way better than “Error code 0x0000007e”