Facebook Autopoke 4.0.1

By Mike Soh Last update Sep 8, 2011 — Installed 229,277 times.

Releasing a debugging version soon

in
Subscribe to Releasing a debugging version soon 12 posts, 3 voices



Mike Soh Script's Author
ieWindows

Good morning everyone!

Sometime in the next week, I'll be releasing a debug version of this script. This version will be DRASTICALLY different than the previous debug version I put out on 12 April.

If you would like to help debug the various issues people are experiencing, please consider installing the update. But before you do, please read below as it will have MAJOR privacy implications.

Please understand that I care about my privacy just as much, if not more, than you. I hate it when websites ask me for an e-mail address just to get content and often use BugMeNot to log into websites where registration is "required". So I don't make the changes below lightly. So PLEASE read below if you plan on installing the debug version.

Let me first explain the problem:
A number of users have reported problems with the script. The problem stems from the new method that Facebook creates the page. Without getting too technical, the main page is drawn first and then populated with content. Because Greasemonkey relies on the load status to execute the script, Firefox will indicate that the page has completed loading, when in fact content is still being pulled from the server.

Second, some people are still getting Autopoke failed! [1.1]. This error usually means that facebook has changed the poke system.

I have only been reproduce these problems sporatically. As a result, I'm asking for your help to make this script better.

In order to properly diagnose these problems, I need willing volunteers to provide technical feedback. I recognize that a large majority of people who use my script are not proficiant in Javascript or web-development in general. If you're one of those people and still want to help, you should properly understand what the debug script will do.

The script will create a new window where it will log all poking activity between you and Facebook. This data will include the names of the friends it pokes, the number of pokes executed, and your unique identifier on Facebook. After the poke is complete, you will be given the option to submit the data to my web server. While you will be given the option to modify the output, it is strongly encouraged that you don't unless you ABSOLUTELY KNOW WHAT YOU'RE DOING!

Your friend's names, your unique identifier...they are all important to the script. If you change this information, please make a notation at the beginning of the output. But note that if you accidently change the wrong thing, it may make your data useless.

I understand that I'm asking you to trust me with a lot of personal information. So if you have a problem with ANY of this, please do not install the update! It's better for me to get a few accurate debug messages than have a lot of improperly edited information.

All of the debuging functions as well as all the information gathered will be deleted when the next public version is released or within two months of their submission, whichever comes first.

If you have any questions regarding your privacy or this new release, please feel free to ask me in this thread.

 
the-ownage User
FirefoxWindows

Hello, Mike. I read your post and will be glad to install the debugging version when it is available. The poking log sounds like a great addition. One question though: is this log solely for debugging problems, or can it also serve as a way for us to examine the number of successful pokes for each user? I think that would be interesting information to see which friends have been the best pokers-- if this is the case, I'd be sad to see this function unsupported in future public releases.

 
Mike Soh Script's Author
ieWindows

the-ownage: There is a way to keep track of how many times people have poked you. But it's a lot more overhead. I would prefer to keep the script as simple as possible.

 
Mike Soh Script's Author
ieWindows

UPDATE: I'm still working on the debugging script. Sorry it's taking a while.

 
Mike Soh Script's Author
FirefoxMacintosh

Thanks for your patience everyone! The script is ready, but not uploaded yet. Some things to note:

If you do not want the debugging, DO NOT INSTALL THE UPDATE!. You can also append "debug=0" at the end of the facebook URL if you do accidentally install the update. You can always roll back to a previous version.

As I stated in the first post, you can edit the output. However, I am strongly encouraging you not to do so.

Submit the output if the autopoking did not work. Try refreshing the page. If the autopoke worked after you refreshed, submit that output as well. If it still didn't work the second time, submit again. Only do this a maximum of two times.

Just as an FYI, all logs that are created are stored securely on my web site. I'm the only one that has access to the logs. They will be deleted upon the next release of the autopoke script.

If you have any questions, please feel free to reply to this thread.

 
Mike Soh Script's Author
ieWindows

Thanks to everyone who has already submitted debugging reports. They are very helpful.

I tweaked the debugging functions so that you can only submit once and only after the script has finished. A few people were submitting before the script was finished. Please install the new version and keep sending the reports in!

Additionally, if you do end up editing the output, PLEASE make a note of it in the output. I am finding myself why the reports only show half of the info only to realize that the output was edited.

 
Mike Soh Script's Author
FirefoxMacintosh

Another release with more bug fixing mojo.

 
Jimmy Cao User
ChromeWindows

I sent one from Chrome, but I'm not sure if it got sent.

If you see one with a message on top saying it was from Chrome, can you tell me on this thread?
Thanks,
Jimmy Cao

 
Mike Soh Script's Author
ieWindows

Jimmy Cao: I haven't found yours yet; does not mean that it didn't get through.

EDITED:
Thanks again to everyone who submitted a debug report! Good news: I think I found the problem. The bad news: I'll have to release another debug version. If you are installing the debug version, make sure you install with the latest release.

Thanks

 
Jimmy Cao User
ChromeWindows

It's alright if it didn't get though actually, I have Firefox and so whenever I have some pokes, I'll just open Firefox for it.

 
Mike Soh Script's Author
ieWindows

Please also check your Javascript Console (Firefox: Ctrl-Shift-J). If there is an error, please paste it into the textbox before submitting.

 
Mike Soh Script's Author
FirefoxMacintosh

Script was updated again. Please make sure you upgrade. In fact, my website will no longer accept debug information from anything older than the latest version.