Compare commits

..

No commits in common. "8a03ea1798f0ee6de8313a69ff5305547d6400f4" and "5cfbf509ee56aa697ef71015f701f276ac889116" have entirely different histories.

View file

@ -270,7 +270,7 @@ functionality rather than trying to send actual files. One quirk of the official
that when it receives plain text, it does not offer you the ability to download it, or approve the
download; you can copy it to your clipboard or close the request, and that's it. So when the
`prepare_upload()` future was canceled, nothing seemed out of the ordinary on the remote side. Had
I tried sending a file, an error would have shown on the remote side when I tried to accept it.
I tried sending a file, an error have shown on the remote side when I tried to accept it.
Despite my blissful ignorance, I knew that this design was not correct, and a few days later I'd
[updated the `prepare_upload()`
@ -318,7 +318,7 @@ to,
and that solved the issue where jocalsend would receive remote datagrams from its own IP.
### Rust too fancy
### Rust so fancy
I'd made a [few more releases](https://crates.io/crates/jocalsend/versions) with the fixes outlined
above, but then I got some reports of people running into build issues when trying to install with a