Encryptr isn't being actively developed #203
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#203
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?
https://github.com/SpiderOak/Encryptr/issues/286
I don't think this should be featured on the site.
The last commit was in July 19, 2016 (https://github.com/SpiderOak/Encryptr/commits/master) and that was to update the README.md file. I checked the App Store (iOS) and last release was in Dec 19, 2015; Play Store in December 7, 2015. Looks like development for the password manager is secretly dropped. Probably a good note to remove software that isn't actively developed and not been given the silent treatment.
Same with some other Spider Oak tools.
I think there should be a threshold for activity, but also for how many developers contribute.
No one should be recommending a tool that only has 1 contributor, either.
As a note that shares some relevance to this issue, I don't think inactivity of development in itself is a reason to drop a project unless there are outstanding security issues. If a tool is secure as is and it works as expected, then I don't see an issue with discontinued development as long as there is a commitment to fixing upcoming security issues (which isn't the case in this example so the removal is okay imo).
Depends on the kind of tool.