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.
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.
Are you on 16k resolution or something?
When i take a screenshot of my 3440x1440 display it’s 1MB big. I mean this doesn’t change the issue in its core but dramatically downsizes it
Running OCR every second sounds like a great way to choke your CPU
That’s what recall is… It’s literally screenshotring and. Ocr / ai parsing Combined with a sqllite database
If only MS used DuckDB then they wouldn’t have such a huge PR disaster on their hands.