On Thu, Apr 9, 2009 at 12:01 PM, Chad Etzel <jazzyc...@gmail.com> wrote:
> > Reviving old thread: > > Seeing duplicates again, and now have examples: > > http://twitter.com/ryanashleyscott/status/1485237579 > http://twitter.com/ryanashleyscott/status/1485239348 > > same exact content, as far as i can tell, posted back-to-back by the user. I'll second this as an issue... I had an annoying such failure with TwURLed News recent, which taught me that it's all too easy to have code fail to properly recognize that a tweet was successful. With any sort of automation, the risk is there; aggregation can amplify it. This reminds me very much of the loop detection built into mailing list software to ensure that the list doesn't keep sending the same messages. I've been embarrassed by that one, too, long ago. Seems that this would fall under the general category of intercepting things that can go wrong when an API becomes popular and lots of code of, shall we say "varying quality" is deployed. Nick
