2000 char limit?

[BobTB]

Is it not possible to work around this?

[jgchristopher]

I have thought about sending the data in chunks. I will give it a try.

[BobTB]

I already tried it, it does not work from bookmarklet, as it looses focus (which stops the code) and therefore sends just the first chunk, but perhaps the extension could do it.

[lwsys]

extension also couldn't do it....

[jgchristopher]

I think I have a potential solution.

I could encrypt the clipping and post it to a storage service provided by the same service that generates chrome extensions (obsidian clipper.com), which would temporarily store the encrypted clipping and return an id.

I could then call the local obsidian:// URL, passing the id and the key to decrypt.

The plugin can make a GET call to the obsidianclipper.com service with the ID, retrieve the encrypted clipping, decrypt with the provided key, and write out the clipped info as usual.

The obsidianclipper service would delete the encrypted clipping from ETS after returning it.

[lwsys]

I think I have a potential solution.

I could encrypt the clipping and post it to a storage service provided by the same service that generates chrome extensions (obsidian clipper.com), which would temporarily store the encrypted clipping and return an id.

I could then call the local obsidian:// URL, passing the id and the key to decrypt.

The plugin can make a GET call to the obsidianclipper.com service with the ID, retrieve the encrypted clipping, decrypt with the provided key, and write out the clipped info as usual.

The obsidianclipper service would delete the encrypted clipping from ETS after returning it.

Are you meanings if clipping can provide an external service to store data, and if Obsidian can fetch encrypted data from that API? That sounds really cool! It would be even better if you could run the service locally.

[lymeswold]

I think I have a potential solution.

I could encrypt the clipping and post it to a storage service provided by the same service that generates chrome extensions (obsidian clipper.com), which would temporarily store the encrypted clipping and return an id.

I could then call the local obsidian:// URL, passing the id and the key to decrypt.

The plugin can make a GET call to the obsidianclipper.com service with the ID, retrieve the encrypted clipping, decrypt with the provided key, and write out the clipped info as usual.

The obsidianclipper service would delete the encrypted clipping from ETS after returning it.

Would this work on Obsidian Mobile? I seem to remember use of Obsidian URIs is limited in the mobile version, if they are usable at all. I ask because I run mobile in the Android container on my Chromebook. It works as a desktop app just as effectively as the native Mac or Win version. Therefore, can I request that if you do implement this, you retain the current transfer mechanism and maybe make it an option in Settings. After all, if I clip something > 2000 chars I can easily perform two or more separate clips to capture the entire text. Thanks.

[jgchristopher]

Thanks for the info!

I will make sure that mobile is supported in whatever approach I end up taking.