Peter
My feedback
10 results found
-
325 votes
An error occurred while saving the comment Peter
supported this idea
·
An error occurred while saving the comment Peter
commented
This should already be possible according to the support article linked below and based on my own testing just now.
-
5,376 votes
An error occurred while saving the comment Peter
commented
Proton’s closest competitor Tuta has now added this feature to their service. Maybe that’ll get things moving at Proton as they often are neck and neck when it comes to features.
https://tuta.com/blog/full-device-contact-integration-is-here
For those in the comments that don’t want this feature. Why are you worried that this will be enabled by default or mandatory? Proton and Tuta has (basically) the same view on privacy, so I expect that the feature will be opt-in in Proton, just as it is in Tuta.
Peter
supported this idea
·
-
2,746 votes
An error occurred while saving the comment Peter
commented
Microsoft, Google and Apple have separate apps for tasks/to-do lists and I feel like this is the way to go for Proton as well. Add yet another app to the portfolio - Proton Tasks, Proton To-Do, Proton Reminders or something along that line.
-
11 votesPeter
supported this idea
·
An error occurred while saving the comment Peter
commented
I think this could be divided into two separate suggestions; "Add Rich Text Editor to event description" and "Remove character limit in event description".
Sure, it would be great to just increase the limit, but as I haven't encountered any other service that has a character limit I think it should simply be removed completely. There's already another suggestion for just that - https://protonmail.uservoice.com/forums/932842-proton-calendar/suggestions/43604232-no-character-limitation-for-calendar-events.
-
22 votes
An error occurred while saving the comment Peter
commented
Proton’s closest competitor Tutanota has now added support for unlimited subfolders as part of preparation for their migration feature.
https://github.com/tutao/tutanota/issues/4829
Proton and Tutanota usually are neck to neck when it comes to implementing certain features. Hopefully this triggers Proton to move this up in their prioritization.
An error occurred while saving the comment Peter
commented
I'll add some votes to this and link to their support page for more details. I'll also add that I don't see why there should be a limit at all. I don't know of any other email provider that imposes a limit to the levels of folder hierarchy, except for Tutanota which does not yet support subfolders at all. And if you compare it to folders in Windows, there's no nesting limit for the folders as long as the the length of the path doesn't exceed 260 characters.
https://protonmail.com/support/knowledge-base/easy-switch/#customize-other
I've also sent a support request regarding this and got the following reply.
"Please note that ProtonMail supports only up to 3 levels of folder nesting and this cannot be changed at the moment.
However, we will provide your feedback to the appropriate team for further consideration to see if this can be changed in the future."I suspect that the limitation has something to do with the encryption tech being used, but at the same time there are many encryption methods you can use which don't have this limitation, so that might not be the reason.
Peter
supported this idea
·
-
1,354 votesPeter
supported this idea
·
-
3,400 votesPeter
supported this idea
·
-
3,724 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.
An error occurred while saving the comment Peter
commented
@Snape
You probably logged in to the old client (https://app.tutanota.com/#login) which I think is still used as the default.
The new client (https://mail.tutanota.com/login) is the one that has support for search.
An error occurred while saving the comment Peter
commented
@SinCabeza Tutanota does have search: https://tutanota.com/blog/posts/first-search-encrypted-data
Peter
supported this idea
·
-
6,372 votesPeter
supported this idea
·
-
818 votes
An error occurred while saving the comment Peter
commented
Right now this seems to be the one regarding this with the most votes and also marked as planned: https://protonmail.uservoice.com/forums/284483-feedback/suggestions/7849656-labels-are-great-but . I suggest everyone move their votes to that one instead.
An error occurred while saving the comment Peter
commented
Folders are now available: https://protonmail.uservoice.com/forums/284483-feedback/suggestions/16535209-being-able-to-create-custom-folders. Regarding sub-folders: right now this seems to be the one with the most votes and also marked as planned: https://protonmail.uservoice.com/forums/284483-feedback/suggestions/7849656-labels-are-great-but . I suggest everyone move their votes to that one instead.
An error occurred while saving the comment Peter
commented
Folders are now available: https://protonmail.uservoice.com/forums/284483-feedback/suggestions/16535209-being-able-to-create-custom-folders. Regarding sub-folders: right now this seems to be the one with the most votes and also marked as planned: https://protonmail.uservoice.com/forums/284483-feedback/suggestions/7849656-labels-are-great-but . I suggest everyone move their votes to that one instead.
An error occurred while saving the comment Peter
commented
Right now this seems to be the one regarding this with the most votes and also marked as planned: https://protonmail.uservoice.com/forums/284483-feedback/suggestions/7849656-labels-are-great-but . I suggest everyone move their votes to that one instead.
An error occurred while saving the comment Peter
commented
As Mick Bert mentioned below. Right now this seems to be the one regarding this with the most votes and also marked as planned: https://protonmail.uservoice.com/forums/284483-feedback/suggestions/7849656-labels-are-great-but . I suggest everyone move their votes to that one instead.
An error occurred while saving the comment Peter
commented
Right now this seems to be the one regarding this with the most votes and also marked as planned: https://protonmail.uservoice.com/forums/284483-feedback/suggestions/7849656-labels-are-great-but . I suggest everyone move their votes to that one instead.
Peter
supported this idea
·
An error occurred while saving the comment Peter
commented
As Mich Bert mentioned below. Right now this seems to be the one regarding this with the most votes and also marked as planned: https://protonmail.uservoice.com/forums/284483-feedback/suggestions/7849656-labels-are-great-but . I suggest everyone move their votes to that one instead.
An error occurred while saving the comment Peter
commented
Protonmail seems to have their mind quite made up about this feature according to this suggestion: http://alturl.com/qftzn where they refer to this kb: http://alturl.com/ef6yf. But just in case they might change their mind about it, I suggest everyone move their vote to the suggestion with the most votes (and that hasn't been marked as "Complete") which seems to be this one: http://alturl.com/t8ef4
Josh is correct, it isn't really working when there are attendees involved. If you try to edit, it will change the entire series.
You can at least delete single instances, even for events with attendees, but you never get the option for "this event and future events".
Until this is fixed, the support article should be updated to reflect the current state. But this needs to be pushed up the priority list as it's a crucial feature. The fact that this issue only occurs when there are attendees should've been caught before the feature was released.