Skip to content

Added base64 encoded attachment support - #966

Merged
AsamK merged 6 commits into
AsamK:masterfrom
KevinRoebert:json-rpc-file-upload
Jun 4, 2022
Merged

AsamK merged 6 commits into
AsamK:masterfrom
KevinRoebert:json-rpc-file-upload

Conversation

@KevinRoebert

Copy link
Copy Markdown
Contributor

Added support for base64 encoded attachments (see also #679 (comment)).

Tested via:

  • dbus
  • JSON-RPC TCP socket

@AsamK

AsamK commented Jun 3, 2022

Copy link
Copy Markdown
Owner

Thanks, i like the approach with using a data url.
I've just two comments for possible improvements.

@KevinRoebert

Copy link
Copy Markdown
Contributor Author

Where can I find the comments?

@AsamK

AsamK commented Jun 3, 2022

Copy link
Copy Markdown
Owner

You should see them now, i forgot to submit them...

@KevinRoebert

Copy link
Copy Markdown
Contributor Author

@AsamK I've added full support for data URI according to RFC 2397.

@KevinRoebert

Copy link
Copy Markdown
Contributor Author

@AsamK Added feedback. Your data URI should work now.

@AsamK

AsamK commented Jun 4, 2022

Copy link
Copy Markdown
Owner

Thanks!

@AsamK
AsamK merged commit cb5e3c6 into AsamK:master Jun 4, 2022
@orazioedoardo

orazioedoardo commented Jun 4, 2022 •

Copy link
Copy Markdown
Contributor

Which filename is used if none is provided?

@AsamK

AsamK commented Jun 4, 2022

Copy link
Copy Markdown
Owner

none ;)

@orazioedoardo

Copy link
Copy Markdown
Contributor

Can the Signal app deal with received attachments with no name?

@KevinRoebert

Copy link
Copy Markdown
Contributor Author

Yes. It can

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants