Closed annevk closed 1 year ago
The only part of this that seems hard is making the code changes to use the v2 API. Currently we're using the twitter-lite
npm package to handle the OAuth stuff. (The actual POST request part is trivial and doesn't really need a package.) That doesn't seem to have been updated yet; https://github.com/draftbit/twitter-lite/issues/186 has some discussion on workarounds and PRs.
https://www.npmjs.com/search?q=twitter%20v2 has some alternatives we could try to drop in.
WHATWG admins got this email:
I'm not interested in trying to sort this out. If someone is let me know.
If nobody steps forward we should probably deactivate https://github.com/whatwg/participate.whatwg.org/blob/main/lib/tweet-webhook.js.