At least it's not Microsoft Recall ... yet. Text version: https://pivot-to-ai.com/2025/03/29/google-screenai-make-your-chromebook-melt-down/

Today Google bricked my Chromebook https://cloudisland.nz/@rmi/114219847307106213 ScreenAI: A Vision-Language Model for UI and Infographics Understanding https://arxiv.org/html/2402.04615v3 Add Screen AI service for accessibility annotations https://chromium-review.googlesource.com/c/chromium/src/+/3358073 All flags on my machines have always operated at the default setting https://support.google.com/chromebook/thread/286204300?hl=en&msgid=289818570 Debian: disable screen_ai binary blob https://salsa.debian.org/chromium-team/chromium/-/commit/ee2d7017ed0b99a27f5b763ee782fdd8a0999660 Did Google publish unsigned code and push it to Mac Chrome Users? https://www.reddit.com/r/macsysadmin/comments/1ei9kk8/did_google_publish_unsigned_code_and_push_it_to/ So turning off three OCR flags in chrome://flags seems to have worked https://support.google.com/chromebook/thread/286204300?hl=en&msgid=289761480

Previously:

Windows AI Copilot+ Recall stores screenshots of sensitive data, regardless of 'sensitive information' filter https://pivot-to-ai.com/2024/12/13/windows-ai-copilot-recall-stores-screenshots-of-sensitive-data-regardless-of-sensitive-information-filter/

Buy me nice things: https://www.amazon.co.uk/hz/wishlist/ls/3Q8VZW46J6DM6

Send money! It's very helpful! Patreon: https://www.patreon.com/davidgerard Ko-Fi: https://ko-fi.com/A1529D5