This is what Twitters new Developer Platform looks like. At the moment it's opt-in, but you can't switch back. /1

It's much cleaner than the old thing, where new products like the Premium APIs felt out of place. /2

I called it Developer Platform in the initial Tweet, but it should be Developer Portal. /3

I own too many apps to create a new one for the v2 API. I guess, it's time for summer cleaning.

I think the message is misleading. I probably have to delete 7 apps. /4

Let's start with my oldest app. App ID: 51706. I only kept it for nostalgic reasons. I set it up to display Tweets on my blog. Long before Twitter offered widgets. /5

As I expected, deleting one app wasn't enough. Twitter tells me the changes are now live, but the message that I have to delete one of my apps is still the same. Luckily there are some more apps, I don't use anymore. /6

Other apps I removed: 4451074 (first visualization experiments), 4327657 (network visualization of bloggers on Twitter), 13712660 (account management experiments), 6406701 (blocklist exporter), 14221917 (Dev app for accountanalysis), 13680478 (URL analyzer). /7

Finally, I am able to create a Project to use the v2 API.

1. Name. Uhm. Accountanalysis?
2. Intend. Currently: Exploring the API. (I hope I can change it late on.)
3. Description. I want to explore the API to some day migrate @accountanalysis to v2. /8

4. Name your app. Damn, I thought that was step 1. But that was only the project name, if I remember correctly. I could add an existing app as well. Too risky for now, as I don't know if that will change something. Let's call it Accountanalysis Dev.

Tokens are displayed once. /9

The user facing description was filled with an default text. To edit it, I need to go into the app settings. That's okay, because to enable third party auth (so users can use the app), you have to got there anyway. /10

When enabling 3rd party auth, callback and website urls are required. The same as it already was with the old API. Other fields stayed the same as well.

Even though we were told otherwise, key and secret are still visible. But only until 2021-12-01. /11

I am slightly confused because in the overview it says V1.1 ACCESS for the newly created project. Let's try it anyways. /12

The keys work fine with the v2 API. Once I sent the first v2 request (requesting all replies to the first Tweet in this thread), the v2 label showed up in the developer portal as well. /13

That's it for now. Everything worked flawlessly. But I won't switch any projects to v2 until the elevated access levels are available. The basic access levels are too low. 500k Tweets per month shared across all users that use the app. /14 https://twitter.com/IgorBrigadir/status/1293912286793314308