thefluffanutta's dashboard

thefluffanutta replied on March 04, 2009 21:59 to the question "Twitter slow in Firefox" in Twitter:

Is it just me, or has this problem been fixed now? Whenever I go to http://twitter.com/home and scroll up and down, it no longer feels sluggish like it did before. Certainly feels better than it used to.

thefluffanutta started following the question "slow typing" in Twitter.

thefluffanutta started following the question "Twitter slow in Firefox" in Twitter.

A comment on the problem "Not all Twurls picked up by Tweetburner" in Tweetburner:

Yeah, this happens. Tweetburner will collect stats for links and export them via the API, but can't display the stats on its website it if hasn't picked them up for your profile. Hope they can fix this... – thefluffanutta, on July 08, 2008 16:03

thefluffanutta replied on July 03, 2008 10:19 to the idea "A handy way to find spammers on Twitter: Squidoo!" in Twitter:

I have been tracking Squidoo spam on Twitter for a while (using Summize), and many get their Lenses or Lensmaster accounts locked. Almost all of them are using some automated spam software. Reporting spammers to Twitter does work, but is too much effort.

However, not every mention of Squidoo on Twitter is spam - there are some good, honest Lensmasters out their sharing their lenses responsibly, and a few mis-guided noobs that will eventually figure it out or give up.

PS: Yes, BettyA1 has been a spammer for a long time.

thefluffanutta marked one of Michiel Sikkes' replies in Tweetburner as useful. Michiel Sikkes replied to the problem "Not all Twurls picked up by Tweetburner".

thefluffanutta replied on June 16, 2008 20:49 to the problem "Not all Twurls picked up by Tweetburner" in Tweetburner:

I'm afraid it's still not quite right. I posted the same Twurl again from another account, and it still hasn't been picked up: http://twitter.com/squidcasts/statuse...

Perhaps the @ or the # is breaking your parsing? The feed from Summize will have 3 <a href> tags for this particular item's description.

thefluffanutta replied on June 15, 2008 20:41 to the problem "Not all Twurls picked up by Tweetburner" in Tweetburner:

TweetBurner missed a Twurl I posted yesterday from www.TwitReponse.com (i.e. a scheduled tweet).

> http://twitter.com/thefluffanutta/sta...

thefluffanutta replied on June 13, 2008 20:24 to the problem "Not all Twurls picked up by Tweetburner" in Tweetburner:

Thanks for implementing Summize API - that's great news, and very quick too. (I hope you were able to use the 'since_id' parameter as well, that should save you some processing and bandwidth).

Can you add a button to the user stats page, that will manually ping their twitter account, perhaps by using Summize again? (i.e. search for from:username twurl.nl) This would be a fall back just in case anyone has a tweet that got missed by Tweetburner.

thefluffanutta replied on May 15, 2008 20:42 to the discussion "Help us developing the Tweetburner Roadmap!" in Tweetburner:

How about an API call that returns the Destination of the Twurl? (Expanded).

There are some mashups like Summize and Twitturly that show the destination of the Twurl, instead of the Twurl itself. They do this for other shorteners too, though I don't know how. Maybe they simply scrape the destination off of the /links/xxxxx page.

So, I thought, why not have some simple HTTP GET or POST API call which takes the link, and returns the Destination. Kinda like the inverse function for the twurl generation API.
For example: sending "unlink[twurl]=6l0xsh" to http;//tweetburner.com/links
could respond with: http://blogsearch.google.com/

I don't have a specific need to for this, I just thought it would be cool to have.

As a bonus, you could also include the total and unique clicks, which would have some interesting applications.

thefluffanutta started following the problem "Tweetburner not tracking all links from Twitterfeed" in Tweetburner.

thefluffanutta reported a problem in Tweetburner on May 13, 2008 08:56:

Not all Twurls picked up by Tweetburner

I posted http://twurl.nl/l53vfs twice yesterday, first from WordPress plugin, the second from the Web. Neither time worked. (It did work when I tweeted this message to you).

These Twurls got missed too, 7 days ago:
> http://twitter.com/thefluffanutta/sta... (from Twitter Tools)
> http://twitter.com/thefluffanutta/sta... (from Web)
> http://twitter.com/thefluffanutta/sta... (from Web)

Is there a manual way to 'ping' Tweetburner with any Twurls it might have missed? Perhaps by sending a link to the original tweet. That would help.

Alternatively, maybe you could use Summize as a backup method to catch twurls, for example: http://summize.com/search?q=http+twur...