Google Chromebook: Difference between revisions
Scorpiomaj27 (talk | contribs) No edit summary |
→Incidents: Summarize use of Google ScreenAI |
||
| (5 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
{{Incomplete}} | |||
{{InfoboxProductLine | {{InfoboxProductLine | ||
| Title = {{PAGENAME}} | | Title = {{PAGENAME}} | ||
| Line 7: | Line 8: | ||
| Logo = Chromebook-logo.png | | Logo = Chromebook-logo.png | ||
}} | }} | ||
==Consumer impact summary== | ==Consumer impact summary== | ||
{{Placeholder box|Overview of concerns that arise from the conduct towards users of products part of the product line. | <!--{{Placeholder box|Overview of concerns that arise from the conduct towards users of products part of the product line. | ||
Touch on relevant topics like: | Touch on relevant topics like: | ||
| Line 22: | Line 16: | ||
* User Privacy | * User Privacy | ||
* Business Model | * Business Model | ||
* Market Control}} | * Market Control}} - --> | ||
{| style="width:55%; background-color:white; border:1px solid #ccc; padding:10px;" | |||
|- | |||
|Overview of concerns that arise from the conduct towards users of products part of the product line. | |||
|- | |||
|Touch on relevant topics like: | |||
*User Freedom | |||
*User Privacy | |||
*Business Model | |||
*Market Control | |||
|} | |||
==Incidents== | ==Incidents== | ||
This is a list of all consumer protection incidents related to this product line. Any incidents not mentioned here can be found in the [[:Category:{{PAGENAME}}|{{PAGENAME}} category]]. | This is a list of all consumer protection incidents related to this product line. Any incidents not mentioned here can be found in the [[:Category:{{PAGENAME}}|{{PAGENAME}} category]]. | ||
{{ | ===Google Chromebook Bricked after Google force-installed ScreenAI into the Google Chrome browser (2025)=== | ||
=== | There have been reports of Google's ScreenAI being enabled on Chromebooks via the Google Chrome webbrowser by default.'''<ref name="CBrick">{{Cite web |last=Isaac |first=Rob |date=24 Mar 2025 |title=Today Google bricked my Chromebook by force-installing a hidden extension |url=https://news.ycombinator.com/item?id=43514087 |url-status=live |archive-url=https://web.archive.org/web/20250331115019/https://news.ycombinator.com/item?id=43514087 |archive-date=31 Mar 2025 |via=Hacker News, originally posted on Mastodon}}</ref>'''<ref name=":0">{{Cite web |last=Gerard |first=David |date=29 Mar 2025 |title=Google ScreenAI: make your Chromebook melt down |url=https://pivot-to-ai.com/2025/03/29/google-screenai-make-your-chromebook-melt-down/ |url-status=live |archive-url=https://web.archive.org/web/20250329233052/https://pivot-to-ai.com/2025/03/29/google-screenai-make-your-chromebook-melt-down/ |archive-date=29 Mar 2025 |access-date=21 Jun 2025 |website=Pivot to AI}}</ref> The accessibility tool was put into the [[wikipedia:Chromium_(web_browser)|Chromium]] project, which provides the foundation for the Google Chrome webbrowsers and other webbrowsers; potentially affecting the majority of webbrowsers that are used.<ref name=":0" /> | ||
Rob Isaac's complaint is that the machine has become hot and that the extra load has essentially made it unusable, while also reducing the battery life severely.<ref name="CBrick" /> Chromebook users confirm these complaints on their own machines, and have posted their complaints on the Chromebook help forums.<ref name=":0" /> Other concerns are that the software is invasive, similar to [[Microsoft#Recall|Microsoft's Recall]] feature, and that the software itself is not transparent; the source code for ScreenAI is developed within Google's internal source code repository google3.<ref>{{Cite web |date=6 May 2024 |title=Development and Deployment of ScreenAI |url=https://github.com/chromium/chromium/blob/main/services/screen_ai/README.md#development-and-deployment |access-date=21 Jun 2025 |website=GitHub}}</ref> | |||
== | |||
==Products== | ==Products== | ||
{{Placeholder box|This is a list of the products with articles on this wiki. | {{Placeholder box|This is a list of the products with articles on this wiki. | ||
| Line 47: | Line 51: | ||
[[Category:{{PAGENAME}}]] | [[Category:{{PAGENAME}}]] | ||
[[Category:Anti-Consumer Practices]] | [[Category:Anti-Consumer Practices]] | ||
[[Category:Planned obsolescence]] | [[Category:Planned obsolescence]] | ||
Latest revision as of 09:33, 21 June 2025
⚠️ Article status notice: This article has been marked as incomplete
This article needs additional work to meet the wiki's Content Guidelines and be in line with our Mission Statement for comprehensive coverage of consumer protection issues.
This notice will be removed once sufficient documentation has been added to establish the systemic nature of these issues. Once you believe the article is ready to have its notice removed, visit the discord and post to the #appeals channel.
Learn more ▼
Google Chromebook
| Basic Information | |
|---|---|
| Release Year | 2011 |
| Product Type | Software/Hardware |
| In Production | Yes |
| Official Website | Google Chromebook |
Consumer impact summary[edit | edit source]
| Overview of concerns that arise from the conduct towards users of products part of the product line. |
Touch on relevant topics like:
|
Incidents[edit | edit source]
This is a list of all consumer protection incidents related to this product line. Any incidents not mentioned here can be found in the Google Chromebook category.
Google Chromebook Bricked after Google force-installed ScreenAI into the Google Chrome browser (2025)[edit | edit source]
There have been reports of Google's ScreenAI being enabled on Chromebooks via the Google Chrome webbrowser by default.[1][2] The accessibility tool was put into the Chromium project, which provides the foundation for the Google Chrome webbrowsers and other webbrowsers; potentially affecting the majority of webbrowsers that are used.[2]
Rob Isaac's complaint is that the machine has become hot and that the extra load has essentially made it unusable, while also reducing the battery life severely.[1] Chromebook users confirm these complaints on their own machines, and have posted their complaints on the Chromebook help forums.[2] Other concerns are that the software is invasive, similar to Microsoft's Recall feature, and that the software itself is not transparent; the source code for ScreenAI is developed within Google's internal source code repository google3.[3]
Products[edit | edit source]
See also[edit | edit source]
References[edit | edit source]
- ↑ 1.0 1.1 Isaac, Rob (24 Mar 2025). "Today Google bricked my Chromebook by force-installing a hidden extension". Archived from the original on 31 Mar 2025 – via Hacker News, originally posted on Mastodon.
- ↑ 2.0 2.1 2.2 Gerard, David (29 Mar 2025). "Google ScreenAI: make your Chromebook melt down". Pivot to AI. Archived from the original on 29 Mar 2025. Retrieved 21 Jun 2025.
- ↑ "Development and Deployment of ScreenAI". GitHub. 6 May 2024. Retrieved 21 Jun 2025.