Paul H
My feedback
16 results found
-
26 votes
An error occurred while saving the comment Paul H
supported this idea
·
-
1,020 votesPaul H
supported this idea
·
-
648 votesPaul H
supported this idea
·
-
44 votesPaul H
supported this idea
·
-
141 votesPaul H
supported this idea
·
-
96 votesPaul H
supported this idea
·
-
182 votesPaul H
supported this idea
·
-
210 votesPaul H
supported this idea
·
-
563 votes
An error occurred while saving the comment Paul H
commented
Even if not screenshots, just having a code window would be nice. Markdown doesn't handle comments and what have you all that well and it messes with the formatting. I never really tested to see if it confuses Lumo, but it looks atrocious and so I don't do it. Or even just allowing a toggle to turn off formatting so we can copy/paste code would be nice.
-
618 votes
An error occurred while saving the comment Paul H
commented
This doesn't seem possible without Lumo breaking some of its current tenets. Storing encrypted chats after the fact is one thing. Lumo doesn't really have access outside your profile settings and what you say in a single session. The value in a memory is clear and obvious, no argument there. But I don't see how it can be possible without opening up access to customer data on the server side of things. That's always been kept to the minimum amount possible and I applaud them for that. I don't like the idea of "just this one time though it'll be ok."
-
255 votesPaul H
supported this idea
·
-
1,127 votesPaul H
supported this idea
·
-
2,256 votesPaul H
supported this idea
·
-
203 votes
An error occurred while saving the comment Paul H
commented
Has anyone tried submitting a ticket to enable it? When you go to SMTP settings on mail, it says you can request it be enabled by submitting a ticket with use cases and expected volume. Not sure if they always deny or what in regards to why this vote exists.
-
2,766 votes
An error occurred while saving the comment Paul H
commented
I can see the difficulty in implementing this. You don't need to purchase mail to purchase vault. So everything is behind a Proton account. It's not behind your Mail account. Mail is just a service that uses your Proton account. Single Sign on would break with this too. It's hardly a giant security concern as virtually all security-minded companies have SSO. If they break your email, they can reset most service passwords anyway. So having a different one doesn't really matter. Just turn on 2FA. It's infinitely better for security.
-
3,031 votes
Partially rolled out, as per: https://proton.me/support/pass-offline-access
As per the Spring/Summer Roadmap this will extend out to the Pass Extension: https://proton.me/blog/pass-roadmap-spring-summer-2026
Paul H
supported this idea
·
this honestly would simplify installation immensely. simple compose file and perhaps a secrets file and boom. i haven't used the linux version yet, but i'd imagine it has a command to print out the needed config options for the mail clients. a simple one liner than prints out all they would need. if wanting to use the bridge for other services, this makes the setup much simpler not having to worry about network access outside of the docker network. plus it allows for some isolation.