Oh ok you mean the application have to be used by both parties, (I understood the protocol). I tried #conversations 24/24h on my #nexus4 but it's killing my battery...
#XMPP should aso be used but both parties and keeping an #XMPP connexion 24/24h is not really battery friendly (I tried). #TextSecure is using push messages which is battery friendly
Hmm yeah you have a point but I was thinking to users moving to an other instance → they change their old account to usernameold and it's updated in other instance DB so @username ping the new account
For example : my dad have an phone + sim provided by the company he works for → He have illimited calls and internet but only illimited texts/sms to his coworkers. With #TextSecure he can send us/family secured texts without paying.
It's great of course but it doesn't protect the metadata (who talks to who) like #TextSecure does and it uses a lot of sms (so you have to have illimited sms), I use #TextSecure a lot and it only use 5-7Mo/month.
vinilox favorited something by andstatus: @vinilox@status.vinilox.eu This is exactly why _I_ use AndStatus: I read and post on a go, in places with intermittent connections...
Quand fair-use #3G dépassé, @vinilox pouvoir uniquement utiliser @andstatus :) / Good job in optimization @andstatus I can still use the app after exceeding my #3G fair-use (15ko/s) :)