Closed JSn1nj4 closed 9 months ago
Currently unsure if should use OAuth 2.0 or Basic Auth. https://developer.twitter.com/en/docs/authentication/oauth-2-0/user-access-token
If I go full OAuth 2.0 with PKCE, I'll have to...
Cache-Control
header for the right amount of timeSome other resources:
Ended up going with this: https://github.com/noweh/twitter-api-v2-php
Well thought-out Twitter API client that supports both OAuth 1.1 and 2.0, depending on endpoints needed, and provides the rate-limiting headers back as well. Will be useful for caching and preventing hitting the API when not appropriate.
This should only happen on first publish, not subsequent. Will need OpenGraph tags and/or Twitter Card tags generated as well - separate issues.