Feature request: support for plurk.com

Here's a relevant link:
http://code.google.com/p/plurkapipy/

Cheers!

Plurk support will not be implemented in Gwibber until they release an official API or provide a clear and unambiguous answer about when we can expect to see a public API. There are technical challenges posed by using workarounds and I don't want to implement support for the service if I can't guarantee that I'll be able to continue supporting it in the future. There is no way of knowing whether the current approach that is based on reverse-engineering will be perpetually accessible. I will reconsider if Plurk opens its own official API or acknowledges that the unofficial backdoor is a valid means of using the service.

Sorry! I'd really like to support Plurk, but I can't do so until Plurk is willing to allow it.

I emailed the Plurk people to ask if this unofficial backdoor is a "valid means of using the service" and they responded:

Hi Tom!

If it is a question of whether the unofficial backdoors are a valid means of using the service, yes it is -- as long as our terms of service are adhered to. It is important to note though, since these are unofficial hacks, they may break at any time/without warning. We may release a public API in the future.

For what its worth, I was the original developer of the RLPlurkAPI (http://code.google.com/p/rlplurkapi/) that is no longer supported.

Hope this answers your question :)

Regards,
Ryan Lim

"It is important to note though, since these are unofficial hacks, they may break at any time/without warning."

That's really the issue. I'm not comfortable merging this feature into Gwibber as long as that problem exists. I do appreciate the work that you have done on this, however, so I'd like to find an alternate way for this feature to be supported and distributed.

I'm thinking about making a plugin system so that unofficially supported service modules can be installed by users in their home directory and used directly in gwibber.

http://www.plurk.com/API
Plurk DOES have an official API, it's through HTTP. It wouldn't be necessary to do workarounds, really.

Now that Plurk does have an official API, perhaps it's time for a status change on this bug?

Would it be alright to ask how to add the .patch file?

Plurk has an official API now, please change the won't fix status if sole reasoning was that Plurk did not have a public API.

I applied the patch and Plurk doesn't work.