The creator didn’t have a good answer, so there may not be a good one for this project. But the value proposition is actually there.

These self-hosted solutions are riddled with configuration options, often obscure requirements, and countless maintenance pitfalls.

For a disciplined tech person, it is no problem to install and maintain.

For people less disciplined or non-tech, self hosting is ill-advised and can be dangerous.

But even for a tech person, when you have enough docker-compose services laying around, it can start to get a bit overwhelming to keep it all up to date, online, and functional. If you change your router etc you have to recall how things were set up, what port-forwards you need, what reverse lookups, etc etc.

There actually is a gap in usability and configuration management. I could see a product that has sensible defaults that unifies config across these self-hosted services without needing to access the command line.

They can’t do that because of accessibility reasons. If they did that, a disabled person has grounds to sue them for proper aria hints & controls.

It doesn’t matter what kind of content it is, either. It must be made accessible.

Only kind of true.

If they did implement all those measures, all you do is launch a puppet browser rendered off screen and scrape the content you want. This could work for any site and it is impossible for anyone to detect.

For ads, as a nuclear option, you can detect when they occur and black the stream out.

I would personally do this if left with no other option.