The telescreen received and transmitted simultaneously. Any sound that Winston made, above the level of a very low whisper, would be picked up by it; moreover, so long as he remained within the field of vision which the metal plaque commanded, he could be seen as well as heard. There was of course no way of knowing whether you were being watched at any given moment.
That's not the worst idea ever. Say a screenshot is 10 mb. 10x60x
8 hours =4800mb per work day. 30 days is 150gb worst case scenario. I suppose you could check the previous screenshot and if it's the same, then don't write a new file. Combine that with OCR and a utility to scroll forward and backward through time, it might be a useful tool.
As said one comment above, check if it's the same composition as before and don't take a screenshot if it didn't change. Make some rules to filter out video content so if you have a youtube video open it doesn't take a screenshot every second just because the video is running.
Or you could actually integrate this with your window manager. Only take a screenshot if you move / resize / open / close a window. Make a small extension for browsers that tell it to make a screenshot if you scroll / close / open a page. Then you don't have to make a screenshot and compare with the one before.
This wouldn't be as thorough as just forcing screenshots all the time and you would probably not catch stuff like writing a text in libreoffice as you don't change anything with the window. But it could be a resourceful way to do that.
And if for example no screenshot was taken for 1 minute because nothing called for that, you could just take one regardless. That way you have a minimum of one screenshot per minute or as often as window manager / browser calls for it.
But obviously I don't want a malware company like Microsoft doing that "for me" (actually the purpose is hyperspecific ads if not long term planning to exfiltrate the data).
Not sure if I even trust myself with the security that data would require.
I mean taking the screenshot is the easy part, getting reliable OCR on the other hand ...
In my experience (tesseract) current OCR works well for continuous text blocks but it has a hard time with tables, illustrations, graphs, gui widgets, etc.
I suppose you could check the previous screenshot and if it’s the same
Hmmm... this gives me an idea... maybe we could even write a special algorithm that checks whether only certain parts of picture have changed, and store only those, while re-using the parts that haven't changed. It would be a specialized compression algorithm for Moving Pictures. But that sounds difficult, it would probably need a whole Group of Experts to implement. Maybe we can call it something like Moving Picture Experts Group, or MPEG for short : )
its a cronjob that runs each minute (*/1) in any hour, any day, any month, on any weekday, gnome-screenshot obviously takes a screenshot and outputs it to the given file path and filename, where the filename is written as the current date as string and .png as format
It's a crontab entry which, once a minute, uses the gnome-screenshot program to take a screenshot of your monitor and save it to /Microsoft/yourPrivacy.
Am I the only one who honestly thinks Recall is totally useless? I feel like everyone is acting like it's useful and the only thing to debate over is whether it's "worth the security risk".
But I feel like it's not even worth anything at all. Even if there was no risk and I was 100% in control I don't think I would ever use such a feature.
Wouldn't you waste just as much (if not more) time looking through old screenshots, than to just go look up a solution the old fashioned way? Whatever you were looking at is probably still in your browser history too.
I know the point is it has some AI crap with it, but that still requires you to remember enough information about what you're looking for to filter them.
And if you know that much information I think you could probably just find whatever you were looking for again normally.
That's because you know how to find information in a computer quickly and precisely. Recalk is for clueless people. They can ask the computer in plain English.
Yeah but to what end? Is a clueless person going to find answers to something by looking back through their past clueless behavior?
Or maybe it's just so they have a record of what they screwed up so they can fix it? In that case I think some sort of changelog to all system wide settings that the user modifies, with timestamps, would be infinitely more useful than Recall.
The problem is, knowing Microsft, its gonna be turned on by default. And half the people who use Windows barely know how to turn the computer on and off. Let alone dive deep into some half baked settings app to figure out where to turn it off.