Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wrong display in wallabag (nitter.net) #7190

Open
wallabag-bot opened this issue Jan 17, 2024 · 3 comments · Fixed by fivefilters/ftr-site-config#1313
Open

Wrong display in wallabag (nitter.net) #7190

wallabag-bot opened this issue Jan 17, 2024 · 3 comments · Fixed by fivefilters/ftr-site-config#1313

Comments

@wallabag-bot
Copy link

Sent by Harold De Voeght and automatically created by email


https://nitter.net/PatriceReviron/status/1721211030355759495

It cannot fetch the content. An idea?

@j0k3r j0k3r changed the title Wrong display in wallabag Wrong display in wallabag (nitter.net) Jan 17, 2024
@jman-schief
Copy link

At the time of writing this comment, nitter.net returns an error

$ curl -i https://nitter.net/PatriceReviron/status/1721211030355759495 
HTTP/2 403 

Using another Nitter instance correctly saves the bookmark, so I'd assume it has something to do with that

@HolgerAusB
Copy link

HolgerAusB commented Jan 19, 2024

I had a short look on it. 403 means 'forbidden', so nitter is preventing to load the real content for non-browsers. I tried to set several different user-agents but had no success. They are doing some 'better' voodoo to identify cURL/wallabag.

Other instances may not blocking crawlers.

@HolgerAusB
Copy link

@jman-schief

nitter.net is blocking non-human crawlers, so

This works NOT with wallabag UI

This only works with wallabagger browser-plugin with activated
option 'Retrieve content from the browser' in it's settings

If you are self-hosting wallabag, copy nitter.net.txt to your <wallabag>/vendor/j0k3r/graby-site-config/, and clear cache.

For app.wallabag.it we need to wait for the next release.

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

Successfully merging a pull request may close this issue.

3 participants