I know everyone is waiting on the release of Autopoke 4.0. The LAST Well is having issues with their credit card merchant. As soon as this is resolved, I'll give you guys directions on how to donate.
Sorry for the delay.
Wednesday, May 25, 2011
Monday, May 9, 2011
Final Features for Facebook Autopoke 4.0
As I finalize the code for 4.0, I'm going through the wishlist of features and deciding their fate. Will they be included, will they not. Unfortunately, there is one major feature that will NOT be included: automatic reload of the script.
While testing, I did program the script to automatically pull the main Facebook page. For some unknown reason, Facebook continues to show people who have already been poked in this pull. I initially thought this was due to a caching issue but have since determined that this is not the case. Since the problem is on Facebook's side, I've decided to remove this feature. Since this is how the Autopoke currently works, I don't see this as a step back. Keeping the feature in the final build creates unnecessary traffic. The code is still contained in the RCS (revision control software) so it's not lost and can be added back in at any time.
I've done my best to make the script as flexible as possible. The script no longer requires the English language and should work on any language, be it fake (e.g. pirate) or real (e.g. German). It is able to do this by relying on the underlying ajaxify library. Should Facebook ever stop using this or start using a different library, the script will have to be rewritten.
Over the next few days, I will be removing much of the extra code that makes debugging possible. I'll also be adding an error reporting tool that will allow you to copy and paste it's output into a bug report.
While testing, I did program the script to automatically pull the main Facebook page. For some unknown reason, Facebook continues to show people who have already been poked in this pull. I initially thought this was due to a caching issue but have since determined that this is not the case. Since the problem is on Facebook's side, I've decided to remove this feature. Since this is how the Autopoke currently works, I don't see this as a step back. Keeping the feature in the final build creates unnecessary traffic. The code is still contained in the RCS (revision control software) so it's not lost and can be added back in at any time.
I've done my best to make the script as flexible as possible. The script no longer requires the English language and should work on any language, be it fake (e.g. pirate) or real (e.g. German). It is able to do this by relying on the underlying ajaxify library. Should Facebook ever stop using this or start using a different library, the script will have to be rewritten.
Over the next few days, I will be removing much of the extra code that makes debugging possible. I'll also be adding an error reporting tool that will allow you to copy and paste it's output into a bug report.
Sunday, May 8, 2011
Thursday, May 5, 2011
Facebook Autopoke 4.0 is almost ready!!
I'm working with The LAST Well to put together an interface so people can donate. Hoping to have it available by the end of next week!
Stay tuned!
Stay tuned!
Subscribe to:
Posts (Atom)