Comments on: Twitter changes break TwitBlock [again]

By: Tim

Tim — Mon, 08 Feb 2010 19:33:35 +0000

yes, off topic, and unecessarily agressive too.

Firstly, it is trivial to post to Twitter with your app name rather than “API” – through my observation, bots and apps that post as “API” are low quality spammy apps written by people who don’t know the Twitter API well enough to do it properly.

Secondly, this indicator has a very low weighting in TwitBlock – it is a very minor factor when scanning your followers, mainly due to the fact that people will continue to give their password to apps like these that tweet on their behalf.

Re sending your blog posts to Twitter: The popular twitterfeed app identifies itself as such, which is the correct way to build this kind of software.

By: Guido Waldenmeier

Guido Waldenmeier — Mon, 08 Feb 2010 16:09:28 +0000

OFF TOPIC

Tweets via API
This account’s last tweet was from an unregistered app.
This can happen if you enter your password directly into a bad app. Only use apps that authenticate you via Twitter.com

BULLSHIT MISTER !
i use the blog CMS
b2evolution.net for my blog
and there is a plugin i can send blog post to twitter
it s a serious software in long term use a lot of peoples
serious as wordpress
!!!

By: Raul Carrillo Garrido aka metsuke

Raul Carrillo Garrido aka metsuke — Mon, 21 Dec 2009 12:16:20 +0000

Maybe turning the image into a B/W could do the work?

By: Patrick

Patrick — Sat, 17 Oct 2009 11:27:48 +0000

Disregard the question, i see it’s already implemented.

By: Patrick

Patrick — Sat, 17 Oct 2009 11:15:20 +0000

Are you going to integrate automatic spam reporting for the new twitter spam report feature?

By: Pepijn de Vos

Pepijn de Vos — Sun, 20 Sep 2009 06:47:00 +0000

How about this option: Have GD check the color of some pixels in the bird if they’re white. All the default pics have the same bird. With this approach Twitter could even add new colors without breaking your code.

Anyway, if I see a default pic not listed here I’ll tell you.

By: Tim

Tim — Sat, 19 Sep 2009 20:54:13 +0000

I'm currently ignoring the file paths, but if anyone wants them the hashes are as follows:

$ curl "http://s.twimg.com/images/default_profile_normal.png" 2>/dev/null | md5
df22f2c8e1a4bd024d02b10a3f3bd1cc
$ curl "http://s.twimg.com/a/1252980779/images/default_profile_0_normal.png" 2>/dev/null | md5
596e7d6cfb43be42dcce2cba80d55838
$ curl "http://s.twimg.com/a/1252980779/images/default_profile_1_normal.png" 2>/dev/null | md5
e616bb5ea460fdef652185e67a112189
$ curl "http://s.twimg.com/a/1252980779/images/default_profile_2_normal.png" 2>/dev/null | md5
045491d2d7051d144f31d35d64328475
$ curl "http://s.twimg.com/a/1252980779/images/default_profile_3_normal.png" 2>/dev/null | md5
1a67b35708dba15234866f8742f1d26b
$ curl "http://s.twimg.com/a/1252980779/images/default_profile_4_normal.png" 2>/dev/null | md5
9880fcc60b9b07c852c015d43c0336de
$ curl "http://s.twimg.com/a/1252980779/images/default_profile_5_normal.png" 2>/dev/null | md5
dcff70117d93e84acac5cfdc1bef70d2
$ curl "http://s.twimg.com/a/1252980779/images/default_profile_6_normal.png" 2>/dev/null | md5
c82efa3074189567b80c85752f5ed441

By: Quix0r

Quix0r — Sat, 19 Sep 2009 20:46:21 +0000

My approach for X default avatars would be:
- Get MD5/SHA1/SHA256 hash from all images twitter is using as default
- Save these in an array:
+ Index is the file name (no path or domain)
+ Values are the hashes
Then you should be able to easily lookup default images:
- If the basename()-name matches with an index (use isset() ) and the MD5 hash of the downloaded (or don’t you download avatars?) matches you have found a default image.
- If you don’t download any avatar to your server for checking then forget about the hash and you need to verify the whole URL (then you need an index array and use in_array() to lookup).