I assume at $200/month it somehow becomes worth it to keep going as someone's side project? I can't imagine twitter would keep it around for that little revenue (unless the acquihire from last year was simply just a hire, without buying the legal mitro entity)
Mitro is Shutting Down on August 31st
21–30 of 41 posts
Re: Mitro is Shutting Down on August 31st
#22I only had a brief look at the source code (it's over at Github) but it seems one could easily run their own server?
yes. you can do this failry easy. There are ansible playbooks and some readmes. There is some mailservice baked in, which you might have to change.
The only 'harder' part is (the last time I tried): You have to build the browser extensions you want to use, and override the path to the mitro server to point to your server. The config file is all centralized. So you change it once and can build all extensions at once. I did not find an options to customize the mitro server via the extension itself. (this is probably a good thing).
To get your customized extensions to your users, you might have to create an extra download site or fix the links in the mitro webpage.
Re: Mitro is Shutting Down on August 31st
#23Earlier quoted context omitted.
Honestly, you'd pay $4 to $8 per month per user for a password manager?
At SeatGeek, we use Lastpass. I don't personally know what it costs - yes, I'm a lazy operations person - but it seems like it might be $24 per person at our size[1]. I personally use 1Password and if it had group password sharing, I would be lobbying to switch every day of the fucking week. The lastpass interface is confusing, slow, and ugly (I've beens spoiled by the spit and polish we've built). $8 per person comp…
I think it's $24/user/year actually, but we'd be happy to pay more, because Mitro offers a superior solution for us. I hate the Lastpass UI and the sharing options aren't nearly as refined. 1Password doesn't work on Linux, and requires installing a local app as far as I remember.
Re: Mitro is Shutting Down on August 31st
#24I assume at $200/month it somehow becomes worth it to keep going as someone's side project? I can't imagine twitter would keep it around for that little revenue (unless the acquihire from last year was simply just a hire, without buying the legal mitro entity)
it seems to be the case. According to [0] Twitter just hired the devs without the legal entity behind Mitro, and seems like with no intention of supporting the project going forward.
[0]https://groups.google.com/d/msg/mitro-dev/cgFhvuPyUiE/o-sFkE... (Legally speaking: Mitro is run by Lectorius Inc, which has no legal relationship to Twitter Inc. It is a wholly owned independent company.)
Re: Mitro is Shutting Down on August 31st
#25I only had a brief look at the source code (it's over at Github) but it seems one could easily run their own server?
yes. you can do this failry easy. There are ansible playbooks and some readmes. There is some mailservice baked in, which you might have to change. The only 'harder' part is (the last time I tried): You have to build the browser extensions you want to use, and override the path to the mitro server to point to your server. The config file is all centralized. So you change it once and can build all extensions at once.…
that makes me wonder if it would not be an interesting idea to have a plugin that points to a known proxy and you register your host with it. then the operations cost is low, a single plugin can be released, and you control the server and data. just a random thought (typing on mobile with no spelling check, please excuse typos).
Re: Mitro is Shutting Down on August 31st
#26I only had a brief look at the source code (it's over at Github) but it seems one could easily run their own server?
yes. you can do this failry easy. There are ansible playbooks and some readmes. There is some mailservice baked in, which you might have to change. The only 'harder' part is (the last time I tried): You have to build the browser extensions you want to use, and override the path to the mitro server to point to your server. The config file is all centralized. So you change it once and can build all extensions at once.…
You can actually change the server in a hidden preferences page. Go to /html/preferences.html in the extension.
Re: Mitro is Shutting Down on August 31st
#27I am interested in taking over. I have a business idea for it, maybe it might just save the project.
Can you provide a bit more info? I'd be interested in maintaining the project as it is right now in my spare time...
Re: Mitro is Shutting Down on August 31st
#28$200/month for the whole technical infrastructure?
Yeah, our largest costs are:
- a primary server running on AWS
- a read-only replica running on google compute engine.
Other smaller costs include networking, DNS, and various tax/administrative/regulatory fees
Re: Mitro is Shutting Down on August 31st
#29Earlier quoted context omitted.
yes. you can do this failry easy. There are ansible playbooks and some readmes. There is some mailservice baked in, which you might have to change. The only 'harder' part is (the last time I tried): You have to build the browser extensions you want to use, and override the path to the mitro server to point to your server. The config file is all centralized. So you change it once and can build all extensions at once.…
that makes me wonder if it would not be an interesting idea to have a plugin that points to a known proxy and you register your host with it. then the operations cost is low, a single plugin can be released, and you control the server and data. just a random thought (typing on mobile with no spelling check, please excuse typos).
A password manager really needs to be a high-availability service -- it should work even (especially) when AWS is down. Since our service (intentionally) does not cache secret data on the client, running a proxy is not substantially easier than running our service. Plus we'd have to write this proxy :)
Re: Mitro is Shutting Down on August 31st
#30This was a fantastic program and it saddens me greatly to see it go. I hope that someone will pick it up again, or perhaps find a way for the rest of us to run our own servers, since switching to another password manager that doesn't do as good of a job (at least not for free) is going to be quite the inconvenience.
The code is open sourced as GPL3, you should be able to run your own server pretty easily. Please let us know if you have issues.