-
Notifications
You must be signed in to change notification settings - Fork 242
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Potential for Mitro Revival #133
Comments
Hey, we're keeping Mitro alive although under a different name to avoid confusion [1], [2]. We've already fixed quite a few bugs. If you don't want to run your own server you can sign up at https://passopolis.com/ and use our servers. |
Ah, I wasn't aware of the passopolis project. Cool stuff. 🍕 |
I wasn't either... trialling now :) On 16 September 2015 at 13:40, Dave Hulihan - [email protected] <
|
oh, very cool! is this server up and running? have you guys set up a RO On Tue, Sep 15, 2015 at 6:07 PM, teh [email protected] wrote:
|
Both secondary and primary are pointing to the same server. We run an hourly backup and we're using an elastic IP so restoring a server takes <10 minutes. We will move to wall-e backups once we're sure we trust its encryption facilities. Edit: And yea, the servers are running :) - we could not live without our passwords. |
@teh This is great! I was looking for an alternative to lastpass and stumbled upon this. |
I'm a big fan of Mitro, and I'm greatly saddened to see it go. However, there's some potential for a great influx of users RIGHT NOW. LastPass users are going to be looking for somewhere to go, as a critical security issue has been discovered by researchers. This exploit will be revealed in November. As you can imagine, the speculation is already causing users to jump ship.
http://www.ghacks.net/2015/09/15/researchers-to-reveal-critical-lastpass-issues-in-november-2015/
I know funding was an issue, but with a large influx of users and the right business plan, maybe there's some potential here? What do you think?
The text was updated successfully, but these errors were encountered: