| 7 Jul 2022 |
 binwiederhier#8517 | So this: | 01:03:30 |
| binwiederhier#8517 | Option 2: Multipart + custom binary enc format without attachment
PUT /mytopic HTTP/1.1
Encryption: yes
<encrypted binary data, ntfy format>
Option 2: Multipart + custom binary enc format with attachment
PUT /mytopic HTTP/1.1
Encryption: yes
Content-Type: multipart/form-data; boundary=--ntfy-boundaryXyASDsdA
----ntfy-boundaryXyASDsdA
Content-Disposition: form-data; name="message"
Content-Length: 1234
<encrypted binary data, ntfy format>
----ntfy-boundaryXyASDsdA
Content-Disposition: form-data; name="attachment"
Content-Length: 42343242
<encrypted binary data, ntfy format>
----ntfy-boundaryXyASDsdA--
| 01:03:32 |
| binwiederhier#8517 | * Option 2: Multipart + custom binary enc format without attachment
PUT /mytopic HTTP/1.1
Encryption: yes
<encrypted binary data, ntfy format>
Option 2: Multipart + custom binary enc format with attachment
PUT /mytopic HTTP/1.1
Encryption: yes
Content-Type: multipart/form-data; boundary=--ntfy-boundaryXyASDsdA
----ntfy-boundaryXyASDsdA
Content-Disposition: form-data; name="message"
Content-Length: 1234
<encrypted binary data, ntfy format>
----ntfy-boundaryXyASDsdA
Content-Disposition: form-data; name="attachment"
Content-Length: 42343242
<encrypted binary data, ntfy format>
----ntfy-boundaryXyASDsdA--
| 01:03:38 |
| binwiederhier#8517 | * Option 2: Multipart + custom binary enc format without attachment
PUT /mytopic HTTP/1.1
Encrypted: yes
<encrypted binary data, ntfy format>
Option 2: Multipart + custom binary enc format with attachment
PUT /mytopic HTTP/1.1
Encrypted: yes
Content-Type: multipart/form-data; boundary=--ntfy-boundaryXyASDsdA
----ntfy-boundaryXyASDsdA
Content-Disposition: form-data; name="message"
Content-Length: 1234
<encrypted binary data, ntfy format>
----ntfy-boundaryXyASDsdA
Content-Disposition: form-data; name="attachment"
Content-Length: 42343242
<encrypted binary data, ntfy format>
----ntfy-boundaryXyASDsdA--
| 01:04:09 |
| binwiederhier#8517 | * Option 2: Multipart + custom binary enc format without attachment
PUT /mytopic HTTP/1.1
Encrypted: yes
<encrypted binary data, ntfy format>
Option 2: Multipart + custom binary enc format with attachment
PUT /mytopic HTTP/1.1
Encrypted: yes
Content-Type: multipart/form-data; boundary=--ntfy-boundaryXyASDsdA
----ntfy-boundaryXyASDsdA
Content-Disposition: form-data; name="message"
Content-Length: 1234
<encrypted binary data, ntfy format>
----ntfy-boundaryXyASDsdA
Content-Disposition: form-data; name="attachment"
Content-Length: 42343242
<encrypted binary data, ntfy format>
----ntfy-boundaryXyASDsdA--
with "encrypted binary data, ntfy format" as:
ntfy2586v1 || tag || iv || ciphertext [aes-256-gcm]
| 01:05:31 |
| binwiederhier#8517 | * Option 2: Multipart + custom binary enc format without attachment
PUT /mytopic HTTP/1.1
Encrypted: yes
<encrypted binary data, ntfy format>
Option 2: Multipart + custom binary enc format with attachment
PUT /mytopic HTTP/1.1
Encrypted: yes
Content-Type: multipart/form-data; boundary=--ntfy-boundaryXyASDsdA
----ntfy-boundaryXyASDsdA
Content-Disposition: form-data; name="message"
Content-Length: 1234
<encrypted binary data, ntfy format>
----ntfy-boundaryXyASDsdA
Content-Disposition: form-data; name="attachment"
Content-Length: 42343242
<encrypted binary data, ntfy format>
----ntfy-boundaryXyASDsdA--
with "encrypted binary data, ntfy format" as:
ntfy2586v1 || tag || iv || ciphertext [aes-256-gcm]
| 01:05:48 |
| binwiederhier#8517 | * Option 2: Multipart + custom binary enc format without attachment
PUT /mytopic HTTP/1.1
Encrypted: yes
<encrypted binary data, ntfy format>
Option 2: Multipart + custom binary enc format with attachment
PUT /mytopic HTTP/1.1
Encrypted: yes
Content-Type: multipart/form-data; boundary=--ntfy-boundaryXyASDsdA
----ntfy-boundaryXyASDsdA
Content-Disposition: form-data; name="message"
Content-Length: 1234
<encrypted binary data, ntfy format>
----ntfy-boundaryXyASDsdA
Content-Disposition: form-data; name="attachment"
Content-Length: 42343242
<encrypted binary data, ntfy format>
----ntfy-boundaryXyASDsdA--
with "encrypted binary data, ntfy format" as:
"ntfy2586v1" || tag || iv || ciphertext [aes-256-gcm]
| 01:07:16 |
| binwiederhier#8517 | (Before you ask: "2586" is my birthday (May 2); I "hide" that in lots of places) | 01:08:23 |
| binwiederhier#8517 | Yes? | 01:11:17 |
| binwiederhier#8517 | No? | 01:11:21 |
| binwiederhier#8517 | Maybe? | 01:11:23 |
| binwiederhier#8517 | I don't know? | 01:11:28 |
| binwiederhier#8517 | Can you repeat the question, ... 🎶 🎼 | 01:11:49 |
| binwiederhier#8517 | * Can you repeat the question? You're not the boss of me ... 🎶 🎼 | 01:12:00 |
| binwiederhier#8517 | In a comment https://github.com/binwiederhier/ntfy/issues/69#issuecomment-1176936377 | 01:23:50 |
 wunter8 | Sorry about the delay | 01:38:23 |
| wunter8 | I think that'll work, yes | 01:38:28 |
| wunter8 | What is the message/payload plaintext going to look like? Because it needs to include HTTP headers and stuff, too, right? | 01:39:32 |
| wunter8 | Just a JSON string? | 01:39:39 |
| binwiederhier#8517 | Yeah I was thinking just the JSON | 01:40:20 |
| binwiederhier#8517 | Actually the multipart thing could even be used without encryption | 01:40:41 |
 karmanyaahm | How about using the same format as webpush. There are already quite a few libraries for it, not sure about cli tools. | 01:40:41 |
| binwiederhier#8517 | Because right now when you send a POST with JSON you cannot also send an attachment | 01:41:25 |
| karmanyaahm | RFC8188 and RFC 8291 | 01:41:30 |
| binwiederhier#8517 | I'll look at this tomorrow thanks! | 01:41:44 |
| binwiederhier#8517 | Great timing | 01:41:52 |
| binwiederhier#8517 | Right after we agreed on something | 01:41:59 |
| karmanyaahm | 😅 you don't have to | 01:42:26 |
| binwiederhier#8517 | ;-) | 01:45:23 |
| wunter8 | I guess it won't actually have HTTP headers, just the parameters that go into the headers. We won't need to rebuild the actual HTTP request on the client | 02:02:05 |
