[META] consider splitting the project in two

[lowne]

Yotter+Twotter FTW! 🥳 (and btw thanks for the excellent work!)

I don't think it makes sense to have both services "integrated", as the use cases don't really overlap (akin to having your Kindle books show up on your tv's Netflix). Especially so from a self-hosting perspective: if you want both services, you just spin up two containers (and in fact I'd further make the case that yt_data_extract should be spun out as its own service, for a number of reasons, but that's a different discussion).

The shared logic is minimal, so the technical aspect is relatively straight-forward (see WIP here). Having a quick glance at the GH issues shows two parallel apps under the same roof, so there's an added side benefit of restoring some order there <bangs gavel> 😄

Same for the user perspective, with the possible exception of "feeds". Assuming there are plans to expand to more services (I have no idea if that's the case), while it might make sense to aggregate "followings" between disparate social-network-like sources (though I don't particularly agree with that either), having YT videos scattered in doesn't seem like an especially compelling feature.

All that's left then is user accounts, and while it might be possible to have an "overseer" app pass sessions around, the technicalities involved just aren't worth the tiny benefit IMO. More generally, every "contamination" of the db models to cater to disparate services potentially creates problems down the line when it comes to expand features tailored to a specific service (which btw is what i'm doing).

Thoughts?

[pluja]

That's actually an interesting idea! Maybe in a future we can work on that.