GIMPS results to Twitter

[Brain]

As a proof of concept, I've written some javascript code that reports factor found / primality results from GIMPS' result page to Twitter (see attachment). It took me 3 evenings and it works. Maybe it's interesting for someone.
Requirements: Firefox 3 with Greasemonkey 0.8 Plugin (runs custom javascripts), self-registered Twitter app with single access token (single user use case).
Skript Flow:
1) User: Loads the result page in Firefox (script is URL triggered).
2) Script: Parses page content, looks for new result.
3a) If not found or not newer than latest, wait some time, then reload unless server is in minutes 55-10 (busy server). Goto 2).
3b) If found, update local cache and send result to your Twitter status.
4) Enjoy your result, even if you're in Far Far Away.

I still have to think about server load (polling), cross site xml http requests, local storage formats... By the way, I'm no real fan of JS and Twitter, I just want the results and do some GIMPS promotion to my friends.

[moebius]

Although , I use Twitter, but I use it not regularly. Where can we download the script / plugin

[Brain]

I will have to add some nice text messages ("XY has a factor") and a description of how to use it. I'll post it here for preview / custom enhancement.

Script only runs when http://www.mersenne.org/results/?ext...B1=Get+results is loaded.

Also, you have to create your personal app as I don't want to release my private app key: http://dev.twitter.com/apps/ . There, you can retrieve the 4 needed twitter keys and copy the into the script.

[Brain]

Script provided as is. No release code.

[Brain]

Tested, works. Last post had error.

[Primeinator]

Assuming this posts your own results, is there any danger of a potential new prime being released to the public before a double check can be completed?

[Brain]

Originally Posted by Primeinator

Assuming this posts your own results, is there any danger of a potential new prime being released to the public before a double check can be completed?

Yes, you are right. I think currently none of the readers would understand the meaning but it is public. I'll modify the script so that this is supressed or obfuscated ("has found a factor: 0").

Installation by the way: Rename file from *.txt to *.user.js and open it in FF with greasemonkey. Firebug is recommended for reading the script's log output.

[Mini-Geek]

Originally Posted by Primeinator

Assuming this posts your own results, is there any danger of a potential new prime being released to the public before a double check can be completed?

If I'm not mistaken, (and if it wasn't just a bug visible when the last prime was found) they can be found through the public data at mersenne.org as soon as they're reported, anyway. But that's quite out of the way, only likely to be found by people who know not to declare to the world (yet) that it is prime. Twitter is a different scenario although, like Brain said, it's likely that few to none of someone's readers would understand that, especially if it was obfuscated in some way.