Comments on: Plurk your tweets

By: Desmond Hume

Desmond Hume — Sat, 03 Oct 2009 16:39:03 +0000

‘TimeLine/addPlurk’ call now needs one more additional parameter.
This parameter is ‘uid’, and the value is, as expected, the user_id of the Plurk User that is posting the Plurk.

By: Plurk Goodies for You : New Linux User - Linux Tips - Information for Using Linux

Fri, 15 May 2009 02:21:01 +0000

[...] Plurk your tweets [...]

By: David

David — Mon, 14 Jul 2008 20:30:12 +0000

Ryan’s Unofficial Plurk API is being ported to Python over at Google Code.

http://code.google.com/p/plurkapipy/

As a project, it’s just starting. But at least you don’t have to burn one of your Google Code allotments on it.

By: Jason Adams

Jason Adams — Sun, 08 Jun 2008 13:47:20 +0000

Thanks for the info! I’ll add the credit for Neville to the code and update my post.

By: Charl van Niekerk

Charl van Niekerk — Sun, 08 Jun 2008 02:57:07 +0000

Hi Jason,

Thanks for building on the code, really cool to see somebody got some benefit out of it! The Python version of the code has actually not been written by me, credit for that goes to Neville Newey. All the best with the Python hacking though!

Cheers,
Charl

By: How to synchronise your plurks and tweets « craniac’s place

How to synchronise your plurks and tweets « craniac’s place — Sat, 07 Jun 2008 21:45:58 +0000

[...] Adams has posted a Python script that does exactly that, posting your tweets as plurks and your plurks as tweets. I have [...]

By: Jason Adams

Jason Adams — Sat, 07 Jun 2008 19:16:39 +0000

The code has been updated. Now you can pass the final parameter as -t or -p to either only update twitter (-t) or plurk (-p).

ex. ./plurk.py twuser twpass pluser plpass -t

will tweet just your plurks.

By: Jason Adams

Jason Adams — Sat, 07 Jun 2008 16:12:45 +0000

Good idea. I’ll add that and fix the documentation. I’m thinking of also moving it to a CC:BSD license, since that makes more sense for software.

By: Steve Crane

Steve Crane — Sat, 07 Jun 2008 11:24:55 +0000

Would be cool to (perhaps optionally) prevent reply tweets from synching to Plurk.

By: Steve Crane

Steve Crane — Sat, 07 Jun 2008 11:15:52 +0000

The documentation block in the script hasn’t been updated to reflect the Plurk password.

By: Jason Adams

Jason Adams — Fri, 06 Jun 2008 18:37:19 +0000

It will create the plurkdb.dat file for you automatically. You just need to pass the usernames and passwords on the command line when you run it. If you are just running it manually, then you can just type:

python plurk.py twitter_username twitter_passwd plurk_username plurk_passwd

If you know where python is installed on your server (usually by typing “which python”) and you’re running linux, you can change the first line of the script to that path. If you are running windows, run it from the command line like I just said.

If you are setting it up as a cron job in linux, edit the script and change the path to the plurkdb.dat file to the path you want it to be stored. This might be like “/home/your_username/plurkdb.dat”. Also if you’re running a cronjob you might need to run python on the script manually. An example cron job might look like this:

*/10 * * * * /usr/bin/python /home/your_username/plurk.py twitter_username twitter_passwd plurk_username plurk_passwd

By: PythonNewbie

PythonNewbie — Fri, 06 Jun 2008 18:18:00 +0000

Just checked with my host and python is installed. No clue what to do with this script though. Where do I define my usernames/pws? Do I create an empty plurkdb.dat for this script to store and reference status messages?