Consumer Rights Wiki - User contributions [en]

Sandbox

2025-02-12T19:16:52Z

Waldo: Waldo moved page Sandbox2 to Sandbox over a redirect without leaving a redirect: test

This is a place to experiment. It's the best place to test out modifications to template code without affecting the rest of the wiki, but it can be used for any form of experimentation.

Some other wikis have their sandboxes in the wiki's namespace (CAT in our case). Also, some wikis reset this page periodically, but that can probably be done manually for now.

----

{{Collapsed|Working around this issue requires a convoluted workaround. For details, click "[Expand]" on the right.|Lorem ipsum dolor sit amet, consectetur adipiscing elit. Fusce luctus magna a diam venenatis fringilla. Pellentesque ultrices interdum pellentesque. Integer sit amet maximus arcu. Sed scelerisque leo diam, id porttitor nisl porttitor non. Praesent risus tellus, eleifend efficitur erat id, consectetur tincidunt nibh. Integer nunc urna, condimentum sit amet tortor ac, accumsan cursus tellus. Proin tempus elit vestibulum nisl mattis consectetur. Etiam ac nisl a quam semper commodo ut eu libero. Phasellus finibus lorem non ultricies vehicula.

In et nisi ac justo scelerisque vulputate a at lectus. Aliquam dapibus justo ac diam suscipit commodo. Aenean sed odio nunc. Morbi eu porttitor mauris. Integer ut pellentesque ligula. Sed non semper lectus, sed mattis turpis. Cras eu lorem finibus, sodales massa sed, egestas lacus. Phasellus suscipit consectetur tristique. Mauris laoreet erat in magna dapibus varius. Nullam arcu arcu, feugiat nec quam sit amet, hendrerit porttitor nibh. }}

Sandbox

2025-02-12T19:16:34Z

Waldo: Waldo moved page Sandbox to Sandbox2: test

Consumer Rights Wiki:Announcements

2025-02-10T00:11:14Z

Waldo: Use ISO 8601 date for consistency with "New pages" section on Main Page

<h2>Announcements</h2>

=== 2025-01-30 ===

We made it easier for you to create a new article! Simply click on [[Consumer_Action_Taskforce:New_here|Create a page]] in the sidebar on the left, fill in the title for your page and click on "Create page".

Main Page

2025-02-10T00:10:17Z

Waldo: Increase new page limit even more

__NOTOC__
<div style="font-size:1.75em;line-height:2em"> Welcome to the Consumer Action Taskforce! </div>

The mission of this Wiki is to document a new generation of consumer exploitation that bears no resemblance to issues of the 1950s-1990s. We focus on the issues that often go unnoticed by review sites, tech press, and traditional consumer protection publications.

<div class="mainpage-contents" style="display: grid; grid-template-columns: repeat(auto-fill, minmax(min(100%, max(24rem, 34%)), 1fr)); gap: 1rem;">
<div><h2>Find an article</h2>{{Category:Wiki_root/Main_page}}</div>
<div>{{Consumer Action Taskforce:Announcements}}</div>
<div>{{Main_Page/Shortened how to help}}</div>
<div><h2>New pages</h2>{{Special:NewPages|namespace=0|limit=15}}</div>
</div>
{{DISPLAYTITLE:<span style="position: absolute; clip: rect(1px 1px 1px 1px); clip: rect(1px, 1px, 1px, 1px);">{{FULLPAGENAME}}</span>}}

Talk:Main Page

2025-02-10T00:04:10Z

Waldo: /* Can we categorize this? */ Fix link so this talk page isn't categorized

== Looking good ==

Looks like we are doing alright so far with this page; lol... people go ahead of me - [[User:Atsumari|Atsumari]] ([[User talk:Atsumari|talk]]) 02:51, 1 February 2025 (UTC)

== Can we categorize this? ==

Just to clean up [[Special:UncategorizedPages]]. I suggest putting this page under [[:Category:CAT]]. [[User:Waldo|Waldo]] ([[User talk:Waldo|talk]]) 08:07, 20 January 2025 (UTC)

Moved this into the CAT category so it isn't eaten by special pages as requested; looks like it may have already been in the root namespace but just for clarity sake until we build a full on mainpage. Thanks for the catch <3 - [[User:Atsumari|Atsumari]] ([[User talk:Atsumari|talk]]) 11:36, 25 January 2025 (UTC)

== Anonymization of non-logged in user IPs ==

I would like to request that users who make edits without user accounts do not have their full IP published in the edit log.

: I made a suggestion on the Discord server on your behalf. [[User:Waldo|Waldo]] ([[User talk:Waldo|talk]]) 10:44, 7 February 2025 (UTC)

==Someone at London meetup213 earlier today==

Hello there,

Thank you for the link to this interesting project.

What is your name?

Regards,

Janos Abel

Category:Wiki root/Main page

2025-02-09T22:49:45Z

Waldo: Make small sections span the full width

=== Browse ===
<div class="cat-but-grid" style="display: grid; grid-template-columns: repeat(auto-fill, minmax(10em, 1fr)); gap: 0.5em">{{:Category:Wiki root/Cat-but|🏢|Organizations|SkyBlue|MidnightBlue}}{{:Category:Wiki root/Cat-but|🧺|Products|Wheat|DimGray}}{{:Category:Wiki root/Cat-but|⛑️|Services|MistyRose|Crimson}}{{:Category:Wiki root/Cat-but|👤|Individuals|SkyBlue|MidnightBlue}}{{:Category:Wiki root/Cat-but|💻|Software|AliceBlue|SlateGray}}{{:Category:Wiki root/Cat-but|🌐|Websites|Lavender|Indigo}}{{:Category:Wiki root/Cat-but|💢|Incidents|PeachPuff|OrangeRed}}{{:Category:Wiki root/Cat-but|⚖️|Lawsuits|LavenderBlush|RebeccaPurple}}{{:Category:Wiki root/Cat-but|🎓|User guides|Honeydew|ForestGreen}}</div>

=== Learn ===
<div class="cat-but-grid" style="display: grid; grid-template-columns: repeat(auto-fill, minmax(max(12em, 26%), 1fr)); gap: 0.5em">{{:Category:Wiki root/Cat-but|📔|Common terms|Wheat|SaddleBrown}}{{:Category:Wiki root/Cat-but|🛰️|Protocols|LightCyan|Teal}}{{:Category:Wiki root/Cat-but|⚖️|Legislation|LavenderBlush|RebeccaPurple}}</div>

=== Contribute ===
<div class="cat-but-grid" style="display: grid; grid-template-columns: repeat(auto-fill, minmax(max(10em, 26%), 1fr)); gap: 0.5em">{{:Category:Wiki root/Cat-but|✍️|Transcripts|AliceBlue|RoyalBlue}}{{:Category:Wiki root/Cat-but|🎞️|Video based|WhiteSmoke|DimGray|Articles based on videos}}{{:Category:Wiki root/Cat-but|🐱|CAT|OldLace|Chocolate}}</div>

Category:Wiki root/Main page

2025-02-09T22:46:46Z

Waldo: Tune minimum widths to save more space

=== Browse ===
<div class="cat-but-grid" style="display: grid; grid-template-columns: repeat(auto-fill, minmax(10em, 1fr)); gap: 0.5em">{{:Category:Wiki root/Cat-but|🏢|Organizations|SkyBlue|MidnightBlue}}{{:Category:Wiki root/Cat-but|🧺|Products|Wheat|DimGray}}{{:Category:Wiki root/Cat-but|⛑️|Services|MistyRose|Crimson}}{{:Category:Wiki root/Cat-but|👤|Individuals|SkyBlue|MidnightBlue}}{{:Category:Wiki root/Cat-but|💻|Software|AliceBlue|SlateGray}}{{:Category:Wiki root/Cat-but|🌐|Websites|Lavender|Indigo}}{{:Category:Wiki root/Cat-but|💢|Incidents|PeachPuff|OrangeRed}}{{:Category:Wiki root/Cat-but|⚖️|Lawsuits|LavenderBlush|RebeccaPurple}}{{:Category:Wiki root/Cat-but|🎓|User guides|Honeydew|ForestGreen}}</div>

=== Learn ===
<div class="cat-but-grid" style="display: grid; grid-template-columns: repeat(auto-fill, minmax(12em, 1fr)); gap: 0.5em">{{:Category:Wiki root/Cat-but|📔|Common terms|Wheat|SaddleBrown}}{{:Category:Wiki root/Cat-but|🛰️|Protocols|LightCyan|Teal}}{{:Category:Wiki root/Cat-but|⚖️|Legislation|LavenderBlush|RebeccaPurple}}</div>

=== Contribute ===
<div class="cat-but-grid" style="display: grid; grid-template-columns: repeat(auto-fill, minmax(10em, 1fr)); gap: 0.5em">{{:Category:Wiki root/Cat-but|✍️|Transcripts|AliceBlue|RoyalBlue}}{{:Category:Wiki root/Cat-but|🎞️|Video based|WhiteSmoke|DimGray|Articles based on videos}}{{:Category:Wiki root/Cat-but|🐱|CAT|OldLace|Chocolate}}</div>

Category:Wiki root/Main page

2025-02-09T22:44:15Z

Waldo: Split into sections and make more compact

=== Browse ===
<div class="cat-but-grid" style="display: grid; grid-template-columns: repeat(auto-fill, minmax(12em, 1fr)); gap: 0.5em">{{:Category:Wiki root/Cat-but|🏢|Organizations|SkyBlue|MidnightBlue}}{{:Category:Wiki root/Cat-but|🧺|Products|Wheat|DimGray}}{{:Category:Wiki root/Cat-but|⛑️|Services|MistyRose|Crimson}}{{:Category:Wiki root/Cat-but|👤|Individuals|SkyBlue|MidnightBlue}}{{:Category:Wiki root/Cat-but|💻|Software|AliceBlue|SlateGray}}{{:Category:Wiki root/Cat-but|🌐|Websites|Lavender|Indigo}}{{:Category:Wiki root/Cat-but|💢|Incidents|PeachPuff|OrangeRed}}{{:Category:Wiki root/Cat-but|⚖️|Lawsuits|LavenderBlush|RebeccaPurple}}{{:Category:Wiki root/Cat-but|🎓|User guides|Honeydew|ForestGreen}}</div>

=== Learn ===
<div class="cat-but-grid" style="display: grid; grid-template-columns: repeat(auto-fill, minmax(12em, 1fr)); gap: 0.5em">{{:Category:Wiki root/Cat-but|📔|Common terms|Wheat|SaddleBrown}}{{:Category:Wiki root/Cat-but|🛰️|Protocols|LightCyan|Teal}}{{:Category:Wiki root/Cat-but|⚖️|Legislation|LavenderBlush|RebeccaPurple}}</div>

=== Contribute ===
<div class="cat-but-grid" style="display: grid; grid-template-columns: repeat(auto-fill, minmax(12em, 1fr)); gap: 0.5em">{{:Category:Wiki root/Cat-but|✍️|Transcripts|AliceBlue|RoyalBlue}}{{:Category:Wiki root/Cat-but|🎞️|Video based|WhiteSmoke|DimGray|Articles based on videos}}{{:Category:Wiki root/Cat-but|🐱|CAT|OldLace|Chocolate}}</div>

User:Waldo

2025-02-09T22:35:52Z

Waldo: Remove "Finish Categorization"

__NOTOC__
== What I need to do ==

# Learn the API
# Start categorizing
# Learn Lua

== What I've done ==

=== Moved all articles under one root category ===

# Before I started, there was no structure in the categories.
# Created the [[:Category:Wiki root|Wiki root]] category and the initial structure, establishing some naming conventions along the way.

=== Wrote documentation for categorization ===

# Worked with Kostas, Keith and Mingyee to design a good category system.
# Wrote [[Categorization]], including making the diagrams.

=== Wrote a page for contributors writing their first article ===

[[Consumer Action Taskforce:Write your first article!|Write your first article!]]

=== Added some color to the root category ===

See [https://wiki.rossmanngroup.com/index.php?title=Category:Wiki_root&oldid=7614 revision 7614].

=== Designed the 2x2 grid main page ===

See [https://wiki.rossmanngroup.com/index.php?title=Main_Page&oldid=7931 revision 7931].

== Subpages ==

{{Special:Prefixindex/{{FULLPAGENAMEE}}/
|hideredirects=1
}}

Consumer Rights Wiki:Categorization

2025-02-09T22:34:22Z

Waldo: Resolve TODOs

This article describes how categories are chosen for different types of pages. This is useful for users who want to help maintain the wiki by clearing out uncategorized pages ([[Special:UncategorizedPages|list]]), uncategorized categories ([[Special:UncategorizedCategories|list]]) and wanted categories ([[Special:WantedCategories|list]]).

Users who frequently create new pages also need this information.
<div class="cat-image-fullwidth">[[File:Category link graph.png|An overview of the company-product category system.]]</div>

== Articles ==
=== Incident articles ===
[[File:Incident category graph.png|349x62px|thumbnail|Incident article categories]]
An incident can apply to a specific product, service, website, piece of software, a whole product line or a company (and/or all of its products).

* An incident that applies to a '''specific product''', service, website or piece of software should belong to that category. For example, the [[Pixel 4a Battery Performance Program]] article belongs to <code><nowiki>[[Category:Pixel 4a]]</nowiki></code>.
* An incident that applies to a '''whole product line''' should belong to that product line's category. For example, [[Fitbit Sense and Versa 3 Battery Performance Program]] belongs to <code><nowiki>[[Category:Fitbit Sense]]</nowiki></code> and <code><nowiki>[[Category:Fitbit Versa 3]]</nowiki></code>.
* An incident that applies to '''all of a company's products''', or that should be known by anyone considering paying for one of their products, should belong to the company's category. For example, [[Disney wrongful-death lawsuit]] belongs to <code><nowiki>[[Category:Disney]]</nowiki></code>.

Incidents should also be categorized according to the categories in [[:Category:Incidents]]. These categories are a work in progress, and this section will be updated once a system has been established.

=== Company articles ===
[[File:Company article category graph.png|67x131px|thumbnail|Company article categories]]
Company '''articles''' belong to their respective category. For example, the [[Sony]] article belongs to <code><nowiki>[[Category:Sony]]</nowiki></code>.

{{Clear}}
=== Product, product line, service, website and software articles ===
[[File:Product article category graph.png|188x55px|thumbnail|Product, product line, service, website and software article categories]]
Product line, service, website and software articles belong to their respective category. For example, the [[Google Pixel]] article belongs to <code><nowiki>[[Category:Google Pixel]]</nowiki></code>.

== Categories ==
=== Company categories ===
[[File:Company category graph.png|140x136px|thumbnail|Company categories]]
==== Rules ====
Company '''categories''' are categorized [[:Category:Companies|by industry]]. To avoid confusion, they are categorized based on how the corresponding article is categorized on Wikipedia.

When transferring the categories from the corresponding Wikipedia article, the following apply:
* Categories must describe the company in a way that relates to the products and services it provides.
* Categories do not contain information about the year or country of establishment. These are not important for the purposes of this wiki.
* Categories that belong to the "Companies by industry" category on Wikipedia belong to the [[:Category:Companies|Companies]] category on this wiki.

==== Example ====
As an example, consider the Wikipedia page for [[wikipedia:Sony|Sony]], one of the companies with the most categories on Wikipedia:

[[File:Screenshot of Sony Wikipedia article categories.png|484x190px]]

The following categories do not describe Sony in a way that relates to its products and services:
* TOPIX 100
* 1950s initial public offerings
* Belgian Royal Warrant holders
* Companies in the Nikkei 225
* Companies listed on the New York Stock Exchange
* Companies listed on the Tokyo Stick Exchange
* Conglomerate companies based in Tokyo
* Mitsui

Examples of categories on other pages that do not relate to the company's products and services include:
* Privately held companies
* Family-owned companies
* Multinational companies

Here are a few categories with years or countries of establishment removed:
* Computer companies of Japan → <code><nowiki>[[Category:Computer companies]]</nowiki></code>
* Electronics companies established in 1946 → <code><nowiki>[[Category:Electronics companies]]</nowiki></code>

<div class="mw-collapsible mw-collapsed">
Click "[Expand]" on the right to view the final list of categories at the bottom of the [[:Category:Sony]] page.

<pre class="mw-collapsible-content">
[[Category:Computer companies]]
[[Category:Computer hardware companies]]
[[Category:Computer storage companies]]
[[Category:Computer systems companies]]
[[Category:Display technology companies]]
[[Category:Electronics companies]]
[[Category:Headphones manufacturers]]
[[Category:Lens manufacturers]]
[[Category:Loudspeaker manufacturers]]
[[Category:Microphone manufacturers]]
[[Category:Netbook manufacturers]]
[[Category:Photography equipment manufacturers]]
[[Category:Portable audio player manufacturers]]
[[Category:Radio manufacturers]]
[[Category:Software companies]]
[[Category:Video equipment manufacturers]]
</pre>
</div>

=== Product categories ===
[[File:Product category graph.png|75x110px|thumbnail|Product categories]]
A product's category page belongs to the product line's category page. For example, [[:Category:Pixel 4a]] belongs to <code><nowiki>[[Category:Google Pixel]]</nowiki></code>.

Some products, such as [[wikipedia:Google Glass|Google Glass]], do not belong to a line of products. These products should be categorized as if they themselves are product lines, i.e. they should follow the rules in the following two sections.

=== Product line, service, website and software categories ===
[[File:Product line category graph.png|607x136px|thumbnail|Product line, service, website and software categories]]
Articles can be about a combination of products, product lines, services, websites and software. The distinction between some of these terms is vague, so this wiki chooses to take liberties from Wikipedia's system.

==== Rules ====
A category page should belong to the manufacturer, service provider and/or developer's category page. For example, [[:Category:Google Pixel]] should belong to [[:Category:Google]].

Categories are also categorized by type. To avoid confusion, they are categorized based on the categories on Wikipedia.

When transferring the categories from Wikipedia, the following apply:
* Categories must describe the type of product, service, website or software.
* Categories do not contain extra information unrelated to the type. This extra information should be omitted.
* Categories that belong to the "<thing> by type" category on Wikipedia belong to the "<thing>" category on this wiki.
* When categorizing product lines, categories are sourced from the following pages on Wikipedia if they exist:
** Any product article.
** That product's corresponding category.
** The product line's article.
** That product line's corresponding category.

==== Example ====
As an example, consider the Google Pixel product line. Categories can be sourced from the following articles on Wikipedia:
* Pixel 4a
* Category:Pixel 4a (does not exist; skip)
* Google Pixel
* Category:Google Pixel

The categories on Wikipedia follow. These categories should be modified according to the rules outlined above.
[[File:Screenshot of Pixel 4a categories on Wikipedia.png|474x64px]]
[[File:Screenshot of Google Pixel categories on Wikipedia.png|474x28px]]
[[File:Screenshot of Category-Google Pixel categories on Wikipedia.png|596x28px]]

The following categories do not describe a type of product:
* Google hardware
* Computer-related introductions in 2013

Here are a few categories with extra information removed:
* Discontinued smartphones → <code><nowiki>[[Category:Smartphones]]</nowiki></code>
* Mobile phones introduced in 2020 → <code><nowiki>[[Category:Mobile phones]]</nowiki></code>

<div class="mw-collapsible mw-collapsed">
Click "[Expand]" on the right to view the final list of categories at the bottom of the [[:Category:Google Pixel]] page.

<pre class="mw-collapsible-content">
[[Category:Google]]
[[Category:Android (operating system) devices]]
[[Category:Mobile phones]]
[[Category:Smartphones]]
[[Category:Tablet computers]]
</pre>
</div>[[Category:CAT]]

== Rationale ==
=== Introduction ===
This section explains the rationale for the current design of the company and product category hierarchy. It approaches the problem of a reader trying to find all incidents associated with a product they're considering purchasing.

In order to learn about the consumer protection flaws of a product, the reader will search for the product on this wiki to see if there are any flaws related to that product specifically. This will land the user at the product's article.

=== Duplication of information ===
There is some information that cannot be represented on the product's article because it affects multiple products. Information that affects multiple products cannot be repeated across those product pages because this information duplication would greatly increase the work associated with improving and amending the information.

In order to avoid repeating the information, it can be extracted into a separate article that covers all affected products. This article must be linked to from the product article, as shown by the blue arrow in the diagram nearby.

As an example, consider information about an issue affecting all Pixel devices. This information can't be repeated across all Pixel product pages for the reasons mentioned above. It needs to be extracted into a separate article. This is a product line article. The product article must link to the product line article so that the user can easily navigate to it.

Some issues apply to all of Google's products, not just its Pixel devices. This information can't be repeated across all the product line articles, so it needs to be extracted into a separate article. This is a company article. The product line article must link to the company article.

=== The importance of product line articles ===
In order to reduce the amount of articles, a contributor may consider moving the product line information to the company article. However, when the user, considering buying the product, looks at the company article, they have to wade through information about product lines that they are not interested in. Thus, product line articles are critical for ensuring that readers only read about incidents that affect the products they are considering buying.

=== Conclusion ===
To recap the user's process: The wiki contains a product article, a product line article and a company article. The user lands on the product article page because they searched for it. This article does not contain all incidents affecting the product, so they navigate to the product line article. After that, they navigate to the company article. None of these articles contain incidents that do not affect their product.

Consumer Rights Wiki:Categorization

2025-02-09T22:23:59Z

Waldo: Update graphs

This article describes how categories are chosen for different types of pages. This is useful for users who want to help maintain the wiki by clearing out uncategorized pages ([[Special:UncategorizedPages|list]]), uncategorized categories ([[Special:UncategorizedCategories|list]]) and wanted categories ([[Special:WantedCategories|list]]).

Users who frequently create new pages also need this information.
<div class="cat-image-fullwidth">[[File:Category link graph.png|An overview of the company-product category system.]]</div>

== Articles ==
=== Incident articles ===
[[File:Incident category graph.png|349x62px|thumbnail|Incident article categories]]
An incident can apply to a specific product, service, website, piece of software, a whole product line or a company (and/or all of its products).

An incident that applies to a specific product, service, website or piece of software should belong to that category. For example, the [[Pixel 4a Battery Performance Program]] article should belong to <code><nowiki>[[Category:Pixel 4a]]</nowiki></code>.

An incident that applies to a whole product line should belong to that product line's category.

An incident that applies to all of a company's products, or that should be known by anyone considering paying for one of their products, should belong to the company's category.

Incidents should also be categorized according to the categories in [[:Category:Incidents]]. These categories are a work in progress, and this section will be updated once a system has been established.

=== Company articles ===
[[File:Company article category graph.png|67x131px|thumbnail|Company article categories]]
Company '''articles''' belong to their respective category. For example, the [[Sony]] article belongs to <code><nowiki>[[Category:Sony]]</nowiki></code>.

{{Clear}}
=== Product, product line, service, website and software articles ===
[[File:Product article category graph.png|188x55px|thumbnail|Product, product line, service, website and software article categories]]
Product line, service, website and software articles belong to their respective category. For example, the [[Google Pixel]] article belongs to <code><nowiki>[[Category:Google Pixel]]</nowiki></code>.

== Categories ==
=== Company categories ===
[[File:Company category graph.png|140x136px|thumbnail|Company categories]]
==== Rules ====
Company '''categories''' are categorized [[:Category:Companies|by industry]]. To avoid confusion, they are categorized based on how the corresponding article is categorized on Wikipedia.

When transferring the categories from the corresponding Wikipedia article, the following apply:
* Categories must describe the company in a way that relates to the products and services it provides.
* Categories do not contain information about the year or country of establishment. These are not important for the purposes of this wiki.
* Categories that belong to the "Companies by industry" category on Wikipedia belong to the [[:Category:Companies|Companies]] category on this wiki.

==== Example ====
As an example, consider the Wikipedia page for [[wikipedia:Sony|Sony]], one of the companies with the most categories on Wikipedia:

[[File:Screenshot of Sony Wikipedia article categories.png|484x190px]]

The following categories do not describe Sony in a way that relates to its products and services:
* TOPIX 100
* 1950s initial public offerings
* Belgian Royal Warrant holders
* Companies in the Nikkei 225
* Companies listed on the New York Stock Exchange
* Companies listed on the Tokyo Stick Exchange
* Conglomerate companies based in Tokyo
* Mitsui

Examples of categories on other pages that do not relate to the company's products and services include:
* Privately held companies
* Family-owned companies
* Multinational companies

Here are a few categories with years or countries of establishment removed:
* Computer companies of Japan → <code><nowiki>[[Category:Computer companies]]</nowiki></code>
* Electronics companies established in 1946 → <code><nowiki>[[Category:Electronics companies]]</nowiki></code>

<div class="mw-collapsible mw-collapsed">
Click "[Expand]" on the right to view the final list of categories at the bottom of the [[:Category:Sony]] page.

<pre class="mw-collapsible-content">
[[Category:Computer companies]]
[[Category:Computer hardware companies]]
[[Category:Computer storage companies]]
[[Category:Computer systems companies]]
[[Category:Display technology companies]]
[[Category:Electronics companies]]
[[Category:Headphones manufacturers]]
[[Category:Lens manufacturers]]
[[Category:Loudspeaker manufacturers]]
[[Category:Microphone manufacturers]]
[[Category:Netbook manufacturers]]
[[Category:Photography equipment manufacturers]]
[[Category:Portable audio player manufacturers]]
[[Category:Radio manufacturers]]
[[Category:Software companies]]
[[Category:Video equipment manufacturers]]
</pre>
</div>



=== Product categories ===
[[File:Product category graph.png|75x110px|thumbnail|Product categories]]
A product's category page belongs to the product line's category page. For example, [[:Category:Pixel 4a]] belongs to <code><nowiki>[[Category:Google Pixel]]</nowiki></code>.

Some products, such as [[wikipedia:Google Glass|Google Glass]], do not belong to a line of products. These products should be categorized as if they themselves are product lines, i.e. they should follow the rules in the following two sections.

=== Product line, service, website and software categories ===
[[File:Product line category graph.png|607x136px|thumbnail|Product line, service, website and software categories]]
Articles can be about a combination of products, product lines, services, websites and software. The distinction between some of these terms is vague, so this wiki chooses to take liberties from Wikipedia's system.

==== Rules ====
A category page should belong to the manufacturer, service provider and/or developer's category page. For example, [[:Category:Google Pixel]] should belong to [[:Category:Google]].

Categories are also categorized by type. To avoid confusion, they are categorized based on the categories on Wikipedia.

When transferring the categories from Wikipedia, the following apply:
* Categories must describe the type of product, service, website or software.
* Categories do not contain extra information unrelated to the type. This extra information should be omitted.
* Categories that belong to the "<thing> by type" category on Wikipedia belong to the "<thing>" category on this wiki.
* When categorizing product lines, categories are sourced from the following pages on Wikipedia if they exist:
** Any product article.
** That product's corresponding category.
** The product line's article.
** That product line's corresponding category.

==== Example ====
As an example, consider the Google Pixel product line. Categories can be sourced from the following articles on Wikipedia:
* Pixel 4a
* Category:Pixel 4a (does not exist; skip)
* Google Pixel
* Category:Google Pixel

The categories on Wikipedia follow. These categories should be modified according to the rules outlined above.
[[File:Screenshot of Pixel 4a categories on Wikipedia.png|474x64px]]
[[File:Screenshot of Google Pixel categories on Wikipedia.png|474x28px]]
[[File:Screenshot of Category-Google Pixel categories on Wikipedia.png|596x28px]]

The following categories do not describe a type of product:
* Google hardware
* Computer-related introductions in 2013

Here are a few categories with extra information removed:
* Discontinued smartphones → <code><nowiki>[[Category:Smartphones]]</nowiki></code>
* Mobile phones introduced in 2020 → <code><nowiki>[[Category:Mobile phones]]</nowiki></code>

<div class="mw-collapsible mw-collapsed">
Click "[Expand]" on the right to view the final list of categories at the bottom of the [[:Category:Google Pixel]] page.

<pre class="mw-collapsible-content">
[[Category:Google]]
[[Category:Android (operating system) devices]]
[[Category:Mobile phones]]
[[Category:Smartphones]]
[[Category:Tablet computers]]
</pre>
</div>[[Category:CAT]]

== Rationale ==
=== Introduction ===
This section explains the rationale for the current design of the company and product category hierarchy. It approaches the problem of a reader trying to find all incidents associated with a product they're considering purchasing.

In order to learn about the consumer protection flaws of a product, the reader will search for the product on this wiki to see if there are any flaws related to that product specifically. This will land the user at the product's article.

=== Duplication of information ===
There is some information that cannot be represented on the product's article because it affects multiple products. Information that affects multiple products cannot be repeated across those product pages because this information duplication would greatly increase the work associated with improving and amending the information.

In order to avoid repeating the information, it can be extracted into a separate article that covers all affected products. This article must be linked to from the product article, as shown by the blue arrow in the diagram nearby.

As an example, consider information about an issue affecting all Pixel devices. This information can't be repeated across all Pixel product pages for the reasons mentioned above. It needs to be extracted into a separate article. This is a product line article. The product article must link to the product line article so that the user can easily navigate to it.

Some issues apply to all of Google's products, not just its Pixel devices. This information can't be repeated across all the product line articles, so it needs to be extracted into a separate article. This is a company article. The product line article must link to the company article.

=== The importance of product line articles ===
In order to reduce the amount of articles, a contributor may consider moving the product line information to the company article. However, when the user, considering buying the product, looks at the company article, they have to wade through information about product lines that they are not interested in. Thus, product line articles are critical for ensuring that readers only read about incidents that affect the products they are considering buying.

=== Conclusion ===
To recap the user's process: The wiki contains a product article, a product line article and a company article. The user lands on the product article page because they searched for it. This article does not contain all incidents affecting the product, so they navigate to the product line article. After that, they navigate to the company article. None of these articles contain incidents that do not affect their product.

MediaWiki:Common.css

2025-02-09T21:56:06Z

Waldo: Add rule for making an image span the full width of a page using class="cat-image-fullwidth"

/* CSS placed here will be applied to all skins */

/** Hide extra footer notices **/
li#footer-info-license-notice,
li#footer-info-privacy-notice{
display: none;
}

/** Category Page **/

.cat-but-grid{

}

.cat-but-grid a{
text-decoration: none;
}

.cat-but{

}

.cat-but:active{
border-color: var( --color-base--active, #404244 ) !important;
}

@media screen {
html.skin-theme-clientpref-night .cat-but:active{
border: 2px solid var( --color-base--hover, #404244 ) !important;
}
}

@media screen and (prefers-color-scheme: dark) {
/* automatic mode */
html.skin-theme-clientpref-os .cat-but:active {
border: 2px solid var( --color-base--hover, #404244 ) !important;
}
}

@media (hover: hover) {
.cat-but:hover{
border-color: var( --color-base--hover, #404244 ) !important;
transform: scale(1.03);
}

html.skin-theme-clientpref-night .cat-but:hover{
border: 2px solid var( --color-base--hover, #404244 ) !important;
}
}
@media (hover: hover) and (prefers-color-scheme: dark) {
html.skin-theme-clientpref-os .cat-but:hover{
border: 2px solid var( --color-base--hover, #404244 ) !important;
}
}
/** -------------------------------- **/

/** Templates **/

/* Notices - Coloured boxes */

.cat-mw-box{
border: 1px solid var(--border-color-base, #a2a9b1);
border-radius: 0.3rem;
margin-bottom:2rem;
}

.cat-mw-box-header{
font-size:1.5rem;
line-height: 1.65rem;
background:rgba(0,0,0,0.03);
padding:0.2rem 1rem;
}

.cat-mw-box-body{
padding:0.2rem 1rem;
}

/* Infobox */

.infobox {
color: var(--color-base, #202122);
background-color: var(--background-color-interactive-subtle, #f8f9fa);
border: 1px solid #aaa;
float: right;
margin: 0 0 1em 1em;
padding: 0.5em;
width: 24em;
}

.infobox-title {
font-size: 2em;
text-align: center;
border-bottom: 0.2em solid #ccc;
padding-bottom: .25em;
}

.infobox-image{
display: flex;
aspect-ratio: 2 / 1;
align-items: center;
justify-content: center;
}

/*bg color to get visible transparent images in darkmode*/

@media screen {
html.skin-theme-clientpref-night .infobox-image{
background-color:#909590;
}
}

@media screen and (prefers-color-scheme: dark) {
/* automatic mode */
html.skin-theme-clientpref-os .infobox-image{
background-color:#909590;
}
}

.infobox-table{
width:100%;
table-layout:fixed;
}

.infobox-table td{
word-wrap:break-word;
text-align: left;
}

.infobox-table th{
text-align: left;
}

.infobox-table-caption{
border-bottom: 0.1em solid #ccc;
font-size:125%;
}

/* Loosely based on https://en.wikipedia.org/wiki/Template:Infobox */
@media (min-width: 640px) {
.infobox {
float: right;
clear: right;
}
}

@media (max-width: 640px) {
.infobox {
width: 95%;
}
}

/** -------------------------------- **/

/** Create page **/

.createPageInput {
padding: 1rem;
border: 2px solid var(--border-color-base, #a2a9b1);
background-color: var(--background-color-interactive-subtle, #f8f9fa);
cursor: pointer;
border-radius: 8px;
}

.pageInputActive {
border-color: var(--border-color-progressive--focus, #36c);
box-shadow: inset 0 0 0 1px var(--box-shadow-color-progressive--focus, #36c);
background-color: var(--background-color-interactive-subtle--active, #fff);
}

@media screen {
html.skin-theme-clientpref-night .pageInputActive {
border: 2px solid var( --color-base--hover, #404244 );
background-color: #101418;
}
}

@media screen and (prefers-color-scheme: dark) {
/* automatic mode */
html.skin-theme-clientpref-os .pageInputActive {
border: 2px solid var( --color-base--hover, #404244 );
background-color: #101418;
}
}

@media (hover: hover) {
.createPageInput:hover{
border: 2px solid var( --color-base--hover, #404244 );
background-color: var( --background-color-interactive-subtle--active, #fff );
}

html.skin-theme-clientpref-night .createPageInput:hover{
border: 2px solid var( --color-base--hover, #404244 );
background-color: #101418;
}
}

@media (hover: hover) and (prefers-color-scheme: dark) {
html.skin-theme-clientpref-os .createPageInput:hover{
border: 2px solid var( --color-base--hover, #404244 );
background-color: #101418;
}
}

/* Work in progress */
.create-page {
position: relative;
}

.create-page .grid {
display: grid;
grid-column-gap: 16px;
grid-row-gap: 16px;
}

.create-page .grid .incident { grid-area: 1 / 1 / 3 / 3; cursor: pointer;}
.create-page .grid .company { grid-area: 1 / 3 / 2 / 4; cursor: pointer;}
.create-page .grid .product-line { grid-area: 2 / 3 / 3 / 4;cursor: pointer; }
.create-page .grid .theme { grid-area: 3 / 1 / 4 / 3; cursor: pointer;}
.create-page .grid .product { grid-area: 3 / 3 / 4 / 4;cursor: pointer; }

.create-page .hidden {
display: none;
}

.create-page .input-wrapper {
padding-top: 16px;
}

@media (max-width: 640px) {
.create-page .grid {
display: flex;
flex-direction: column;
gap: 8px;
}

.create-page .input-wrapper {
position: sticky;
background-color: var(--background-color-base, #fff);
bottom: 0;
display: flex;
flex-direction: column;
border-top: 1px solid var(--border-color-muted, #dadde3);
margin-left: -1.5rem;
margin-right: -1.5rem;
padding-left: 1.5rem;
padding-right: 1.5rem;
margin-top: 8px;
}
}

/* Main page, new page summary */
.mainpage-contents .mw-contributions-list li{
padding-bottom: 0.5rem;

margin: 0;
}
.mainpage-contents a.mw-newpages-time,
.mainpage-contents span.mw-newpages-length,
.mainpage-contents span.comment,
.mainpage-contents span.mw-usertoollinks,
.mainpage-contents span.mw-tag-markers { display: none;}

/** -------------------------------- **/

/* Utility classes */

/* Make an image span the full width of the page (should only be used for very narrow horizontal images) */
.cat-image-fullwidth img {
max-width: 100%;
height: auto;
}

File:Product line category graph.png

2025-02-09T21:45:51Z

Waldo: Category:CAT wiki files

== Summary ==
[[Category:CAT wiki files]]

File:Product category graph.png

2025-02-09T21:41:38Z

Waldo: Category:CAT wiki files

== Summary ==
[[Category:CAT wiki files]]

File:Company category graph.png

2025-02-09T21:39:49Z

Waldo: Category:CAT wiki files

== Summary ==
[[Category:CAT wiki files]]

File:Product article category graph.png

2025-02-09T21:36:27Z

Waldo: Category:CAT wiki files

== Summary ==
[[Category:CAT wiki files]]

File:Company article category graph.png

2025-02-09T21:34:13Z

Waldo: Category:CAT wiki files

[[Category:CAT wiki files]]

File:Company article category graph.png

2025-02-09T21:33:28Z

Waldo:

File:Incident category graph.png

2025-02-09T21:30:46Z

Waldo: Category:CAT wiki files

== Summary ==
[[Category:CAT wiki files]]

File:Category link graph.png

2025-02-09T21:22:56Z

Waldo: Waldo uploaded a new version of File:Category link graph.png

== Summary ==
[[Category:CAT wiki files]]

File:Category link graph.png

2025-02-09T21:21:08Z

Waldo: Waldo uploaded a new version of File:Category link graph.png

== Summary ==
[[Category:CAT wiki files]]

File:Category link graph.png

2025-02-09T21:19:27Z

Waldo: Waldo uploaded a new version of File:Category link graph.png

== Summary ==
[[Category:CAT wiki files]]

Category:CRW files

2025-02-09T21:16:44Z

Waldo: Category:Files

[[Category:Files]]

File:Category link graph.png

2025-02-09T21:16:19Z

Waldo: Category:CAT wiki files

== Summary ==
[[Category:CAT wiki files]]

Starlink

2025-02-09T19:13:07Z

Waldo: Waldo moved page Starlink to Subaru Starlink: Could be confused with the Starlink satellite internet service

#REDIRECT [[Subaru Starlink]]

Subaru Starlink

2025-02-09T19:13:07Z

Waldo: Waldo moved page Starlink to Subaru Starlink: Could be confused with the Starlink satellite internet service

{{InfoboxProductLine
| Title = Subaru Starlink
| Release Year = 2013
| Product Type = Software
| In Production = Yes
| Official Website = https://subaru.com/
| Logo = Subaru-starlink.png
}}

==Overview==
Starlink is a connectivity service equipped on most modern Subaru vehicles, enabling extensive data collection from the vehicle and its occupants. The service has faced significant criticism and legal challenges over privacy concerns related to its data-collection and -sharing practices.<ref name="MozillaReview" />

==Data collection==
===Types of data collected===
Subaru’s privacy policy and STARLINK terms of service specify that the following data may be collected:<ref name="SubaruPrivacy">[https://www.subaru.com/support/privacy-policies.html Subaru Privacy Policy] - subaru.com - accessed 2025-01-16</ref>

*'''Personal information'''
**Names, addresses, and contact details.
**Phone numbers and email addresses.
**Social-security numbers (in specific cases).
**Driver's license numbers.
**Vehicle identification numbers (VIN).
*'''Vehicle data'''
**Location and GPS coordinates.
**Speed, acceleration, and braking patterns.
**Time and duration of trips.
**Maintenance and diagnostic information.
**Sensor data, such as crash severity, tire pressure, and coolant temperature.
*'''Audio and biometric data'''
**Audio recordings through onboard microphones.
**Voice data from STARLINK service-center calls.
**Biometric data from systems that driver attention.
**Search content and commands issued by occupants.

===Collection methods===
Data collection is performed through:
*Vehicle sensors and diagnostic modules.<ref name="MozillaReview">[https://foundation.mozilla.org/en/privacynotincluded/subaru/ "Mozilla Foundation Privacy Review: Subaru"] - foundation.mozilla.org - accessed 2025-01-16</ref>
*GPS tracking systems.
*Cellular-connectivity modules.
*STARLINK mobile apps and web portals.<ref name="MozillaReview" />

==Data sharing and sales==
===Third-party data sharing===
Subaru shares data with several entities, including:
*Data brokers, such as LexisNexis<ref name="SubaruPrivacy" /> and Verisk.<ref name="TorqueNews">[https://www.torquenews.com/1084/subaru-now-involved-vehicle-data-collection-lawsuit-investigation "Vehicle Data Collection Lawsuit"] - torquenews.com - accessed 2025-01-16</ref><ref name="NYT">[https://www.nytimes.com/2024/03/11/technology/carmakers-driver-tracking-insurance.html "Automakers Are Sharing Drivers’ Data"]- nytimes.com - accessed 2025-01-16</ref>
*Insurance companies for risk assessment and pricing.<ref name="TorqueNews" />
*Marketing firms.
*Emergency services and law enforcement (when required by law).
*Subaru dealerships and distributors.
*Third-party service providers.<ref name="SubaruPrivacy" />
===Insurance-industry usage===
Data brokers aggregate and sell this information to insurance companies, who may:
*Increase insurance premiums based on driving patterns.
*Monitor driving behaviors to assess risk.
*Use driving data for personalized coverage offerings.<ref name="NYT" />

==Privacy concerns==
===Consent issues===
Key concerns include:
*Simply being a passenger in a STARLINK-equipped vehicle constitutes consent.<ref name="MozillaReview" />
*Lack of active notification during data collection.
*Limited opt-out options that might impact vehicle functionality.

===Difficulties in opting out===
Subaru’s opt-out process involves:
*Submitting detailed personal information.
*Potentially long response times.
*No verification mechanism for successful opt-out.<ref name="ConsumerForum">[https://www.subaruoutback.org/threads/privacy-not-included-subaru-report-connected-services-etc.556583/ "Privacy Report Discussion"] - subaruoutback.org - accessed 2025-01-16</ref>

===Legal challenges===
Subaru faces legal scrutiny for:
*Allegations of insufficiently disclosing its data-collection policies what it does with data.
*Potential non-compliance with privacy laws.
*[[Class-action lawsuit]] investigations over consent practices.<ref name="TorqueNews" />

==Technical details==
===System architecture===
STARLINK is built upon:
*Embedded telematics devices.
*4G LTE cellular networks.
*GPS receivers and cloud-based data-processing systems.<ref name="StarlinkTerms">[https://www.subaru.com/support/terms-and-conditions/subaru-starlink/subaru-starlink-services.html "Subaru STARLINK Terms and Conditions"] - subaru.com - accessed 2025-01-16</ref>

===Data transmission===
*Real-time data transmission through LTE networks.
*Local storage when connectivity is unavailable.<ref name="StarlinkTerms" />

==Consumer-protection issues==
===Privacy rights===
Critics cite:
*Minimal control over data retention.
*Broad sharing permissions in privacy policies.
*Limited transparency about how data is used.<ref name="MozillaReview" />

===Economic harm===
*Insurance-rate adjustments based on driving data.
*Subscription fees for connected services.
*Potential effects on vehicle resale value.<ref name="NYT" />

==References==
<references />

[[Category:Automotive privacy]]
[[Category:Data Collection]]
[[Category:Consumer rights]]

Template:IncidentPreload

2025-02-09T17:51:02Z

Waldo: Clarify categories

{{Placeholder box|Short summary of the incident. Usually 2-3 sentences that summarize the contents or the article.}}
$1
==Background==
{{Placeholder box|Information about the product/service history to provide the necessary context surrounding the incident}}
$2
==[Incident]==
{{Placeholder box|Change this section's title to be descriptive of the incident.

Impartial and complete description of the events, including actions taken by the company, and the timeline of the incident coming to the public's attention.}}

===[Company]'s response===
{{Placeholder box|If applicable, add the proposed solution to the issues by the company.}}

==Lawsuit==
{{Placeholder box|If applicable, add any information regarding litigation around the incident here.

===Claims===
Main claims of the suit.

===Rebuttal===
The response of the company or counterclaims.

===Outcome===
The outcome of the suit, if any.}}

==Consumer response==
{{Placeholder box|Summary and key issues of prevailing sentiment from the consumers and commentators that can be documented via articles, emails to support, reviews and forum posts.}}

==References==
{{reflist}}

{{Placeholder box|[[mw:Help:VisualEditor/User_guide#Editing_categories|Add a category]] with the same name as the product, service, website, software, product line or company that this article is about.

The "Incidents" category is not needed.}}<noinclude>
[[Category:Article sample templates]]
</noinclude>

Template:IncidentPreload

2025-02-09T17:47:16Z

Waldo: Remove </includeonly>

{{Placeholder box|Short summary of the incident. Usually 2-3 sentences that summarize the contents or the article.}}
$1
==Background==
{{Placeholder box|Information about the product/service history to provide the necessary context surrounding the incident}}
$2
==[Incident]==
{{Placeholder box|Change this section's title to be descriptive of the incident.

Impartial and complete description of the events, including actions taken by the company, and the timeline of the incident coming to the public's attention.}}

===[Company]'s response===
{{Placeholder box|If applicable, add the proposed solution to the issues by the company.}}

==Lawsuit==
{{Placeholder box|If applicable, add any information regarding litigation around the incident here.

===Claims===
Main claims of the suit.

===Rebuttal===
The response of the company or counterclaims.

===Outcome===
The outcome of the suit, if any.}}

==Consumer response==
{{Placeholder box|Summary and key issues of prevailing sentiment from the consumers and commentators that can be documented via articles, emails to support, reviews and forum posts.}}

==References==
{{reflist}}

{{Placeholder box|[[mw:Help:VisualEditor/User_guide#Editing_categories|Add a category]] named after the associated product, service, website, software, product line or company}}<noinclude>
[[Category:Article sample templates]]
</noinclude>

Linea Sketch revokes lifetime licenses

2025-02-09T17:40:26Z

Waldo: Categorize according to the incident template (the category on an incident article should be the same as the product that the incident is about)

[https://linea-app.com/ Linea Sketch] originally offered a one-time "lifetime" purchase, promising access to existing premium features as well as free future updates, but the developer later switched to a subscription model, replacing the lifetime purchase with a one-year subscription.
==Background==
[[File:Linea purchase policy v2.png|alt=Linea purchase policy that promises feature updates for lifetime purchases|thumb|252x252px|Linea purchase policy that promises feature updates for lifetime purchases]]
Linea Sketch is an iOS application by [https://iconfactory.com/ iconfactory], originally offering a free universal download with premium features. The free tier including subscription reminders and watermarks. The original purchase policy included<ref>https://web.archive.org/web/20211128061711/http://support.iconfactory.com/kb/linea/linea-purchase-policy</ref> an option for a one-time purchase:<blockquote>
If you’d prefer get these Premium features without a subscription, we're also offering a one-time purchase that unlocks the new features, as well as new ones in the future, without recurring payments.

...

Customers with an active Linea Premium subscription or a one-time purchase will automatically get access to the new features.</blockquote>

==Lifetime license revocation==
On the 7th of April, 2020 the company [https://blog.iconfactory.com/2020/04/introducing-linea-sketch-3/ released] the version 3.0 update under the same application bundle, with the following release note<blockquote>
NOTE: Linea Sketch v3 is now a free download. Subscribing removes banners, periodic reminders to support development and watermarks on exported artwork. Customers who purchased Linea Sketch v2 in 2019-20 get one year free!</blockquote>
Effectively replacing the lifetime purchase with a single year of subscription.

The company [https://blog.iconfactory.com/2019/12/linea-28-and-beyond/ justification] for not allowing users to use the previous version of the application was inability to promise the application functionality in case of an operating system update:<blockquote>
It is very likely that future changes to the operating system will break the ability to export your existing sketches entirely. If and when that happens, all of your valuable work would forever be lost.</blockquote>It also included a suggestion for further actions in case of disagreement:<blockquote>If you still don’t agree, then feel free to export your work and move on.</blockquote>

==Consumer response==
Some users noted<ref>https://forums.macrumors.com/threads/linea-sketch-joins-the-subscription-band-wagon.2229950/post-28356268</ref> that with the automatic app-updates enabled they lost access to the premium features without knowing it:<blockquote>
Version 2 auto-updated and now I'm stuck with watermarks and a little nag message. Stupid move. I liked version 2. Been using it since version 1.0. All my artwork is kind of useless with that watermark unless I pay. If I knew this was going to happen I would have exported everything while I was still on version 2. I've been told that they announced this in December on their blog. Too bad I don't read the blogs from every developer's apps I use.</blockquote>Others criticized<ref>https://mjtsai.com/blog/2020/04/14/linea-sketch-3/#comment-3200933</ref> the company's approach to communicate the change:<blockquote>This is not about people being unwilling to pay for good software. This is about a series of terrible decisions that culminated in people who did pay for good software getting screwed.</blockquote>

==Lifetime purchase option==
The company still [https://iconfactory.happyfox.com/kb/article/17-convert-subscription-to-lifetime-purchase/ offers] a lifetime purchase option for the new application version, which still could be revoked at any time since the lifetime purchase option is not defined in the terms of use<ref>https://linea-app.com/terms</ref> and the company has the right to revoke the license at any point in time:<blockquote>8. Termination

You agree that the Iconfactory may terminate your access to the Application, at our sole discretion, without cause or notice, and without penalty, at any time. The Iconfactory may also at any time discontinue providing access to Linea, or any part thereof, with or without notice. You agree that any termination of your access to Linea or any portion thereof may be effected without prior notice, and you agree that the Iconfactory will not be liable to you or any third party for any such termination. Upon termination, your right to use the Application will immediately cease. If you wish to terminate your account, you may simply discontinue using the Application.</blockquote>

==References==
{{reflist}}
[[Category:Linea Sketch]]

Adobe Digital Editions' ebook DRM

2025-02-09T17:34:52Z

Waldo: Categorize according to Categorization#Incident articles

Modern-day ebook publishers have been utilizing various forms of [[Digital rights management|digital-rights management]] (DRM) to protect the books they sell to make sure that "copyright laws are respected and that authors and publishers are fairly compensated" <ref name=":1">https://help.barnesandnoble.com/hc/en-us/articles/5445106302107-DRM-for-NOOK-Content</ref>. However, the end user who purchases the content legally ends up being restricted in what they are able to do with the ebook once they have purchased it. One of Adobe's version of this DRM is called "Adobe Digital Editions" which is the client the user uses to read their ebooks.

==Background==
Adobe eBook Platform is a platform for publishers to leverage when selling ebooks. This includes the following software suite: Adobe InDesign® CC software, Adobe Content Server software, the Adobe Reader® Mobile Software Development Kit (SDK), and Adobe Digital Editions <ref name=":0">https://www.adobe.com/content/dam/cc/us/en/solutions/ebook/adobe_ebook_platform_whitepaper.pdf</ref>. A summary of each of the software is outlined below at a high level (mostly extracted from the Adobe white paper on the platform):

*Adobe Content Server - "Adobe Content Server allows publishers, retailers, distributors, and libraries to host and manage eBook distribution. This server software encrypts PDF and EPUB eBook files and allows publishers and retailers to manage the rights on the eBook files they distribute <ref name=":0" />".
*Adobe Reader Mobile SDK - The SDK " allows e-reader device manufacturers and eBook application developers to support EPUB and PDF files protected by Content Server in their products. It enables tethered and over-the-air downloads so that consumers can order eBooks directly through their devices or “side-load” them by copying files from their desktops to their mobile devices" <ref name=":0" />.
*Adobe InDesign - InDesign allows the publishers to export EPUB and EPUB3 files from print layouts. This also allows publishers to export ebooks to hardware such as the "Sony Reader, the Barnes & Noble nook, and smartphones, as well as personal computers using Microsoft® Windows® or Mac OS" <ref name=":0" />.
*Adobe Digital Editions (ADE) - "Adobe Digital Editions is a free, lightweight desktop reading application for PC and Mac that allows eBook consumers to easily download and organize their eBooks easily. Consumers can read their eBooks online and offline, transfer copy-protected eBooks from their personal computers to other devices, organize eBooks into a custom library, and annotate page" <ref name=":0" />.

All these solutions come together to give publishers control over their ebook content. The main product discussed on this page is Adobe Digital Editions (ADE). ADE allows for the following benefits <ref>https://www.adobe.com/solutions/ebook/digital-editions.html</ref>:

*Download and transfer of books between devices
*EPUB3 support
*Keyword search across ebooks
*Voiceover accessibility
*Multi-language support
*Bookmarking, highlighting, and note support
*Support for borrowing ebooks from libraries
*ebook printing (publishers decide whether they opt-in for allowing printing or not)
*EPUB, EPUB3 and PDF support

ADE also has system requirements, as it is an application running on your system <ref>https://www.adobe.com/solutions/ebook/digital-editions/tech-specs.html</ref>:

Windows:

*Intel® Pentium® 4 processor or later
*Windows® 7 (32 or 64 bit running in 32-bit mode) or later
*512MB of RAM (1GB recommended)
*40MB of available hard-disk space

Mac OS:

*Intel Core™ Duo or faster processor
*Mac OS X v10.8 or later
*Compatible with Apple Retina Display
*512MB of RAM (1GB recommended)
*75MB of available hard-disk space

iOS:

*Minimum requirement 9.0 or later.
*Compatible with iPhone and iPad.

Android:

*Minimum requirement 4.4 or later.
*Compatible with the Mobile and Tablet.

== Adobe Digital Edition's Consumer Effects ==
With the release of the platform and specifically the Adobe Digital Edition application, consumers have been restricted on what they are allowed to do with ebooks that they have purchased. Although unlimited downloads are mentioned by publishers and ebook sites, those are tied to an account <ref name=":12">https://help.barnesandnoble.com/hc/en-us/articles/5445106302107-DRM-for-NOOK-Content</ref>. This means that if access to an account is lost, then the access to those ebooks is lost as well. eBooks.com is one of the various e-bookstores that sells both non-DRM and DRM books leveraging ADE. When purchasing an ebook from them, you get a .acsm file. This format only works with the Adobe Digital Editions application. The user needs to create an Adobe account (after already creating an ebooks.com account) in order to add the book to their account. ADE (pertaining to purchases from ebooks.com) allows for authorization of up to 10 devices with a single Adobe ID, but only one computer <ref name=":2">https://support.ebooks.com/hc/en-gb/articles/360000726656-What-is-DRM-DRM-FAQs</ref>. The end user would not be able to read a book on a home computer and then later on a laptop simultaneously due to this limitation. Barnes and Noble uses ADE as well for their ebooks, with their limitations being a bit different in comparison to ebooks.com's. They have 4 versions of DRM types they leverage for the books sold on their site <ref>https://help.barnesandnoble.com/hc/en-us/articles/5445106302107-DRM-for-NOOK-Content</ref>:

#Consumer DRM (eBook)
##Unlimited downloads
##Up to six (6) devices/computers
##No copying and printing
#Business DRM (eBook)
##One (1) download
##Up to one (1) device/computer
##No copying and printing
#Education DRM (eTextbook)
##Two (2) downloads
##Up to two (2) devices/computers
##Limited copying and printing
#Hard DRM
##Six (6) downloads
##Up to six (6) devices/computers
##Used for Case Studies made available by professors and specific courses

In both cases, the user is limited to only a certain number of devices and has to constantly authorize and un-authorize readers in order to be in compliance. This leads to a lack of autonomy for the user who has purchased the book. In addition, with the Barnes and Noble "Consumer DRM" section, a user is not able to print the ebook they have purchased either. Going back to the ebooks.com example, ebooks.com has a bit more control on the consumer stating that due to DRM: "the amount of printing or copying and pasting you can do may be restricted, or prevented entirely. It will also determine whether the read aloud functionality is enabled for the ebook or not" <ref name=":2" />.

With ADE, a consumer will always need to download the application to access books that they have purchased. This is under the assumption that the user is able to have the technical know-how to do all the ADE overhead in order to finally read the book they have purchased. In addition, individuals who do not have access to the most modern technology, thus not being able to download ADE on their system, are also then prevented from reading ebooks they have purchased.

If a user were to be able to remove DRM from a ebook purchased from an e-bookstore leveraging ADE, they would then be breaching the compliance with an end-user license agreement or a customer license. On ebook.com's customer license page, they mention the following: "You promise to keep any eBook in the form in which it was supplied to you. We may include other information (including information identifying the author, the copyright owner, or the terms upon which the eBook is supplied) to any eBook supplied to you. You promise not to circumvent any measures that we have taken to protect the rights in the eBook that we have supplied, including removing this information or otherwise facilitating an infringement of copyright" <ref>https://www.ebooks.com/en-us/information/customerlicense/</ref>. Although no lawsuits have been found being documented (as of writing this article), the door for this kind of consumer abuse is still present.

In 2014, the Electronic Frontier Foundation had published an article regarding how Adobe Digital Edition was tracking its end users by logging what the end-user reads and what happens to those files <ref>https://www.eff.org/deeplinks/2014/10/adobe-spyware-reveals-again-price-drm-your-privacy-and-security</ref>. This data was also being sent in plain-text undermining the privacy of the users.

==Consumer response==
On Reddit, consumers are constantly inquiring about steps to remove the Adobe DRM, as it is obstructing the end-users method of being able to comfortably read the ebooks they have purchased. One of the multiple examples, can be seen at the following link: https://www.reddit.com/r/DataHoarder/comments/xvct89/adobe_digital_editions_drm/.

==Adobe Ebook DRM Removal==
In the Abbey House Media v. Apple Inc ruling on an ebookstore notifying users of how to remove ebook DRM, a judge has ruled that telling users to remove DRM from books they have legally purchased is "not contributory copyright infringement"<ref>https://www.eff.org/document/abbey-house-media-v-apple-inc</ref><ref name=":3">https://www.eff.org/deeplinks/2014/12/pointing-users-drm-stripping-software-isnt-copyright-infringement-judge-rules?language=en</ref>. The summary of this case being that the removal of DRM protection on books in non-infringing cases of the Digital Millennium Copyright Act (DMCA) does not necessarily lead to the piracy of digital books<ref name=":3" />.

An online persona known as ApprenticeAlf, has also gone ahead to create a tool to remove DRM as well from multiple forms of ebook DRM, not only Adobe's. This can be found here: https://apprenticealf.wordpress.com/2012/09/10/drm-removal-tools-for-ebooks/.

An external guide on removing Adobe ebook DRM on a Debian-based system exists on https://www.harisqazi.com/configurations/digital-books#adobe-drm-removal-linux. This guide serves as a complete walk-through to set up a system to remove the Adobe ebook DRM leveraging multiple publicly available tools. A copy of this guide can be found archived on archive.org as well: https://web.archive.org/web/20250209023155/https://www.harisqazi.com/configurations/digital-books/#adobe-drm-removal-linux.

==References==
{{reflist}}
[[Category:Digital rights management]]
[[Category:Adobe]]

Consumer Rights Wiki:Categorization

2025-02-09T17:34:10Z

Waldo: /* Incident articles */ Grammar

[[File:Company-product category system overview.png|thumb|An overview of the company-product category system.]]
This article describes how categories are chosen for different types of pages. This is useful for users who want to help maintain the wiki by clearing out uncategorized pages ([[Special:UncategorizedPages|list]]), uncategorized categories ([[Special:UncategorizedCategories|list]]) and wanted categories ([[Special:WantedCategories|list]]).

Users who frequently create new pages also need this information.

== Articles ==

[[File:Incident categories.png|thumbnail]]
=== Incident articles ===

An incident can apply to a specific product, service, website, piece of software, a whole product line or a company (and/or all of its products).

An incident that applies to a specific product, service, website or piece of software should belong to that category. For example, the [[Pixel 4a Battery Performance Program]] article should belong to <code><nowiki>[[Category:Pixel 4a]]</nowiki></code>.

An incident that applies to a whole product line should belong to that product line's category.

An incident that applies to all of a company's products, or that should be known by anyone considering paying for one of their products, should belong to the company's category.

Incidents should also be categorized according to the categories in [[:Category:Incidents]]. These categories are a work in progress, and this section will be updated once a system has been established.

[[File:Screenshot of top of Nike page.png|thumbnail|An example of a company article]]
<span id="Company pages"/>

=== Company articles ===

[[File:Company category.drawio.png|thumbnail|Company '''articles''' belong to their corresponding category. Company '''categories''' can belong to multiple categories, each of which can also belong to multiple categories, with the top level ones belonging to the [[:Category:Companies|Companies]] category.]]
Company '''articles''' belong to their respective category. For example, the [[Sony]] article belongs to <code><nowiki>[[Category:Sony]]</nowiki></code>.

<span id="Product articles"/>
<span id="Product line articles"/>
<span id="Service articles"/>
<span id="Website articles"/>
<span id="Software articles"/>
<span id="Product pages"/>
<span id="Products"/>
=== Product, product line, service, website and software articles ===

[[File:Product line category.png|thumbnail|'''Articles''' belong to their corresponding category. '''Categories''' can belong to multiple categories, each of which can also belong to multiple categories, with the top level ones belonging to the [[:Category:Products|'''Products''']] category. '''A category page should belong to the manufacturer, service provider and/or developer's category page.''']]
Product line, service, website and software articles belong to their respective category. For example, the [[Google Pixel]] article belongs to <code><nowiki>[[Category:Google Pixel]]</nowiki></code>.

== Categories ==
=== Company categories ===
==== Rules ====

Company '''categories''' are categorized [[:Category:Companies|by industry]]. To avoid confusion, they are categorized based on how the corresponding article is categorized on Wikipedia.

When transferring the categories from the corresponding Wikipedia article, the following apply:
* Categories must describe the company in a way that relates to the products and services it provides.
* Categories do not contain information about the year or country of establishment. These are not important for the purposes of this wiki.
* Categories that belong to the "Companies by industry" category on Wikipedia belong to the [[:Category:Companies|Companies]] category on this wiki.

==== Example ====

As an example, consider the Wikipedia page for [[wikipedia:Sony|Sony]], one of the companies with the most categories on Wikipedia:

[[File:Screenshot of Sony Wikipedia article categories.png|484x190px]]

The following categories do not describe Sony in a way that relates to its products and services:
* TOPIX 100
* 1950s initial public offerings
* Belgian Royal Warrant holders
* Companies in the Nikkei 225
* Companies listed on the New York Stock Exchange
* Companies listed on the Tokyo Stick Exchange
* Conglomerate companies based in Tokyo
* Mitsui

Examples of categories on other pages that do not relate to the company's products and services include:
* Privately held companies
* Family-owned companies
* Multinational companies

Here are a few categories with years or countries of establishment removed:
* Computer companies of Japan → <code><nowiki>[[Category:Computer companies]]</nowiki></code>
* Electronics companies established in 1946 → <code><nowiki>[[Category:Electronics companies]]</nowiki></code>

<div class="mw-collapsible mw-collapsed">
Click "[Expand]" on the right to view the final list of categories at the bottom of the [[:Category:Sony]] page.

<pre class="mw-collapsible-content">
[[Category:Computer companies]]
[[Category:Computer hardware companies]]
[[Category:Computer storage companies]]
[[Category:Computer systems companies]]
[[Category:Display technology companies]]
[[Category:Electronics companies]]
[[Category:Headphones manufacturers]]
[[Category:Lens manufacturers]]
[[Category:Loudspeaker manufacturers]]
[[Category:Microphone manufacturers]]
[[Category:Netbook manufacturers]]
[[Category:Photography equipment manufacturers]]
[[Category:Portable audio player manufacturers]]
[[Category:Radio manufacturers]]
[[Category:Software companies]]
[[Category:Video equipment manufacturers]]
</pre>
</div>





Articles can be about a combination of products, product lines, services, websites and software. The distinction between some of these terms is vague, so this wiki chooses to take liberties from Wikipedia's system.

Product categories are treated differently, so they are discussed first.

[[File:Product category.png|thumbnail]]
<span id="Product categories"/>
=== Product categories ===

A product's category page belongs to the product line's category page. For example, [[:Category:Pixel 4a]] belongs to <code><nowiki>[[Category:Google Pixel]]</nowiki></code>.

Some products, such as [[wikipedia:Google Glass|Google Glass]], do not belong to a line of products. These products should be categorized as if they themselves are product lines, i.e. they should follow the rules in the following two sections.

<span id="Product line categories"/>
<span id="Service categories"/>
<span id="Website categories"/>
<span id="Software categories"/>
=== Product line, service, website and software categories ===

==== Rules ====

A category page should belong to the manufacturer, service provider and/or developer's category page. For example, [[:Category:Google Pixel]] should belong to [[:Category:Google]].

Categories are also categorized by type. To avoid confusion, they are categorized based on the categories on Wikipedia.

When transferring the categories from Wikipedia, the following apply:
* Categories must describe the type of product, service, website or software.
* Categories do not contain extra information unrelated to the type. This extra information should be omitted.
* Categories that belong to the "<thing> by type" category on Wikipedia belong to the "<thing>" category on this wiki.
* When categorizing product lines, categories are sourced from the following pages on Wikipedia if they exist:
** Any product article.
** That product's corresponding category.
** The product line's article.
** That product line's corresponding category.

==== Example ====

As an example, consider the Google Pixel product line. Categories can be sourced from the following articles on Wikipedia:
* Pixel 4a
* Category:Pixel 4a (does not exist; skip)
* Google Pixel
* Category:Google Pixel

The categories on Wikipedia follow. These categories should be modified according to the rules outlined above.
[[File:Screenshot of Pixel 4a categories on Wikipedia.png|474x64px]]
[[File:Screenshot of Google Pixel categories on Wikipedia.png|474x28px]]
[[File:Screenshot of Category-Google Pixel categories on Wikipedia.png|596x28px]]

The following categories do not describe a type of product:
* Google hardware
* Computer-related introductions in 2013

Here are a few categories with extra information removed:
* Discontinued smartphones → <code><nowiki>[[Category:Smartphones]]</nowiki></code>
* Mobile phones introduced in 2020 → <code><nowiki>[[Category:Mobile phones]]</nowiki></code>

<div class="mw-collapsible mw-collapsed">
Click "[Expand]" on the right to view the final list of categories at the bottom of the [[:Category:Google Pixel]] page.

<pre class="mw-collapsible-content">
[[Category:Google]]
[[Category:Android (operating system) devices]]
[[Category:Mobile phones]]
[[Category:Smartphones]]
[[Category:Tablet computers]]
</pre>
</div>[[Category:CAT]]

[[File:Company-product category system overview.png|thumb|An overview of the company-product category system.]]

== Rationale ==

=== Introduction ===

This section explains the rationale for the current design of the company and product category hierarchy. It approaches the problem of a reader trying to find all incidents associated with a product they're considering purchasing.

In order to learn about the consumer protection flaws of a product, the reader will search for the product on this wiki to see if there are any flaws related to that product specifically. This will land the user at the product's article.

=== Duplication of information ===

There is some information that cannot be represented on the product's article because it affects multiple products. Information that affects multiple products cannot be repeated across those product pages because this information duplication would greatly increase the work associated with improving and amending the information.

In order to avoid repeating the information, it can be extracted into a separate article that covers all affected products. This article must be linked to from the product article, as shown by the blue arrow in the diagram nearby.

As an example, consider information about an issue affecting all Pixel devices. This information can't be repeated across all Pixel product pages for the reasons mentioned above. It needs to be extracted into a separate article. This is a product line article. The product article must link to the product line article so that the user can easily navigate to it.

Some issues apply to all of Google's products, not just its Pixel devices. This information can't be repeated across all the product line articles, so it needs to be extracted into a separate article. This is a company article. The product line article must link to the company article.

=== The importance of product line articles ===

In order to reduce the amount of articles, a contributor may consider moving the product line information to the company article. However, when the user, considering buying the product, looks at the company article, they have to wade through information about product lines that they are not interested in. Thus, product line articles are critical for ensuring that readers only read about incidents that affect the products they are considering buying.

=== Conclusion ===

To recap the user's process: The wiki contains a product article, a product line article and a company article. The user lands on the product article page because they searched for it. This article does not contain all incidents affecting the product, so they navigate to the product line article. After that, they navigate to the company article. None of these articles contain incidents that do not affect their product.

Adobe Digital Editions' ebook DRM

2025-02-09T17:32:19Z

Waldo: Reverted edit by Waldo (talk) to last revision by Harisfromcyber

Adobe Digital Editions' ebook DRM

2025-02-09T17:32:11Z

Waldo: Re-add placeholder box since the section's title hasn't been changed yet

Modern-day ebook publishers have been utilizing various forms of [[Digital rights management|digital-rights management]] (DRM) to protect the books they sell to make sure that "copyright laws are respected and that authors and publishers are fairly compensated" <ref name=":1">https://help.barnesandnoble.com/hc/en-us/articles/5445106302107-DRM-for-NOOK-Content</ref>. However, the end user who purchases the content legally ends up being restricted in what they are able to do with the ebook once they have purchased it. One of Adobe's version of this DRM is called "Adobe Digital Editions" which is the client the user uses to read their ebooks.

== Background ==
Adobe eBook Platform is a platform for publishers to leverage when selling ebooks. This includes the following software suite: Adobe InDesign® CC software, Adobe Content Server software, the Adobe Reader® Mobile Software Development Kit (SDK), and Adobe Digital Editions <ref name=":0">https://www.adobe.com/content/dam/cc/us/en/solutions/ebook/adobe_ebook_platform_whitepaper.pdf</ref>. A summary of each of the software is outlined below at a high level (mostly extracted from the Adobe white paper on the platform):

* Adobe Content Server - "Adobe Content Server allows publishers, retailers, distributors, and libraries to host and manage eBook distribution. This server software encrypts PDF and EPUB eBook files and allows publishers and retailers to manage the rights on the eBook files they distribute <ref name=":0" />".
* Adobe Reader Mobile SDK - The SDK " allows e-reader device manufacturers and eBook application developers to support EPUB and PDF files protected by Content Server in their products. It enables tethered and over-the-air downloads so that consumers can order eBooks directly through their devices or “side-load” them by copying files from their desktops to their mobile devices" <ref name=":0" />.
* Adobe InDesign - InDesign allows the publishers to export EPUB and EPUB3 files from print layouts. This also allows publishers to export ebooks to hardware such as the "Sony Reader, the Barnes & Noble nook, and smartphones, as well as personal computers using Microsoft® Windows® or Mac OS" <ref name=":0" />.
* Adobe Digital Editions (ADE) - "Adobe Digital Editions is a free, lightweight desktop reading application for PC and Mac that allows eBook consumers to easily download and organize their eBooks easily. Consumers can read their eBooks online and offline, transfer copy-protected eBooks from their personal computers to other devices, organize eBooks into a custom library, and annotate page" <ref name=":0" />.

All these solutions come together to give publishers control over their ebook content. The main product discussed on this page is Adobe Digital Editions (ADE). ADE allows for the following benefits <ref>https://www.adobe.com/solutions/ebook/digital-editions.html</ref>:

* Download and transfer of books between devices
* EPUB3 support
* Keyword search across ebooks
* Voiceover accessibility
* Multi-language support
* Bookmarking, highlighting, and note support
* Support for borrowing ebooks from libraries
* ebook printing (publishers decide whether they opt-in for allowing printing or not)
* EPUB, EPUB3 and PDF support

ADE also has system requirements, as it is an application running on your system <ref>https://www.adobe.com/solutions/ebook/digital-editions/tech-specs.html</ref>:

Windows:

* Intel® Pentium® 4 processor or later
* Windows® 7 (32 or 64 bit running in 32-bit mode) or later
* 512MB of RAM (1GB recommended)
* 40MB of available hard-disk space

Mac OS:

* Intel Core™ Duo or faster processor
* Mac OS X v10.8 or later
* Compatible with Apple Retina Display
* 512MB of RAM (1GB recommended)
* 75MB of available hard-disk space

iOS:

* Minimum requirement 9.0 or later.
* Compatible with iPhone and iPad.

Android:

* Minimum requirement 4.4 or later.
* Compatible with the Mobile and Tablet.

==[Incident]==
{{Placeholder box|Change this section's title to be descriptive of the incident.}}

With the release of the platform and specifically the Adobe Digital Edition application, consumers have been restricted on what they are allowed to do with ebooks that they have purchased. Although unlimited downloads are mentioned by publishers and ebook sites, those are tied to an account <ref name=":12">https://help.barnesandnoble.com/hc/en-us/articles/5445106302107-DRM-for-NOOK-Content</ref>. This means that if access to an account is lost, then the access to those ebooks is lost as well. eBooks.com is one of the various e-bookstores that sells both non-DRM and DRM books leveraging ADE. When purchasing an ebook from them, you get a .acsm file. This format only works with the Adobe Digital Editions application. The user needs to create an Adobe account (after already creating an ebooks.com account) in order to add the book to their account. ADE (pertaining to purchases from ebooks.com) allows for authorization of up to 10 devices with a single Adobe ID, but only one computer <ref name=":2">https://support.ebooks.com/hc/en-gb/articles/360000726656-What-is-DRM-DRM-FAQs</ref>. The end user would not be able to read a book on a home computer and then later on a laptop simultaneously due to this limitation. Barnes and Noble uses ADE as well for their ebooks, with their limitations being a bit different in comparison to ebooks.com's. They have 4 versions of DRM types they leverage for the books sold on their site <ref>https://help.barnesandnoble.com/hc/en-us/articles/5445106302107-DRM-for-NOOK-Content</ref>:

# Consumer DRM (eBook)
## Unlimited downloads
## Up to six (6) devices/computers
## No copying and printing
# Business DRM (eBook)
## One (1) download
## Up to one (1) device/computer
## No copying and printing
# Education DRM (eTextbook)
## Two (2) downloads
## Up to two (2) devices/computers
## Limited copying and printing
# Hard DRM
## Six (6) downloads
## Up to six (6) devices/computers
## Used for Case Studies made available by professors and specific courses

In both cases, the user is limited to only a certain number of devices and has to constantly authorize and un-authorize readers in order to be in compliance. This leads to a lack of autonomy for the user who has purchased the book. In addition, with the Barnes and Noble "Consumer DRM" section, a user is not able to print the ebook they have purchased either. Going back to the ebooks.com example, ebooks.com has a bit more control on the consumer stating that due to DRM: "the amount of printing or copying and pasting you can do may be restricted, or prevented entirely. It will also determine whether the read aloud functionality is enabled for the ebook or not" <ref name=":2" />.

With ADE, a consumer will always need to download the application to access books that they have purchased. This is under the assumption that the user is able to have the technical know-how to do all the ADE overhead in order to finally read the book they have purchased. In addition, individuals who do not have access to the most modern technology, thus not being able to download ADE on their system, are also then prevented from reading ebooks they have purchased.

If a user were to be able to remove DRM from a ebook purchased from an e-bookstore leveraging ADE, they would then be breaching the compliance with an end-user license agreement or a customer license. On ebook.com's customer license page, they mention the following: "You promise to keep any eBook in the form in which it was supplied to you. We may include other information (including information identifying the author, the copyright owner, or the terms upon which the eBook is supplied) to any eBook supplied to you. You promise not to circumvent any measures that we have taken to protect the rights in the eBook that we have supplied, including removing this information or otherwise facilitating an infringement of copyright" <ref>https://www.ebooks.com/en-us/information/customerlicense/</ref>. Although no lawsuits have been found being documented (as of writing this article), the door for this kind of consumer abuse is still present.

In 2014, the Electronic Frontier Foundation had published an article regarding how Adobe Digital Edition was tracking its end users by logging what the end-user reads and what happens to those files <ref>https://www.eff.org/deeplinks/2014/10/adobe-spyware-reveals-again-price-drm-your-privacy-and-security</ref>. This data was also being sent in plain-text undermining the privacy of the users.

==Consumer response==
On Reddit, consumers are constantly inquiring about steps to remove the Adobe DRM, as it is obstructing the end-users method of being able to comfortably read the ebooks they have purchased. One of the multiple examples, can be seen at the following link: https://www.reddit.com/r/DataHoarder/comments/xvct89/adobe_digital_editions_drm/.

An online persona known as ApprenticeAlf, has also gone ahead to create a tool to remove DRM as well from multiple forms of DRM, not being limited to Adobe's. This can be found here: https://apprenticealf.wordpress.com/2012/09/10/drm-removal-tools-for-ebooks/.

==References==
{{reflist}}
[[Category:Digital rights management]]
[[Category:Adobe]]

Template:CompanyPreload

2025-02-09T17:30:19Z

Waldo: Fix typo

{{InfoboxCompany
| Name = {{PAGENAME}}
| Type =
| Founded =
| Industry =
| Official Website =
| Logo =
}}{{Placeholder box|An introductory paragraph starting with "'''{{PAGENAME}}''' is a ...<ref name":0">ref goes here</ref>"}}

$1
==Consumer impact summary==
{{Placeholder box|Overview of concerns that arise from the company's conduct regarding (if applicable):
* User Freedom
* User Privacy
* Business Model
* Market Control}}

$2
==Incidents==
{{Placeholder box|If the company page is short enough and/or the incident is not deserving of it own page, add incidents below in sub-sections (including the points outlined in [[Consumer_Action_Taskforce:Sample/Incident/Help]]) and delete the list after this box.

If the company has various incidents listed and/or this page is getting too long, do not add sub-sections, and instead complete the list after this box.}}
This is a list of all consumer protection incidents this company is involved in. Any incidents not mentioned here can be found in the [[:Category:{{FULLPAGENAME}}|{{PAGENAME}} category]].
* [[Example incident one]] (date): Short summary of the incident (could be the same as the summary preceding the article).
* [[Example incident two]] (date):

==Products==
{{Placeholder box|This is a list of the company's product lines with articles on this wiki.
* [[Example product line one]] (release date): Short summary of the product's incidents.
* [[Example product line two]] (release date):}}

==See also==
{{Placeholder box|Link to relevant theme articles or companies with similar incidents.}}

==References==
{{reflist}}

<includeonly>[[Category:{{PAGENAME}}]]</includeonly>
<noinclude>
[[Category:Article sample templates]]</noinclude>

User:Waldo

2025-02-09T14:25:02Z

Waldo: /* What I've done */ Add more stuff I'm done

__NOTOC__
== What I need to do ==

# Learn the API
# Start categorizing
# Finish [[Categorization]]
# Learn Lua

== What I've done ==

=== Moved all articles under one root category ===

# Before I started, there was no structure in the categories.
# Created the [[:Category:Wiki root|Wiki root]] category and the initial structure, establishing some naming conventions along the way.

=== Wrote documentation for categorization ===

# Worked with Kostas, Keith and Mingyee to design a good category system.
# Wrote [[Categorization]], including making the diagrams.

=== Wrote a page for contributors writing their first article ===

[[Consumer Action Taskforce:Write your first article!|Write your first article!]]

=== Added some color to the root category ===

See [https://wiki.rossmanngroup.com/index.php?title=Category:Wiki_root&oldid=7614 revision 7614].

=== Designed the 2x2 grid main page ===

See [https://wiki.rossmanngroup.com/index.php?title=Main_Page&oldid=7931 revision 7931].

== Subpages ==

{{Special:Prefixindex/{{FULLPAGENAMEE}}/
|hideredirects=1
}}

Steam

2025-02-09T10:27:27Z

Waldo:

{{ProductPage
|infobox_logo=Steam.png

|infobox_1_key=Release Year
|infobox_1_value=2003

|infobox_2_key=Product Type
|infobox_2_value=Video-game distribution platform

|infobox_3_key=In Production
|infobox_3_value=Yes

|infobox_4_key=Official Website
|infobox_4_value=https://store.steampowered.com

|description='''Steam''' is a digital storefront and service for video-game distribution, operated by [[Valve|Valve Corporation]]. Launched in 2003, it has grown to become the largest digital-distribution platform for PC gaming, with over 130 million monthly active users as of 2024. The platform offers services for [[digital rights management]] (DRM), server hosting, video streaming, and social networking.<ref>[https://www.valvesoftware.com/en/about "At Valve we make games, Steam, and hardware."] ''Valve Corporation''. 2024. Retrieved January 17, 2025.</ref>

|summary_privacy_1=Collects extensive personal data including email, location, payment details, and device information<ref name="privacy-policy">[https://store.steampowered.com/privacy_agreement/ "Privacy Policy Agreement."] ''Steam''. February 14, 2024. Retrieved January 17, 2025.</ref>
|summary_privacy_2=Records and stores all user communications through platform features<ref name="privacy-policy" />
|summary_privacy_3=Keeps certain user data indefinitely for "gameplay consistency" even after account deletion<ref name="privacy-policy" />
|summary_privacy_4=Tracks gaming behavior including preferences, progress, playtime, and device usage<ref name="privacy-policy" />
|summary_privacy_5=Shares user data with game developers and third-party service providers<ref name="privacy-policy" />
|summary_privacy_6=Makes user profile data publicly available through Steamworks API<ref name="privacy-policy" />
|summary_privacy_7=Uses cookies and similar technologies for tracking across websites<ref name="privacy-policy" />
|summary_privacy_8=Retains transaction data for up to 10 years after account closure<ref name="privacy-policy" />

|summary_freedom_1=Users do not own purchased games, only receive limited licenses<ref name="subscriber-agreement">[https://store.steampowered.com/subscriber_agreement "Steam Subscriber Agreement."] ''Steam''. September 26, 2024. Retrieved January 17, 2025.</ref>
|summary_freedom_2=Can terminate access to paid content at Valve's discretion<ref name="subscriber-agreement" />
|summary_freedom_3=No right to transfer or resell purchased games<ref name="subscriber-agreement" />
|summary_freedom_4=Imposes regional restrictions on game activation and playing<ref name="subscriber-agreement" />
|summary_freedom_5=Can unilaterally modify terms with 30-day notice<ref name="subscriber-agreement" />
|summary_freedom_6=Mandatory client updates required to access library<ref name="subscriber-agreement" />
|summary_freedom_7=Users must accept all changes to maintain access to purchased content<ref name="subscriber-agreement" />
|summary_freedom_8=No option to opt out of core data collection while using service<ref name="privacy-policy" />

|summary_transparency_1=Provides clear refund policy for games (any game played less than 2 hours within 14 days)<ref name="subscriber-agreement" />
|summary_transparency_2=It will mainly reference instances where the product prevents inspection or is intentionally confusing
|summary_transparency_3=Maintains detailed system requirements information for all games<ref name="subscriber-agreement" />
|summary_transparency_4=Offers comprehensive privacy policy in accessible language<ref name="privacy-policy" />
|summary_transparency_5=Unclear processes for account termination and data removal<ref name="privacy-policy" />
|summary_transparency_6=Limited transparency about content moderation decisions<ref name="subscriber-agreement" />
|summary_transparency_7=Vague about specific data retention timeframes<ref name="privacy-policy" />
|summary_transparency_8=No clear disclosure of recommendation algorithm factors<ref name="privacy-policy" />

|incidents_1_title=Modification to terms-of-service
|incidents_1_date=Sep. 2024
|incidents_1_text=
In September 2024, Steam implemented significant changes to its subscriber agreement that altered user rights and game ownership terms. Additionally, it removed [[Forced Arbitration|forced arbitration]] from the Steam Subscriber Agreement.<ref>Carpenter, Nicole (September 27, 2024). [https://www.polygon.com/explained/457557/valve-arbitration-steam-subscriber-agreements "Valve removes arbitration from its Steam agreements — here's what that means for you"]. ''Polygon''. Retrieved January 17, 2025.</ref><ref>Rossmann, Louis (September 27, 2024). [https://www.youtube.com/watch?v=1f81qXxggo8 "Steam altered the terms of the sale; you'll be happy they altered it further!"] ''YouTube''. Retrieved January 17, 2025.</ref> Key changes included:
*Enhanced ability to terminate accounts for violations
*Additional data collection and sharing provisions
*Modified dispute resolution procedures

|incidents_2_title=Customer database hack
|incidents_2_date=Oct. 2011
|incidents_2_text=In October 2011, Valve was forced to temporarily close the Steam Community forums following security-breach concerns. Days later, the company confirmed that hackers had compromised one of its customer databases. The compromised database contained user information, including encrypted credit-card numbers, billing addresses, purchase histories, email addresses, and encrypted passwords for Steam accounts.<ref>Johnson, Casey (November 10, 2011). [https://arstechnica.com/gaming/2011/11/valve-confirms-steam-hack-credit-cards-personal-info-may-be-stolen/ "Valve confirms Steam hack: credit cards, personal info may be stolen"]. ''Ars Technica''. Retrieved January 17, 2025.</ref>

At the time of disclosure, Valve stated they had no evidence that the encrypted credit-card numbers or personally identifying information had been taken, nor was there evidence that the encryption on the credit-card numbers or passwords had been cracked. Nevertheless, they advised users to closely monitor their credit-card activity and statements as a precautionary measure.
}}

== References ==
{{reflist}}

[[Category:Services]]
[[Category:Valve Corporation]]

Minecraft Beta pre-1.8's lack of authentication

2025-02-09T10:20:29Z

Waldo: Categorize according to template (good article btw, some more references would be good though)

Minecraft is a video game made by Mojang Studios (owned by [[Microsoft]] and Xbox Game Studios since 2014). It was officially released on 18th September 2011, but development builds were publicly available since 17 May 2009.

Affected versions covered by this article range up to July 8, 2011.

==Background==
In version Beta 1.8, Mojang has changed the endpoint that's used for authentication on Minecraft servers from "www.minecraft.net" to "session.minecraft.net". Unknown amount of time later the original endpoint used for the authentication was shut down, breaking authentication support for several old Minecraft versions, despite no actual changes in the behaviour of the endpoint. The latter endpoint still works, despite being insecure (supports HTTP requests, with token being within the URL parameters) - this means that the shutdown is likely not a security concern.

Lack of authentication has caused several Minecraft servers to:

*lose part of the playerbase due to a need of modding the game client (and server) to fix the authentication issue,
*become completely insecure by allowing non-premium Minecraft users to join (e.g. opens the risk of botting the server, or brute-forcing user login passwords),
*break the EULA of the game due to allowing non-premium Minecraft users to join their server.

==Timeline==

===March 30th, 2014===
A post titled "[https://bukkit.org/threads/cant-connect-to-my-beta-1-7-3-bukkit-server.250510/ Cant connect to my beta 1.7.3 bukkit server]" has appeared on bukkit.org forums - it seems to be the earliest mention of the issue, as the forum's staff member (at the time) has stated that "[https://bukkit.org/threads/cant-connect-to-my-beta-1-7-3-bukkit-server.250510/#post-2370332 older MC versions (...) no longer authenticate properly with Mojang's servers]".

===September 10th, 2019===
A user named "[https://web.archive.org/web/20200414095750/https://bugs.mojang.com/browse/WEB-1429 Rhys B]" has [https://bugs.mojang.com/browse/WEB-1429 reported a lack of authentication support] for older versions of Minecraft (affecting versions preceding Beta 1.8) on Mojang's bug reporting website, where they've explained the root cause of the issue.

===October 25th, 2021===
Mojang Studios has left their [https://web.archive.org/web/20211204004633/https://bugs.mojang.com/browse/WEB-1429 first note] on the issue, stating that they're "planning to work on this during the first quarter of 2022".

===April 27th, 2022===
The note [https://web.archive.org/web/20220429191927/https://bugs.mojang.com/browse/WEB-1429 has been changed], stating that they "will look into this during summer 2022", where Mojang staff member (at the time) stated that "it has been pushed back slightly" (see: latest comment under the [https://web.archive.org/web/20220429191927/https://bugs.mojang.com/browse/WEB-1429 archived version of the website]).

==Current situation==
The note states that they "will look into this during October-December 2022", while the issue isn't resolved to this day. It's hard to tell whether the latest note is real or not, as the Mojang's Bug Tracker's moderator has stated that the original author has "[https://bugs.mojang.com/browse/WEB-1429?focusedId=1276309&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-1276309 added an official-looking notice without consent from bug tracker staff]", but the previous notes are likely to be real (see: April 27th, 2022 on the timeline).

It's currently the most [https://bugs.mojang.com/projects/WEB/issues/WEB-1429?filter=allopenissues&orderby=watchers+DESC%2C+priority+DESC%2C+updated+DESC watched] and [https://bugs.mojang.com/projects/WEB/issues/WEB-6665?filter=allopenissues&orderby=votes+DESC%2C+priority+DESC%2C+updated+DESC upvoted] issue in the "Mojang Web Services" category, with almost 300 votes and nearly 180 viewers.

==Scale of the issue==
Nostalgia related Minecraft servers, such as [https://puucraft.net/ PuuCraft] (6,000 players total, as stated on the website) and [https://www.retromc.org/ RetroMC] (around [https://statistics.retromc.org/ 10 players daily]) still exist and run on version Beta 1.7.3 of the game - that means they're unable to authenticate their players (whether they want to or not). Any sort of "nostalgia trips" with friends also require server and client modifications to prevent bad actors from accessing their server (assuming whitelist is enabled).

==Community response==

===Securely fixing the game client===
On November 2nd, 2021 user named "craftycodie" has [https://github.com/Mojang/LegacyLauncher/pull/33 made a pull request] on Mojang's GitHub repository, [https://github.com/Mojang/LegacyLauncher/ LegacyLauncher], which is Mojang's way of running older versions of Minecraft in the modern launcher, that's capable of modifying the game's behaviour - it fixes issues and incompatibilities that had appeared over time without having to re-release older versions of the game. The pull request made by "craftycodie" fixes several issues, including authentication support. It's using Mojang's latest authentication methods (only in versions older than Beta 1.8 as of now, with a suggestion of improvement), which are way more secure in comparison to the no longer working approach. Mojang has never accepted nor responded to the pull request, despite it having 30 reactions, 28 approves and 27 comments from the GitHub community.

===Securely fixing the game server===
Released on October 1st, 2020 by user named "craftycodie", [https://github.com/craftycodie/OnlineModeFix OnlineModeFix] is one of the ways of fixing the authentication issue for Minecraft servers. While Mojang doesn't need to patch it, because it's easy for server owners to fix the authentication method by themselves, they didn't release any fixed server files, nor solutions to the problem.

==Workarounds==
While the core issue is caused by Mojang ignoring it, there are a few more or less secure ways of fixing the issue.

===Client===

====Using an unofficial launcher====
This is the easiest, widest (and in some cases most secure) fix for the client side of the issue.

Some trusted open-source Minecraft launchers such as [https://github.com/PrismLauncher/PrismLauncher/pull/443 Prism Launcher] have implemented the craftycodie's [https://github.com/Mojang/LegacyLauncher/pull/33 pull request] to their launchers. You can use them to bring back authentication to the game.

====Using a proxy====
You can proxy all requests coming from "<nowiki>http://www.minecraft.net/game/(...)</nowiki>" to "<nowiki>https://session.minecraft.net/game/(...)</nowiki>". Note that this is still less secure than the first method, unless you proxy the request to the Mojang's [https://minecraft.wiki/w/Mojang_API#Verify_login_session_on_client latest authentication method].

====Editing the game's source code====
You can edit the game's source code, to change the old request URL (see: using a proxy). Note that Minecraft source code is obfuscated and class/field/method names vary depending on the version of the game, so there is no strict guide on how to do it - you have to manually search for the URL to replace it or patch it for even more secure experience.

===Server===

====Using open-source fixes====
This is the easiest fix for the server side of the issue.

You can use [https://github.com/craftycodie/OnlineModeFix OnlineModeFix] to fix the issue - you can use it as a plugin, or even as the launcher in the vanilla version of the server.

====Other ways====
For other ways to address the issue, see client workarounds. Note that the full authentication link slightly differs between client and server.

==References==
{{reflist}}

[[Category:Minecraft]]

Minecraft Beta pre-1.8's lack of authentication

2025-02-09T10:18:48Z

Waldo: /* Community intervention */ Rename to /* Community response */ to fit the template (please use "Create a page" in the sidebar to create new pages)

User:Waldo

2025-02-08T21:09:33Z

Waldo:

__NOTOC__
== What I need to do ==

# Learn the API
# Start categorizing
# Finish [[Categorization]]
# Learn Lua

== What I've done ==

=== Moved all articles under one root category ===

# Before I started, there was no structure in the categories.
# Created the [[:Category:Wiki root|Wiki root]] category and the initial structure, establishing some naming conventions along the way.

=== Wrote documentation for categorization ===

# Worked with Kostas, Keith and Mingyee to design a good category system.
# Wrote [[Categorization]], including making the diagrams.

=== Wrote a page for contributors writing their first article ===

[[Consumer Action Taskforce:Write your first article!|Write your first article!]]

== Subpages ==

{{Special:Prefixindex/{{FULLPAGENAMEE}}/
|hideredirects=1
}}

Template:IncidentPreload

2025-02-08T20:46:33Z

Waldo: Amend last edit

{{Placeholder box|Short summary of the incident. Usually 2-3 sentences that summarize the contents or the article.}}

==Background==
{{Placeholder box|Information about the product/service history to provide the necessary context surrounding the incident}}

==[Incident]==
{{Placeholder box|Change this section's title to be descriptive of the incident.

Impartial and complete description of the events, including actions taken by the company, and the timeline of the incident coming to the public's attention.}}

===[Company]'s response===
{{Placeholder box|If applicable, add the proposed solution to the issues by the company.}}

==Lawsuit==
{{Placeholder box|If applicable, add any information regarding litigation around the incident here.

===Claims===
Main claims of the suit.

===Rebuttal===
The response of the company or counterclaims.

===Outcome===
The outcome of the suit, if any.}}

==Consumer response==
{{Placeholder box|Summary and key issues of prevailing sentiment from the consumers and commentators that can be documented via articles, emails to support, reviews and forum posts.}}

==References==
{{reflist}}

{{Placeholder box|[[mw:Help:VisualEditor/User_guide#Editing_categories|Add a category]] named after the associated product, service, website, software, product line or company}}<noinclude>
[[Category:Article sample templates]]</noinclude>

Template:IncidentPreload

2025-02-08T20:46:11Z

Waldo: Amend last edit

Bloomberg

2025-02-08T20:37:04Z

Waldo: Make it easier to add text after each placeholder box (won't be a problem for future pages)

{{StubNotice}}

{{InfoboxCompany
| Name = {{PAGENAME}}
| Type =
| Founded =
| Industry =
| Official Website =
| Logo =
}}

{{Placeholder box|An introductory paragraph starting with "'''{{PAGENAME}}''' is a ...<ref name":0">ref goes here</ref>"}}Bloomberg is a software company with a news website that has recently changed its terms of service. The terms of service pops up in front of everything forcing you to agree to it without being able to access any of the site. This new terms of service includes forced arbitration

==Consumer impact summary==
{{Placeholder box|Overview of concerns that arise from the company's conduct regarding (if applicable):
* User Freedom
* User Privacy
* Business Model
* Market Control}}

==Incidents==
{{Placeholder box|If the company page is short enough and/or the incident is not deserving of it own page, add incidents below in sub-sections (including the points outlined in [[Consumer_Action_Taskforce:Sample/Incident/Help]]) and delete the list after this box.

If the company has various incidents listed and/or this page is getting too long, do not add sub-sections, and instead complete the list after this box.}}
This is a list of all consumer protection incidents this company is involved in. Any incidents not mentioned here can be found in the [[:Category:{{FULLPAGENAME}}|{{PAGENAME}} category]].
*[[Example incident one]] (date): Short summary of the incident (could be the same as the summary preceding the article).
*[[Example incident two]] (date):

==Products==
{{Placeholder box|This is a list of the company's product lines with articles on this wiki.
* [[Example product line one]] (release date): Short summary of the product's incidents.
* [[Example product line two]] (release date):}}

==See also==
{{Placeholder box|Link to relevant theme articles or companies with similar incidents.}}

==References==
{{reflist}}

[[Category:{{PAGENAME}}]]

Flat Earth Clock App

2025-02-08T20:15:17Z

Waldo:

{{StubNotice}}{{InfoboxProductLine
| Title = {{PAGENAME}}
| Release Year =2016
| Product Type =Mobile Social Network
| In Production =Yes
| Official Website =https://flatearthdave.com/
| Logo =Flatearthclockapp.jpg
}}"'''{{PAGENAME}}''' is a social network for "flat earthers" to connect and to provide a echo chamber among likeminded people.

the app serves a "clock" that tries (and fails) to show how day/night does progress on a Flat earth, and serves as a platform for content to reinforce science denial regarding everything we learned about our universe.

As being a "flat earther" has the common side effect of one losing real human connections/friends even family in some cases, the Creator David Weiss, capitalizes on people that are easy to manipulate, providing the platform as replacement.

The application is available in the Google Play Store<ref>Flat Earth Clock app in the [https://play.google.com/store/apps/details?id=com.flatearthsun&referrer=utm_source Google Play Store]</ref> and Apple's App Store<ref>Flat Earth Sun, Moon & Zodiac in the [https://apps.apple.com/us/app/flat-earth-sun-moon-zodiac/id1440996640 Apple App Store]</ref> respectively for a one time payment of $3 (no trial), and in-app purchases in form of a subscription for a "friend finder feature" despite being reported multiple times by serval individuals, including myself fo major breaches of security, privacy, wrong statements about collected data and breaches of EU and US regulations.

==Consumer Impacts==

*Reinforcement of Science denial
*Major violations in Privacy regulations in the US and the EU
*Data breaches spanning over multiple years including some that published all usernames, emails, locations and plain text passwords.
*publishing of Realtime Locations (latitude/longitude) of ALL registered users without consent.

==Consumer impact summary==
==Incidents==
This is a list of all consumer protection incidents related to this product. Any incidents not mentioned here can be found in the [[:Category:{{PAGENAME}}|{{PAGENAME}} category]].
{{Placeholder box|* [[Example incident one]] (date): Short summary of the incident (could be the same as the summary preceding the article).
* [[Example incident two]] (date):
Incidents affecting the entire product line can be found in the product line article: [[Product line article, or company article if there is no product line]]}}

==See also==
a comprehensive (but incomplete to protect actual members) list of the security breaches was compiled years ago, mostly ignored by the creator or used to gain more media traction by calling out the people informed him of the shortcomings.

on February 7 2025 part of this issues were released on Github<ref>[https://github.com/globesec/flatearthsun_public Release of a list of issues on Guthub]</ref> after 3 Years onf non-compliance by the creator, and a 90 Day Warning period was given.

"McToon" a notable debunker of science deniers on Youtube and a developer himself posted a video detailing some of the shortcomings and issues<ref>[https://www.youtube.com/watch?v=grjDlOIdf5Q a video detailing some of the shortcomings and issues]</ref>.

==References==
{{reflist}}

[[Category:{{PAGENAME}}]]
[[Category:Software]]

HP Printers locking functionality behind ink availability

2025-02-08T20:13:14Z

Waldo: Apply incident template (please use "Create a page" in the sidebar to create new pages)

{{Placeholder box|Short summary of the incident. Usually 2-3 sentences that summarize the contents or the article.}}
[[HP]] produces all-in-one printers, which are marketed as a complete solution for printing, scanning documents, and sending faxes. However, these printers enter an error state when the ink level in one of the cartridges is too low, disabling all functionalities—including scanning and faxing—even though these features do not require ink.<ref>https://arstechnica.com/gadgets/2023/08/the-printers-that-require-ink-to-scan-and-fax/</ref><ref>https://h30434.www3.hp.com/t5/Scanning-Faxing-Copying/can-t-scan-due-to-low-ink-I-shouldn-t-need-ink-to-scan-a/td-p/8308292</ref> HP has faced legal actions<ref>https://regmedia.co.uk/2023/08/11/freund-hp-judge-order.pdf</ref> because it sells its products as all-in-one solutions but does not clearly disclose that ink is necessary to use any of the functionalities.
==Background==
{{Placeholder box|Information about the product/service history to provide the necessary context surrounding the incident}}

==[Incident]==
{{Placeholder box|Change this section's title to be descriptive of the incident.

Impartial and complete description of the events, including actions taken by the company, and the timeline of the incident coming to the public's attention.}}

===[Company]'s response===
{{Placeholder box|If applicable, add the proposed solution to the issues by the company.}}

==Lawsuit==
{{Placeholder box|If applicable, add any information regarding litigation around the incident here.

===Claims===
Main claims of the suit.

===Rebuttal===
The response of the company or counterclaims.

===Outcome===
The outcome of the suit, if any.}}

==Consumer response==
{{Placeholder box|Summary and key issues of prevailing sentiment from the consumers and commentators that can be documented via articles, emails to support, reviews and forum posts.}}

==References==
{{reflist}}

[[Category:HP]]

Rocksmith

2025-02-08T20:10:23Z

Waldo: Update based on template

{{InfoboxProductLine
| Title = {{PAGENAME}}
| Release Year =
| Product Type =
| In Production =
| Official Website =
| Logo =
}}
{{Placeholder box|Add a 2-3 sentence introduction starting with "'''{{PAGENAME}}''' is a ...<ref name":0">ref goes here</ref>"}}

Editing later.

'''Rocksmith''' was a line of games by Ubisoft that's one of the few sources to learn guitar, and played like Guitar Hero with a real guitar. DLC was one time purchase. Game got delisted from all storefronts. It was a maior target for custom modding. Ubisoft didn't like that. They made it impossible to get a legitimate copy of in favor of Rocksmith+, which has COVERS of the previous licensed songs, no dlc transfer, and went to a expensive online-only subscription model that prevents modding.

==Consumer impact summary==
{{Placeholder box|Overview of concerns that arise from the conduct towards users of products part of the product line (if applicable):
* User Freedom
* User Privacy
* Business Model
* Market Control}}

==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]].
{{Placeholder box|* [[Example incident one]] (date): Short summary of the incident (could be the same as the summary preceding the article).
* [[Example incident two]] (date):
Incidents affecting all of the company's products can be found in the company article: [[Company article]]}}

==Products==
{{Placeholder box|This is a list of the products with articles on this wiki.
* [[Example product one]] (release date): Short summary of the product's incidents.
* [[Example product two]] (release date):}}

==See also==
{{Placeholder box|Link to relevant theme articles or product lines with similar incidents.}}

==References==
{{reflist}}

[[Category:{{PAGENAME}}]]

Rocksmith

2025-02-08T20:09:52Z

Waldo: Move text outside of placeholder box (I know it was hard to add text below the box; I've fixed this problem for new pages)

Template:ThemePreload

2025-02-08T19:44:55Z

Waldo: Add a line containing a single space character after each box to make it easier to add text in the visual editor

{{Placeholder box|Add a 2-3 sentence introduction starting with "'''{{PAGENAME}}''' is a practice in which businesses ... Per Wikipedia: ...<ref name=":1">ref goes here</ref>"}}

==How it works==
{{Placeholder box|How the practice works.}}

==Why it is a problem==
{{Placeholder box|If the theme or common term is positive for the consumer this section can be omitted.

===Point 1===

===Point 2===
}}

==Examples==
{{Placeholder box|Some examples of {{PAGENAME}} include:

*
*
*}}

==References==
{{reflist}}

<includeonly>[[Category:Common terms]]</includeonly>

<noinclude>
[[Category:Article sample templates]]</noinclude>

Template:ProductLinePreload

2025-02-08T19:44:43Z

Waldo: Add a line containing a single space character after each box to make it easier to add text in the visual editor

{{InfoboxProductLine
| Title = {{PAGENAME}}
| Release Year =
| Product Type =
| In Production =
| Official Website =
| Logo =
}}
{{Placeholder box|Add a 2-3 sentence introduction starting with "'''{{PAGENAME}}''' is a ...<ref name":0">ref goes here</ref>"}}

==Consumer impact summary==
{{Placeholder box|Overview of concerns that arise from the conduct towards users of products part of the product line (if applicable):
* User Freedom
* User Privacy
* Business Model
* Market Control}}

==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]].
{{Placeholder box|* [[Example incident one]] (date): Short summary of the incident (could be the same as the summary preceding the article).
* [[Example incident two]] (date):
Incidents affecting all of the company's products can be found in the company article: [[Company article]]}}

==Products==
{{Placeholder box|This is a list of the products with articles on this wiki.
* [[Example product one]] (release date): Short summary of the product's incidents.
* [[Example product two]] (release date):}}

==See also==
{{Placeholder box|Link to relevant theme articles or product lines with similar incidents.}}

==References==
{{reflist}}

<includeonly>[[Category:{{PAGENAME}}]]</includeonly>
<noinclude>
[[Category:Article sample templates]]</noinclude>

Template:ProductPreload

2025-02-08T19:44:31Z

Waldo: Add a line containing a single space character after each box to make it easier to add text in the visual editor

Template:IncidentPreload

2025-02-08T19:44:14Z

Waldo: Add a line containing a single space character after each box to make it easier to add text in the visual editor