-
Notifications
You must be signed in to change notification settings - Fork 720
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
Age-restricted tweets #419
Comments
I don't know when this was introduced exactly, but it has been happening for at least several days now (I first saw it on the 26th). If anyone knows of a workaround to access this content, I'm all ears. But snscrape does not and will not support anything that requires authentication: #270 |
That's a shame. I don't think that any workaround's going to come up. |
Yeah, it's unlikely. Until such time, this is impossible to fix in snscrape. This was introduced into Twitter's 'Sensitive media policy' in early January, by the way: https://web.archive.org/web/diff/20220105171207/20220106023308/https://help.twitter.com/en/rules-and-policies/media-policy |
Me of little faith: mikf/gallery-dl#2354 (comment) |
Lovely. I haven't thought yet about how that would best be integrated, but at least it's an option. My initial thought would be a separate Quoting that comment here just in case that issue vanishes:
|
Can confirm that syndication URL seems to still work. |
Example (NSFW):
https://twitter.com/TabletKnight/status/1499083203881099264 (NSFW)
EDIT: Viewing the tweet without an account will result in this message, which has been preventing SNScrape from recording any data:
You can view the tweet as long as you're signed into an account (even a suspended one, meaning you can view them with one of those accounts that get instantly banned for not having a phone number).
Going by that, I think that SNScrape should still be able to download NSFW posts made in the future without having to resort to private/requested/developer API access, but possibly not without using the sign-in cookies of an existing user. Supporting this would also allow for the scraping of users marked as private (as long as your own account can see it), so double win I think.
It could also be possible to put a mechanism in place for automatically creating new accounts and saving those details just for scraping, but I think that kind of abuse of the service wouldn't be overlooked by Twitter.
The text was updated successfully, but these errors were encountered: