cross-posted from: https://lemmy.dbzer0.com/post/50693956

Transcript

A post by [object Object] (@[email protected]) saying: courtesy of @[email protected], Proton is now the only privacy vendor I know of that vibe codes its apps: In the single most damning thing I can say about Proton in 2025, the Proton GitHub repository has a “cursorrules” file. They’re vibe-coding their public systems. Much secure! I am once again begging anyone who will listen to get off of Proton as soon as reasonably possible, and to avoid their new (terrible) apps in any case. https://circumstances.run/@davidgerard/114961415946154957

It has a reply by the author saying: in an unsurprising update for those familiar with how Proton operates, they silently rewrote their monorepo’s history to purge .cursor and hide that they were vibe coding: https://github.com/ProtonMail/WebClients/tree/2a5e2ad4db0c84f39050bf2353c944a96d38e07f

given the utter lack of communication from Proton on this, I can only guess they’ve extracted .cursor into an external repository and continue to use it out of sight of the public

  • Daniel Quinn@lemmy.caEnglish
    112·
    9 hours ago

    So a Cursor config file made it into the repo and was later removed and they just declare that this must be a case of trying to obfuscate their vibe coding policy? “They must have moved it to a private repo!” That seems like a logical jump made out of personal bias.

    A far more likely case, (and one I’ve seen in dozens of projects myself) is that someone was using Cursor locally and committed the file by mistake. Then when they realised this, they removed it.

    People (especially juniors) commit their .idea or .vscode files all the time. Normally, I catch this at review time, but sometimes it slips by. It’s still not great that anyone was using Cursor in the first place, but this alone is hardly evidence of policy or conspiracy.