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.

As someone with two kids who play games on the switch, physical carts keep me from having to buy every game two or three times.

So losing the ability to buy a game and share it between three switches will severely increase the costs of games for me.

Depriving someone of years of their life isn’t a trivial thing. If someone was wrongfully convicted of a crime, the time they spend in jail is time that they could have been spending making a career, saving for retirement, building equity, etc. The things people do to prepare for retirement.

Should we just say “oops, our bad, no hard feelings right?” and just leave them to be homeless?

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

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.