Closed liliakai closed 9 years ago
And probably have a sync method...users will not be happy if they have to reinstall ts-bro just to update their contact list.
That would require users to install flock... On Jan 18, 2015 12:03 PM, "Frederic Jacobs" notifications@github.com wrote:
If we want to have a consistent branding here, shouldn't this be part of Flock?
— Reply to this email directly or view it on GitHub https://github.com/WhisperSystems/TextSecure-Browser/issues/135#issuecomment-70428457 .
Or we could just use the flock servers in the background, assuming (a) they werent so expensive to run (ie the server were rewritten) and (b) the server were rewritten so we werent using horrible protocols to talk to it (ie the server were rewritten).
Replicating a full blown contact manager appears to be unprecedented in a chrome extensions.
It seems like the minimal thing for sane usability is some mechanism for sharing between devices.
My sense is this more nice to have but the shared secret between devices could be used to sync over the wire.
In my opinion, requiring the users to install flock should not even be an option. Flock is not free and that would mean forcing the users to pay, which would probably prevent many people from using the app at all (consider that most people are too lazy to even install just one app, let alone having to install one paid app to use a browser extension..) If the problem is really the lack of money to run the servers as @TheBlueMatt said, then maybe you can start adding some "Donate" buttons here and there in your apps, and if necessary offer some very non-essential features in a freemium way (like changing themes, or the possibility to edit photos within the app before sending them, etc...)
@volcano99: one semi-precedent strikes me -- Telegram, which somehow accesses your contacts (on the phone, perhaps) and cross-references them with registered Telegram users. This works in the browser extension as well as on every dedicated platform.
We need to import contacts from your primary device during multi-device provisioning.