tldw: dont use hotspot shield ![]()
seriously though, cool video, great to see this type of VPN evaluation.
tldw: dont use hotspot shield ![]()
seriously though, cool video, great to see this type of VPN evaluation.
Haha, as said in my initial message I did not miss it (as shown by the green arrows) but it is an easy thing to actually miss indeed. Thanks for considering an update! ![]()
I understand the limited bandwidth and need to stay focused on a given goal, but thanks for considering the idea! ![]()
10 posts were merged into an existing topic: Mullvad has partnered with Obscura VPN
Feel free to reach out to me directly if yāall have any questions: carl@obscura.net
@sp_rtings I see in your Proton review you have āKill switch works as intended.ā
I know the kill switch has been a big issue here as of late.
Are you guys considering looking more into that feature, especially for Linux and Mac?
Are you guys considering looking more into that feature, especially for Linux and Mac?
Considering, yes! Doing it: ā¦itās not feasible for us to maintain this test over time!
Itās not technically hard, but there are too many variables for us to manage at the moment unfortunately. For Linux, there are a few different network managers that we would need to test, which multiplies quickly the number of different setups we need to test. For Mac, the network manager works differently than Windows or Linux, so we would probably need to tailor itās own test.
That said, those tests are still possible to do. The main problem comes from how we do reviews: We maintain the review through time by retesting the products either continuously, or when major updates/events happen. It would not be possible for us to maintain this test over time. However, there is a possibility we do a one-time test for a few selected VPNs for this. Iāll add this to our special projects!
I donāt think the world is expecting you to maintain a list of everywhere on Linux you have tested and evaluated VPNs. Even covering just one like Fedora for example and maintaining that is enough. The real point here is to have all OSs covered with VPNs, is all. Not to provide info on many all the time where everything must remain accurate. That of course will be a logistical nightmare to ensure or keep ensuring.
Fair point! Testing one disto, one network manager is still better than none. Our main hesitation was that people would not care much if it wasnāt their own. The more direct feedback I can get on this from users, the better I can convince my peers to move on this!
People who own Macās are not going to care about Windows or Linux, doesnāt mean there should not be testing for all.
Same logic applies here. I suggest choosing a super popular stable one like Fedora. They keep up with the latest updates and are rock solid stable. Plus they also have immutable variants so thatās a plus. I donāt think DE matters and anyone on another distro on the DE of their choice can also move to Fedora should they want to if VPN work best or know about how it works on Fedora even if not on their preferred.
Thatās just my thinking. You can deliberate on this more internally if needed.
When you do have a business, allocating resources is important and putting 50% of extra time into a 3% usage OS might not be the right call.
Rtings are doing great on that regard and want to do the effort but most people donāt want to invest crazy effort for a super niche community that wonāt bring them any views/money/etc (this is a generic statement as of why people do not care that much about Linux in general).
Sure. Thatās why Proton lacks on Linux so much and hence the reason for the majority of the gripe against it on the VPN and Drive fronts to say the least.
But if youāre considering desktop Linux, it also means considering the 3%. Otherwise Linux will continue to be disparaged and not be taken seriously even in 2026.
When you do have a business, allocating resources is important and putting 50% of extra time into a 3% usage OS might not be the right call.
This is the main reason why we did not test the killswitch on other OS in the first place and focused on Windows.
The new argument now, is if we are testing VPN for a privacy recommendation, it makes little sense to test the killswitch on Windows onlyā¦. so the arguments changed since the initial discussion!
The more traction we get on this new privacy test, the more I can convince the need to test the killswitch on Linux internally!
There already is traction. I just canāt prove it to you but I assure you, anyone even new to Linux (along with those using it for years) are going to want this. Itās valuable info!
Also think of it in another way - youāll be one of the only entities performing a truly holistic testing of VPNs and will be continuing and building on the great work you have been doing and did on this video thus far. The critical thinking passionate tech users are going to recognize your quality work. This community already does.
Or at the very least, it should be obvious to users that the test is for Windows only. I am not sure āKill switch works as intended.ā provides that clarity unless you feel its safe to assume most readers donāt just look at the pros / cons summary and leave.
it should be obvious to users that the test is for Windows only.
We noticed that today as well when taking a new look at it! Weāll make it clearer.
Proton definitely has no excuse indeed, especially given their size + employees.
At the same time, it doesnāt look like they are hiring/interested into getting people to code for desktop/Linux environment, they stick to Web/mobile from the offer I last checked.
This is why FOSS is so appreciated into some communities, because people coming from Open Source usually consider the following order: Linux ā MacOS ā Windows because of ecosystem/friction/OS BS.[1]
You can always submit a new thread with a topic to check the interest of people willing to have a Linux test.
The more people interested, the more reason to do it for Linux.
The more Linux stuff available, the more people will be interested.
If it picks up well enough, could be a very virtuous loop overall. ![]()
Side note but if you make the test on Linux, you can also share it on OpenWrt because their community will also be very happy to learn about it.[2]
Same for quite a few Linux news/websites that would gladly share a cool group effort.
Windows is more popular and the go-to basic OS, but Linux is more of a passionate-driven community-centric hardcore believers that might be worth fighting alongside if you want an audience that keeps coming back and support the Rtings team!
![]()
After testing it properly, Iāve started to like it more. I did have to install Proton back on my other phone because I couldnāt confirm payments, and I really tried every possible method several times. This isnāt a problem because I plan to keep my Unlimited subscription. If anything, it shows the opposite of a problem. This also happened with Mullvad, but on my PC as well, despite all the tricks I tried.
On my PC, I can handle my banking when I use V2Ray. One time, a CDN probably blocked the traffic, but luckily you can change the port very easily and continue. Switching between single-hop and multi-hop has been made so easy that it only takes a few seconds.
Changing the protocol when needed is also simple. And the fact that you can automate WireGuard key changes is something I didnāt even know to wish for, as I had never seen anything like it before. Thanks @sp_rtings for the article that made me give IVPN a chance!
Iāve been a complete and utter moron. Itās only now that I finally grasped the idea of installing the Proton VPN on the profile I use for handling payments. It eliminates all the unnecessary fiddling, and at least I havenāt managed to produce any leaks in any of the tests Iāve run. Now I can just keep it on multi-hop permanently.