You could use Blocky for this. It can do both, apply some block lists and use DoT/DoH resolvers.

I liked this explanation:

https://alexyorke.github.io/2025/06/29/list-is-a-monad/

Well the causality is obvious here.

Yes, because you wrote the config and she didn’t need anything fancy. Could she write or update the config by herself, or even upgrade?

Between channels and flakes, the old and new CLI, the lack of documentation of a lot of options…

I mean I love it and wouldn’t go back but it was a difficult journey, at leat at the beginning. Even today I sometimes find myself having to go read the code because the documentation is lacking.

I love NixOS but it’s clearly not a good distro to suggest for a first time on Linux.

Yes but

1. as far as we know they had no idea that it was hacked, so I don’t see how you can get a “vibe” if they are blind to it
2. the criminals were already using it when LE discovered it and then hacked into it

I don’t see how being hacked make it “still a honeypot”.

Where did you read that they gave police full access? I thought they were hacked.

What makes you think encrochat was a honeypot? Am I missing something?

Couldn’t this simply be a case of the Baader–Meinhof phenomenon?

Isn’t it against the EU’s DSA?

Just enable the annoyance lists, I’ve not seen one of those pop-up in years.

Can you explain how to make it work for this use case?

There is no need to pay for an external service for this and I don’t think Mullvad would work for this use case.

https://github.com/arkenfox/user.js/wiki/4.1-Extensions

Linux and Windows compress it too, for 10 years or more. And that’s not how you avoid zip bombs, just limit how much you uncompress and abort if it’s over that limit.

There are some examples of projects that use CleanURLs db in its readme but most have not been updated for a long time.

There are plenty of sites that use more than one parameters. It’s true that a lot of sites now use the history API instead of url parameters but you can still find plenty, and you have no garante about the parameters order. Any site with a search page that have a few options will probably use url parameters instead of the history API. It’s easier to parse and will end up being shorter most of the time.

Well for youtube it’s quite easy, there are only 4 useful parameters that I can think of, the video id v, the playlist id list and index if it’s a playlist and the time t if you’re sending a specific time in the video. Everything else can be removed. Here’s what uBlock Origin with the AdGuard URL Tracking filter list:

! Youtube
$removeparam=embeds_referring_euri,domain=youtubekids.com|youtube-nocookie.com|youtube.com
$removeparam=embeds_referring_origin,domain=youtubekids.com|youtube-nocookie.com|youtube.com
$removeparam=source_ve_path,domain=youtubekids.com|youtube-nocookie.com|youtube.com
||youtube.com^$removeparam=pp

There is no logic as to which parameters is useful and which is used for tracking. But there are databases.

Here is the one for the CleanURLs extension and here is the one for the AdGuard URL Tracking filter list (which I recommend everyone should enable in uBlock Origin).