Flutterby™! : TextSecure and RedPhone on Android are

Next unread comment / Catchup all unread comments User Account Info | Logout | XML/Pilot/etc versions | Long version (with comments) | Weblog archives | Site Map | | Browse Topics

TextSecure and RedPhone on Android are

2015-11-03 02:05:07.015087+00 by Dan Lyke 4 comments

TextSecure and RedPhone on Android are becoming Signal, uniting w/iOS. You are using encrypted messaging, right? https://whispersystems.org/blog/just-signal/

[ related topics: Weblogs Cryptography ]

comments in ascending chronological order (reverse):

#Comment Re: TextSecure and RedPhone on Android are made: 2015-11-03 19:57:57.28728+00 by: Mars Saxman

Wish I were! I used TextSecure for a while, but too many messages just never got delivered, and it had a lot of trouble with group messages.

I also refuse to allow personal data and google account credentials to coexist on a phone, which makes life difficult when developers pull some "upgrade now or else" bullshit.

#Comment Re: TextSecure and RedPhone on Android are made: 2015-11-03 20:09:56.402686+00 by: Dan Lyke

Huh. TextSecure went through a short period where I had two instances of delayed messages, but I haven't had any problems aside from those moments. And I was told about those delays as the sender.

#Comment Re: TextSecure and RedPhone on Android are made: 2015-11-04 03:08:57.598606+00 by: meuon

Heck, I can't even get "IT professionals" to use encrypted emails. Let alone encrypted texts.

#Comment Re: TextSecure and RedPhone on Android are made: 2015-11-04 11:47:18.73143+00 by: DaveP

I have Signal. I've received one text from a guy who's also concerned about security who wanted to make sure it worked. "Is this thing on?" "Yeah. Cool that someone else uses this!" "Yeah. Well, talk to you later."

That's the extent of my Signal use since it became available. Sigh.

Add your own comment:

(If anyone ever actually uses Webmention/indie-action to post here, please email me)




Format with:

(You should probably use "Text" mode: URLs will be mostly recognized and linked, _underscore quoted_ text is looked up in a glossary, _underscore quoted_ (http://xyz.pdq) becomes a link, without the link in the parenthesis it becomes a <cite> tag. All <cite>ed text will point to the Flutterby knowledge base. Two enters (ie: a blank line) gets you a new paragraph, special treatment for paragraphs that are manually indented or start with "#" (as in "#include" or "#!/usr/bin/perl"), "/* " or ">" (as in a quoted message) or look like lists, or within a paragraph you can use a number of HTML tags:

p, img, br, hr, a, sub, sup, tt, i, b, h1, h2, h3, h4, h5, h6, cite, em, strong, code, samp, kbd, pre, blockquote, address, ol, dl, ul, dt, dd, li, dir, menu, table, tr, td, th

Comment policy

We will not edit your comments. However, we may delete your comments, or cause them to be hidden behind another link, if we feel they detract from the conversation. Commercial plugs are fine, if they are relevant to the conversation, and if you don't try to pretend to be a consumer. Annoying endorsements will be deleted if you're lucky, if you're not a whole bunch of people smarter and more articulate than you will ridicule you, and we will leave such ridicule in place.

Flutterby™ is a trademark claimed by

Dan Lyke
for the web publications at www.flutterby.com and www.flutterby.net.