I'm reworking the bookmarklet entirely. CSP is causing issues with just allowing the bookmarklet to run. I'm working on a new solution that bypasses this by grabbing the image and uploading it from the user's browser instead of pulling an image from the server.

Any news on that approach?
If it's possible already server-side, I could help bookmarklet-side.

No progress on this feature currently. I'm working on the new UI built by vue.js with Bluma(like bootstrap).
Once that work done, we may have time to add this feature ( to both bookmarklet or browser-extension are okay).
I have tried a image-resource manager application named eagle, you could pull any image on the page to a specified eagle area to upload it to your eagle manager.
The UX of eagle chrome extension works like a charm and make me feel excellent, you chould have a try if you have time : )

I like Vue.JS a lot too (so maybe I can help on the client-side of Pinry in the future, even if I don't know any Python), but I'd like to keep the bookmarklet as lean as possible, and using only VanillaJS as far as possible. But that doesn't make it easy to upload a local URL… or maybe yes, the image is probably cached (and thus, avoid origial website Refer checks) even when called from a different tab (the bookmarklet opens a new one).

@lapo-luchini Keep bookmarket alone make sense!

Basically the image we find on a website should be uploaded via the bookmarklet directly to pinry and not pulled via the pinry server, it would solve a lot of issues...

Now the API level works well with image upload.
@lapo-luchini Files below is the way how upload-then-create-pin work:
https://github.com/pinry/pinry/blob/master/pinry-spa/src/components/pin_edit/FileUpload.vue
https://github.com/pinry/pinry/blob/master/pinry-spa/src/components/pin_edit/PinCreateModal.vue