https://lemmy.world/u/madthumbs

He also made ‘Linux vs Windows’ but got removed from that community, and the new mod removed all his posts or I’d post links to a discussion we had.

A user made a community called LinuxSucks.

Poe’s law being what it is, it can be hard to tell the difference between satire and someone actually drinking the kool-aid, but having talked to this person and been banned from his little fiefdom, he strikes me as the non-satirical kind of poster.

Trolls revel in the attention. They want the outrage that comes from interaction, and he’s locked down his community, disallowing anyone from posting anything at all last I checked.

He’s taken stances like “Open Source software is inherently bad for society because it takes jobs away from companies” and “the spyware companies like Microsoft build into Windows (IE Windows Recall or any other data aggregation system) are where things are going and you should be happy because you’re helping a company make money”.

I’d personally describe him as a Temporarily Embarrassed Billionaire trying to find a cock to deepthroat so he can join their ranks.

“Over the top” like what?

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.

run win.exe
Open AOL
Log in
https://www.youtube.com/watch?v=gsNaR6FRuO0

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”