ZeDoTelhado

Mooltipass looks sick actually. I have my reservations regarding the ble part, but I would have to look into it more to understand it. Might get one to check around how well it works (once availability is there)

Curiously enough, I never heard of those. Do you happen to know good ones so I can further check?

That's how i want my canisters: with good posture

I am not sure if by any chance they do the extra mile to check on that. However, as a rule of thumb you should try to keep private stuff away from work stuff, meaning, at work maybe is not the best idea to boast about your reddit profile where you happen to follow some nsfw stuff (or other stuff that can be considered offensive and/or can lead to controversy). I would imagine they try to check things such as accounts attached to an email or phone number (for instance). If a set of aliases were used for this (or different info) from your work email phone etc., you should be able to keep it separate.

For me feels someone is chasing a KPI on PSN users that, quite frankly, gives no one but Sony executives satisfaction on bigger number = better number. Steam on that sense made the correct decision to give back the money on people that cannot play a game anymore because of a future requirement (as mentioned by op, not everywhere psn exists). But for me, even if psn is available, you should be able to refuse to further engage on a game based on a future requirement like this and get the money back (same applies if for instance a game all of a sudden has something like denuvo).

So my take away of this is: please, get rid of kpis, it's about time we learn to get away from hard metrics that can be cheated

Fantastic. Time to deliver opnsense and/or pfsense to the masses. Or better, recycle a router with openwrt or similar

When are we going to riot to have the same button to enter bios setup everywhere? For me personally grinds my gears every time I have a different machine, check the bios boot message like a hawk to get what key I need to press to enter setup (after a while you sort of know by vendor, but for me that should not even be a thing)

Thanks for taking the time to explain. I was trying to get my head around on how this works but could not understand much of it. A lot of people here are very much against systemd in all senses, but this sounds like a better approach. Even if it not done as systemd, makes more sense than checking files and getting elevated privileges for a scope and use guardrails everywhere

Not sure how new, but has a turbo button. That should be good for something, right?

I was making a quick check, and yes, the DoH situation is a bit more dicey. From how I see it, the best way to make this work is to, at the firewall level, either block as much as possible any requests that look like DoH (and hope whatever was using that falls back to regular DNS calls) or setup a local DoH server to resolve those queries (although I am not sure if it is possible to fully redirect those). In that sense, pihole can't really do much against DoH on its own

EDIT: decided to look a bit further on the router level, and for pfsense at least this is one way to do this recipe for DNS block and redirect

Hm.... I am not familiar with that device myself, and since I use opnsense for a while I forget most people do not use routers outside of the provided one.

But in a theoretical sense, this firewall rule should look something like this:

• origin of traffic is any IP that goes into port 53
• outgoing traffic has to go to pi hole on port 53