rugk

I like this idea.

> Storable and Cacheable Content Do we miss some caching headers for these @elrido?

Maybe it is because [that caching then is only a heuristic](https://developer.mozilla.org/en-US/docs/Web/HTTP/Caching#heuristic_caching) and not reliable? Did not find a guideline right now, but maybe one should better explicitly specify how long...

Original KDEConnect implemented this in https://cgit.kde.org/kdeconnect-kde.git/commit/?id=239f7f68304b9537ec7609a2157bffc47b285e6e.

Actually a problem for this is how to efficiently get the image data from a video element without saving it in a canvas first. @edi9999, do you have any suggestions/ideas?

Okay, I found some ways, but actually decoding does not work at all on mobile devices (tested with Firefox for Android). It always fails with: `Couldn't find enough finder patterns:0...

No, but it's easy to create new images. (I only wanted to share them, so you can reproduce the issues…) The real link is https://gist.github.com/rugk/44e9cd89f3b67adfcb229843fffed02f.

Is there a proof of concept one can use to test it?

> Besides, I havn't checked if the sslStatus interface etc. Yep, that's also my fear. > It is not allowed for Chrome, so not sure how is it going to...

From a quick research I could not found anything, so I opened a bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1322748