Skip to content

Conversation

@SqrtMinusOne
Copy link
Contributor

Also increased caching time yet again because of CloudFlare.

@github-actions
Copy link

github-actions bot commented Sep 21, 2025

Pull request artifacts

Bridge Context Status
InstituteForTheStudyOfWar 1 untitled (current) Bridge returned error 0! (20394)
Type: Error
Message: Call to a member function find() on null
InstituteForTheStudyOfWar 1 untitled (pr) ✔️

last change: Sunday 2025-11-02 16:48:28

Copy link
Contributor

@Mynacol Mynacol left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, this works great.
I'm still wondering if adding another toggle for fetching the full page content is necessary when it was made by default beforehand. Could it be that you experience excessive Cloudflare captchas due to your local network? I tried accessing the feed in rapid succession with the last 20 items (cache disabled) and no Cloudflare captcha/block was happening.

On the other hand, adding a limit option is standard practice and helps keeping the feed fetch time in check.

@SqrtMinusOne
Copy link
Contributor Author

Could it be that you experience excessive Cloudflare captchas due to your local network?

Maybe. I run RSS-Bridge on a VPS I pay for with crypto; perhaps this got the network blacklisted. But it used to be fine for me as well.

I honestly have no clue how Cloudflare decides when to block requests, and it seems kinda random from site to site. It also changes over time, usually in the worse direction. E.g., on phys.org I can fetch a maximum of 3 feeds every 4 hours.

I wish they never existed :-(

@Mynacol
Copy link
Contributor

Mynacol commented Oct 31, 2025

I run RSS-Bridge on a VPS I pay for with crypto

That is a strong indicator that it is IP reputation based (thank your neighbors). I want to kindly ask you to remove this option again. I expect you have problems with other (Cloudflare-querying) bridges as well, and we won't add an option to each of them. There are some general "Cloudflare handling" elements in rss-bridge, e.g. curl-impersonate. But I don't want such options in specific bridges if they generally behave like others contacting Cloudflare.

I'm also confused by those HTML encoded & parts in the categories. It seems the bridge makes the right thing. But somehow they get double-encoded. @dvikan can you have a look at this?

@SqrtMinusOne
Copy link
Contributor Author

SqrtMinusOne commented Nov 2, 2025

I want to kindly ask you to remove this option again.

Ah, I've misread your original comment, sorry. The note about Cloudflare referred to a week-long caching time; the contents option was there for debugging, mostly. Removed it.

I'm also confused by those HTML encoded & parts in the categories.

No, it's the website. Adding html_entity_decode fixes the issue.

@Mynacol Mynacol merged commit c0cb44d into RSS-Bridge:master Nov 2, 2025
13 checks passed
@Mynacol
Copy link
Contributor

Mynacol commented Nov 2, 2025

Thanks. Now this is a great PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants