Identi.ca/Status.net support

yea I just upgaded to this version and I can't see the identi.ca option either

is there an easy way to downgrade to the other version? I am now stuck on a version that doesn't work for me.

Can you please put something on http://drupal.org/project/twitter telling people that other sites supporting the twitter api, such as identi.ca and status.net, no longer work with the 6.x-3.x branch of this module? People really should be warned that this feature has been dropped before upgrading.

update: i successfully downgraded to the older version

It would be nice to make at least the URL to be configurable again. I used it with status.net some time ago.
#947978: Ability to simulateously have twitter/identi.ca/status/net would be the more advenced solution.

This definitely should be restored. I'll add it to the use cases that should be supported in the future, once those are actually documented.

Closing duplicates to this issue. Let us gather all work into this issue.

• #416562: All links point to Twitter
• #819542: Questions on using Identi.ca
• #947978: Ability to simulateously have twitter/identi.ca/status/net
• #810750: Allow selection of Twitter(like) service
• #1328870: Connection to Identi.ca
• #850912: cck fields not saved when triggerering an action to post to identi.ca

I just did a quick test to see if Identi.ca is still compatible and it does look like. After applying this patch I could load an Identi.ca account and list its messages.

I have committed three text fields that allow api.twitter.com, twitter.com and search.twitter.com to be changed. This will be available next week in the next stable release.

If anyone using Identi.ca/Status.net wants to help testing this, please download the development version available at the Twitter module project page.

However, note that I am reluctant to do heavy coding just to support other microbloging services as it would affect negatively in the module's architecture.

Looking forward for your feedback.

No further feedback. Closing then.

I have just installed 6.x-3.0 here, and i don't see any fields in the Twitter Setup page. I see there are variables in the code that can be changed, so I tried:

drush vset twitter_host http://status.orangeseeds.org
drush vset twitter_search http://status.orangeseeds.org/search

Next, the website need to be registered in statusnet. So I headed to my statusnet install at http://status.orangeseeds.org/settings/oauthapps/new to create a new application. The callback URL, http://anarcat.koumbit.org/twitter/oauth in my case, need to be entered in the Callback URL field (duh).

However, this is where things start to fail, as there is no way to customize the api.twitter.com URL defined in twitter.lib.php, even if we change the TWITTER_API constant from twitter.module. I have tried hardcoding status.orangeseeds.org/api in there, but it fails to authentify. The weird thing there is that when I fill in my Oauth credentials in the Twitter setup page, the user-specific "Twitter accounts" page fails to give out a field for the "twitter username". When I click on the "add account" button anyways, I end up at http://status.orangeseeds.org/api/oauth/authorize?oauth_token= which, obviously, complains about "No oauth_token parameter provided"... The workaround for this was to bypass the "_twitter_use_oauth()" check, or otherwise hack at the oauth_callback url as done in the patch.

After hacking directly in the code to change all those URLs, I have finally been able to add an account. I attach a patch of the hacks that were necessary for this to work. However, I cannot post to the status.net site. The node form posts without a user-visible error.

The second patch provided is also an attempt to associate with an account purely in oauth instead of providing the username. This fails at some point with the following error from statusnet:

Invalid request token or verifier.

If I just disable the consumer/secret keys, I can add an account fine, but I can't post to it.

Note that I had to resort to tcpdump to get those errors as the Drupal side of things just crash completely with a 500 error as there is absolutely no exception handling in the twitter module, so the exceptions propagate upwards the stack and never get caught. Booom. (See also #902640: Twitter error messages are not propagated about this.)

So it seems that, at the very least, some customization need to happen for this to work, then there are some API clunking fixes to work on so that we can be compatible with status.net...

I guess this can be won't fixed as this branch is no longer supported.

Feel free to reopen for another version if this is still an issue.