4.0 (6/6/2011)- Complete rewrite of the Autopoke script
- Issue #2 has been fixed as a result.
- XMLHttpRequest used to copy the main page: GM_XMLHttpRequest was used by the original script. There is a lot of overhead with with using GM_XMLHttpRequest that simply isn't necessary. I've replaced it with XMLHttpRequest which is native to Firefox, Chrome, and pretty much any other standard-compliant browser (read: doesn't work with IE). Please note that only Firefox is officially supported.
- New status/error messages: Messages are more informative and allows users to see why the poke failed. Debug variable can still be set to see the "console".
- Makes use of XML 1.0 standards: Facebook is XML 1.0 compliant. The script makes use of this to retrieve important information to pass to the poke function. (If you want to see this in action, set debug to 3 or higher.)
- Tracks poke wars: Users will now see how many times the script has poked a specific person. This is not a global number and only reflect pokes performed and recorded by the script.
3.5 (10/30/2010)- FIXED: Script fixes issue #3 where autopokes were no longer being processed due to Facebook's new protocol.
- REMOVED: Removed the ability to submit bug reports via the script.
3.4 (9/14/2010)- MODIFIED: Set debug to 0. Debug functions were left in-tact and can be activated by either URL or changing the debug variable within the script.
3.3 (8/5/2010)- ADDED: Various DEBUGGING functions were added. Please read this thread for more information.
3.2.1 (8/5/2010)- MODIFIED: The usoCheckup URL was changed.
3.2 (6/24/2010)- MODIFIED: Script will now look for pokes 40 times, pausing for 1.5 seconds. This works out to a total of one minute.
3.1 (6/20/2010)- REMOVED: Language test was not working properly and was disabled.
3.0 (6/18/2010)- MAJOR VERSION CHANGE: Poke confirmation function and poke function were rewritten from the ground up. The functions have sufficiently changed that they no longer are similar to Lukas Fragodt's Auto-Poke and EZ-Poke. However, since this script was inspired by them, I've still made an attribution.
- ADDED: Various debugging lines were added so that users can assist in debugging the script. To activate, either edit the script and change the debug variable value or add "autopoke_debug=x" where x is a value of 1 or greater. The highest value the script checks for is 2. Higher values show more detail.
- ADDED: @license metadata. All scripts I author are licensed under the General Public License 3.0.
2.5 (5/28/2010)- MODIFIED: Script will wait 1.5 seconds before auto-poking begins. This fixes the issue of the script not picking up any pokes as soon as the page loads.
2.4.3 (4/21/2010)- FIXED: Script searches for the poke back URL instead of the text.
2.4.2--debug (4/12/2010 @ 1148 ET)- UPDATE: I apparently left out a curly bracket. It's been fixed. Please download again
- This is a debug version of the current code. This will allow me to see why the pokes are not automatically being handled. Please install this script. If you find that a poke does not properly go through, please open up the Error Console (Ctrl-Shift-J or Tools, Error Console) and provide the error codes. Debug messages from the autopoke script will start with autopoke-5200:.
2.4.1 (3/3/2010)- Added two includes: http*://*.facebook.com/?* and http*://*.facebook.com/#* This should allow the script to run on the main page. If you're still having problems, please submit an @include request and I'll add it to the next release.
2.4 (2/26/2010)2.3 (2/24/2010)2.2 (2/17/2010)2.1 (10/19/2006)- Modified regular expression for post_form_id to better capture the confirmation code.
2.0 (8/17/2006)- Seperated the code to two sections: one for getting the confirmation poke page and one for doing the actual poking.
- Fixed poking for facebook's new code:
- Retreives post_form_id from the confirmation page and then passes it along to the POST function in the script.
- Provided more descriptive errors with error codes. Anytime the script fails, autopoke will provide a failure code in brackets. The full-text of the failure is noted in the JavaScript console. Provide this information when submitting bug reports.
|
