kickscondor

Ok, I've done some preliminary design and am assembling a prototype in NativeScript. This isn't ultimately where I want to end up, but at least it will give us a...

Ok good - thank you for this! In my playing around with this, I've made quite a bit of improvement already. (I confess that I'd forgotten the details behind JavaScript's...

Further progress on this - I've located the primary source of trouble. For some strange reason, if I save data to `storage.sync` in the web extension and I'm monitoring it...

Okay, this is out for Firefox. You can reinstall from mozilla.org. I am going to keep this issue open for now, as a reminder to stay vigilant.

Sweet! Thank you for returning to check it out. I have some ideas for reducing this to zero - but it will take a few months to get there.

Ok - for some reason memory use has climbed recently. It's strange because the JS memory footprint looks fine in the background window (10-15 MB) - but the browser task...

It looks like I have a good lead on this issue! The Web API DOMParser class appears to hang on to old HTML documents after they've been parsed. https://stackoverflow.com/questions/56451731/dom-parser-chrome-extension-memory-leak

Updating works on Windows - but not on Mac. This is due to signing issues with Electron/NPM something in there. However, I'm moving away from Electron in an upcoming release...

Well the current builds are notarized, but not signed. I don't recall the issue I had with signing - but I couldn't even complete builds with Electron if I attempted...

Hi, tooironic! Lovely - I'm so glad you get such utility out of Fraidycat. And, of course, I want to support as many network as I can. Just doing some...