MCV-Software / TWBlue

TWBlue, an accessible, open source and multiplatform twitter application.
GNU General Public License v2.0
58 stars 36 forks source link

Feature Request: Support for other Systems than Twitter #58

Open annando opened 9 years ago

annando commented 9 years ago

I'm one of the developers of Friendica, a decentralized social network: http://github.com/friendica/friendica/

Friendica is using a Twitter compatible API, so (nearly) every Twitter client should work with it. To make a Twitter client work with Friendica there are only small changes needed:

If that would be done, TW Blue should work with Friendica. (And maybe with GNU Social that is using a Twitter compatible API as well)

Thanks!

Menelion commented 9 years ago

@annando, I'm not a TwBlue developer so far, but I'm developing a similar social networking client (we're not competitors but friends with TwBlue :)).
So my questions to you are: do you have a documentation of your API? And do you have or are you planning to have a Python wrapper for your API?
Thanks!

manuelcortez commented 9 years ago

It is a great idea! I read about your project and GNU Social and I think we could use requests for making calls to them, it needs user and password authentication. I think I need to read the API Docs, when we release the next major version, I think I'm going to start to work in session handlers for Friendica.

annando commented 9 years ago

@Oire The API documentation is here: https://github.com/friendica/friendica/wiki/Friendica-API

There is no special Python wrapper, but you could use every wrapper that works with GNU Social/Statusnet as well. And you could use every Twitter wrapper that allows dynamic API paths and login via username and password.

@manuelcortez If you use a Twitter API call that behaves differently in Friendica, please just tell. We have a quick release cycle of about 2 to 3 month per release. Additionally I could create accounts on servers that run the development branch.

But if you want to support GNU Social as well, then you had to use the "old style" API calls (from Twitter version 1.0).

I have to have at look at your program. I just stumbled upon it, because a person used it with whom I had a discussion about accessibility.