Court settlement calls for NPR to get $36M to operate US public radio system
Mood
thoughtful
Sentiment
mixed
Category
politics
Key topics
public radio
NPR funding
media policy
A court settlement has NPR receiving $36M to operate the US public radio system, sparking discussion on the cost and potential alternatives for funding public radio.
Snapshot generated from the HN discussion
Discussion Activity
Active discussionFirst comment
32m
Peak period
19
Hour 3
Avg / period
8.2
Based on 49 loaded comments
Key moments
- 01Story posted
11/18/2025, 6:19:10 PM
1d ago
Step 01 - 02First comment
11/18/2025, 6:50:56 PM
32m after posting
Step 02 - 03Peak activity
19 comments in Hour 3
Hottest window of the conversation
Step 03 - 04Latest activity
11/19/2025, 2:08:59 AM
17h ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
Or, what if a hurricane or ice storm knocks out some internet connectivity? That would be a time when you really want to broadcast a message to anyone with a cheap fm/am radio.
Cheaper isn't always the metric here.
Is affected by? No idea, but I'm sure there's some cloudflare rep convincing you that you need cloudflare to make sure your high-availability stream stays highly available when just yesterday azure got a ddos measured with Tbs. Just not today... today those cloudflare reps happen to be busy.
Point is, radio comms serve a public utility that often is a Plan-B if internet links go down. Multicast it onto your podcatcher of choice, sure, but don't make that your backbone.
...
I guess HN is the new Reddit. Downvotes, not a single response. You can do better, HN.
The actual radio equipment is a tad more sophisticated - and in poor areas (where it's barely hanging on) is held together with spit, glue, and prayers (exaggeration, joke, but aspects of it are true).
Believe it or not, the RF cables are (in many cases) more expensive than the radios themselves.
Background: Computer systems, radio systems, General class HAM, but certainly not an expert.
Please don't post comments saying that HN is turning into Reddit. It's a semi-noob illusion, as old as the hills.
Presumably this would be feasible for most populated areas, but broadband availability is so crap outside of urban/suburban, I bet half of those really remote stations are already getting their Internet over Starlink or Hughesnet.
Now, I think there are plenty of reasons that the satellites (which are already in the sky, presumably) are probably more robust in the face of emergencies than the entire Internet infrastructure.
If I may steelman a good counterargument: "The Internet itself is supposed to be resilient to nuclear war!"
True, but that doesn't mean outages of critical pinch points like AWS, Azure and Cloudflare don't constantly affect even services like GitHub that have huge budgets. A fully robust Internet solution with a ton of high-uptime redundancy in many POPs nationwide would likely cost more than maintaining the satellite systems.
(And these aren't remote/unpopulated areas: you can find plenty of satellite dead zones 2-3 hours outside of NYC in the Catskills.)
Yes, I agree that satellite coverage is not 100%. But neither is radio.
It's the radio stations who are in charge of situating their reception equipment where it can see the sat, and also for figuring out how to best broadcast to their served area (e.g. AM and/or FM? Tower height, power, setting up some translator stations on a different frequency to serve outlying areas, giving the feed to local cable systems to be sent with TV service, etc.)
I've had the same experience as you around remote places, but those places were generally the flat-and-desolate kind :-)
I remember this being quite an issue trying to target geosync broadcast satellites like DirectTV/Dish. Even being in the shadow of a relatively small hill could block access if your location and local topology happened to create an unfortunate alignment. I've naively assumed Starlink's rotating constellation of thousands of LEO satellites reduces how often this is an issue - but maybe it doesn't?
Most stations can also receive this programming over the internet, another reason for the satellite system is that it provides a completely redundant path for programming delivery. This is important for general reliability but especially so in an emergency.
Historically, radio networks distributed their programming over leased telephone lines. Satellite took over because it was cheaper. That gap has probably narrowed as terrestrial communications infrastructure continues to expand, but the internet struggles with low-latency real-time media, and an arrangement like leased fiber wavelengths to member stations would still be more expensive than the satellite system. There's a lot of member stations in a lot of places, satellite reaches all of them at once.
Is that true? Round trip to/from geostationary satellites is about 240ms.
And, with most stations using HD encoding, which adds 8 seconds to the transmission delay, any network latency isn't going to be that important anyway.
https://en.wikipedia.org/wiki/Public_Radio_Satellite_System
> In 2007, the SOSS was retired for the newest and current system of the PRSS, the ContentDepot. The ContentDepot no longer uses linear feeds of SCPC-based digital audio bitstreams like the SOSS. Instead, it uses a dedicated TCP/IP-based one-way connection uplinked via satellite from PRSS, which is received by a storage receiver (a combination satellite data receiver & file server) manufactured by International Datacasting [5]. Program feeds are requested and set up at a special internet-accessible web site (known as the ContentDepot Portal) that member stations can log on to, where they can subscribe to specific programs and live feeds. The subscribed programs are then delivered via satellite as a file transfer to the storage receiver in the form of MP2-encoded ACM-based WAV files, which then can be imported into a station's automation and/or playback system.
> Live feeds are sent in the ContentDepot system as streaming MP2 audio, sent over the same satellite transponder, but as an IP multicast stream (as opposed to a file transfer for pre-recorded programs) which is decoded by a special streaming audio receiver (called a stream decoder) set to the IP multicast addresses assigned for live audio streams on the satellite transponder used by ContentDepot.
> The newest generation of ContentDepot hardware for the PRSS, as of 2014 and also manufactured by International Datacasting, is a special version custom-manufactured for PRSS of their commercially available "Superflex Pro Audio" receiver. It combines both the stream decoder for live programming and storage receiver for pre-recorded programming in one rack-mounted system, in previous comparison to separate units for live decoding and program storage respectively with the introduction of ContentDepot.
> Some components of the previous SOSS still are in use in the ContentDepot era: one of the ABR-700 demods (as well as the downconverter) is still used by NPR as a "squawk box" for verbal announcements regarding programming to NPR stations
What would it mean to have one-way communication over TCP? Don't you need to send the acknowledgements back?
In the case where you don't expect a response, you can still rely on the rudimentary error checking of TCP (checksum and sequence numbers) to detect when damaged or dropped - but this smells like a custom implementation of the protocol.
But this is a scientific wild ass guess.
And because of congressional action not executive, so probably legal.
> The Corporation for Public Broadcasting, the conduit for federal funds to NPR and PBS, announced on Friday that it is beginning to wind down its operations given President Trump has signed a law clawing back $1.1 billion in funding for public broadcasting through fiscal year 2027.
> The announcement follows a largely party-line vote last month that approved the cuts to public broadcasting as part of a $9 billion rescissions package requested by the White House that also included cuts to foreign aid. While public media officials had held a glimmer of hope that lawmakers would restore some of the money for the following budget year, the Senate Appropriations Committee declined to do that on Thursday.
https://www.npr.org/2025/08/01/nx-s1-5489808/cpb-shut-down-p...
Also, this isn't relevant anyway, because the article is about a dispute about a particular program that NPR was running.
11 more comments available on Hacker News
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.