Over the past 3 years the pace of development in APS has steadily fallen off as maintainers including myself have moved on to other things. I no longer have time and motivation to dedicate to this project, and in the absence of significant external contributions there is no-one else I can offer the project’s stewardship to.
To that effect, I will be archiving the repository on Monday, October 14th 2024 at 7AM GST. In the situation that a serious and viable fork emerges, I will help them as much as I can with the transition. The criteria for what counts as “serious and viable” is entirely vibes-driven for now, and may become more specific in the future. In case I determine that a fork does not live up to my made up standard, they will have to come up with a slightly more creative name than “Android Password Store” and watch low 4 figures of cash wither away in OpenCollective’s bank account.
Yeah, with all the stuff going on with password managers, I wonder if there’s a truly future-proof setup that can be self-hosted and will never have these issues.
I was a Keepass user many years ago, but I’m not confident that a Keepass-like system would work well with some very computer-illiterate family members. Bitwarden is hard enough to teach them, and it’s one of the easy ones!
There is no such solution but you could just not update your mobile app and keep using vault warden. Nothing will change for you.
Well, I’d prefer that the apps that are a gateway to my most important pieces of data (passwords) be updated to plug vulnerabilities and exploits. If it were any other app/service, then I can live without updates. But not something related to passwords.
Someone will fork it, once Bitwarden close the source you won’t know if they are even patching vulnerabilities.
Yup. I’m either hoping for a more sustainable alternative, or a fork with active updates.
For now, I’m holding my position, but preparing for an exit from Bitwarden.