Signal, and likely other clients as well, don't actually send attachments inline as messages, they upload the (encrypted) file to another server and send the URI in the message. This could make a significant difference in behavior, since it makes large messages non-blocking.
P2P messages should still be inline, until we start using cwtch-style servers, at which point we'll need to think more carefully about what to do.
Signal, and likely other clients as well, don't actually send attachments inline as messages, they upload the (encrypted) file to another server and send the URI in the message. This could make a significant difference in behavior, since it makes large messages non-blocking.
P2P messages should still be inline, until we start using cwtch-style servers, at which point we'll need to think more carefully about what to do.
Signal, and likely other clients as well, don't actually send attachments inline as messages, they upload the (encrypted) file to another server and send the URI in the message. This could make a significant difference in behavior, since it makes large messages non-blocking.
P2P messages should still be inline, until we start using cwtch-style servers, at which point we'll need to think more carefully about what to do.
Fixed via
04bc61c9b7