📝 Correction | Nextcloud's end to end encryption is now production ready. #2054
Labels
No Label
🔍🤖 Search Engines
approved
dependencies
duplicate
feedback wanted
high priority
I2P
iOS
low priority
OS
Self-contained networks
Social media
stale
streaming
todo
Tor
WIP
wontfix
XMPP
[m]
₿ cryptocurrency
ℹ️ help wanted
↔️ file sharing
⚙️ web extensions
✨ enhancement
❌ software removal
💬 discussion
🤖 Android
🐛 bug
💢 conflicting
📝 correction
🆘 critical
📧 email
🔒 file encryption
📁 file storage
🦊 Firefox
💻 hardware
🌐 hosting
🏠 housekeeping
🔐 password managers
🧰 productivity tools
🔎 research required
🌐 Social News Aggregators
🆕 software suggestion
👥 team chat
🔒 VPN
🌐 website issue
🚫 Windows
👁️ browsers
🖊️ digital notebooks
🗄️ DNS
🗨️ instant messaging (im)
🇦🇶 translations
No Milestone
No Assignees
1 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: privacyguides/privacytools.io#2054
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description
On the privacytools.io website next to Nextcloud (in the self-hosted cloud server section), there is a warning saying that nextcloud's end to end encryption is still in an "alpha state" (hover over the Experimental E2EE flag). However, in a recent announcement by nextcloud, they said that end to end encryption is now production ready.
https://nextcloud.com/blog/production-ready-end-to-end-encryption-and-new-user-interface-arrive-with-nextcloud-desktop-client-3-0/
Why I am making the suggestion
I am making this suggestion as an update to status of Nextcloud on the privacytools.io website.
My connection with the software
I am just a user, not affiliated with the company in any way.
By their words, yes. But, if you will look at they opened issues and at the forum, you will find a lot of bugs and unsolved issues.
Well, technically, we need to mark it as "production ready". But everyone must think twice before using it (Of course, if you do not want to spend the rest of your time recovering your files and fixing bugs.). E2EE is still a nightmare... Maybe not in alpga stage, but still an unfinished work.
I will take a look at the E2EE module soon; see what known issues are open/not-resolved, and look at their implementations on clients.
Definitely doesn't feel production ready.
That's not the point. They announced that it is production ready, so the tag that says that e2ee is still in "alpha" should be changed. Since they announced it was production ready, it should not be called "alpha" software.
Thank you for taking the time to review the issues and code.