New version that supports Twitter API v2?

Thanks for reporting this and for your potential offer for help in providing compatibility with the Twitter API v2.

The EOL of v1 was not on our team's radar, but we plan to continue to support this module, so we will need to provide v2 support, and we welcome any contributions in that direction. Ideally a solid plan and roadmap should be established before any work on the actual code implementation.

Let's get the conversation going :)

Thanks so much for your interest! This module has been great for what we needed.

The road map should account for differences in the Twitter V2 API including:

• Endpoint URLs
• App and Project requirements
• Request parameters

The Twitter API v2 endpoints require that you use credentials from a developer App that is associated with a Project when authenticating your requests.

The module would need to be updated to account for these differences, but overall it looks like the same functionality would remain. There might be additional credentials for authentication.

What components should a road map include? Do you have an example we can reference?

I'm thinking of something along the lines of https://www.drupal.org/project/linkit/issues/3345480 🌱 LinkIt Release Roadmap and Issue Prioritization Active , which will provide a estimated timeframe and sequence of actions for when the Twitter Profile Widget starts supporting v2, when it stops support of v1, and what the major version releases relate to (for example, I expect that version 3.x of Twitter Profile Widget will support v1 of the Twitter API, while we will create a new major version release, 4.x, to support Twitter API v2.

Just something to spell it out to the community, with a rough timeline, one that is not set in stone.

We should also call out what Twitter API v1's EOL date is.

There isn't an official EOL for v1 but they are limiting access to it.

They announced they are ending the Premium v1.1 access tier on April 29th. The API v1 list endpoint will no longer be available unless on an Enterprise tier. Migrating to API v2 will allow us to continue to pull tweets from a list on the Basic tier. On the Free tier it it will allow puling tweets from a user. And it looks like it will also allow pulling tweets from multiple user accounts, which may make it possible replicate a list feature in some cases, but the rate limits on the free tier will make it not very usable in our development workflows.

Thanks for the update on the available tiers, @squiggy.

As an informational note, our team also investigated options and determined that Twitter's embed option, https://publish.twitter.com/# , may meet the minimum needs of sites we support that are currently using the Twitter Profile Widget module.

It doesn't have feature parity -- it doesn't support listing Tweets matching a search parameter, or favorited tweets -- but that may not be a deal-breaker for our users.

So, for expectations-setting: I am happy to continue to work on supporting API v2 in this module in collaboration, but it is probably not a high priority for our work at this point.

It appears that Twitter has now broken, possibly temporarily, the embed feature. I think @Squiggy and I may be back in a position to work on porting to V2, things are still in flux. @mark_fullmer have you also seen your embeds stop working?