-
-
Notifications
You must be signed in to change notification settings - Fork 0
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
instagram: oembed endpoint deprecated #1
Comments
I don't think Facebook understands what "deprecated" means. Deprecated stuff should still work, just with a warning that it will stop working later. The state described here is "unavailable". Self-assigning to move |
As reported in #1996, Facebook "deprecated" the oEmbed API endpoint. However, instead of a true deprecation where the endpoint simply starts returning a warning (or even just is marked as deprecated in docs), FB essentially *removed* the endpoint. It no longer returns valid JSON at all, let alone the expected result. Sopel receives plain text stating that the endpoint is "deprecated", with a link for more details. The replacement API endpoint requires an API key, and this seems like a good time to consider removing the Instagram plugin to its own package. I will prepare that change separately, mostly so this fix can be easily cherry-picked into 7.0.x for maintenance, but also because it could be enough to wait for removing the plugin entirely until Sopel 8.0. I'm not personally signed up for Instagram's developer program, so it wouldn't be fair if I alleged that FB never sent a warning before this endpoint stopped working. They might have. I'm just taking issue with the use of the term "deprecated" for something that is *nonfunctional* rather than merely unmaintained or scheduled for removal.
Realized that sopel-irc/sopel#2000 obsoleted this issue in its original location, so it made sense to move it over to this standalone plugin repo. |
Should anyone wish to work on this, using an InstaFix instance as the "backend" seems sanest. |
Description
When sopel tries to get info on an instagram link it fails with the message:
That happens because, instead of a json, sopel gets the following message:
So not only has the endpoint changed, but it also requires an access token now.
Reproduction steps
Expected behavior
Sopel is able to display instagram metadata
Logs
Environment
.version
: 82e3939a471e5f4d2909a8fb3cfbdad6d14388c9Notes
Anything else we should know?
The text was updated successfully, but these errors were encountered: