rss-bridge
rss-bridge copied to clipboard
Bridge request for Ko-fi
Bridge request
General information
-
Host URI for the bridge (i.e.
https://github.com): https://ko-fi.com/ -
Which information would you like to see?
Posts by a specific user
- How should the information be displayed/formatted?
Given the paywall nature of the site, output similar to Patreon is probably best (showing only the title and a link to the post, which a logged in supported would be able to use to view the content)
-
Which of the following parameters do you expect?
- [X] Title
- [X] URI (link to the original article)
- [ ] Author
- [ ] Timestamp
- [ ] Content (the content of the article)
- [ ] Enclosures (pictures, videos, etc...)
- [ ] Categories (categories, tags, etc...)
Options
- [ ] Limit number of returned items
- Default limit: 5
- [ ] Load full articles
- Cache articles (articles are stored in a local cache on first request): yes
- Cache timeout (max = 24 hours): 24 hours
- [X] Balance requests (RSS-Bridge uses cached versions to reduce bandwith usage)
- Timeout (default = 5 minutes, max = 24 hours): 5 minutes
Seems that we have a Ko-Fi bridge as of now, but I get an unpleasant message from CloudFlare when I try to use it.
The website is protected by CloudFlare RSS-Bridge tried to fetch a website. The fetching was blocked by CloudFlare. CloudFlare is anti-bot software. Its purpose is to block non-humans.
I don't know if there are any workarounds for this.
@walkero-gr
ko-fi.com uses Cloudflare for years, but it seems they changed something, making it more difficult to parse its content. I am not sure what kind of workaround could be used to bypass it.
I am experimenting with https://github.com/FlareSolverr/FlareSolverr as an extra docker container in my set up. I am not sure if that would be a good solution or not. I will get back with findings.
Well, I had some success using the FlareSolverr
What I did is along the rss-bridge docker container, to set up a new service for FlareSolverr, like below
flaresolverr:
# DockerHub mirror flaresolverr/flaresolverr:latest
image: ghcr.io/flaresolverr/flaresolverr:latest
container_name: flaresolverr
environment:
- LOG_LEVEL=${LOG_LEVEL:-info}
- LOG_HTML=${LOG_HTML:-false}
- CAPTCHA_SOLVER=${CAPTCHA_SOLVER:-none}
- TZ=Europe/London
ports:
- "${PORT:-8191}:8191"
restart: unless-stopped
I also needed to make some changes in the ko-fi bridge code, to make it work. I am not sure at all if such a solution would be acceptable, for creating a PR. If the maintainers believe that this should be in the repo, please let me know.
How can I increase the timeout period, to avoid getting a timeout from rss-bridge? I am getting the following error and the page returning 504
upstream timed out (110: Connection timed out) while reading response header from upstream,