Irakli Gozalishvili

Love it! I've been suggesting doing same thing for ipfs urls across all gateways as well! P.S. I would even drop `nft-data-by-url` part

Thanks for asking @lidel, indeed goals are very similar here. I think there couple of things I'd share from building that: 1. [freeze-dry](https://github.com/WebMemex/freeze-dry) is a great library that does some...

@ikreymer that is really impressive work, I'm blown away! > I think this approach works much better than saving static DOM, which generally is limited to pages that are self-contained...

> > I think it really depends on what the goals are. That said your work got me thinking that it may indeed be better to capture all you can...

> If not, @Gozala had some ideas on keeping ServiceWorker alive in [ipfs/in-web-browsers#137 (comment)](https://github.com/ipfs/in-web-browsers/issues/137#issuecomment-450530548), but the net result will be to actually use more CPU by artificially keeping it alive...

> Personally I don't think this change will stick in the form proposed in the draft as having `declarativeNetRequest` as the only blocking option [makes it impossible to write things...

I'm not sure if there are some way to engage with the corresponding people driving these changes but I think best bet would be to convince them to expose SharedWorker...

Thanks @ept for thoughtful and detailed explanation. I understand now what you meant by third format. I do have some followup question though regarding this segment: > The question is...

> Are you writing a new rich-text editor or trying to integrate with an existing one? I think the best approach here is going to be determined by that question....

> I'd suggest you consider a couple of other features like cursors (which need to be tracked in the document but won't be permanently persisted), and comments (which might be...