Axel Kittenberger

> As these are all individual third party repos/scripts/... they will never be "deprecated" in the programming sense. Wouldn't it be better to tag a repo as "abandoned" instead? But...

As I found out, as the Readme says "some" devices started to stop working is when remarkable rolled out a new cloud API.. and this aint it, and by now...

There has been some progress reverse engineering the new API: https://github.com/juruen/rmapi#warning-experimental-support-for-the-new-sync-protocol or https://github.com/subutux/rmapy/issues/25 Put it isn't fully conclusive how the state is (a shame remarkable keeps it's API a secret...

> Should that use `Accept-Encoding` and `Content-Encoding`, or `TE` and `Transfer-Encoding`? I imagine the difference would matter for range requests. In my opinion it's obviously Accept-Encoding, because the server is...

Thanks, yes to be honest I gave resumeabilty no thought so far. And yes it complicated things. The basic idea is to mirror the HTTP download as much as possible,...

The last point is the most important to me, Upload-Token, this elegantly eliminates all discussions about non bijective compression. One client is deterministic, and as long it uses the same...

> Instead of writing `Accept-Encoding: "gzip, identity"` at that level, let's write `encodings: ["gzip", "identity"]` there. All the other keys are downcase and that would make more sense, I think....

Just a note since I happened to read deeper into this once, AFAIK xxhash (or murmur hash) collisions are not feasible in the sense of more likely, but contrary to...

Bummer, I'm using ldapi all over the place and Ruby seems to be the only ecosystem not supporting it.

Same I guess the API has been broken and this project isn't actively maintained :(