I'd be pretty shocked if any ProtonMail users used IE.
The typical scenario is forced use by enterprises where the employees have no choice. But now that Windows 7 is on its last legs, this may be less of an issue.
ProtonMail is dropping support for Internet Explorer 11
21–30 of 63 posts
Re: ProtonMail is dropping support for Internet Explorer 11
#22Maybe I'll be able to reach other ProtonMail users here - does anyone else have persistent issues logging in to the web client? I use Firefox, LastPass, and Authy for 2FA. I have to try 6-7 times to log in every time, it drives me nuts. If it weren't for the mobile app I would have dumped this service long ago (for which I pay $50/year). This is the only site where I have issues logging in.
Re: ProtonMail is dropping support for Internet Explorer 11
#23Maybe I'll be able to reach other ProtonMail users here - does anyone else have persistent issues logging in to the web client? I use Firefox, LastPass, and Authy for 2FA. I have to try 6-7 times to log in every time, it drives me nuts. If it weren't for the mobile app I would have dumped this service long ago (for which I pay $50/year). This is the only site where I have issues logging in.
Re: ProtonMail is dropping support for Internet Explorer 11
#24I understand them wanting to discontinue browsers that have very low usage and have discontinued support from Microsoft, but I can't help but feel a little sad about the narrowing browser engine ecosystem.
At my company we're in this weird spot where Chrome has overwhelming adoption but IE11 has more usage than some of the other modern browsers. For example, if we only went by usage (or even more so: conversion/$$$), we'd be dropping Firefox support before we drop IE11.
That obviously doesn't feel great. I don't want to be in a "This website is optimized for Chrome in 2560x1440 resolution and 32 bit colors!", reminiscent of the old Netscape vs IE days. But we're getting very close to it. Firefox's usage is dwindling. Safari is pretty bad at anything except saving battery. Chrome is good but Google is pretty sketchy with how they bully their feature requests into the standards. IE11 can go to hell, but I still want people to test across browsers. It's happening less and less.
Re: ProtonMail is dropping support for Internet Explorer 11
#25Maybe I'll be able to reach other ProtonMail users here - does anyone else have persistent issues logging in to the web client? I use Firefox, LastPass, and Authy for 2FA. I have to try 6-7 times to log in every time, it drives me nuts. If it weren't for the mobile app I would have dumped this service long ago (for which I pay $50/year). This is the only site where I have issues logging in.
Re: ProtonMail is dropping support for Internet Explorer 11
#26I understand them wanting to discontinue browsers that have very low usage and have discontinued support from Microsoft, but I can't help but feel a little sad about the narrowing browser engine ecosystem.
Exactly how many browser engines do we need? There's currently Blink(Chrome|Edge|Brave), Gecko(Firefox), and WebKit(Safari and various OSS browsers). With web technology standards, it doesn't really make sense that there would be that much competition, so having 3 competing engines seems sufficient to me.
A world where Blink has 80%+ marketshare (which is pretty much what we have or where we're headed) is one where a single group can dictate the standard for everyone else.
Re: ProtonMail is dropping support for Internet Explorer 11
#27Earlier quoted context omitted.
Yes that seems a pretty odd combination, you want more secure email but using IE11 at the same time?
Wouldn't be surprising to find that security conscious people are more apt to alter their user agent string or have a plugin that rotates it often to counter fingerprinting. There are probably fewer genuine IE11 users than what is being detected.
That's not going to fool any competent fingerprinting scripts. Blink/webkit/gecko have different javascript implementations so it's easy to cross-check whether your user agent header matches your "real" user agent. The only thing you're really going to fool are server side logs for user agent. If anything, using user agent spoofer is an entropy source (makes you stick out more) because most people don't spoof their user agent.
Re: ProtonMail is dropping support for Internet Explorer 11
#28Earlier quoted context omitted.
Last major update for IE11 was like 6 years ago? Supporting anything related to this browser is painful and is blocking multiple new web features (or even not so new). I would love to use CSS Grid without thinking whether it will work however it happens that IE11 has only partial (and buggy) support for it. I believe that supporting IE11 blocks innovation.
What sort of features does a mail client need though? Up until recently i was using SquirrelMail and only stopped because my webhost removed it (likely because there hasn't been an official release for a few years now... which is weird since there is progress in the code repository, just not official releases). In case you haven't used it, SqurrelMail barely uses anything beyond a couple of frames (normal ones, not i…
Then you need to be careful to include enough polyfills because even what you assume would be there probably isn't, there's no Promises, no Array.prototype.includes, no arrow functions.
Re: ProtonMail is dropping support for Internet Explorer 11
#29Maybe I'll be able to reach other ProtonMail users here - does anyone else have persistent issues logging in to the web client? I use Firefox, LastPass, and Authy for 2FA. I have to try 6-7 times to log in every time, it drives me nuts. If it weren't for the mobile app I would have dumped this service long ago (for which I pay $50/year). This is the only site where I have issues logging in.
Re: ProtonMail is dropping support for Internet Explorer 11
#30Earlier quoted context omitted.
Wouldn't be surprising to find that security conscious people are more apt to alter their user agent string or have a plugin that rotates it often to counter fingerprinting. There are probably fewer genuine IE11 users than what is being detected.
>or have a plugin that rotates it often to counter fingerprinting That's not going to fool any competent fingerprinting scripts. Blink/webkit/gecko have different javascript implementations so it's easy to cross-check whether your user agent header matches your "real" user agent. The only thing you're really going to fool are server side logs for user agent. If anything, using user agent spoofer is an entropy source…