Leaderboard

I don't think I need to explain much here. The embedded map is fetched from Google, so Google potentially tracks all users playing with their VPN connection turning it on and off. Further I don't know whether this embed is violating GDPR or not: does Google set custom (not technically required) cookies? Either way, Chromium browsers send a presumably identifiable header to Google domains by default. The alternative is either OpenStreetMap, no map at all or only load the map after a click (user confirmation). I have only once wanted to view the map out of numerous times visiting ipleak.net

qBittorrent, Tixati. There's an advanced configuration option in uTorrent too but it is not automatic. For detailed help, PM me.

IMPORTANT CORRECTION TO THE PREVIOUS MESSAGE. If you define a "quick" connection mode at boot, Bluetit will consider and respect white and black list directives included in bluetit.rc during the connection at bootstrap. Therefore, the proposed solution is optimal and does not require Goldcrest: just remember to change connection mode to quick (and do not set it to country), and define white lists according to the conditions written in our previous message (i.e. three empty intersection subsets, one subset per device). Kind regards

The Eddie version currently on Play Store still has compression enabled by default. It's been a while since a vulnerability has been known (VORACLE if I'm right) I think it's best to disable and remove the option completely because practical gains from compression are negligible at best (most traffic is TLS or otherwise incompressible).

What do you mean by technically impossible? There are other VPN providers out there (I can name a couple that I have previously used) that do it: you have an option in their connection tool that you can turn on or off: when it is on, they block ads, when it is off, you just get everything. I find that very handy. We are not interested in traffic inspection, not even to block ads. Traffic inspection has profound effects and legal consequences: it's contrary to our policy and mission, it weakens remarkably the anonymity layer, it opens the doors dangerously to logging and monitoring and affects in both major and subtle ways the mere conduit status of a service provider in the information society (exemption of liability for users of the service behavior is reduced when the provider selects the content to re-transmit, as past jurisprudence in the EU has widely shown). About traffic discrimination on your end (in your system) you can of course do as you prefer, there are many tools around which meet your needs without overloading our software with options unrelated to our mission or (even worse!) making it become bloatware. Kind regards