Hey everyone! Hope you're all doing well, all two or three of you hanging around here ;) I've got a few ideas in mind for the future of TypeType, and before diving into another mountain of code, I'd like to hear what you think. Nothing is set in stone yet. These are just a few things I've been thinking about, and I'm still trying to figure out which direction to take. Anyway, here are the three main ideas!

1. Twitch integration?

I've been thinking about adding Twitch livestream support to TypeType. But I'm not sure whether it makes sense to integrate it directly into TypeType, build a separate application dedicated to livestreams, or just make a small POC to see how it goes. There's also the option of dropping the idea entirely if there isn't much interest in it. For now, I'm just exploring the possibilities.

2. Building a proper video downloader CLI

This is something I've wanted to do for quite a while :D I'd like to build a command-line tool for downloading videos from YouTube, NicoNico, and BiliBili. But here's the interesting part: it would FINALLY NOT be yet another yt-dlp wrapper! The goal would be to build an independent tool, with its own extraction logic, download engine, and format handling. TypeType already has some of the technical foundations needed for this, thanks to the work I've done on extraction and downloading. I'm still thinking about the technical side. I could build the whole thing in Go or TypeScript, or maybe use Go for the backend and TypeScript with OpenTUI for the frontend. Nothing is decided yet, but I'd like to make it a standalone tool that anyone could use directly from their terminal, without having to deploy the entire TypeType stack.

3. Building a recommendation system

This one is probably the most complicated of the three. I've been thinking about adding a recommendation system to TypeType to help users discover new videos and creators based on their interests. But I don't want to turn TypeType into another YouTube algorithm. One of the reasons I started TypeType was to have my own personal video space, where my data stays on my own instance and I remain in control of my experience. I don't want to compromise that just to add recommendations. Ideally, recommendations would be generated locally, using information already available on your instance, such as your subscriptions, watch history, or favorite videos, without sending your personal data to an external recommendation service. The system would also be completely optional. If you don't want recommendations, you should be able to disable them and continue using TypeType as you do today. There are still quite a few technical questions to figure out, especially when it comes to discovering relevant content across different platforms without relying entirely on their own recommendation algorithms. And honestly, I haven't decided yet how I would implement this.

So, what do you think?

These are just ideas for now, not official announcements or promises for the next release. TypeType is still a project I develop mostly on my own, in my free time, and there's already quite a bit to juggle between new features, bug fixes, testing, and everything else. I'd rather take my time and release something I'm genuinely satisfied with than rush to add features just for the sake of filling up a changelog. That's also why I'm sharing these ideas with you. Before spending weeks or months working on something, I'd like to know whether it's actually something people would use. So, I'd love to hear your thoughts on a few things: • Twitch: Would you use Twitch livestreams in TypeType? Would you prefer having them integrated directly into TypeType, a separate dedicated application, or should I just make a small POC first? Or maybe it's simply not something you're interested in? • Downloader CLI: Would you be interested in a standalone video downloader for YouTube, NicoNico, and BiliBili that doesn't rely on yt-dlp? What features would you want from it? • Recommendations: Would you actually use a recommendation system in TypeType? What kind of recommendations would you want, and how do you think such a system should work while respecting user privacy? And more generally, which of these three ideas interests you the most? Feel free to share your thoughts, suggestions, or even completely different ideas in the comments. I'm always interested in hearing what you think, even if I don't always have the time to reply to everyone. And as always, thanks for supporting TypeType :) Stay tuned, and I'll keep you posted ;)

Hey everyone! I wanted to make a proper post, because a lot has happened and I don’t think a simple changelog does it justice. First, TypeType is more mature than it used to be. When I started, it was a small wrapper around PipePipeExtractor that I mostly built for myself. Today it has a web client, a native Android app, a native iOS client in progress, a separate playback engine, a Go downloader, and a token service. That’s a lot more surface area, and honestly, a lot more responsibility but im loving it ! The second thing is AI, and how people contribute. I published the AI Transparency statement. This one matters to me because AI is now part of how software gets written, including here. I use it myself. My position is simple: AI is a tool, not an author, not a maintainer, and not a decision-maker. You can use it as much as you want, including for complete implementations. What matters is that a human understands the change, reviews it, tests it, and takes responsibility for it. If you’ve been hesitating to contribute because you weren’t sure what the rules were around AI, now it’s written down. And if you disagree with something in it, open an issue and tell me. It’s my current position, not a dogma. Third, the community feedback is actually moving things. Over the last few weeks, more than ten issues have been closed, and a lot of them started with your reports: Takeout imports failing, BiliBili channel errors, the cursor staying hidden over a paused player, configurable grid density, autoplay split between opening and next video, subscription groups, simplified setup, and more. Some were small, some were real headaches, but they’re all in the code now. That includes fixes from other contributors too, not just me. kapdon worked on subscription groups, Aquarius-Situla on playback and BiliBili configuration, tam1m on character encoding. That’s the part I’m the most proud of, honestly. TypeType is starting to be a real project with several people in it. Fourth, TypeType for Android has left beta and is stable now. Android 1.9.0 is out, and it’s a big one for the app: UnifiedPush subscription notifications with a channel bell and a dedicated settings screen (not perfectly perfect but we are getting it there), animated skeleton loading states instead of blank areas, SABR prewarming so playback starts sooner, previous/next player controls, bullet comments on BiliBili, and support for Android 6.0 through Android 17, without Play Services. You can grab it from F-Droid or the GitHub release. And finally, recommendations. This request came back so many times that I’m building it. I don’t want to clone an algorithm blindly. What I want is a system where you can see which signals are used, choose what the feed optimizes for, and turn it off completely if you don’t want it. The user controls the algorithm, not the other way around. I think I can get something out of the oven soon, but I don't expect it to be perfect so I announce it it will be another service (yes sorry) and it will be optional, if u don't want any recommendation, no problem just don't deploy it, it's that easy. I’ve been working on it for the past two days, and here’s a quick video: Video For now it’s just mock data, but by now you know me: I’m picky, and I hate AI slop UI, so I spend way too much time on the UI, the UX, and the clarity... And just so you know, I’m not starting the algorithm from scratch. A few months ago I had started one and it was honestly awful. A friend who is a data scientist explained to me what I had screwed up. I don’t expect it to be perfect, but lucky me, I know one or two things about reverse engineering, so maybe, and I really mean maybe, I had already built a custom tool to reverse engineer a well-known algorithm, long before I found out how bad I was at algorithms ;p One last thing. I know some of you are still waiting for a reply from me. I read everything, I really do. I’m just completely swamped with development, reviews and testing right now, and I can’t answer everyone. If I haven’t gotten back to you yet, it’s not because I ignored your message. Thanks for being here :) TypeType on GitHub · 1.9.0 release notes · Android 1.9.0

Hey! If you're coming from Reddit, you might already know what happened. If you have no idea what TypeType is, don't worry, I'll get to that too :) The short version: a few days ago, the TypeType subreddit got banned from Reddit, and the account posting about it got banned too. I'm still trying to understand exactly why. No warning, no modmail, nothing. The announcement posts on other subs were removed by Reddit's filters as well. I'm not gonna pretend I'm not a bit sad about it, a lot of people found the project through those posts. But the adventure continues. After thinking it over, I decided to give TypeType a new home here, on Lemmy. And honestly? It makes more sense than I first thought. TypeType is an open-source, self-hostable project. Lemmy is an open-source, self-hostable community platform. We should have been neighbors from the start :) So, what is TypeType? It's a self-hostable video app where your history, playlists, favorites, subscriptions, watch progress and settings live on your own instance. YouTube, NicoNico and BiliBili, no ads, no trackers, no recommendation feed trying to eat your whole evening. You run it with Docker, your data stays in your PostgreSQL, and you access it from a web app or the Android app. Under the hood it's a Kotlin/Ktor backend, a token service, a downloader service, and PipePipeExtractor doing the extraction work (TypeType was literally born from my years around PipePipe). What you'll find here: • Release posts (web, Android, and more coming) • News and behind-the-scenes stuff • Help with self-hosting and troubleshooting • Ideas and feedback, I read everything The project is at 421 stars on GitHub, actively maintained, and I use it every day myself. If you self-host, if you came from Piped/Invidious/NewPipe looking for a new home, or if you're just curious, you're welcome here. Every little exchange helps keep the project alive. See you around :) TypeType: https://github.com/TypeType-Video/TypeType