Loading Profile...
twitterfeed update problems (although using delicious through yahoo pipes)
I'm feeding my Twitter account with my del.icio.us bookmarks via Yahoo Pipes. This solution seemed to work quite well until a few days ago. As a matter of fact twitterfeed keeps importing the rss entries of my delicious-through-yahoo-pipes rss feed over and over again. Thus every bookmark is being posted at least twice (or even more).
Any suggestions?
Edit: It seems as if shortening the URL using tweetburner is the problem. Actually I'd like to omit a switch to a different shortening service because I like the way I can keep track of my posted URLs using tweetburner.
Any suggestions?
Edit: It seems as if shortening the URL using tweetburner is the problem. Actually I'd like to omit a switch to a different shortening service because I like the way I can keep track of my posted URLs using tweetburner.
I’m frustrated
1 person has this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
-
Inappropriate?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.. -
Inappropriate?Yes, after re-running the pipe all (!) timestamps remain the same. Unfortunately everything worked fine a few days ago... :(
I’m confused.
-
Inappropriate?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.
EMPLOYEE