Skip to content

Noah Ertz

My feedback

1 result found

  1. 7,760 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Noah Ertz commented  · 

    While I do understand the viewpoint (and somewhat lean towards that viewpoint myself) of the commenters who say that creating a "Proton Browser" is basically trying to reinvent another "privacy wheel", it will be ultimately Protonmail's decision. I believe it is beneficial to have a variety of ideas recorded for later use no matter if people say they are "good" or "bad"; nonetheless, a "Proton Browser" is something that should be avoided for a long while as the developers of ProtonMail have so many other features and optimizations they need to make for this email service before they would ever consider expanding to other territories. One thing to note is that plenty of people have switched to other services, software, etc. to not become completely dependent on using Google for everything (there's a lot of risk when being reliant and giving information away to a single company through the use of its popular software). Maybe it is best to not rely on one company to give all of the software you use, no matter what their intentions are. Do we really need ProtonMail to become another Google? I don't mean they would have malicious intentions and start making unethical decisions; but even if they became "The Ethical Google," it's unlikely that most of the people using ProtonMail will use all of their other services. It would probably be better for ProtonMail to just be an email service. By focusing on being a great email service, they won't need to make so many sacrifices to make up for other services. The same goes for other companies making different kinds of software. When a company puts all of its efforts into making a single type (and occasionally a few types that go along together is okay as well) of software with a special focus, one can expect that this piece of software will appeal to a certain market. The company can focus their efforts to appeal to that market; and if all goes well, a great piece of software for specific purposes is created and enjoyed. For ProtonMail, there could be other things they could expand to, like have a cloud storage as it would easily tie in with the email service (the cloud service would store email files as Google Drive stores Gmail files). Overall, a "Proton Browser" would probably be better left with some other company to make, but it doesn't mean that ProtonMail won't surprise us one day and give us a Proton Browser that nobody expected could exist. If they were to do this, I would suggest for the browser to have a specific purpose without ending up becoming another Google Chrome or FireFox attached with a "We Love Privacy and Security!" slogan. Perhaps a browser that focuses on encryption, simplicity, and speed (maybe a different kind of Lynx (but not as clone, of course)).

    I noticed that you said that you didn't like how Google "snapshots and keylogs our protonmail logins." Maybe instead of a browser, why not a standalone application for ProtonMail? I don't mean having a Bridge, but an actual application solely for its own service. Another suggestion is to make an alternative to Thunderbird with a special focus on Protonmail's internal encryption (perhaps it would work better with the internal encryption and become much faster, more reliable, more optimized, and cleaner without the need for a lot fo addons that end up making Thunderbird cluttered and buggy). Mozilla has lost some respect from some its users, and ProtonMail users have suggested that the developers should be careful with creating a Bridge as they would rather sacrifice having IMAP, POP3, etc. support than to sacrifice security and privacy. Maybe this would be a better long-term solution.

Feedback and Knowledge Base