Technology

59578 readers

3381 users here now

This is a most excellent place for technology news and articles.

Our Rules

Follow the lemmy.world rules.
Only tech related content.
Be excellent to each another!
Mod approved content bots can post up to 10 articles per day.
Threads asking for personal tech support may be deleted.
Politics threads may be removed.
No memes allowed as posts, OK to post as comments.
Only approved bots from the list below, to ask if your bot can be added please contact us.
Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago

MODERATORS

872

Proton launches privacy-focused Google Docs alternative: Docs in Proton Drive is an open-source, end-to-end encrypted collaborative document editor (proton.me)

submitted 4 months ago by ForgottenFlux@lemmy.world to c/technology@lemmy.world

167 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] Gestrid@lemmy.ca 1 points 4 months ago* (last edited 4 months ago) (1 children)

I admittedly should've done more research before my first comment, but it does actually turn out that everything I said is true. Proton's technology was previously audited by Mozilla and is currently audited by SEC Consult and other companies regularly, and the audits are available for everyone to view. Additionally, they do have a bug bounty program. Also (and this is something I didn't mention), the ProtonVPN and Proton Mail apps are all open source.

[–] Excrubulent@slrpnk.net 0 points 4 months ago (1 children)

Is that the backend code? It seems like they're talking about the apps, not backend code. The thing being discussed here is backend code.

[–] lastweakness@lemmy.world 1 points 4 months ago (1 children)

Nearly all of Proton's stuff uses publicly verifiable client side encryption, so idk what all this is about

[–] Excrubulent@slrpnk.net 1 points 4 months ago

It's about the server-side code. If that's not an issue then someone needs to make the argument, not throw up smokescreens about the apps and frontend code.

You're right that the encryption needs to be verifiable on the client side, but then why not share the server side code?

I mean if they did, anyone could theoretically spin up an instance, which would be good, actually.