Twitter error **solved**
Moderator: Mattk
- WA4OPQ
- Senior Boarder
- Posts: 44
- Joined: Mon Feb 29, 2016 5:36 am
- Location: Tennessee, USA About 40 miles west of Nashville y'all.
- Contact:
Re: Twitter error
My 7PM summary is posting every other day, so it looks like Twitter will allow similar messages after 24 hours. My real concern is on my incremental tweets. Just yesterday I had winds where a 34mph gust was reported but the 42mph tweet was blocked. I've revamped my wind tweets and I'm hopeful they are different enough that Twitter will let them through. We are having a windstorm tomorrow so I should be able to find out.
[HH]:[mm][APM] -
#if# {*([wind0wind-max10=mph.1:0] < 20)*} #then# It's windy in #else##fi#
#if# {*([wind0wind-max10=mph.1:0] > 20) & ([wind0wind-max10=mph.1:0] < 30)*} #then# Gusty winds are blowing though #else##fi#
#if# {*([wind0wind-max10=mph.1:0] > 30) & ([wind0wind-max10=mph.1:0] < 40)*} #then# Watch for very strong gusts in #else##fi#
#if# {*([wind0wind-max10=mph.1:0] > 40) & ([wind0wind-max10=mph.1:0] < 50)*} #then# Wow, some really strong winds in #else##fi#
#if# {*([wind0wind-max10=mph.1:0] > 50) & ([wind0wind-max10=mph.1:0] < 60)*} #then# Lord have mercy, it is blowing crazy in #else##fi#
downtown Centerville, TN. : Winds [wind0wind-avg10=mph.1:--]mph [wind0dir-act=endir:---] Gust [wind0wind-max10=mph.1:--]mph #if# {*([wind0wind-max10=mph.1:0] > 40)*} #then# #HickmanSevereWx #TNwx #else##fi#
[HH]:[mm][APM] -
#if# {*([wind0wind-max10=mph.1:0] < 20)*} #then# It's windy in #else##fi#
#if# {*([wind0wind-max10=mph.1:0] > 20) & ([wind0wind-max10=mph.1:0] < 30)*} #then# Gusty winds are blowing though #else##fi#
#if# {*([wind0wind-max10=mph.1:0] > 30) & ([wind0wind-max10=mph.1:0] < 40)*} #then# Watch for very strong gusts in #else##fi#
#if# {*([wind0wind-max10=mph.1:0] > 40) & ([wind0wind-max10=mph.1:0] < 50)*} #then# Wow, some really strong winds in #else##fi#
#if# {*([wind0wind-max10=mph.1:0] > 50) & ([wind0wind-max10=mph.1:0] < 60)*} #then# Lord have mercy, it is blowing crazy in #else##fi#
downtown Centerville, TN. : Winds [wind0wind-avg10=mph.1:--]mph [wind0dir-act=endir:---] Gust [wind0wind-max10=mph.1:--]mph #if# {*([wind0wind-max10=mph.1:0] > 40)*} #then# #HickmanSevereWx #TNwx #else##fi#
- WessexWeather
- Senior Boarder
- Posts: 53
- Joined: Sun Apr 17, 2016 9:54 am
- Location: Wimborne, Dorset, UK
- Contact:
Re: Twitter error
I have just noticed that no automated tweets via Meteobridge have been posted for three days. I post at 7:30am, 1:30pm and 7:30pm, always starting with the time so each is different.
This has been working flawlessly for years, so I guess Twitter have changed something (again).
This has been working flawlessly for years, so I guess Twitter have changed something (again).
Simon

Re: Twitter error
Did someone try to add the epoch time (large fast changing integer) at the end? Template variable is [epoch]. May be that gives twitter enough of a difference between posts.
Re: Twitter error
One thing I have read elsewhere is Twitter strictly enforcing limits for tweets from applications. I have no idea what the limit may be, but this came up in a Cumulus forum post.
Guy
Guy
Re: Twitter error
Limit is 300 in 3 hours. I guess this is the problem. I just raised a ticket, asking for setting up the limit by factor 10 for Meteobridge.
- WA4OPQ
- Senior Boarder
- Posts: 44
- Joined: Mon Feb 29, 2016 5:36 am
- Location: Tennessee, USA About 40 miles west of Nashville y'all.
- Contact:
Re: Twitter error
The problem I have is not a number or how frequent. It's that the canned messages I use are seen as duplicate messages, as just the weather data has changed in each message, not the general wording. Wind speed and temperature will tweet incrementally, but now only the first one makes it past Twitter.
Question: If I re-write the strings to use a large number of text strings, when will I reach a memory limit?
Re: Twitter error
I think what was meant was to simply add a single unix type time stamp (epochtime U) seconds since Jan 1, 1970 to the end of each tweet which would be forever something unique and ever changing.
Re: Twitter error
Yes, that was the idea. But my deeper research yesterday makes me think that we as a Meteobridge community hit the 300 tweets per 3 hours limit they introduced shortly. I hope my request on lifting that - as it is clearly no misuse imho - will get a go from twitter.
As dealing with these large companies is not always going as expected, we will need some luck here. So please keep fingers crossed...
As dealing with these large companies is not always going as expected, we will need some luck here. So please keep fingers crossed...
- WA4OPQ
- Senior Boarder
- Posts: 44
- Joined: Mon Feb 29, 2016 5:36 am
- Location: Tennessee, USA About 40 miles west of Nashville y'all.
- Contact:
Re: Twitter error
I can't explain why, but I will give you the credit...but it seems to be working again.
Here is a shot of the rain from tonight. If Twitter was still blocking duplicate posts I should not have been able to do this.
Here is a shot of the rain from tonight. If Twitter was still blocking duplicate posts I should not have been able to do this.
- Attachments
-
- Clipboard01.jpg (66.64 KiB) Viewed 5442 times
Re: Twitter error
I slowly understand what is going on. Twitter has started to enforce a policy that every app (Meteobridge in total is one app in their counting) has a limit of 300 tweets in 3 hours. When the limit is reached, we get error 185. The current error message (duplicate) given by Meteobridge is misleading, this will be changed with next update to better reflect the twitter return codes.
I started the exemption process with twitter to get this limit raised. I can't say how fast they will do that and if they are willing to do so at all. I think we are not doing misuse, so I have good hopes.
Please also see this snippet from a discussion in the web:
I started the exemption process with twitter to get this limit raised. I can't say how fast they will do that and if they are willing to do so at all. I think we are not doing misuse, so I have good hopes.
Please also see this snippet from a discussion in the web:
- WessexWeather
- Senior Boarder
- Posts: 53
- Joined: Sun Apr 17, 2016 9:54 am
- Location: Wimborne, Dorset, UK
- Contact:
Re: Twitter error
Good to know there might be a resolution... albeit eventually.
It seems a little unfair of Twitter to restrict the apps, rather than users that abuse their quotas. Place a restriction on individuals, not the software they use.
Like I say I post just three automated tweets per day whereas some people post hundreds. I have lost followers in the past for posting too many automated conditions tweets - it’s not what the average follower wants to see.
It seems a little unfair of Twitter to restrict the apps, rather than users that abuse their quotas. Place a restriction on individuals, not the software they use.
Like I say I post just three automated tweets per day whereas some people post hundreds. I have lost followers in the past for posting too many automated conditions tweets - it’s not what the average follower wants to see.
Simon

Re: Twitter error
Meteobridge users should be fine again with twitter!
- WessexWeather
- Senior Boarder
- Posts: 53
- Joined: Sun Apr 17, 2016 9:54 am
- Location: Wimborne, Dorset, UK
- Contact:
- WA4OPQ
- Senior Boarder
- Posts: 44
- Joined: Mon Feb 29, 2016 5:36 am
- Location: Tennessee, USA About 40 miles west of Nashville y'all.
- Contact:
Re: Twitter error **solved**
This is awesome! Thanks for the great work.
Re: Twitter error **solved**
Looking good so far - thanks!!
Guy
Guy