GreenStar
My feedback
43 results found
-
197 votes
GreenStar supported this idea ·
-
3 votes
An error occurred while saving the comment GreenStar supported this idea ·
-
1 vote
An error occurred while saving the comment GreenStar commented
Everything the App can do the website can too, equally if not better.
GreenStar shared this idea ·
-
5 votes
An error occurred while saving the comment GreenStar commented
To clarify; a user with account username abc could have the proton social account Goku@social.proton.me
GreenStar shared this idea ·
-
267 votes
GreenStar supported this idea ·
-
17 votes
An error occurred while saving the comment GreenStar commented
1. This reads like it’s ai generated.
2. Google profits off violating users privacy, with googles free services you are the product. With protons services you pay for the product. Proton cannot provide what Google can for free, since Proton is not profiting off of “Free” users while Google is. -
7 votes
An error occurred while saving the comment GreenStar commented
Apples method should also be implemented but... apple does it weird so their method isn't as important.
GreenStar shared this idea ·
-
202 votes
An error occurred while saving the comment GreenStar commented
There's 2 different ways for this, both of google and apple, proton pass should implement and use both.
Googles: https://developers.google.com/identity/passkeys/developer-guides/upgrades (https://github.com/ms-id-standards/MSIdentityStandardsExplainers/blob/main/PasskeyEndpointsWellKnownUrl/explainer.md)
Personally I think google does this better.
Apples: https://developer.apple.com/documentation/AuthenticationServices/ASAuthorizationPlatformPublicKeyCredentialRegistrationRequest/RequestStyle-swift.enum/conditionalGreenStar supported this idea ·
-
1,956 votes
We have given this quite a bit of thought, but at the present moment, it is not clear the advantages would outweigh the disadvantages.
The biggest problem is search. Encrypting all metadata would break metadata search entirely on the web client as there is still no efficient way to handle search of encrypted data within a browser.
Secondly, metadata encryption’s value from a privacy standpoint is also somewhat dubious. Because we ultimately must deliver the message to the recipient, we must know who the recipient is. At the current time, there still isn’t any proven and viable way to work around this.
Metadata encryption is an area of continued research for us, and when the opportunity arises and the technology for doing this matures, we will definitely implement it in ProtonMail.
GreenStar supported this idea ·
-
1,449 votes
GreenStar supported this idea ·
-
164 votes
GreenStar supported this idea ·
-
232 votes
GreenStar supported this idea ·
-
383 votes
GreenStar supported this idea ·
-
323 votes
GreenStar supported this idea ·
-
562 votes
GreenStar supported this idea ·
-
226 votes
GreenStar supported this idea ·
-
244 votes
GreenStar supported this idea ·
-
4 votes
An error occurred while saving the comment GreenStar commented
Pretty sure this can already be done via custom filters, ends with. Something like "ends with .tld" should already do this.
-
267 votes
GreenStar supported this idea ·
-
116 votes
An error occurred while saving the comment
This would be EXTREMELY easy for proton considering they could take their PWA version and do this: https://learn.microsoft.com/en-us/microsoft-edge/progressive-web-apps-chromium/how-to/microsoft-store