twitter's graphql api started returning 404 on every request from cobalt a few hours ago. all instances are affected.
update: the issue is not with request itself, same exact request works fine when done with curl. could be something related to fetch/undici?
Originally created by @wukko on GitHub (Jun 15, 2024).
Original GitHub issue: https://github.com/imputnet/cobalt/issues/573
twitter's graphql api started returning 404 on every request from cobalt a few hours ago. **all instances are affected**.
**update:** the issue is not with request itself, *same exact request* works fine when done with curl. could be something related to fetch/undici?
instagram is not related to this; instagram also works, but cobalt can't get all links due of instagram/profile restrictions
<!-- gh-comment-id:2169494872 -->
@lostdusty commented on GitHub (Jun 15, 2024):
instagram is not related to this; instagram also works, but cobalt can't get all links due of instagram/profile restrictions
turns out twitter blocked nodejs TLS client fingerprint, this is why curl worked fine while fetch got 404. now cobalt randomizes it just like chrome :)
<!-- gh-comment-id:2170380085 -->
@wukko commented on GitHub (Jun 15, 2024):
turns out twitter blocked nodejs TLS client fingerprint, this is why curl worked fine while fetch got 404. now cobalt randomizes it just like chrome :)
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @wukko on GitHub (Jun 15, 2024).
Original GitHub issue: https://github.com/imputnet/cobalt/issues/573
twitter's graphql api started returning 404 on every request from cobalt a few hours ago. all instances are affected.
update: the issue is not with request itself, same exact request works fine when done with curl. could be something related to fetch/undici?
@Yumega commented on GitHub (Jun 15, 2024):
Both Instagram and Twitter are out of work
@lostdusty commented on GitHub (Jun 15, 2024):
instagram is not related to this; instagram also works, but cobalt can't get all links due of instagram/profile restrictions
@wukko commented on GitHub (Jun 15, 2024):
turns out twitter blocked nodejs TLS client fingerprint, this is why curl worked fine while fetch got 404. now cobalt randomizes it just like chrome :)