2018-02-02 03:29:09 +01:00
|
|
|
/*
|
2012-10-29 00:04:24 +01:00
|
|
|
* Copyright (C) 2012 Moxie Marlinpsike
|
|
|
|
*
|
|
|
|
* This program is free software: you can redistribute it and/or modify
|
|
|
|
* it under the terms of the GNU General Public License as published by
|
|
|
|
* the Free Software Foundation, either version 3 of the License, or
|
|
|
|
* (at your option) any later version.
|
|
|
|
*
|
|
|
|
* This program is distributed in the hope that it will be useful,
|
|
|
|
* but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
|
|
* GNU General Public License for more details.
|
|
|
|
*
|
|
|
|
* You should have received a copy of the GNU General Public License
|
|
|
|
* along with this program. If not, see <http://www.gnu.org/licenses/>.
|
|
|
|
*/
|
|
|
|
package org.thoughtcrime.securesms.database.model;
|
|
|
|
|
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.
2013-04-20 21:22:04 +02:00
|
|
|
import android.content.Context;
|
|
|
|
import android.text.Spannable;
|
|
|
|
import android.text.SpannableString;
|
2014-12-29 23:32:29 +01:00
|
|
|
import android.text.style.RelativeSizeSpan;
|
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.
2013-04-20 21:22:04 +02:00
|
|
|
import android.text.style.StyleSpan;
|
|
|
|
|
2021-05-31 07:53:25 +02:00
|
|
|
import androidx.annotation.NonNull;
|
2021-04-14 08:37:04 +02:00
|
|
|
|
2021-04-26 03:23:09 +02:00
|
|
|
import org.session.libsession.messaging.sending_receiving.data_extraction.DataExtractionNotificationInfoMessage;
|
2021-05-12 00:40:10 +02:00
|
|
|
import org.session.libsession.messaging.utilities.UpdateMessageBuilder;
|
|
|
|
import org.session.libsession.messaging.utilities.UpdateMessageData;
|
2021-05-18 08:03:47 +02:00
|
|
|
import org.session.libsession.utilities.IdentityKeyMismatch;
|
|
|
|
import org.session.libsession.utilities.NetworkFailure;
|
|
|
|
import org.session.libsession.utilities.recipients.Recipient;
|
2012-10-29 00:04:24 +01:00
|
|
|
|
2015-01-15 22:35:35 +01:00
|
|
|
import java.util.List;
|
|
|
|
|
2012-10-29 00:04:24 +01:00
|
|
|
/**
|
|
|
|
* The base class for message record models that are displayed in
|
|
|
|
* conversations, as opposed to models that are displayed in a thread list.
|
|
|
|
* Encapsulates the shared data between both SMS and MMS messages.
|
|
|
|
*
|
|
|
|
* @author Moxie Marlinspike
|
|
|
|
*
|
|
|
|
*/
|
|
|
|
public abstract class MessageRecord extends DisplayRecord {
|
2015-01-15 22:35:35 +01:00
|
|
|
private final Recipient individualRecipient;
|
|
|
|
private final List<IdentityKeyMismatch> mismatches;
|
|
|
|
private final List<NetworkFailure> networkFailures;
|
2016-08-16 05:23:56 +02:00
|
|
|
private final long expiresIn;
|
|
|
|
private final long expireStarted;
|
2018-05-22 11:13:10 +02:00
|
|
|
private final boolean unidentified;
|
2021-05-31 08:20:46 +02:00
|
|
|
public final long id;
|
2021-08-10 08:00:06 +02:00
|
|
|
public final boolean deleted;
|
2021-05-31 08:20:46 +02:00
|
|
|
|
|
|
|
public abstract boolean isMms();
|
|
|
|
public abstract boolean isMmsNotification();
|
2014-02-03 04:38:06 +01:00
|
|
|
|
2019-03-13 22:28:16 +01:00
|
|
|
MessageRecord(long id, String body, Recipient conversationRecipient,
|
2021-05-31 08:20:46 +02:00
|
|
|
Recipient individualRecipient,
|
|
|
|
long dateSent, long dateReceived, long threadId,
|
|
|
|
int deliveryStatus, int deliveryReceiptCount, long type,
|
|
|
|
List<IdentityKeyMismatch> mismatches,
|
|
|
|
List<NetworkFailure> networkFailures,
|
|
|
|
long expiresIn, long expireStarted,
|
|
|
|
int readReceiptCount, boolean unidentified)
|
2012-10-29 00:04:24 +01:00
|
|
|
{
|
2019-03-13 22:28:16 +01:00
|
|
|
super(body, conversationRecipient, dateSent, dateReceived,
|
2021-05-31 08:20:46 +02:00
|
|
|
threadId, deliveryStatus, deliveryReceiptCount, type, readReceiptCount);
|
2012-10-29 00:04:24 +01:00
|
|
|
this.id = id;
|
|
|
|
this.individualRecipient = individualRecipient;
|
2015-01-15 22:35:35 +01:00
|
|
|
this.mismatches = mismatches;
|
|
|
|
this.networkFailures = networkFailures;
|
2016-08-16 05:23:56 +02:00
|
|
|
this.expiresIn = expiresIn;
|
|
|
|
this.expireStarted = expireStarted;
|
2018-05-22 11:13:10 +02:00
|
|
|
this.unidentified = unidentified;
|
2021-08-10 08:00:06 +02:00
|
|
|
this.deleted = false;
|
2012-10-29 00:04:24 +01:00
|
|
|
}
|
|
|
|
|
2021-05-31 08:20:46 +02:00
|
|
|
public long getId() {
|
|
|
|
return id;
|
|
|
|
}
|
|
|
|
public long getTimestamp() {
|
|
|
|
return getDateSent();
|
|
|
|
}
|
|
|
|
public Recipient getIndividualRecipient() {
|
|
|
|
return individualRecipient;
|
|
|
|
}
|
|
|
|
public long getType() {
|
|
|
|
return type;
|
|
|
|
}
|
|
|
|
public List<NetworkFailure> getNetworkFailures() {
|
|
|
|
return networkFailures;
|
|
|
|
}
|
|
|
|
public long getExpiresIn() {
|
|
|
|
return expiresIn;
|
|
|
|
}
|
|
|
|
public long getExpireStarted() { return expireStarted; }
|
2021-05-31 08:26:46 +02:00
|
|
|
|
2021-05-31 08:20:46 +02:00
|
|
|
public boolean isMediaPending() {
|
|
|
|
return false;
|
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.
2013-04-20 21:22:04 +02:00
|
|
|
}
|
|
|
|
|
2021-05-31 08:20:46 +02:00
|
|
|
public boolean isUpdate() {
|
|
|
|
return isExpirationTimerUpdate() || isCallLog() || isDataExtractionNotification();
|
2014-04-11 00:20:43 +02:00
|
|
|
}
|
|
|
|
|
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.
2013-04-20 21:22:04 +02:00
|
|
|
@Override
|
2019-03-13 22:28:16 +01:00
|
|
|
public SpannableString getDisplayBody(@NonNull Context context) {
|
2021-08-10 08:00:06 +02:00
|
|
|
if (this.deleted) {
|
|
|
|
return new SpannableString("This message has been deleted."); // TODO: localize
|
|
|
|
} else if (isGroupUpdateMessage()) {
|
2021-05-12 00:40:10 +02:00
|
|
|
UpdateMessageData updateMessageData = UpdateMessageData.Companion.fromJSON(getBody());
|
|
|
|
return new SpannableString(UpdateMessageBuilder.INSTANCE.buildGroupUpdateMessage(context, updateMessageData, getIndividualRecipient().getAddress().serialize(), isOutgoing()));
|
2021-04-15 06:41:29 +02:00
|
|
|
} else if (isExpirationTimerUpdate()) {
|
|
|
|
int seconds = (int) (getExpiresIn() / 1000);
|
2021-05-12 00:40:10 +02:00
|
|
|
return new SpannableString(UpdateMessageBuilder.INSTANCE.buildExpirationTimerMessage(context, seconds, getIndividualRecipient().getAddress().serialize(), isOutgoing()));
|
2021-05-31 07:53:25 +02:00
|
|
|
} else if (isDataExtractionNotification()) {
|
|
|
|
if (isScreenshotNotification()) return new SpannableString((UpdateMessageBuilder.INSTANCE.buildDataExtractionMessage(context, DataExtractionNotificationInfoMessage.Kind.SCREENSHOT, getIndividualRecipient().getAddress().serialize())));
|
|
|
|
else if (isMediaSavedNotification()) return new SpannableString((UpdateMessageBuilder.INSTANCE.buildDataExtractionMessage(context, DataExtractionNotificationInfoMessage.Kind.MEDIA_SAVED, getIndividualRecipient().getAddress().serialize())));
|
2014-02-20 06:06:54 +01:00
|
|
|
}
|
|
|
|
|
2018-02-02 03:29:09 +01:00
|
|
|
return new SpannableString(getBody());
|
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.
2013-04-20 21:22:04 +02:00
|
|
|
}
|
2012-10-29 00:04:24 +01:00
|
|
|
|
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.
2013-04-20 21:22:04 +02:00
|
|
|
protected SpannableString emphasisAdded(String sequence) {
|
|
|
|
SpannableString spannable = new SpannableString(sequence);
|
2014-12-29 23:32:29 +01:00
|
|
|
spannable.setSpan(new RelativeSizeSpan(0.9f), 0, sequence.length(), Spannable.SPAN_EXCLUSIVE_EXCLUSIVE);
|
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.
2013-04-20 21:22:04 +02:00
|
|
|
spannable.setSpan(new StyleSpan(android.graphics.Typeface.ITALIC), 0, sequence.length(), Spannable.SPAN_EXCLUSIVE_EXCLUSIVE);
|
|
|
|
|
|
|
|
return spannable;
|
|
|
|
}
|
2014-12-14 03:10:59 +01:00
|
|
|
|
|
|
|
public boolean equals(Object other) {
|
2021-05-31 08:20:46 +02:00
|
|
|
return other instanceof MessageRecord
|
|
|
|
&& ((MessageRecord) other).getId() == getId()
|
|
|
|
&& ((MessageRecord) other).isMms() == isMms();
|
2014-12-14 03:10:59 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
public int hashCode() {
|
|
|
|
return (int)getId();
|
|
|
|
}
|
2012-10-29 00:04:24 +01:00
|
|
|
}
|