Comments for Gizzmo's Blog

Comment on Default Avatar by Elme3allam

Elme3allam — Sun, 22 Aug 2010 08:01:18 +0000

I think that the next step will be to include avatars from Gravatar as alternative, what do you think ?

Comment on Wowhead Goes To Blizzard by Malgayne

Malgayne — Sun, 13 Jun 2010 08:34:58 +0000

Thank you. I worked hard on that coverage, I’m glad you liked it.

Comment on Meebo by StevenBullen

StevenBullen — Wed, 12 May 2010 07:07:04 +0000

I have used Meebo for all my IM clients and have to say it works a treat. But you don’t mention the awesome Meebo iPhone app. Free and works.

Comment on Fried PSU by Rob

Rob — Sun, 28 Mar 2010 21:35:19 +0000

Looks pretty messy!

Comment on Blizzard To Wowhead Talent converter by Gizzmo

Gizzmo — Fri, 05 Mar 2010 02:01:13 +0000

If i read you correctly when you removed the one point from arcane barrage you made the string shorter, in turn making the string invalid. Blizzard build strings will always be the same length. In this instance (mage tree) it will always be 30+28+28 characters long, no matter how many talents you’ve spent. Let me know if im wrong.

In the new version of the function ill add a check to make sure the provided string is the correct length for that character

Comment on Blizzard To Wowhead Talent converter by Vontre

Vontre — Thu, 04 Mar 2010 16:31:00 +0000

Hi, thanks for the code here. I was working on reversing the algorithm so I could de-encode these as well, and I think I found a bug with your encoding algorithm. Specifically I tried encoding a cookie-cutter mage arcane build, but I removed the point from arcane barrage for testing. When I did that the encoded build no longer loaded into wowhead correctly. I believe the problem is in this line:

$return .= (strlen($b)==strlen($cur_tree))? $pre_return: $pre_return.$none;

The problem here is that the wowhead links encode 1 character for every 2 lines, so if the blizzard string uses 29 of the 30 allotted characters it will fill the full 15 lines of the wowhead string and not require a Z terminator. However because your check for the Z terminator uses the blizzard string, it will incorrectly use a Z terminator whenever the only right-trimmed zero is in the last space. I have a correction here:

$return .= (strlen($pre_return) == ceil($trees[$class][$tree_index] / 2)) ? $pre_return : $pre_return . $none;

This checks the length of the wowhead encoded string for the Z terminator, which fixed my issue and should work correctly. I haven’t tested this against a tree with an odd number of characters in the blizzard string since all mage trees contain an even number, but I’m pretty sure ceil() will come up with the correct result for odd-numbered trees. Let me know if that works!

Comment on Im a Justhost Affiliate by Justhost Affordable Hosting Plans Justhost - WuiWui.com

Justhost Affordable Hosting Plans Justhost - WuiWui.com — Sat, 20 Feb 2010 05:23:37 +0000

[...] Im a Justhost Affiliate « Gizzmo's Blog Sponsored links: [...]

Comment on 5 Reasons Why I like DestroyTwitter more then TweetDeck by TweetDeck Vs DestroyTwitter 2 « Gizzmo's Blog

TweetDeck Vs DestroyTwitter 2 « Gizzmo's Blog — Fri, 23 Oct 2009 03:40:19 +0000

[...] a back i made a post sharing a list of 5 reasons why i liked DestroyTwitter more then TweetDeck (Link). I was shocked that it was such a hit, over 800 hits in one day. Well its been a while since iv [...]

Comment on Twitter Mirror? by Christine

Christine — Sat, 10 Oct 2009 23:35:49 +0000

Boo

Comment on Twitter Mirror? by Steven Bullen

Steven Bullen — Sat, 10 Oct 2009 13:36:50 +0000

I’m pretty sure Tweetdeck will add the sync option pretty soon.

Not sure on grabbing the information from your machine, would be easier just to download all the tweets on both desktop and iphone and keep them synced on what is read/unread.

I never run out of API calls, what am I doing wrong? lol