Honestly, the 60% is a rough estimate, not a precise measurement. I still spend a lot of time reviewing the docs. AI is especially handy for the screenshots and repetitive parts, which would take much longer to put together manually. It just makes that side of the work a lot quicker.
TypeType
I love pomme 🍏🍎
- 1 Post
- 3 Comments
- TypeType@lemmy.zipOPtoSelfhosted@lemmy.world•[AIP] TypeType: a self-hosted video app for YouTube, NicoNico and BiliBiliEnglish12·7 days ago
- TypeType@lemmy.zipOPtoSelfhosted@lemmy.world•[AIP] TypeType: a self-hosted video app for YouTube, NicoNico and BiliBiliEnglish23·8 days ago
Hey, thx for the kind words about the project, and for taking the time to write this up (˶ᵔ ᵕ ᵔ˶)
Just to clear up the NewPipe and FreeTube part: TypeType doesn’t use them, we run on PipePipeExtractor, and I contribute upstream to PipePipe whenever I can.
PipePipe is a different project with its own services and its own direction, and we have nothing to do with them these days.
On the generated code, I totally get the concern. It’s not a mass of code nobody ever looked at, I read what ships, I test it, and I maintain it myself. These days I also maintain it with other contributors, but I still review what goes in, for example https://github.com/TypeType-Video/TypeType-Frontend/pull/62
The disclosure is just me being honest about the tools involved. I understand why people focus on that first, with all the AI slop out there, but it’s a bit frustrating sometimes. There’s a real history behind the project, with reviews, tests and releases.
I try to stay as transparent as I can. And honestly, at the end of the day I have a great community, friendly and supportive, and that’s enough for me.
I just share the project to offer an alternative. Concretely, I have nothing to gain from it. As long as I’m alive, TypeType will be properly maintained ♡
Thanks, glad the allow-list sounds useful! I meant the whole stack on one box: the app/server, Token, Postgres, Dragonfly, Downloader and Garage. There isn’t a separate media-proxy container; playback goes through the Server.
I was too optimistic with the 2 GB figure in the post. For a small personal setup, I’d go with 2 vCPU, 4 GiB RAM and about 20 GiB free disk space (SSD preferred, but HDD should work too). For a few users and regular downloads, 4 vCPU, 8 GiB RAM and about 40 GiB free disk space would be a better starting point. Downloads use disk rather than RAM, and need extra room while they’re being processed.
The sizing details are here: https://typetype-video.github.io/Docs-TypeType/self-hosting/prerequisites