Content pfp
Content
@
0 reply
0 recast
0 reaction

kei.eth pfp
kei.eth
@keikumata
interesting challenge we ran into yesterday for @deform many users were unable to connect their Twitter account due to one of the Twitter OAuth APIs returning a 404. we think it was some kind of rate limiting or an unannounced decrease in allowed throughput most platform issues we have are caused by Twitter
3 replies
1 recast
2 reactions

kei.eth pfp
kei.eth
@keikumata
the "random poodle" for reference - it's weird that an API endpoint would return this as a response instead of a proper 429 though.
0 reply
0 recast
3 reactions

kei.eth pfp
kei.eth
@keikumata
it's also certainly possible that their APIs are just completely borked atm and there's not much we can do to alleviate this looks like some people had this issue back in July 2023 https://devcommunity.x.com/t/get-404-web-page-not-json-message-with-404-status-code-when-calling-v2-api/198795/5?u=keikumata
0 reply
0 recast
2 reactions

albert pfp
albert
@thatguyintech
rip twitter
0 reply
1 recast
2 reactions