Twitter Dev Accounts Changes - Does it hamper Twitter embeds for NodeBB?
-
From testing Twitter embeds still appear to work on NodeBB, not so for other platforms that require API key's, with the latest changes and suspensions of dev accounts (apps/keys) they are all broken and at $100/month to bring that back I can't see anyone stumping up that for embeds only. Something might give but in the meantime on the twitter side as they see traffic drop (surely that has to happen once embeds on other platforms dry up), we can only wait and wonder. Or not.
Is there anything that might might jeopardise the twitter embeds working in NodeBB at present, which if I am correct the embedding in NodeBB doesn't require API's or third party service, only the plugin or maybe with v3, since I haven't been paying attentions perhaps it is native now?
-
I don't think NodeBB embeds tweets by default. It's still a plugin, not sure which one you're referring to though.
My guess is that it's using OEmbed API (https://developer.twitter.com/en/docs/twitter-for-websites/oembed-api - if you're using the iframely plugin, then I think it uses this) or their script (https://publish.twitter.com/) - which are AFAIK still free (and do not require an API key), but not that customizable.
Before the absurd pricing change, as far as I can tell, it was fairly common to use the read API to get the post data and then create a custom interface around it, which is why many websites broke.
-
@oplik0 Do you have any idea then what is the status of the twitter going. having never set this up in NodeBB but other platform require a dev account to allow this feature to work?
@julian @baris What is the status of the SSO with recent change in twitter, does tha plugin require Key and tokens via a twitter Dev account?
-
Would a plugin that just parses meta og tags work? Or does Twitter not like that?
