story behind tuberepair-python

2024-11-04


how it started

It was summer, 2023. Also the year I'm interested in old iOS stuff. The glossy icons did it for me. I bought a 4th generation iPod touch, and slowly building a collection of them.

After jailbreaking, the thing to do is install TubeFixer. But after a few months, the goddamn thing stopped. Great, now I can't watch 144p DankPods vids anymore. So, a amazing team of developers made a (sort of) TubeFixer revival. It was named TubeRepair.

Everything was the same. You enter the API Key and fire up YouTube after a respring, only this time, with the "new" Google YouTube app (they wanted ui change & easier app updates via the App Store). I used it every day, tried multiple videos just to listen to a song, app crashed randomly, playback error, etc... Crippled, to say the least.

After a month of use, I surrender. It was too buggy. I asked them to open source the code (PHP), even planned to pay for it. Declines after decline, I decided to create a new backend. This is a community-based project, so I can improve/contribute! That's what I did, using my crappy knowledge of Python. Nights spending finding responses from YouTube's old API, and fixing bugs. No break at all, laser-focus. It was fun, I forgave them (they did release it after), everyone's excited, but I was getting insane over the tiniest bug in the code.

Burnout. Bad, bad, bad shit. Posts of Legacy Childs (unironically me) complaining about stuff not working, combined with my newly discovered ADHD, I broke down crying.

TEEHEE, check it out: tuberepair.bag-xml.com

back