Greg Pass's dashboard

Chris Thomson marked one of Greg Pass' replies in Twitter as useful. Greg Pass replied to the question "Are Overheard/Summize keywords cap sensitive?". Chris Thomson and 3 other people think it's one of the best replies.

mdy replied on July 18, 2008 12:30 to the question "Delete a tweet permanently?" in Twitter:

Hi Tico. There's a blogpost on the Twitter Technology blog that may be of interest.

Here's the relevant excerpt:

Will status deletions be correctly deleted from Summize's index?

Answer: Yup, that's in the pipeline.

Tico replied on July 10, 2008 02:03 to the question "Delete a tweet permanently?" in Twitter:

Not happy with not having control over deleted stuff I do not want to appear in Twitter and anywhere else. The simplest would be for summize to have a button that allows a deletion when it checks the status update page and it returns an unexisting page.

Greg Pass' reply to "Are Overheard/Summize keywords cap sensitive?" was just promoted to the most useful! Lane Becker and 3 other people think it's one of the best replies.

No, Summize queries are not cap sensitive.

Cameron Walters marked one of Greg Pass' replies in Twitter as useful. Greg Pass replied to the question "Are Overheard/Summize keywords cap sensitive?". Cameron Walters and 3 other people think it's one of the best replies.

Eric Suesz marked one of Greg Pass' replies in Twitter as useful. Greg Pass replied to the question "Are Overheard/Summize keywords cap sensitive?". Eric Suesz and 3 other people think it's one of the best replies.

Greg replied on July 09, 2008 13:48 to the question "Delete a tweet permanently?" in Twitter:

Hi Kaushal --

Our index reflects all of the tweets pushed to us from Twitter. Unfortunately, Twitter's API does not yet indicate when deletes occur, so they remain in our index.

This is affecting many Twitter Apps, Twitter is aware of the problem, and a fix is in their pipeline.

Sorry for the inconvenience.

Greg replied on July 09, 2008 02:09 to the question "Are Overheard/Summize keywords cap sensitive?" in Twitter:

No, Summize queries are not cap sensitive.

A comment on the question "Why don't any of my tweets show up in Summize?" in Twitter:

Hi Ken --

We followed up with Twitter on this. Twitter has been working on spam detection, and accidentally flagged your account as spam.

Looks like you are now appearing on Summize as expected:
http://summize.com/search?q=from%3Aga...

Look good? – Greg, on June 27, 2008 00:52

A comment on the question "Why don't any of my tweets show up in Summize?" in Twitter:

me too. summize has just 15 of my 200 tweets. And just 3 within the last month. And my image url is shorter than 100 chars. – JackH, on June 21, 2008 08:44

OccasionallyAnnoyed replied on June 20, 2008 16:44 to the question "Why don't any of my tweets show up in Summize?" in Twitter:

I am in the same boat: http://twitter.com/gaeblerdotcom

A comment on the question "Why don't any of my tweets show up in Summize?" in Twitter:

Hi Michael --

We received three of your tweets from Twitter on 5/20 (http://summize.com/search?q=from%3Abiocs), but have received none since. This means that Twitter is no longer posting your tweets to the public timeline, as we index all (and only) tweets on the public timeline.

Unfortunately, we don't know why Twitter is filtering you. We'll inquire with Twitter and try to determine what's up.

Thanks for the feedback! – Greg, on June 20, 2008 14:51

Michael replied on June 20, 2008 13:57 to the question "Why don't any of my tweets show up in Summize?" in Twitter:

Hmm, I have the same problem (but a short image URL): http://quotably.com/biocs http://twitter.com/biocs

wes replied on June 12, 2008 03:56 to the question "Why don't any of my tweets show up in Summize?" in Twitter:

Great, thanks Greg!

My posts are indeed showing up just fine, now. Went ahead and shortened my image filename as well.

Greg Pass replied on June 11, 2008 20:39 to the question "Why don't any of my tweets show up in Summize?" in Twitter:

We tracked this down.

The problem is that your profile image URL is over the max of 128 characters: http://s3.amazonaws.com/twitter_produ...

Unfortunately, this resulted in our rejecting your tweets. We've updated the code to default to Twitter's default profile image in this event, and to not reject the tweet. Therefore, you'll see your tweets appear in Summize from here on.

Better yet, if you update the filename of your profile image to be shorter, it will appear in Summize rather than the default.

We've added some instrumentation to measure this event, and by our estimate 0.02% of profile images are too long. We'll likely end up increasing the limit given this frequency. Seems that our knowledge of the hard limit is incorrect.

Wes, thanks for clueing us into this bug!