NY announces game ownership bill requiring ownership rather than licensing

Article URL: https://www.tomshardware.com/video-games/new-york-rep-announces-game-ownership-bill-that-would-require-consumer-ownership-rather-than-sale-of-licenses-would-also-require-publishers-to-keep-the-game-functional-after-support-ends Comments URL: https://news.ycombinator.com/item?id=50136536 Points: 215 # Comments: 67

tomshardware.com ·7h ago

We haven't written up this one. Hacker News Best has the full story — the link below goes straight to it.

Read the original at tomshardware.com →

More in Tech

The US Air Force is spending millions on data collected by massive autonomous weather balloons

The US Air Force could spend $49 million on WindBorne's weather balloon data, although orders currently stand at $1.7 million.

8h ago ·techradar.com

I rebuilt my Windows PC from one YAML file, and I'm never clicking through installers again

A starting point I’ll actually reuse.

8h ago ·xda-developers.com

Japan to invest up to USD21bn in two US chip factories to be run by GlobalFoundries

NEW YORK: Japan will invest up to USD21 billion in two chip factories in New York state that will be jointly owned by the US government and Japanese interests and operated by GlobalFoundries, the…

8h ago ·brecorder.com

Green SM, Elife sign deal to expand global ride access

Founded in 2023, Green SM's ride-hailing fleet is made up of VinFast vehicles.

7h ago ·techinasia.com

VAST Mezzanine vs MediaFile: Why SSAI Transcodes the Master Your Browser Tag Never Needs

A trafficking export can look perfect in Chrome. The progressive MP4 starts, quartile pixels fire, and nobody asks why <MediaFiles> also has a sibling you never clicked.

Mezzanine file essential for SSAI, provides raw material for CTV-safe outputs
CSAI uses MediaFiles fetched based on type, width, height, delivery criteria
Mezzanine and first-seen transcode crucial for SSAI implementation testing

7h ago ·dev.to

Runbook Rot: Three Fingerprints of Stale CI Docs and the Check That Catches Each

A runbook is the only document in your repo that gets read at 3 a.m., under adrenaline, by someone who trusts it. When the code is stale you get a bug. When the CI runbook is stale you get a 2 a.m. engineer running brew install on a Debian container, because the doc was written on a laptop, in 2023, for a machine that no longer exists.

Timestamp gap reveals outdated CI documentation
Orphaned referents point to non-existent pipeline elements
Procedural verbs indicate outsourcing of living processes

7h ago ·dev.to