Open thymjan opened 7 years ago
Oh, yes. I had the same problem, and (apparently) fixed it in the version I run but forgot to push it to Github.
For me, it happened for the "storm has ended" tweets, which were exactly the same, so it triggered the Twitter protection preventing bots from posting duplicates. So I added a timestamp (date and time) to the tweets' text.
But I don't know how (on what criterias) Twitter considers tweets from being duplicates. And apparently, for you, it happened for a tweet signaling a strike has been detected... and it shouldn't be a duplicate (distance and strength values change and I doubt it would be the same as the previous tweets).
You could try adding a timestamp to the tweets, and hope that Twitter no longer flags them as duplicate. Otherwise... I don't really see a way around.
Could you add a duplicate check loop into the software - something along the line of lastTweet != tweet send, otherwise throw it away until one that is different. If there is a way for the software not to crash if an error is raised but gracefully start looking for next lightning strike and try again?
I don't really understand what the problem is. Do you know/understand this error?