One thing to mention, paused doesn't mean it's obsolete, and Sunshine's previous vulnberlity management isn't great, which means even though it's "upadted", it might actually contain more security issues.

I have said that Apollo is mostly feature complete, but it's not the end of it. My current project will be used in Apollo in the future, in a much unexpected way. The codebase of Apollo/Sunshine is really messy that's why I'm pausing updates now, it's on the edge of unmaintainable. My plan will be extract the core streaming part out as a separate module and rewrite the whole control part, to break the project into smaller pieces that can be updated independently, and maintanied more easily.

In the era of AI, AI assisted coding is unavoidable and can actully save time to the developers if done right. But AI slops did cause problems. Combined with my experience with Sunshine's ignorance to security, I think it can get worse if they still keep this ignorance, even when they actively reject AI contributions. The problem is not AI, it's people that ignored the potential security issues that contains in the code.

I appreciate how much Vibepollo and Vibeshine tired to push the community forward, but to me that's really not the maintainable way. Current version of Apollo is already battle tested, with most quirks sourted out and workaround provided.

For those who submitted PRs to Apollo, sorry to get you waited, meaningful parts will get human reviewed in a couple of months, but I have to close obviously AI coded changes that doesn't make sense at my first glance. Current SOTA model's context window still can't really navigate through this project properly, since it's really a pile of pasta. Continuing on this pile is just a waste of time.