Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Patch: Support for Identica/Laconica and other Twitter-compliant APIs #53

Closed
GoogleCodeExporter opened this issue Nov 19, 2015 · 13 comments

Comments

@GoogleCodeExporter
Copy link

I've written a patch that allows twitter.py to be used with other
Twitter-compliant sites.  I've tested it as working on Identi.ca (well,
most parts of it; the Laconica API does not as of yet support every
function that the Twitter API does).

The implementation is pretty simple: a new argument to the Api constructor,
siteurl, that allows a different site to be specified.  For Identi.ca, the
URL would be http://identi.ca/api  Note that it defaults to
http://twitter.com so as to not break backwards compatibility with older
scripts.

Original issue reported on code.google.com by cydeweys on 11 Mar 2009 at 7:48

Attachments:

@GoogleCodeExporter
Copy link
Author

I'm not sure if I messed something up when submitting this or what, but it 
should
probably be an enhancement.

Original comment by cydeweys on 11 Mar 2009 at 7:49

@GoogleCodeExporter
Copy link
Author

Okay, here's an updated patch against the latest version in trunk.  Can we 
please
commit this soon so I don't have to keep updating the patch?  Thanks.

Original comment by cydeweys on 13 Mar 2009 at 1:17

Attachments:

@GoogleCodeExporter
Copy link
Author

dclinton, any word?

Original comment by cydeweys on 22 Mar 2009 at 6:50

@GoogleCodeExporter
Copy link
Author

patch has a syntax error on line 111:

+      url = '%s/statuses/friends.json' $ self._siteurls

should be:

+      url = '%s/statuses/friends.json' % self._siteurl

Original comment by michaelj...@gmail.com on 6 May 2009 at 6:33

@GoogleCodeExporter
Copy link
Author

How can I apply this patch on 0.5? I would like to use it for identi.ca

Original comment by niels.eg...@gmail.com on 21 May 2009 at 1:31

@GoogleCodeExporter
Copy link
Author

I have reworked the patch against the latest revision from trunk (r177). All
testcases work fine. Could you pleasy apply it for 0.7?

Original comment by martin.thurau on 17 Jul 2009 at 6:12

Attachments:

@GoogleCodeExporter
Copy link
Author

I would very much like to see this put into place. Program I am working on that 
use 
python-twitter (you guys are doing amazing work) would really benefit from 
being able 
to integrate with identi.ca (and other laconi.ca sites) with the same module, 
rather 
than going to look for another one.

thanks 
x1101

Original comment by helpd...@nexusmgmt.com on 21 Aug 2009 at 4:02

@GoogleCodeExporter
Copy link
Author

I would like to see it ;)

Original comment by walter.php on 21 Aug 2009 at 2:23

@GoogleCodeExporter
Copy link
Author

I have forked python-twitter as it is going in a direction that is different 
from my needs.  You might find it useful 
as I have already intergraded alt base urls : 
http://bitbucket.org/jrossi/tweethon/ 

Still would like to that the developers of python-twitter it is a great lib and 
still take all my ideas from it ;) 

Original comment by jeremyro...@fastmail.fm on 22 Aug 2009 at 1:59

@GoogleCodeExporter
Copy link
Author

Any update on this?

Original comment by muczy...@gmail.com on 12 Apr 2010 at 12:55

@GoogleCodeExporter
Copy link
Author

Identi.ca support is already in trunk thanks to 
http://code.google.com/p/python-twitter/issues/detail?id=114
you just need to call twitter.Api(..., base_url='http://identi.ca/api')

Original comment by inverniz...@gmail.com on 10 Jun 2010 at 12:18

@GoogleCodeExporter
Copy link
Author

While not technically a duplicate of Issue 37 this issue was fixed when Issue 
37 landed

Original comment by bear42 on 18 Aug 2010 at 6:56

  • Changed state: Fixed

@GoogleCodeExporter
Copy link
Author

Issue 48 has been merged into this issue.

Original comment by bear42 on 18 Aug 2010 at 7:02

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant