Google Chromebook: Difference between revisions

Scorpiomaj27 (talk | contribs)
No edit summary
 
(9 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{{Incomplete}}
{{InfoboxProductLine
{{InfoboxProductLine
| Title = {{PAGENAME}}
| Title = {{PAGENAME}}
| Release Year =  
| Release Year =2011
| Product Type =  
| Product Type = Software/Hardware
| In Production =  
| In Production = Yes
| Official Website =  
| Official Website = [https://www.google.com/chromebook Google Chromebook]
| Logo =  
| Logo = Chromebook-logo.png
}}
}}
==Introduction==
A certain hidden extension that was forcibly installed onto a Chromebook by Google essentially '''bricked that Chromebook.<ref name="CBrick">[https://news.ycombinator.com/item?id=43514087 ChromeBook Bricked by Hidden Extension]</ref>
'''


The user's complaint is that the machine has become hot and that the extra load has essentially made it unusable. <!--For an accurate account I refer you to the source material:
==Consumer impact summary==
Overview of concerns that arise from the conduct towards users of products part of the product line.  


https://news.ycombinator.com/item?id=43514087-->
Touch on relevant topics like;


==Consumer impact summary==
User Freedom
{{Placeholder box|Overview of concerns that arise from the conduct towards users of products part of the product line.
 
User Privacy
 
Business Model


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]].
{{Placeholder box|Replace the placeholder text in the sections below with the incidents that affect this product line and a short summary. Also replace the link so it point to the right company article.}}
===Google Chromebook Severely Impacted after Google force-installed ScreenAI into the Google Chrome browser (2025)===
===Example incident one (''date'')===
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" />
{{Main|link to the main article}}
 
Short summary of the incident (could be the same as the summary preceding the article).
Rob Isaac's complaint is that the machine has become "too hot to touch" and that the extra load has essentially made it unusable, while also reducing the battery life significantly.<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>
===Example incident two (''date'')===
...


Incidents affecting all of the company's products can be found in the company article: [[Company article]]
==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 41:
[[Category:{{PAGENAME}}]]
[[Category:{{PAGENAME}}]]
[[Category:Anti-Consumer Practices]]
[[Category:Anti-Consumer Practices]]
[[Category:Computers]]
[[Category:Laptops]]
[[Category:Planned obsolescence]]
[[Category:Planned obsolescence]]