Yesterday evening I received this answer from Twitter: Thanks for your message. Unfortunately, this is an issue we do not currently support. I realize this can be frustrating and I appreciate your understanding.
Well, that will help..... OMG
I have mine set for 'after each new day' and 'after each new month'. I am now getting fail to tweet because of 'duplicate tweets'. It has been working fine for over a year now so something has changed at twitter hq.
The strange thing is that some / most? users of the Meteobridge service are still working without any problem, just one example: https://twitter.com/MeteoOudkarspel
But a lot of others are banned by twitter.
I always used to send weather tweets every 30 minutes with Weather Display up until I changed systems around 22nd October to MB Pro. As we are all aware Twitter had changed their policy in an attempt to stop duplicate posts. I changed my tweet interval to one hour and they seemed to be posting every 3 hours. Last evening I did an experiment and changed the interval to 15 minutes just to see what this might produce. This morning I was pleasantly surprised with the result. Not perfect but a big improvement. Has anybody else seen a change. No doubt after posting this it will revert back to 3 hours but I thought I would share this.
Don’t get your hopes up to high Bob I saw this morning also a (short) change because at 8.00 9.00 and 10.00 it worked and then it stopped again. Also I see a change in frequency when I send a different tweet “by hand” ??? After that it looks like it’s shortly back to normal (every hour) and then it changes back again to once every three hours.
Hi Gents, I have also been using diffrent timing sequences to try and get regular obs out from my weather station via MeteoPro and Twitter and it works for the first one or two post then it reverts back to 'cannot post duplicate tweets' As it stands I cannot see away of automatically getting wx data out from Pro via Twitter. Any work arounds would be appreciated. Regards Paul @GuisboroughWx
I wish I can come up with a simple solution. Unfortunately, twitter does not tell when a tweet looks like being too similar. Did you try adding an epoch timestamp at the end? Not really something useful but might add diversity and we can see if this tricks twitter. Just add [epoch] to get a nasty, big, non-repeating number (seconds since 1.1.1970 or so).
Thanks for the info, my knowledge on epoch is limited, however, I used (Y-m-d H:i:s) and this worked for 3 posts between 11:00 and 12:00 (see below). I also noticed that i:s was replicated at the end of each post, so there must be something wrong?
GuisboroughWx wrote: ↑Tue Nov 06, 2018 10:12 pm
Thanks for the info, my knowledge on epoch is limited, however, I used (Y-m-d H:i:s) and this worked for 3 posts ....