josh83's dashboard

Hmm.. that's odd, I haven't touched any code in twitterfeed in the last couple of weeks.. could you let me know the feed URL and I'll try and take a look to figure out why this may be happening.

Yes, after re-running the pipe all (!) timestamps remain the same. Unfortunately everything worked fine a few days ago... :(

It sounds like this is a combination of time stamps and shortened URLs. Twitterfeed first checks the time stamps in the feed to see if there are any new items, and if it finds a new post checks the item link to see if this has been tweeted before.

If tinyurl is given then same link to shorten twice, it creates the same shortened URL, but tweetburner will create 2 different short URLs, even if the original link is the same. This means that the de-duplication against previously posted items won't work if you use tweetburner. Not much I can do about that, but perhaps you could contact tweetburner to see if they could change this behaviour.

However, as the url check is only the second check that is being made, this shouldn't even come into play unless twitterfeed thinks the items are new. Could you take a look at how the date/timestamps in the Y! Pipes feed work? Does the same item get a new timestamp when the Pipe is re-run? If it does, then it would explain why twitterfeed thinks the item is new, so some way of keeping the original timestamp on the feed items would solve that.

Let me know what you find, thanks..