Open denadai2 opened 9 years ago
Not really. However, if you have specific questions I'm happy to try and help.
My idea is to transform Mitro in a serverless extension, thanks to Dropbox et simili. I would have liked to be sure about all the communications :))
(I think this would make the nitro project self sustainable)
Sent from my iPhone
On 25 Nov 2014, at 15:03, Evan Jones notifications@github.com wrote:
Not really. However, if you have specific questions I'm happy to try and help.
— Reply to this email directly or view it on GitHub.
@denadai2 Do you have place to talk about the dev status of this? I'd be curious about your implementation of it, especially regarding syncing.
@alexggordon I planned to use the Datastore API of Dropbox, but right now they are discontinued :(
Google drive has something similar, with a limit of 5MB. Try to check them :)
Could also be worth looking at an OwnCloud back-end, which would allow users to have everything run on their own servers.
On Thu, Jul 16, 2015 at 9:56 AM, Marco De Nadai notifications@github.com wrote:
@alexggordon https://github.com/alexggordon I planned to use the Datastore API of Dropbox, but right now they are discontinued :(
Google drive has something similar, with a limit of 5MB. Try to check them :)
— Reply to this email directly or view it on GitHub https://github.com/mitro-co/mitro/issues/90#issuecomment-121964346.
@denadai2 has anyone thought about simply setting up a paid hosting solution? Something that charges people a $1 a month to use it? There are a lot of complications that arise from trying to transition mitro to a "synced" solution, and it seems like the barrier to simply setting up a paid solution would be less.
I think many thought so, including the mitro's team
Inviato da iPhone
Il giorno 17 Jul 2015, alle ore 19:34, Alex Gordon notifications@github.com ha scritto:
@denadai2 has anyone thought about simply setting up a paid hosting solution? Something that charges people a $1 a month to use it? There are a lot of complications that arise from trying to transition mitro to a "synced" solution, and it seems like the barrier to simply setting up a paid solution would be less.
— Reply to this email directly or view it on GitHub.
Hello, do you have time to document the server API? I would like to change something, but a minimal documentation is needed (in order to avoid disasters) :)