TweetMyPC is a utility to control your PC remotely via the popular social network Twitter. You just tweet a message that represents a command, and this utility receives it in your PC and executes it transparently returning a response depending on the case. You simply install it and associate it with your Twitter and Gmail accounts, and you are set to start monitoring and controlling your PC while you are away (it is strongly recommended to use alternate Twitter and Gmail accounts in order to keep your primary user accounts and passwords private).
You can control options like shutdown, hibernation, and many more. From the official site you can view a list of commands. This utility also has a CustomCommand window, where you can create your custom commands to control programs or shell commands. For example, you can start your defragmenter program, or your FTP program with a URL and port as a parameter to start a download.
Some commands return an output string. When those are more than 140 characters long, this is when the e-mail comes into play. For instance, the "getprocesslist ", which lists all the running processes and process ID, just like the Task Manager.
This utility consumes a lot of RAM. The problems can start because of a faulty implementation, which allows many instances of it to be run at the same time, when only one is needed. If you start many instances, you will notice many icons in the Tray Bar. more
Comments (2)
This works already for more than a year.
I just released the new version 4.0.4 of TweetMyPC for Windows and it fixed the screenshot and the ip command. Also it is now compatible with the new Twitter Api 1.1 and a couple of bugs are fixed now. I also changed the garbage collection so TweetMyPC now consumes less RAM; but also remember that for .Net Applications running in Windows, you can't measure the RAM usage with the task manager because that would also show all the cached .Net libraries. Also compare that to "www.google.com" opened in a google chrome or firefox browser tab, it will show up with a higher ram usage because of the caching.
Best regards,
Stefan