dangered wolf
dangered wolf
Translation is working in API, so this time it affects just embeds
I pushed the fix above, which should fix translation again. Let me know if you still have any problems. Btw, if you want to add a query string to invalidate...
Confirmed, if you try translating, it says post not found. Working on the underlying cause
Last night, i was able to confirm translations had stopped working, but they started working again today. It seems the issue might have been a server-side one.
The issue from the very beginning is that short (especially memorable) .com domains are quite expensive, so not really sure what I can do about this tbh :/
Well apparently enough people agree with you because now we have incredible domains such as `girlcockx`, `yiffx`, `skibidix` which host their own instance of / redirect to fxtwitter. They are...
Yeah no problem! :D
Probably related to #435 / #455
For some reason the GraphQL endpoint for TweetResultByRestId is returning a 404 now, which we typically use when fetching translations from Twitter API. Otherwise, we would normally use the TweetDetail...
This issue seems to have been resolved now so I will go ahead and close it