Q: How does RSSHub work？
A: When a request is received, RSSHub fetches the corresponding data from the original site, the resulting contents will be outputted in RSS format. Caching is implemented to avoid requesting original sites for content. And of course, we throw in a little magic 🎩.
Q: Can I use the demo instance？
A: rsshub.app is the demo instance provided, running the latest build of RSSHub from master branch, the cache is set 120 minutes and it's free to use. However, if you see an badge 🚨 Strict anti-crawling for route, this means popular websites such as Facebook etc. may pose a request quota on individual IP address, which means it can get unreliable from time to time for the demo instance. You are encouraged to host your own RSSHub instance to get a better usability.
Q: Why are images/videos not loading in some RSSHub routes？
A: RSSHub fetches and respects the original image/video URLs from original sites, in which some are behind anti-hotlink filters.
referrerpolicy="no-referrer" attribute is added to all images to solve the issues caused by cross-domain requests. Third party RSS service providers such as Feedly and Inoreader, strip this attribute off, resulting in cross-domain requests being blocked. Meanwhile, the attribute is not available for videos yet, resulting in most RSS readers unable to pass the anti-hotlink check. Here are some workarounds:
- Migrate to RSS readers that do not send Referer，such as Inoreader for Web with a user script disabling Referer, fix-image-error at inoreader, RSS to Telegram Bot, etc. If your RSS reader can bypass the anti-hotlink check successfully and play embedded videos, it's an RSS reader that do not send Referer. Please consider adding it to the documentation to help more people.
- Set up a reverse proxy, refer to Parameters->Multimedia processing for more details.
- Navigate back to the original site.
Q: The website I want is not supported QAQ
Q: Where do I get the changelog for RSSHub？
A: Subscribe our RSS here: RSSHub added a new route.