Unnecessary and deeply concerning bow to the new “king”

Update: position got backed up by an official Proton post on Mastodon, it’s an official Proton statement now. https://mastodon.social/@protonprivacy/113833073219145503

Update 2, plot-twist: they removed this response from Mastodon - seems they realize it exploded into their face!

  • radioactivefunguy@lemmy.world
    23·
    2 days ago

    I literally signed up for their VPN last night since NordVPN doesn’t offer port forwarding. . . Oh well, I can 30 day guarantee it and get mullvad I guess. All I lost was a bit of time setting it up in all my containers, and any respect I had for Proton

    • Rogue@feddit.uk
      1·
      2 days ago

      Give AirVPN a chance. The website looks terrible but it’s a great service and port forwarding is far simpler than Proton’s weird solution

      • radioactivefunguy@lemmy.world
        1·
        1 day ago

        Update: I just signed up for AirVPN, but speeds are very slow. With both Nord and Proton, spp d tests come back at ~800/700 on my gigabit fiber. The fastest AirVPN server I’ve found is 60/10, most are 10/10.

        Is this normal in your experience (just a slow VPN service) or do you know of anything I can do to get faster speeds? (I’m using the Eddie client on windows)

      • radioactivefunguy@lemmy.world
        1·
        2 days ago

        Looks like they’re taking advantage of the controversy with a sale! Requested my 30 day money back from Proton, and signed up for AirVPN ($10 cheaper!)

    • EP51L0N@sh.itjust.works
      2·
      2 days ago

      I would personally recommend Windscribe. They have a free tier, and include port forwarding, unlike Mullvad

      • radioactivefunguy@lemmy.world
        1·
        2 days ago

        Yup, that’s the one I use in a few projects. I also run torrent software/soulseek in containers that use OpenVPN config files directly which is both simple to setup and very secure in terms of IP leaks.

        I just switched over to AirVPN, so now I just need to generate new config files and go switch them out for all the affected containers