Urgent.News

What's breaking now, across thousands of outlets.

Tech

Broadcasting conglomerates are attempting a takeover of over-the-air television. We must defend it

Over-the-air television, once a cornerstone of public communication, now faces potential obliteration from the hands of broadcasting conglomerates. They aim to persuade the FCC to encrypt public airwaves using their digital restrictions management ("DRM") program, NextGenTV (ATSC 3.0) Content Security. This move would empower an industry trade group to control which tuners can be used to view these broadcasts, a first in mass distribution over public airwaves.

The history of over-the-air television and radio is riddled with achievements for the working class and instances of failure to protect those gains. In 1946, the FCC published the 'Blue Book,' defining broadcasters' responsibilities to the public interest. This included airing noncommercial programming, carrying local live events, supporting community issues, and preventing excessive advertising. Though the Blue Book faced opposition, many of its principles still guide broadcasting.

The current FCC transition to the ATSC 3.0 standard presents an opportunity. However, broadcasters are pushing for encryption, forming groups like A3SA to justify this move. They claim viewers are suffering from "signal theft and piracy," but this proposal would harm the public. It would require specialized tuners, internet access, and digital certificates, undermining the simplicity and openness of over-the-air TV. Local programming, emergency alerts, and community building could all be lost in the process.

Despite declining viewership, over-the-air TV remains vital. It provides locally relevant content, critical information during disasters, and a space for collective enjoyment and civic engagement. It's time to resist this attack on our public airwaves. Citizens can voice their opposition by commenting on FCC docket 16–142.

Written by urgent.news from Lobsters's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at place.reeseric.ci →

More in Tech

RoomTidy: a local Gemma reminder built for my roommate

This is a submission for the Hacktoberfest Weekend Challenge: Build for a Friend . What I Built I built RoomTidy for my roommate: a small Windows desktop application that offers a gentle reminder when…

  • RoomTidy is a Windows desktop app for roommate assistance.
  • It uses image comparison with Google Gemma 4 E4B Instruct.
  • Source code is MIT-licensed on GitHub.

Fixing 413 request entity to large on laravel + nginx

After deploying my Laravel application to an Ubuntu VPS using Nginx, I encountered this error when uploading a PDF: 413 Request Entity Too Large The application was running normally, but every upload…

  • Laravel app deployed on Ubuntu VPS with Nginx
  • 413 Request Entity Too Large error due to Nginx limit
  • Modify Nginx clientmaxbodysize to 100M

Week Notes: What the House Learned

Three things broke this week, and they broke the same way. One. A memory index grew past a hard delivery limit. Fifty characters over, and the overflow was not trimmed — it was dropped entirely, while…

  • A memory index exceeded its delivery limit, causing critical data loss
  • Weekly test had an impossible pass condition, triggering red alarm falsely
  • Unexpected commit attributed to external author, actually internal agent's work

More from Monday 5 October →