Hi, first of all "Thank you" for this cool little tool. I use it on a regular basis to automatically convert my notes and store them in my Obsidian vault.
However, I have frequently the use case that I want to review scientific papers on the Remarkable. Currently, I copy them using the web interface. However, there is already some specific tooling for that (see here) that is using the rmapi library and I am unsure whether rmapi works for the latest 3.5.2 release of the Remarkable.
Hence, I thought that a good alternative would be to use your tool and to extend the API by an upload function. I could then pre-process the PDFs to reduce the file size and upload them to the RM2 using the USB interface or even create an adapted version of paper2remarkable that is using your API for the upload.
Have you ever checked whether the upload would be easy to implement? I checked the network trace in Google Chrome and it looked as if it would be manageable but I am not really familiar with REST APIs and the treatment of the PDF content as the payload. I also do not know whether I could break something on the device by using the REST API in an erroneous way.
Hi, first of all "Thank you" for this cool little tool. I use it on a regular basis to automatically convert my notes and store them in my Obsidian vault.
However, I have frequently the use case that I want to review scientific papers on the Remarkable. Currently, I copy them using the web interface. However, there is already some specific tooling for that (see here) that is using the rmapi library and I am unsure whether rmapi works for the latest 3.5.2 release of the Remarkable.
Hence, I thought that a good alternative would be to use your tool and to extend the API by an upload function. I could then pre-process the PDFs to reduce the file size and upload them to the RM2 using the USB interface or even create an adapted version of paper2remarkable that is using your API for the upload.
Have you ever checked whether the upload would be easy to implement? I checked the network trace in Google Chrome and it looked as if it would be manageable but I am not really familiar with REST APIs and the treatment of the PDF content as the payload. I also do not know whether I could break something on the device by using the REST API in an erroneous way.