@Gte Nope. It’s a fad. I recommend blogs. 🙂

@manton Did you decide to pay for API access?

@fahrni I am going to guess ‘no’ - but then I am not 🥳

@agiletortoise @Gte Yeah, it is hard to tell. I decided to jump into it this week after a couple web apps (Bridgy and Jetpack) were shut down with weeks still to go before the deadline.

@manton sorry about that; I wish we could have talked about it at the developer conference in November, but that was cancelled, which made me ready to quit, and then we were laid off, so…

@fahrni @JohnPhilpin My plan was to pay for a limited number of months to help people transition away. I’m not sure, though.

yes - heard you to that effect in one of the CoreInt podcasts - but haven’t people had enough warning that they will have transition? It’s not as if it will come as a surprise. My two cents? FAGEDDAABOUTIT - and build for the future.

/end two cents/

@andypiper I was just thinking while reading docs earlier how frustrating it must’ve been for Twitter employees to have work on the 1.1 → 2.0 transition effectively halted by layoffs. Hope things have worked out for you, though.

@manton can you even use one of the two non enterprise plans?

@paul Not the free one, but enough people have been disabling cross-posting anyway that I thought we’d fit in Basic. I don’t read any tweets. Now I’m confused, though, because the announcement said 50k posts (fine) but the web site says 3k tweets (not fine). It’s all half-baked.

@manton Right, you’d mentioned that on Core Int. I forgot about that, but it makes sense to me.

@manton 3k per authenticated user, 50k per app.

@paul @manton Wait, is this about cross posting? I was thinking it was about Twitter auth?

I was working on a project earlier using API 2.0; I was wondering how I was going to handle image uploading on an old API gracefully… and now they want me to pay for that privilege?

@paul Got it, thanks. That’s what I had remembered but got led astray by the web site.

@manton look at the rate limits too, I think its all based on that and there's 24 hour app/user rate limits.

@fahrni Both. Auth has to change to use the new API to continue to support cross-posting.

I sort of hope you discontinue it so I can actually have a reason to quit posting to Twitter. LOL!

@agiletortoise @Gte @manton I noticed this while poking around today. The implication being that part of 1.1 will be sticking around, for the time being at least. It also implies that handful of 1.1 endpoints will work under the free tier…

But the entry for the cap for returned tweets is a big red X for the free tier, so what does that mean? 🤷‍♂️

It seems the only way to really know is just wait and see.

@montyhayter It’s confusing. Because 1.1 and 2.0 use different versions of OAuth, you can’t mix both endpoints. It would require asking a user to authenticate twice, unless I’m missing something, or I guess reverting back to 1.1 again.

@manton Confusing and frustrating. How is anyone supposed to plan with the way this has all been handled?

So for the time being I’ll work on other things until something breaks - Twitter integration is, while desirable, thankfully non-critical for me. And it won’t let me create a project for v2 access, so there’s not much I can do at the moment in any case.