• fixed one more potential bug where tweetmypc shows a messagebox instead of a tweet when an error occurred when tweetmypc tried to get the external ip address

• fixed one more potential bug where tweetmypc shows a messagebox instead of a tweet when an error occurred when tweetmypc tried to get the external ip address

• fix handling of .docx files - tested

• fix handling of .docx files - tested

• tweet an answer-message after executing the print-command, so tweetmypc doesn't reprint the file every time it gets restarted. --- this version is also the code-base for TweetMyPC version 3 released at the 2/13/2010

• http://randomfunnypictures.com seems to have problems with hackers right now -> changed the link in the answer for "ping" to http://www.dilbert.com ToDo for release:
• re-add installer
• add api-key for bit.ly - search for "addhere" or "bit.ly" in the code
• add de/encrypt-code for the passwords - just replace the stub-functions by it...
• (do a basic test....)

• added print-feature for being able to remotely print a file stored online by using the command like for example "print http://website.org/something/pdfname.pdf" (currently supports pdf, doc and docx - you need a program at your PC installed, which is able to open and print documents, e.g. adobe reader and Microsoft office)
• added header with license, distribution and developer information to the code-files ToDo for release:
• re-add installer
• add api-key for bit.ly - search for "addhere" or "bit.ly" in the code
• add de/encrypt-code for the passwords - just replace the stub-functions by it...

I showed TweetMyPC to a few friends of me, and one of them got the api-rate limit problem (max 150 requests per hour)

Because of this I started researching about this problem and found a few useful information:

If you are developing an application that requires a lot of requests to the API, you can submit a web form (https://twitter.com/help/request_whitelisting) and ask Twitter to be considered for addition to the white-list of high-volume screen names. This will raise your upper limit from 150 to 20,000 API requests per hour.

Also I will change the source code of TweetMyPC, so it will after it is started or a command has been received, re-check 15 seconds after the first time the event has happened, and then it checks the next time after 25 seconds, then 30, then 3 times 38, then 45 and all following checks with 60 seconds between them.

With this change, you are more unlikely to get a problem with the twitter-api-limit-counter. This change also causes TweetMyPC to react slower to the first command you send after a while, but it will then react faster if you send a command short after another one. (in the worst case you still can do 15 commands per hour and in a good case up to 45 commands per hour - if I calculated correctly) And if you then still get a problem with the limit, the user can just submit the request-white-list form.

If you see any problem in this strategy, just email me a better way :)

---

• changed command virtual memory and command physical memory to also report the amount of total by the system mapped memory
• readded Service References/TweetMyPC.mdb - I already did this before, but TortoiseSVN didn't upload it to the svn +++ ToDo for release:
• re-add installer
• add api-key for bit.ly - search for "addhere" or "bit.ly" in the code
• add de/encrypt-code for the passwords - just replace the stub-functions by it...

• if getfile for a *.exe file is called, make a copy, name it file.exe.name and then mail it - googlemail blocks *.exe files...
• add directories to getfilelist output and fix a bug in sending the file after such a file has already been sent before
• move cursor to deactivate the screensaver for stopscr