{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreibzxmhzat2qf3jo3xpx7rftspa3u7vze7446gws6mdpot257ktqly",
    "uri": "at://did:plc:haakkg7y3xdghcdmprxeexso/app.bsky.feed.post/3mn4cj5g7mlh2"
  },
  "path": "/t/proton-pass-a-password-manager-for-ai-agents-proton/38051?page=2#post_38",
  "publishedAt": "2026-05-30T23:46:24.000Z",
  "site": "https://discuss.privacyguides.net",
  "tags": [
    "this topic",
    "What should we require of VPN providers on macOS?",
    "Site Development",
    "Remove ProtonVPN - #332 by ph00lt0",
    "Proton markets Lumo as \"open source,\" but support calls it a \"long-term intention, not the instantaneous state\"",
    "General",
    "https://lumo.proton.me/about",
    "How should we handle Proton's misleading marketing?",
    "Remove ProtonVPN",
    "Tool Suggestions",
    "What is a kill…",
    "here"
  ],
  "textContent": "To me, it’s again all about trust.\n\nBitwarden is still open source, but some people after this topic, won’t be using them anymore and understandably.\n\nNothing to my knowledge prevents Proton form undoing what they did with their structure kind of like what Bitwarden is changing their core values.\n\nThere’s several red or at least yellow flags and these four topics cover most of them:\n\nWhat should we require of VPN providers on macOS? Site Development\n\n> The discussion surrounding Remove ProtonVPN - #332 by ph00lt0 is so random and all over the place, that I am not even going to attempt to sort it out and try to move some posts over here. See: I think the main question is: Should we require providers to use hacky workarounds like pfctl filters on macOS instead of standard tools the OS provides? It feels like the answer is probably no, but if anyone wants to continue this discussion then this is a fine place to do so.\n\nProton markets Lumo as \"open source,\" but support calls it a \"long-term intention, not the instantaneous state\" General\n\n> Hello, I’m hoping to get some perspective on a recent interaction I had with Proton support that has left me feeling concerned. I was looking into Proton’s new AI thingy, Lumo, and was really encouraged by this claim on their website: \"Unlike other AI assistants, my code is fully open source, so anyone can verify that it’s private and secure — and that we never use your data to train the model.” (Source: https://lumo.proton.me/about) Naturally, I wanted to check out the code. When I couldn…\n\nHow should we handle Proton's misleading marketing? Site Development\n\n> Currently, Proton’s kill switch documentation is incorrect, which seems fairly severe: Now, we can certainly note this ourselves, and I have a PR open to do so: Do we want to take stronger action against Proton for this?\n\nRemove ProtonVPN Tool Suggestions\n\n> Why should this tool be removed? ProtonVPN should be removed from recommendations as its kill switch for MacOs is known to not work: When switching to another ProtonVPN server On computer boot up → In both of these instances, the user’s real IP becomes exposed to any online service it is connected to prior to re-connection to new ProtonVPN server. On ProtonVPN’s official website they claim that “[regular kill switch] does protect you while switching servers with Proton VPN” : What is a kill…\n\nAlthough lot have been addressed and I would love to be one to cheer for Proton, I still have the red light in my mind on some of their marketing lies.\n\nKind of my first red light from here when I think about it.",
  "title": "Proton Pass: A password manager for AI agents | Proton"
}