this thread is not because there is a problem in Tiny Tiny RSS - Its working fine and I am using it since long years. Thank you for your great work!
This thread is about the fact that Tumblr changed something with its RSS feeds, causing problems. And maybe you can give me a hint to find a workaround.
The facts:
Tumblr-RSS feeds worked fine before. But now they made a change: When accessing any Tumblr-RSS-feed in any browser (for example: Pictures/Gifs about the Funny Gaming World.), there is a redirect, showing a page with privacy-related informations. After hitting the OK-button, the RSS-page is shown.
Because of this redirect Tiny Tiny RSS is not able anymore to read the feeds. I am searching for a way to override this OK-button, so the feeds are working again. Maybe anyone has an idea?
If you have some technical skills, see if there is anything unique about the redirect (added query strings, cookies, etc.) and then modify the feed in TT-RSS accordingly.
I have a handful of Tumblr feeds as well; both normal and login gated.
As far as testing with browser, I wouldn’t recommend it. Use feed debugger (f shift+d in TTRSS) and see what happens there. Especially, as JustAMacUser pointed out, what’s going on with the redirect URLs.
In a browser, Tumblr will still force a login for an RSS feed on a gated feed. TTRSS (or CURL, etc) will still fetch the feed without any questions.
Same issue as the original poster. Works fine with a US IP address, doesn’t work with a EU one. Feed debugger:
[19:05:06/7669] start
[19:05:06/7669] local cache will not be used for this feed
[19:05:06/7669] last unconditional update request: 2018-05-19 19:04:19
[19:05:06/7669] stored last modified for conditional request:
[19:05:06/7669] fetching [http://redacted.tumblr.com/rss] (force_refetch: 1)...
[19:05:07/7669] fetch done.
[19:05:07/7669] source last modified:
[19:05:07/7669] fetch error: LibXML error 68 at line 21 (column 29): xmlParseEntityRef: no name
[19:05:07/7669] + LibXML error 68 at line 21 (column 29): xmlParseEntityRef: no name
[19:05:07/7669] + LibXML error 68 at line 21 (column 30): xmlParseEntityRef: no name
[19:05:07/7669] + LibXML error 68 at line 21 (column 41): xmlParseEntityRef: no name
[19:05:07/7669] + LibXML error 68 at line 21 (column 42): xmlParseEntityRef: no name
[19:05:07/7669] + LibXML error 76 at line 30 (column 313): Opening and ending tag mismatch: link line 10 and head
[19:05:07/7669] + LibXML error 68 at line 38 (column 1098): StartTag: invalid element name
[19:05:07/7669] + LibXML error 68 at line 38 (column 1482): StartTag: invalid element name
[19:05:07/7669] + LibXML error 68 at line 39 (column 81): StartTag: invalid element name
[19:05:07/7669] + LibXML error 38 at line 41 (column 111): Unescaped '<' not allowed in attributes values
[19:05:07/7669] + LibXML error 65 at line 41 (column 111): attributes construct error
…
I forgot to mention. Yes, I am from EU and this problem is GDPR-related, right.
The OK-Button is not just a simple link, there is some script involved. And Im a noob in that matter… @mamil was faster and already provided the debugger log.
Ok, so this is just a problem for european users. I will try to understand how this redirect works (not very hopeful), maybe I will be able to give more informations.
The GDPR page promises to vanish once you log in. I’ve signed up to Tumblr and tried to login with curl hoping that it would set the cookie, but no luck so far. Here’s what I tried.
I confirm. Thanks ever so much for the tip. I’ll stick with FeedBurner for now, hoping that Tumblr will eventually get its act together and remove the GDPR screen.
maybe someone should contact tumblr and ask them to unfuck their rss feeds
I already did that before opening this thread, of course But I have little hope that they understand the problem right and I doubt that they are really caring about their feeds. Lets see.
@reibuehl I dont think so. I spent some hours now, creating all the feeds (a lot!) in feedburner and telling Tiny Tiny RSS about the new (feedburner-)URLs.
Its a lot of work, but thats the way to workaround the bulls**** that Tumblr has done.
wouldn’t it be easier to get a lowest tier VDS outside of EU? probably even something like openshift would work
put a simple noncaching http proxying script on it (that’s like 10 lines of code in php or w/e) and you’re done (well, limit it to tumblr rss feeds)
screwing around manually with feedburner looks like too much effort
I managed to find a temporary workaround (temporary since there is an exp value with a unix timestamp in the cookie).
Get a user-agent switcher addon for your browser. Set it to use your TTRSS user-agent (should be Tiny Tiny RSS/17.12 (a7265d9) (http://tt-rss.org/) with a7265d9 being a part of the git hashsum of the latest commit of your TTRSS).
Go to a tumblr RSS URL. Accept or say “later” on the consent page
Open your browser dev tools, get the content of the pfg cookie
Apply this patch to your TTRSS (the line numbers may differ from yours as my TTRSS is patched for other purposes) and change the value of the cookie for yours: