14 Commits (68747142d65d06f31e34b401fc0e395d98963ae0)

Author	SHA1	Message	Date
Moxie Marlinspike	68747142d6	Add correct contextual menu options on 'Send' button. ... [Send TextSecure message | Send unencrypted SMS | Send encrypted SMS] // FREEBIE	11 years ago
Moxie Marlinspike	9614dc9055	Refactor group database model and flow. ... 1) Use existing DB types instead of adding new columns. 2) Store group attributes in message body, like everything else.	11 years ago
Moxie Marlinspike	b9f4fba98a	Handle identity key mismatch on outgoing group messages. ... Additionally, make the group creation process asynchronous.	11 years ago
Moxie Marlinspike	49daa45dca	wip	11 years ago
Moxie Marlinspike	dadabdfaa8	Make UI responsive to UniversalTransport upgrades.	11 years ago
Moxie Marlinspike	b8f663b69c	Move common crypto classes into TextSecureLibrary. ... 1) Move all the crypto classes from securesms.crypto. 2) Move all the crypto storage from securesms.database.keys 3) Replace the old imported BC code with spongycastle.	11 years ago
Ruben Pollan	04eafd5fab	Allow to resend a failed message ... Add an option to the context menu of the message to resend it if it has failed.	12 years ago
Moxie Marlinspike	c86e414c5f	Include (somehow missed) support for send/receive encrypted MMS.	12 years ago
Moxie Marlinspike	dd0aecc811	First cut at group messaging refactor.	12 years ago
Moxie Marlinspike	83e260436b	Major storage layer refactoring to set the stage for clean GCM. ... 1) We now try to hand out cursors at a minimum. There has always been a fairly clean insertion layer that handles encrypting message bodies, but the process of decrypting message bodies has always been less than ideal. Here we introduce a "Reader" interface that will decrypt message bodies when appropriate and return objects that encapsulate record state. No more MessageDisplayHelper. The MmsSmsDatabase interface is also more sane. 2) We finally rid ourselves of the technical debt associated with TextSecure's initial usage of the default SMS DB. In that world, we weren't able to use anything other than the default "Inbox, Outbox, Sent" types to describe a message, and had to overload the message content itself with a set of local "prefixes" to describe what it was (encrypted, asymetric encrypted, remote encrypted, a key exchange, procssed key exchange), and so on. This includes a major schema update that transforms the "type" field into a bitmask that describes everything that used to be encoded in a prefix, and prefixes have been completely eliminated from the system. No more Prefix.java 3) Refactoring of the MultipartMessageHandler code. It's less of a mess, and hopefully more clear as to what's going on. The next step is to remove what we can from SmsTransportDetails and genericize that interface for a GCM equivalent.	12 years ago
Moxie Marlinspike	5df88cc0a7	Scrub recipients for MMS messages so they'll be valid PLMN.	12 years ago
Moxie Marlinspike	187ec95817	Add collating support for group SMS/MMS messages. ... 1) When sending an SMS or MMS to multiple recipients, only show one ConversationItem, but provide statistics on the number of recipients delivered to. 2) Still break up the messages for secure and insecure messages.	13 years ago
Moxie Marlinspike	c13a3a8181	Fix "Group Threads" so that messages are encrypted when possible. ... 1) Change the MessageSender logic so that individual SMS messages are encrypted whenever there is a secure session, unless the UI explicitly specifies otherwise. 2) Change the MMS logic so that messages to a recipient with a secure session are all sent individually, instead of including those recipients into the batch plaintext message.	13 years ago
Moxie Marlinspike	bbea3fe1b1	Initial Project Import	14 years ago