033 and identi.ca
Closed this issue · 7 comments
The changes in 033 for the Twitter API v1.1 are not good for identi.ca. Posting still works (if one ignores the "operation failed" message with exit code 234). Retrieving with -'-action friends --debug' shows returned JSON but no output and again "operation failed"/234).
OTOH I don't know if it's worth to investigate since identi.ca is supposed to switch to pump.io Any Day Now (since 4 weeks). Not sure about other statusnet instances ...
I'm willing to fix this, only issue, I don't have an identi.ca account and I believe you need an invite to get one (?)
[Interesting, I seem to remember adding some notes here 2 weeks ago about identi.ca and pump.io. Anyway:]
identi.ca has switched from using StatusNet to pump.io some hours ago.
The documentation is at https://github.com/e14n/pump.io/wiki , API e.g. at https://github.com/e14n/pump.io/blob/master/API.md
This will require a few (lot) of changes to do with the way oauth and curl are (not) currently used together with callback functions - a requirement for streams in both twitter and pump.io. I haven't looked closely enough to see if they are implemented in the same way. Twitter streams will probably add another 50-100 lines of code and take probably 6 or 7 hours of coding/testing but it is achievable. Then there is pump.io...
This probably needs reviewing as to what we want to achieve here... Maybe create a milestone from the "consensus" of what we want to achieve?
(By the way there is about 50 lines that can be taken out from the hurried implementation of json - I will do that real-soon-now)
On Thu, 11 Jul 2013 01:39:54 -0700, paulrho wrote:
This will require a few (lot) of changes to do with the way oauth
and curl are (not) currently used together
Ack.
This probably needs reviewing as to what we want to achieve here...
Right.
To sum it up: We have in theory 3 APIs:
- Twitter v1.1, used by Twitter since a few weeks
- Twitter v$whatever, used by Twitter before and still used by
StatusNet (formerly laconi.ca) instances; this is broken with the
change of the URLs for the Twitter v1.1 API in the last bti release- StatusNet was used by identi.ca until a few hours ago
- pump.io, used by, well, pump.io instances
- identi.ca is now using pump.io
Ok, so I'll rip out all of the libxml stuff from bti, as even if we do add support for identica, it's not going to be needed there.
I think it's probably not worth adding pump.io support, as there must be other apps for that api, right?
On Thu, 11 Jul 2013 16:39:00 -0700, Greg Kroah-Hartman wrote:
Ok, so I'll rip out all of the libxml stuff from bti, as even if we
do add support for identica, it's not going to be needed there.
Right, it would only help for other StatusNet instances but there are
probably not many around.
I think it's probably not worth adding pump.io support, as there
must be other apps for that api, right?
Hardly anything so far.
2 Qt applications:
https://github.com/e14n/pump.io/wiki/Clients
And a python library:
https://github.com/e14n/pump.io/wiki/Libraries
And a feature request for bitlbee :)
http://bugs.bitlbee.org/bitlbee/ticket/1076
Right, it would only help for other StatusNet instances but there are
probably not many around.
Well yes, there are :)
I only use bti for posting though, so at least for me, the current state is fine.