in July Twitter is removing the 140 character limit

[OhioRVHawk]

I do not know if it is known yet, or how this will effect Cumulus program itself. but I thought it would be a good Idea to post it here, so the owner can make any changes to it. if need be before Cumulus goes down on twitter posts....

Twitter Removing the 140 character limit from Direct Messages

We’ve done a lot to improve Direct Messages over the past year and have much more exciting work on the horizon. One change coming in July that we want to make you aware of now (and first!) is the removal of the 140 character limit in Direct Messages. In order to make this change as seamless as possible for you we’ve included some recommendations below to ensure all your applications and services can handle these longer format messages before we flip the switch.

We recommend taking the following actions in preparation:

Review the new API additions below.
Update your GET requests so you will be able to receive the full length of DM text.
Adjust your app UI to accommodate longer DM text.
We encourage you to test and deploy the above changes in advance, but you won’t be able to send longer DMs until we launch in July. In the coming weeks though, we will update this post to include directions on how to test these changes, as well as a more specific launch date.

You may be wondering what this means for the public side of Twitter. Nothing! Tweets will continue to be the 140 characters they are today.

API updates:

REST API
DM read endpoints (GET direct_messages240, GET direct_messages/sent67 and GET direct_messages/show65)
Send “full_text=true” as a query parameter to receive long DM text. If this parameter is not provided, you will get a truncated version of the DM. There will be no structural changes to the response returned by these endpoints.
DM write endpoint (POST direct_messages/new61)
The “text” parameter will start accepting text longer than 140 characters. The new limit for DMs will be 10k characters.

Streaming API
User Streams (GET user67) and Site Streams (GET site24) will automatically start receiving DMs that have text longer than 140 characters. Unlike the REST API, no additional parameter is needed. There will be no structural changes to the objects returned by these endpoints.

https://twittercommunity.com/t/removing ... rce=Eloqua

[BigOkie]

I do not know if it is known yet, or how this will effect Cumulus program itself. but I thought it would be a good Idea to post it here, so the owner can make any changes to it. if need be before Cumulus goes down on twitter posts....

Twitter Removing the 140 character limit from Direct Messages

We’ve done a lot to improve Direct Messages over the past year and have much more exciting work on the horizon. One change coming in July that we want to make you aware of now (and first!) is the removal of the 140 character limit in Direct Messages. In order to make this change as seamless as possible for you we’ve included some recommendations below to ensure all your applications and services can handle these longer format messages before we flip the switch.

We recommend taking the following actions in preparation:

Review the new API additions below.
Update your GET requests so you will be able to receive the full length of DM text.
Adjust your app UI to accommodate longer DM text.
We encourage you to test and deploy the above changes in advance, but you won’t be able to send longer DMs until we launch in July. In the coming weeks though, we will update this post to include directions on how to test these changes, as well as a more specific launch date.

You may be wondering what this means for the public side of Twitter. Nothing! Tweets will continue to be the 140 characters they are today.

API updates:

REST API
DM read endpoints (GET direct_messages240, GET direct_messages/sent67 and GET direct_messages/show65)
Send “full_text=true” as a query parameter to receive long DM text. If this parameter is not provided, you will get a truncated version of the DM. There will be no structural changes to the response returned by these endpoints.
DM write endpoint (POST direct_messages/new61)
The “text” parameter will start accepting text longer than 140 characters. The new limit for DMs will be 10k characters.

Streaming API
User Streams (GET user67) and Site Streams (GET site24) will automatically start receiving DMs that have text longer than 140 characters. Unlike the REST API, no additional parameter is needed. There will be no structural changes to the objects returned by these endpoints.

https://twittercommunity.com/t/removing ... rce=Eloqua

Wouldn't think it would affect it at all, since Cumulus posts to the timeline, not to direct messages. Timeline messages will still have the 140 character limit is my understanding.

[steve]

Cumulus does "Tweets" - 'status updates' (i.e. public messages) not 'direct messages' (i.e. private messages to a person or group), so shouldn't be affected.

[OhioRVHawk]

Thanks Steve, I didn't know if it would effect the software in any way. Steve if I may Ask, would this mean that we could add a little more to the tweets sent out by the software? or would that have to be a we write to the software to do it?? (Sorry I get confused with all this junk . thanks

[steve]

You will still be limited to 140 characters as Cumulus sends 'Tweets' (public messages) and not direct messages (private). Only private messages are having the limit lifted. I don't propose to add direct (private) messages to Cumulus, I can't imagine that it would be of use to most people - the point of this surely is to publish your weather data for everyone to read?

[OhioRVHawk]

Thank You again for your reply.

AS I said I know nothing of this GET and SeND junk. Probably would loose my mind trying to figure it out. My Thought in this was just a question as if it would extend how much info that Cumulus would, or could send out if it were something different by Twitter. and to be able to add more information to twitter, from Cumulus, for example, I have into my twitter.txt

Temp <#temp>°F. Feels Like <#apptemp>°F, Winds <#wdir>-<#wspeed><#windunit>, Gust to <#wgust>. DewPoint <#dew>, Rain <#rfall>, Pressure <#press> <#pressunit> <#presstrendenglish> #shelbyohwx

Sadly sometimes it gets cut off if the values were larger than the normal (lower) output of the program. I truly wish that Twitter would lift the limit to 165 for regular twitter tweets.. this way I could add more information to the normal program tweet....

If I may ask this question, is there maybe another way to say, let the program send out its tweet with data to twitter, and maybe add something like a addendum tweet, from say a batch file, that could read the twitter.txt, and send it along as a seperate addendum to the Main tweet??? Please forgive me for the trying to explain this. I do not do so well with getting out whats in my brain, to text lol, (I think it happened when I turned 50) and not to mention the medications I take for the pain of being disabled.

I hope you understand of what I am trying to do Sir's.
Thank you In Advance, Ray

[steve]

Cumulus could send multiple tweets - people sometimes do this when they have more to say than will fit in 140 chars. But I don't propose to change the Twitter code in Cumulus, it's a complete pain to maintain already,with Twitter changing their API so often. They don't seem to want third party applications updating Twitter at all. I'm sure the day will come when they stop third party applications accessing Twitter completely.