The goal of this issue is to find out where we should place our efforts to maximally improve rss-bridge and its long-term survival and prosperity.

This is an issue in which we discuss midterm/longterm goals for the project and prioritize them.

An initial list from my memory:

1. Find a solution to anti-bot systems (e.g. cloudflare captcha/DataDome)
2. Bridge discovery from url (e.g. resolving http://twitter.com/foo to the correct bridge) (Integration with Tiny Tiny RSS #2361)
3. Improve html sanitization (Improve html sanitization #2540)
4. Introduce a new document root to prevent direct access to files in the ./cache folder
5. Improved automatic detection of broken bridges
6. Attract more bridge maintainers so that bridges get repaired faster
7. make rss-bridge usable as a software library.
8. Improve DX (improve the developer experience of making and maintaining bridges)
9. Add feature to reconfigure an existing feed
10. Add some protections to instances with high traffic volume (to prevent being banned, throttled etc., internal rate limiter)

Inputs from the community is very much appreciated here.

Feel free to suggest more goals and better goal ordering.