A wiki is quietly building the case that Sony sold you games you don't own

What happened

A volunteer-run reference site, consumerrights.wiki, has been quietly assembling something that looks a lot like a discovery packet. The page in question — *Sony PlayStation digital game ownership lawsuit* — is a growing catalog of URLs, screenshots, and archived captures where Sony's own marketing, storefront copy, and support docs tell PlayStation customers they are "buying" or "owning" digital games. The list currently spans product pages, checkout flows, PS Store category headers, help-center articles, and legacy marketing.

The mechanic is boring and that's the point: someone is doing the unglamorous work of pinning Sony's language to a wall so it can be read back to them under oath. The page hit the Hacker News front page this week with a score around 380, in the same news cycle as ongoing scrutiny of Ubisoft (post *The Crew* shutdown), Nintendo's Wii U/3DS eShop closure, and the FTC's warning shot at storefronts that pretend a revocable license is a purchase.

The context matters. In September 2024, California signed AB 2426 into law. As of July 1, 2024 (the operative date for compliance), digital storefronts selling to California residents can't use the words "buy," "purchase," or similar language for a digital good unless they disclose, at the point of transaction, that the customer is receiving a license that can be revoked. The EU's Digital Content Directive has adjacent teeth. And the Federal Trade Commission has been vocal — after the *Crew* takedown — that "you don't own what you bought" is squarely on its radar.

Why it matters

The interesting thing here isn't the lawsuit theory. Plenty of people have argued that clicking "Buy" on a store that can later delete your library is, at minimum, deceptive. The interesting thing is the method: a distributed, low-cost, publicly auditable evidence-gathering operation that any competent plaintiff's firm — or regulator — can pick up and use tomorrow.

Traditional consumer-rights litigation collapses under the weight of discovery: you need to prove a pattern, not a slip. Screenshotting one product page won't get you past a motion to dismiss. You need to show Sony did this everywhere, consistently, for years, across surfaces the average buyer would actually see. That is expensive if a law firm has to do it from scratch. It is nearly free if a volunteer wiki has been doing it in the background, with edit histories, archive.org captures, and dated citations.

Compare this to what happened with *right-to-repair*. The movement gained real regulatory traction only after groups like iFixit spent years documenting specific, repeatable examples of manufacturer obstruction — parts pairing on iPhones, error messages on John Deere tractors, glued batteries. Once the evidence was cataloged in a form journalists and legislators could cite without a subpoena, the political cost of ignoring it dropped to zero. Consumer rights around digital ownership is following the same playbook, roughly a decade behind.

Community reaction on Hacker News split along a predictable seam. One camp argued the language is a red herring — the license terms are in the EULA, buyers agreed, case closed. The other pointed to a growing stack of regulatory decisions (FTC, CMA in the UK, French DGCCRF) that treat point-of-sale language as the operative representation, not a 40-page EULA nobody reads. The legal center of gravity has already shifted: what your marketing page says at checkout increasingly matters more than what your terms of service say on page 12.

There's also a subtler point in the wiki's approach. It's not advocating for a specific verdict. It's not accusing Sony of fraud. It's just… linking to Sony's own pages. That framing is deliberate. It's the same posture Wikipedia takes on contentious topics: neutral catalog, cited sources, let the reader (or the court) draw the inference. It also insulates the wiki from defamation exposure, which matters when your subject is a multinational with a large legal budget.

What this means for your stack

If you ship software with any of the following properties, this is now your problem, not just Sony's:

- A subscription that grants access to content the user perceives as "theirs" (media libraries, downloaded courses, purchased fonts, cloud-stored designs). - A one-time purchase that requires ongoing server availability to function (online-only games, cloud-authenticated desktop apps, DRM-gated ebooks). - Regional licensing that lets you revoke access when a distribution deal changes. - Any "purchase" flow where the underlying grant is actually a revocable license.

Audit your storefront copy the way you'd audit an auth flow: every string that says "buy," "purchase," "own," or "yours" is now a potential exhibit. The fix is mechanical and cheap — a disclosure line at the point of transaction that says, in plain English, "This is a license to access, not a transfer of ownership. Access can be revoked if [conditions]." California requires it, the EU is heading there, and the FTC has telegraphed that it considers the current status quo deceptive.

For engineering teams the implications go beyond marketing. If your product architecture assumes you can silently deprecate content, region-lock a title, or shut down a game server without customer recourse, you should assume that plan is now legally load-bearing. Build the sunset story into the SKU. Some studios are already doing this — GOG's DRM-free model, Steam's clearer "license" language, and Microsoft's recent tweaks to Xbox store copy — precisely because the compliance overhead of the alternative is climbing.

There's a related, quieter implication for indie developers on Steam, itch.io, or the App Store. When Apple or Valve gets sued, the language on your product page is inside their store's language. If a court decides a platform's "Buy" button is deceptive, remediation flows downstream to every developer on that platform. It's worth understanding what your storefront tells buyers on your behalf, because you don't control that copy but you inherit its risk.

Looking ahead

The consumerrights.wiki page will grow. Someone will file. A court, or a regulator, or an attorney general — probably California's — will use exactly this kind of catalog to build a pattern-and-practice argument. Sony will settle or lose, then quietly rewrite its storefront copy, and the industry standard will shift by a few degrees. The interesting shift isn't the outcome; it's the infrastructure. Consumer-rights enforcement in software is starting to look like open-source vulnerability tracking: distributed, cheap, permanent, and searchable. If you ship software that pretends to sell something it actually licenses, treat every marketing page as a commit into a public evidence log — because that is now, functionally, what it is.