Comment 2 for bug 275004

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.