You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have encountered AmputatorBot's API incorrectly returning a "canonical" link for a tweet from a user account ending in "amp":
input: https://twitter.com/winamp/status/1791121664689725683
# at time of writing, this is a valid tweet
output: https://twitter.com/winstatus/1791121664689725683
# Twitter in a browser says "Page not found", but the HTTP status is still 200 😡
This is similar to #10, but different enough (triggered by the path component of the link instead of a parameter) that I thought creating a
new issue would be worthwhile. As a workaround, I believe it's safe enough to simply add Twitter to my project's default exclusion list.
The text was updated successfully, but these errors were encountered:
dgw
added a commit
to dgw/sopel-amputator
that referenced
this issue
May 16, 2024
AmputatorBot API treats Twitter links containing "amp" in the username
as AMP and tries to guess a canonical URL, e.g. `/winamp/status/tweetID`
becomes `/winstatus/tweetID`. Adding Twitter/X to the default list
should be a safe workaround.
Reported upstream at jvdburgh/AmputatorBot#19
I have encountered AmputatorBot's API incorrectly returning a "canonical" link for a tweet from a user account ending in "amp":
This is similar to #10, but different enough (triggered by the path component of the link instead of a parameter) that I thought creating a
new issue would be worthwhile. As a workaround, I believe it's safe enough to simply add Twitter to my project's default exclusion list.
The text was updated successfully, but these errors were encountered: