• 0 Posts
  • 15 Comments
Joined 1 year ago
cake
Cake day: June 30th, 2023

help-circle

  • Why think of it as a compression problem? Isn’t the spy device already getting compressed video form some source? That makes it a filtering problem. You would set it to grab and ship key frames (or equivalent term) if you wanted a human to be able to see the intel. But for content matching, maybe count some interval of key frames and then grab the smallest difference frame between the next two key frames. Gives a nice, premade small data chunk. A few of those in sequence starts looking like a hash function (on a dark foggy night).

    Would want some way to sync up the frames that the spy device grabs and the ones grabbed when building the db to match against. Maybe resetting the key frame interval counter when some set of simple frames come through would be enough. Like anything with a uniform color across the whole image or something similar.

    Just spitballing here. I like your impulse to math this.











  • When it first took big bites out of Firefox, it wasn’t slight at all. I have only my hazy human memory on this, but some pals and I ran a test script at the time. Iirc, Chome would routinely load enough to start reading in 2 seconds while Firefox was more like 6 on average with our site list and went over 10 way too often to ignore.

    It had been very easy before that to blame the sites for all the crud they were larding in. But it was like Google’s clean, fast search page compared to Yahoo’s “junk you don’t need” frontpage all over again. Chrome won on speed fair and square.

    Thus ends this yarn by one internet fogey.