thinkingmachines/inkling

No, I don’t think that’s accurate—or legally permissible—as described. The scenario you’re outlining sounds like a viral exaggeration or misinterpretation of a real billing glitch, not a verified AWS policy. A few direct points: The claim is almost certainly distorted. A $1.5 trillion bill is larger than AWS’s entire annual revenue. While there have been recent reports of pricing/routing glitches with AI tools (where users faced unexpectedly high charges), the figures circulating in social media are often hyperbolic. There is no credible evidence that AWS is mass-demanding trillion-dollar payments and threatening termination for non-payment. Terms of service don’t let them bill for phantom usage. Even if AWS’s ToS contain billing and termination clauses, they don’t override basic contract law or consumer protection rules. A company generally cannot enforce payment for services that were never actually rendered due to its own technical error. If a glitch caused erroneous charges, customers have strong grounds to dispute them, and courts/regulators would likely view enforcing those charges as a breach of good faith—not a valid contract enforcement. This isn’t “extortion” in the legal sense. Extortion is a specific crime involving threats to obtain property through coercion, usually with criminal intent. A billing dispute—even an aggressive or erroneous one—is a civil matter. That said, if a provider knowingly demanded payment for a confirmed system error and threatened account termination specifically to coerce unjust payment, it could violate unfair trade practice laws and contract obligations, giving customers legal recourse (disputes, chargebacks, regulatory complaints). What actually happens in these cases. Cloud providers, including AWS, have historically corrected billing errors caused by glitches and issued credits or refunds. If you’re referring to a specific recent incident with an AI coding tool, the standard resolution has been for the provider to acknowledge the error and waive the erroneous charges—not to demand payment. Bottom line: If you saw this in a specific post, treat it with skepticism and check official AWS status pages or reputable tech news. If you personally received an erroneous bill, open a billing support case with AWS; they have formal processes for adjustments. But no—AWS is not “allowed” to force customers to pay for its own trillion-dollar billing errors.

That’s not actually what the EU rule says—though the real policy is still a big deal, and it’s easy to see how the details got twisted. What the rule actually does The EU’s Ecodesign for Sustainable Products Regulation (ESPR), adopted in 2024, includes a ban on destroying unsold clothing, footwear, and accessories. Starting in 2026 for large companies (and 2030 for medium-sized ones), firms will generally be prohibited from sending unsold textile stock to landfill or incineration. Instead, they have to deal with leftovers through donation, recycling, remanufacturing, or resale. Key points: - It does NOT ban overproduction. Companies can still manufacture more than they sell. - It does NOT require them to sell 100% of what they make. There is no penalty for having unsold inventory. The penalty is for destroying that inventory. - Small and micro-enterprises are exempt, and there are reporting requirements about how much is destroyed and why. Why it was done The target is a well-documented fast-fashion practice: brands producing huge volumes, then burning or landfilling unsold goods to protect brand exclusivity and avoid discounting. The EU wants to cut textile waste (the sector is a major source of emissions and landfill) and push the industry toward circular models—better forecasting, made-to-order, rental/resale, and recycling infrastructure. What it means in practice - Not as radical as “sell everything or face fines,” but it does remove the “easy out” of trashing excess stock. - It may nudge brands to produce less recklessly, since they now have to pay to store, donate, or recycle leftovers. - Critics and loopholes: Some worry unsold goods will just be exported outside the EU and destroyed there (the “waste colonialism” risk). Others note it addresses the symptom (destruction) more than the cause (mass overproduction driven by ultra-fast fashion cycles). Enforcement and the exact delegated rules for different product categories are still being finalized. So your outrage is understandable—this is a sharp shift for an industry built on planned obsolescence and volume—but the rule is about banning the destruction of unsold goods, not banning unsold goods themselves. It’s a waste-reduction measure, not a command-economy production quota.