> ## Content Index > Fetch the complete content index at: https://moomean.com/blog/llms.txt > Use this file to discover other available public pages before exploring further. # What If Windows Media Player Could Understand YouTube? - URL: https://moomean.com/blog/what-if-windows-media-player-could-understand-youtube/ - Published: 2026-09-27T09:25:01.000Z - Updated: 2026-09-27T09:26:29.000Z - Description: What if an old Windows PC could stream modern YouTube without ever opening a modern browser? RetroStream is my self-hosted bridge between today’s media services and the old computers I still love using. - Author: Moomean Alshemali Aldeiri - Tags: Retro Computing, HomeLab I was born in the early 1990s, which means I belong to that generation that didn't discover Windows 95, 98, ME, 2000, and XP through YouTube retrospectives. We actually used them. As a kid, I went through all of them. Windows 95, Windows 98, Windows ME, Windows 2000, and eventually Windows XP. Then, like everyone else, I continued moving forward as newer versions of Windows came along. But there was one thing about those early computers that always fascinated me: streaming. Windows Media Player, RealPlayer, and other media applications of the era already had features for Internet radio and streaming media. The idea that you could click something and have music or video arrive continuously through the Internet seemed incredibly futuristic to me. There was only one slight problem. My Internet connection was dial-up. And it was terrible. Streaming audio was basically a fantasy, never mind video. I remember once managing to stream something from an Internet café. Their connection was considerably better than what I had at home—probably some early ADSL connection around a few hundred kilobits per second—and even that felt incredible at the time. Eventually, of course, none of this mattered anymore. Broadband arrived. Google Video existed for a while. YouTube appeared. Internet connections got faster and faster, and streaming went from being futuristic to being completely ordinary. Today we stream 4K video without even thinking about it. But for me, that wasn't quite the end of the story. ## Going Back My fascination with old computers never really disappeared. There was a long period where I simply moved on and used modern machines like everyone else, but around 2022 I started getting heavily interested in old operating systems again. At first I used virtual machines. They were fun, but something was missing. Running Windows 2000 in a VM doesn't feel the same as turning on an actual old computer, hearing its fans, dealing with its weird hardware, installing real drivers, and using it as though it were still a functioning machine. So naturally, things escalated. Today I have several computers capable of running old versions of Windows. Some are genuinely old machines from the period, while others are slightly newer systems that still have proper native driver support for older operating systems. One of them is my retro desktop: an Intel Core i5-2500, 16 GB of DDR3 RAM, and a GTX 750 Ti. By Windows XP standards, that thing is basically a supercomputer. It runs XP beautifully, with native drivers and enough power that something like Supermium—a Chromium-based browser designed to keep older Windows versions usable on the modern web—actually works reasonably well. You can open YouTube on it. You can even play ridiculously high-resolution video that would have seemed like science fiction during XP's prime. So RetroStream was not born because "Windows XP can't play YouTube." That problem can already be brute-forced with sufficiently powerful hardware. The interesting problem begins when you move further backward. I also have machines with much more realistic retro specifications: old processors, one gigabyte of DDR2 RAM, and hardware that absolutely does not want anything to do with a modern web browser. Technically, you can sometimes force a newer browser onto one of these machines. Then you open YouTube. And the poor computer essentially begs you: **Please let me die in peace.** Forget 1080p. Forget 720p. Sometimes even asking it to play a 144p YouTube video feels abusive. That made me start thinking differently. What if the old computer didn't need to become modern? ## The Idea Had Been Sitting There for a While About a year earlier, while working on one of my personal projects called Cybernode, I had built a small media player into the website. The idea was simple. Take media from YouTube, extract the audio stream, and play it through my own interface. It worked. And somewhere in the back of my head, a thought appeared: What if you put a middleman between YouTube and an old computer? The middleman could retrieve the modern stream, transcode it into something much simpler, and feed the result to software that already existed twenty or twenty-five years ago. I didn't build it. The idea just sat there for almost a year. Then recently I started brainstorming another project: RetroProxy. RetroProxy is a much bigger idea—essentially exploring how to make more of the modern Internet usable from genuinely old computers. While thinking about that project, something clicked. Before trying to fix the entire Internet for retro computers, why not solve multimedia first? That's much easier. And more importantly: **You don't actually need a browser to stream media.** Old operating systems already have media players. Windows Media Player exists. Winamp exists. RealPlayer exists. JetAudio exists. These programs were designed to receive network streams decades ago. The problem isn't the media player. The problem is that today's Internet no longer speaks its language. So instead of forcing a twenty-five-year-old computer to understand modern YouTube, modern JavaScript, modern codecs, modern TLS, and everything else we've piled onto the web since then, why not make the modern server translate everything into something the old computer already understands? That became [RetroStream](https://github.com/moomean712/RetroStream?ref=moomean.com). ![](https://moomean.com/blog/content/images/2026/09/Screenshot-2026-09-22-192339.png) ****RetroStream Dashboard** ## Make the Modern Internet Do the Hard Work The idea behind RetroStream is fairly straightforward. You give the server a YouTube video, playlist, album, or other supported media source. The server handles the modern side of the equation: retrieving the source, processing it, transcoding it into an appropriate format, and caching it where necessary. It then gives you a stream that an old media player can understand. The retro machine doesn't need to know anything about how YouTube works. It doesn't need a modern browser. It doesn't need to execute a mountain of JavaScript. It doesn't need to decode a modern web video format. It just sees a media stream. That's it. I also added different transcoding profiles because "old computer" covers a surprisingly enormous range of hardware and software. Something appropriate for a later Windows XP machine isn't necessarily appropriate for Windows 2000 or Windows Media Player 6. RetroStream therefore supports more conservative legacy output for older players, including very old versions of Windows Media Player, while still providing options suitable for newer systems. And because there was no reason not to, it also works perfectly well with modern media players. You could run RetroStream and use it from Windows 10 or Windows 11 if you really wanted to. That's not why I made it. But hey. Why not? ## HTTPS Is Great Until It's 1999 There was another problem. Security protocols. Old computers don't merely struggle with modern websites because those websites are heavy. Old operating systems and media players may not understand current TLS versions, certificate requirements, cipher suites, and other security mechanisms at all. Trying to make every ancient client understand the security infrastructure of 2026 would defeat the entire point. So RetroStream is designed around a trusted local-network model. My own retro computers live on a dedicated Retro VLAN, isolated from the rest of my home network. I don't store sensitive information on those machines. They're recreational systems. They're there because I enjoy using them. RetroStream itself runs on modern infrastructure, and my firewall only allows the necessary RetroStream ports from the retro network to the server. You could also put the entire RetroStream VM directly inside the retro network if you preferred. The important idea is that the old machine doesn't need to communicate directly with the modern Internet. RetroStream does that for it. On one side you have modern HTTPS, YouTube, modern codecs, and modern infrastructure. On the other side you have a very simple HTTP media stream that Windows Media Player from another century can happily understand. ![](https://moomean.com/blog/content/images/2026/09/Diagram1.png) ****Modern YouTube on one side, Windows Media Player on the other. RetroStream does the ugly work in between.** This is one of those cases where deliberately using old protocols makes sense, because they're being used inside a controlled local environment for compatibility. ## And Then AI Made This Hobby Project Practical RetroStream is also very much a product of the current era of software development. I've been making websites since I was about sixteen, so purely on the personal side I've spent roughly eighteen years building, breaking, redesigning, and experimenting with things on the web. But that's only one part of my background. I also studied software engineering academically, and went on to build a professional career around software, systems, and technology. So when I use AI-assisted coding tools, I'm not throwing a sentence into a box and blindly trusting whatever comes back. I understand software architecture. I can read the code, evaluate the decisions being made, recognize when something is wrong, test the output, debug it, question the implementation, and keep refining it until it behaves the way I intended. That distinction matters. RetroStream is exactly the kind of project I might never have completed before modern coding agents became practical. Not because I couldn't write it. Because I probably wouldn't bother. This is a hobby project whose purpose is largely to let me stream music and videos to Windows ME and Windows 2000. I have work. I have university. I have a wife. I have a life. If someone told me this silly idea would require several weeks of sitting down every evening writing boilerplate, dealing with dependencies, building interfaces, and debugging everything manually, it probably would have remained in my "one day I'll build this" folder for several more years. Instead, I could spend my time on the part I actually find interesting: defining the problem, thinking through the architecture, deciding what old systems should be supported, working out the compatibility model, testing the result on real hardware, finding the edge cases, and refining the design. I brainstormed the project, turned the idea into requirements, refined those requirements into prompts, and used Codex to accelerate the implementation. The AI dramatically reduced the amount of mechanical work between the idea and a functioning prototype. It didn't eliminate engineering. If anything, the engineering became concentrated in different places: architecture, validation, testing, debugging, compatibility decisions, security, and knowing when the generated implementation was wrong. And no, the first version wasn't magically perfect. Far from it. ## The First Prototype My initial prompt barely discussed appearance. I didn't care about themes, animations, or making the dashboard pretty. I wanted to know whether the basic engineering idea worked. The first version was essentially a proof of concept. I hadn't even tested it on an old computer yet. I tested it from Windows 11. I gave RetroStream a YouTube link. It retrieved and cached the media. It generated a streaming URL. I copied that URL into the legacy Windows Media Player included with Windows 11. And it played. That was the first moment where I knew the concept itself was sound. There were also bugs everywhere. Which is normal. Whether the code comes from a human being or a coding agent, building software still means testing, finding problems, fixing them, breaking something else, testing again, and slowly turning a prototype into something reliable. I started working on it at around eight in the morning. By roughly six that evening, I had something genuinely functional. Then I kept going. I redesigned the interface. I made sure the dashboard remained usable from much older browsers in case someone wanted to control RetroStream from the retro computer itself. I added multiple transcoding modes. I worked on compatibility with old versions of Windows Media Player. I checked security. I tested. I broke things. I fixed them. And then came the fun part. ## Turning On Basically Every Computer in the House At some point my house started looking like a small Microsoft museum. Windows ME was running. Windows 2000 was running. Windows XP was running. Windows Vista was running. I even had virtual machines with Windows 95 and Windows 98 involved in the testing. Every time another machine successfully started playing a stream, I reacted like a child. **We did it!** **We did it!** There is something ridiculously satisfying about seeing software you just built communicate successfully with an operating system released more than two decades ago. But testing on genuine old systems also exposes problems that no modern development environment is ever going to predict. Missing codecs. Different media-player behaviors. Strange networking assumptions. Old security limitations. Driver bugs. And then there was Windows 2000. That one was special. ## The Dial-Up Modem Returns for Revenge One of my Windows 2000 laptops has a built-in dial-up modem. The computer was connected to the network through Wi-Fi. Everything was working. But every time I attempted to open a network stream in Windows Media Player, the entire computer crashed with a blue screen. Eventually I discovered the problem. The modem driver was buggy. For some reason, despite having a perfectly functional network connection, Windows 2000 decided that opening a media stream meant it should try to involve the dial-up modem. Windows Media Player would attempt the connection. The modem driver would wake up. The modem driver would fall over. And Windows 2000 would blue-screen. There is something wonderfully appropriate about this. The entire story began with me as a kid wishing my dial-up Internet connection were fast enough to stream music. More than twenty years later, I finally built my own system for streaming modern media to an old computer… …and a dial-up modem came back from the dead to stop me. Retro computing is beautiful. ## Version 0.1 By around the following afternoon, I reached a point where I was satisfied. Not because RetroStream couldn't be improved. It absolutely can. But because it did what I originally wanted it to do. That distinction is important to me. Not every piece of software needs to become an endless product. Sometimes you build a thing because you want the thing. And when the thing works, you're allowed to enjoy it. RetroStream became version 0.1. I packaged it as a Docker container because I wanted installation to remain simple. The project has dependencies, and I didn't want someone to spend an afternoon manually installing and configuring them one by one. If you have Docker, you should be able to get the service running without turning the installation itself into another retro-computing experience. Media can be cached rather than repeatedly processed from the source, and RetroStream manages that cache automatically. Content that remains unused can eventually expire, while frequently accessed media can remain available locally. The project isn't meant to replace your music library, Spotify, YouTube Music, or anything else. It's simply a compatibility layer. A translator. Modern media goes in. Old-computer-friendly media comes out. ![](https://moomean.com/blog/content/images/2026/09/Screenshot-2026-09-22-192405.png) ![](https://moomean.com/blog/content/images/2026/09/Screenshot-2026-09-22-192351.png) ****Adding a YouTube playlist to RetroStream "The Death of Slim Shady"** ## So What Do I Actually Do With It? Mostly? I have fun. On weekends I sometimes turn on one of my retro computers, open MSN Messenger through Escargot, talk to friends, browse some old-style websites, and play music in the background. Basically, I use the computer like any respectable person from the early 2000s would. Except the music might actually be coming from YouTube Music through a Docker container running somewhere else on my network. I can choose one of the playlists I've already prepared in RetroStream, open it in Windows Media Player, and let it play. And one of my favorite little details is that MSN Messenger can display what I'm currently listening to. So yes. There may be a modern server, broadband Internet, Docker, transcoding, caching, VLANs, firewalls, and twenty-first-century AI-assisted software development hiding behind the scenes… …but my friends on MSN Messenger still get to see what song I'm listening to. Priorities. ![](https://moomean.com/blog/content/images/2026/09/Screenshot-2026-09-21-140655.png) ****Windows Media Player playing RetroStream music** ![](https://moomean.com/blog/content/images/2026/09/windows-media-player-9-1.jpg) ****MSN Messenger showing “What I’m Listening To** And I don't only use it for music. There's something particularly entertaining about sitting at an old Windows computer and watching videos about old Windows computers. I like channels such as Michael MJD, Action Retro, and The 8-Bit Guy, and seeing their videos playing inside an actual old operating system just feels right. Retro computing content. On retro hardware. Through Windows Media Player. Delivered from modern YouTube by my own server. Completely unnecessary. Absolutely wonderful. ![](https://moomean.com/blog/content/images/2026/09/20260923_171906.jpg) ![](https://moomean.com/blog/content/images/2026/09/20260927_175110.jpg) ![](https://moomean.com/blog/content/images/2026/09/20260927_175154.jpg) ****Watching Action Retro, The 8-Bit Guy, and Michael MJD on my Windows 2000 laptop with RetroStream** ## Open Source, Because Why Not? I decided to keep RetroStream open source and put the project on [GitHub](https://github.com/moomean712/RetroStream?ref=moomean.com). I may eventually come back and build version 0.2. Maybe I'll add more formats. Maybe I'll improve compatibility with even stranger media players. Maybe RetroProxy will eventually integrate with it somehow. Or maybe version 0.1 will remain exactly what it is for quite a while. I'm fine with either outcome. What would make me particularly happy is seeing someone else discover the project, use it on their own collection of ridiculous old computers, change something, improve something, or take the idea in a direction I never considered. That's part of the fun of building these things. ## The Stream I Never Got The funny part is that RetroStream solves a problem that essentially stopped existing decades ago. I don't need it. Nobody needs it. I have a modern phone. I have modern computers. I have fast Internet. YouTube already works. Spotify already works. Every modern device in my house can stream more media than the kid sitting behind my old dial-up connection could ever have imagined. But that's not really the point. Sometimes the experience itself is the point. There was a kid in the late 1990s and early 2000s staring at Windows Media Player and RealPlayer, fascinated by the idea that these programs could somehow pull music and video directly through the Internet. The software could do it. His Internet connection couldn't. More than twenty years later, he still likes turning on those computers. Only now the connection is fast enough. And when he clicks Play… the stream finally starts.