Topic: Goodbye to the free Twitter API

[CNYWeather]

I've been using this since forever ago for TweetWX.
Looks like it's time has come to an end with no more free use of the Twitter API.

https://www.cnbc.com/2023/02/02/twitter-to-start-charging-developers-for-api-access.html

[saratogaWX]

Sigh.. If they cut off the free API, I'll stop posting conditions/forecasts with TweetWX to my site (and deprecate the script set).

[chief-david]

most likely will kill WeatherDisplay users (like me) also.

[chief-david]

Wanted to bump this


Got this from IFTTT

We wanted to let you know about a potential impact to your Twitter Applets.

Starting Monday, February 13th, 2023, Twitter will no longer support free access to their API. As a result, we expect that any Applet that connects with Twitter will stop working. You can learn more about Twitter's upcoming API change here.

We're notifying you because you're using an Applet that leverages the Twitter integration. To see which of your Applets may be affected, you can refer to your My Applets page.

We know this might be disruptive and we're working with Twitter to find the best solution. We will continue to inform you of any progress on the matter.

Thanks,
- IFTTT team

[Bashy]

Well, thats just poop there goes my long standing WD to twitter feed and IFTTT twitter to FB feed.

I do pay for IFTTT so i wonder if this is why I've not had the email yet? even so, without the WD feed, the IFTTT will be dead anyway

[chief-david]

This one from Hennepin co WX


craig483
@craig483
·
16h
On Monday 2/13,
@HennepinWxAlert's automated weather alert system may stop working, as a result of changes made by
@Twitter
. I'm planning to send automated test messages periodically over the next few days to keep tabs on what's working and what's not!
Quote Tweet
craig483
@craig483
·
Feb 2
This change will likely lead to the closure of @HennepinWxAlert. I will let you know as soon as I know more. ☹️ twitter.com/TwitterDev/sta…

[saratogaWX]

They haven’t shut off my conditions/forecast tweets using TweetWX script (yet). Been doing those automated tweets since 2009.  I’ll keep watching.

[chief-david]

Got this from IFTTT

Starting on May 23, all free users will be limited to 2 Applets and unable to access Twitter Applets.

We hope you understand this change is designed to help us support our community and continue to focus on improving IFTTT. To ensure that your existing Applets continue without interruption, consider upgrading to Pro or manage your Applets via My Applets.

any info from anyone?

[K6GKM]

Got this from IFTTT

"Starting on May 23, all free users will be limited to 2 Applets and unable to access Twitter Applets.

We hope you understand this change is designed to help us support our community and continue to focus on improving IFTTT. To ensure that your existing Applets continue without interruption, consider upgrading to Pro or manage your Applets via My Applets."

any info from anyone?

IFTTT lost my business after they had a multi-day Facebook integration outage.  I figured out I could accomplish the same automation tasks for free (to a point I haven't reached yet) over at Make, formerly Intergromat.

Twitter, though, requires a paid subscription, but the integration is much richer than what is available in IFTTT.

[saratogaWX]

TweetWX scripts no longer function after 12:00 13-Jun-2023 Pacific.  Twitter has suspended the application ID for TweetWX for 'rules violations' (likely over 1500 tweets per month with all the instances sharing the same app ID).
Sigh.. I've now deprecated the scripts and suggest you take them off your cron executions.

[BaseLine]

1500 tweets per month

Did you guys expect a free lunch to last forever?  Why should someone provide a free service to hundreds of millions of people who spam it 24/7/365 with self promoting BS, scams and every form of degeneracy known to man?

Why should someone provide a free API access for someone who makes money off that very same API access?
Unless you are running a business that depends on Twitter API (then pay up like you pay for utilities etc.) nothing changes for you.
Good news is, millions of bot farms crash and burn. Maybe one day, Twitter noise to useful info ratio becomes acceptable and I actually bother to sign up. Probably not. I cant care any less if Twitter, Reddit, Facebook, Insta-blah and the rest go out of business tomorrow. Good riddance.

[chief-david]

Weather Display still working (for now) (knock on wood)

[mkutche]

Well looks like they killed it my observation no longer tweets!! So dumb!!! People are so money hungry now adays!!

[mkutche]

I have a few choice words for that Elon Musk idiot! but i'll just post it on twitter

[CNYWeather]

TweetWX scripts no longer function after 12:00 13-Jun-2023 Pacific.  Twitter has suspended the application ID for TweetWX for 'rules violations' (likely over 1500 tweets per month with all the instances sharing the same app ID).
Sigh.. I've now deprecated the scripts and suggest you take them off your cron executions.

If I have a Twitter Developer API account, Can I create my own key and ID to continue to use this?
I've been Auto-Tweeting other stuff on my account with this without any issues.

[saratogaWX]

TweetWX scripts no longer function after 12:00 13-Jun-2023 Pacific.  Twitter has suspended the application ID for TweetWX for 'rules violations' (likely over 1500 tweets per month with all the instances sharing the same app ID).
Sigh.. I've now deprecated the scripts and suggest you take them off your cron executions.

If I have a Twitter Developer API account, Can I create my own key and ID to continue to use this?
I've been Auto-Tweeting other stuff on my account with this without any issues.

You may be able to use a new APP key with the scripts.  It uses the V1.1 API, not the V2 API so I don't know if a API 1.1 app key can be created with your developer ID.. give it a try.

[CNYWeather]

Gotcha. I have both a 1.1 and 2 account so I'll give it a show when I get a chance to play with it.

[mkutche]

Gotcha. I have both a 1.1 and 2 account so I'll give it a show when I get a chance to play with it.

fill me in on how you are doing this? jw

[Maumelle Weather]

I have raised the time interval on when the forecast Tweets to once every 6 hours, but left my current conditions as is which is every hour. This should allow me to stay under their stupid post limit.

The question is does this 1500 tweets a month limit reset on the 1st? Guess I'll find out.


John

[CNYWeather]

TweetWX scripts no longer function after 12:00 13-Jun-2023 Pacific.  Twitter has suspended the application ID for TweetWX for 'rules violations' (likely over 1500 tweets per month with all the instances sharing the same app ID).
Sigh.. I've now deprecated the scripts and suggest you take them off your cron executions.

If I have a Twitter Developer API account, Can I create my own key and ID to continue to use this?
I've been Auto-Tweeting other stuff on my account with this without any issues.

You may be able to use a new APP key with the scripts.  It uses the V1.1 API, not the V2 API so I don't know if a API 1.1 app key can be created with your developer ID.. give it a try.

I was able to regenerate new keys and tokens using the API v1.1, paste them into the Globals and WX Conditions scripts, and my account it tweeting the current conditions once again.

[mkutche]

TweetWX scripts no longer function after 12:00 13-Jun-2023 Pacific.  Twitter has suspended the application ID for TweetWX for 'rules violations' (likely over 1500 tweets per month with all the instances sharing the same app ID).
Sigh.. I've now deprecated the scripts and suggest you take them off your cron executions.

If I have a Twitter Developer API account, Can I create my own key and ID to continue to use this?
I've been Auto-Tweeting other stuff on my account with this without any issues.

You may be able to use a new APP key with the scripts.  It uses the V1.1 API, not the V2 API so I don't know if a API 1.1 app key can be created with your developer ID.. give it a try.

I was able to regenerate new keys and tokens using the API v1.1, paste them into the Globals and WX Conditions scripts, and my account it tweeting the current conditions once again.

how did u do that? jw can you share please.

Thanks

[CNYWeather]

With my developer account, I created new secret and consumer keys within the API.
I then pasted them into the TweetWX Globals and within the TweetWX conditions.

But, someone decided to be a jerk and report my account for some reason
so thats all for nothing for the time being.

[mkutche]

With my developer account, I created new secret and consumer keys within the API.
I then pasted them into the TweetWX Globals and within the TweetWX conditions.

But, someone decided to be a jerk and report my account for some reason
so thats all for nothing for the time being.

Wow! Well crap.. idk how IEM Bot is still posting auto tweets..

[saratogaWX]

With my developer account, I created new secret and consumer keys within the API.
I then pasted them into the TweetWX Globals and within the TweetWX conditions.

But, someone decided to be a jerk and report my account for some reason
so thats all for nothing for the time being.

It may not have been a someone but a something that auto-flagged your account.  I had my original APP key suspended permanently by Twitter.  I used a different id (saratogaWXPHP) to sign up for a free developer ID, created an appid and consumer/secret keys.  Used them with the TweetWX-global/Tweet-forecast script (oath authenticated to the SaratogaWX id) and found this return status

Code: [Select]

status={
  "errors": [
    {
      "message": "You currently have access to a subset of Twitter API v2 endpoints and limited v1.1 endpoints (e.g. media post, oauth) only. If you need access to this endpoint, you may need a different access level. You can learn more here: https://developer.twitter.com/en/portal/product",
      "code": 453
    }
  ]
  so the V1.1 api doesn't seem to allow status posts using a free developer API.  Sigh.

[CNYWeather]

Ah. Thanks for that Ken.

I may create a new account then apply for a developer account again and see what happens.

It does suck after filing an appeal you get an email back with pretty much no info. At least i'd like to know
what part of the TOS were violated.