u/MorroWtje

Open RSS put out a post this week laying out everything wrong with YouTube's feeds and it crystallized something I've been feeling for a while. The official channel feed URL is buried so deep most people don't know it exists. Shorts are mixed in with no way to filter them at the source. Tracking parameters get injected into the item links. The old gdata.youtube. com endpoint that a lot of readers still default to has been dead for ages and nobody told the readers.

And the workarounds all have asterisks. Proxies work until they get rate-limited or the service goes down. Self-hosted scrapers break every time YouTube tweaks the page. The official feed only shows the 15 most recent videos and won't go further back no matter what you do. Live streams and Premieres show up as items that point to nothing for hours.

What bugs me most is that RSS is the one way to follow creators that doesn't feed the recommendation algorithm or require an account, and it feels like that's exactly why it's being left to rot. Not killed outright — just neglected until everyone gives up and opens the app.

Curious where people here land on this. Is it actually getting worse or has it been this bad the whole time and I'm just noticing? And is the answer self-hosting something, paying a third party to proxy it, or accepting that YouTube-via-RSS is on borrowed time and planning accordingly?

Two years ago, putting a UI in front of a LangGraph agent and a UI in front of a CrewAI agent meant writing two different adapters. Different events, different state models, different ways to handle tool calls. Switch frameworks, you end up writing a third.

AG-UI is an attempt at a fix: a stream of typed events for runs, tool calls, and state, plus a channel for state updates that flow both ways. That's the whole protocol.

I'm one of the contributors in the AG-UI community, and while many haven't noticed us, we've quietly gotten adoption from Google's ADK, Microsoft, AWS, LangChain, CrewAI, Mastra, and basically the entire agent framework ecosystem.

The concrete thing this unlocks: frontend can edit agent state on the same connection the agent streams from. User clicks an inline edit, the agent sees the change on its next turn. No backend round-trip, no separate WebSocket, no per-framework adapter. That's the part I actually care about — human-in-the-loop without the plumbing tax.

It's very powerful for shipping interactive agent applications.

I'm not sure why not more people are noticing or talking about this. If you've checked out AG-UI lmk if you have any more ideas on how we can build on top of this standardization to make it better!