(Credit to Nemo for noticing this, BTW.)

Someone should warn the social media team, they also are taking care of some identi.ca migration stuff and are interested in identi.ca<->Twitter coordination.

Yes, we have been discussion this in the social media team. After Erik reached out to Evan last week, we are currently proceeding under the assumption that a Twitter bridge will become available again soon after the pump.io transition.

I think for the time being we should drop identi.ca support and just post directly to twitter for adminbot (morebots). The follower count on identi.ca is far smaller than twitter (85 vs 599) and there's only a single pump.io python library that is mostly incomplete, isn't packaged, requires python 3.3, and requires us to drop another unpackaged library into its path. The following on pump.io is likely to be even smaller than identi.ca's and without the pump.io -> twitter bridge we'd be cutting off a larger following for a much smaller following.

Related URL: https://gerrit.wikimedia.org/r/70032 (Gerrit Change I18c836dea5d39aff4811780abdedd24a7865d3d7)

(In reply to comment #4)

The following on
pump.io is likely to be even smaller than identi.ca's and without the pump.io
-> twitter bridge we'd be cutting off a larger following for a much smaller
following.

Just so it's clear: the following count won't change post pump.io transition. If anyhting, it might go up as people try out pump.io either via their identi.ca account or via another pump.io powered site. Think of it as a backend rewrite where the users will just experience the site differently. All their follows/etc will stay intact.

(In reply to comment #6)

(In reply to comment #4)

The following on pump.io is likely to be even smaller than identi.ca's and
without the pump.io -> twitter bridge we'd be cutting off a larger following
for a much smaller following.

Just so it's clear: the following count won't change post pump.io transition.
If anyhting, it might go up as people try out pump.io either via their
identi.ca account or via another pump.io powered site. Think of it as a
backend rewrite where the users will just experience the site differently.
All their follows/etc will stay intact.

Patch 70032 (above) adds the ability to log directly to Twitter via v1.1 of their API. It doesn't disable or remove the code that logs to identi.ca.

Since the patch is in, the question of priorities is now moot. If we want to throw our support behind pump.io by adding pump.io integration to adminlog, that's totally cool, but unrelated to Twitter.

It doesn't look like https://github.com/xray7224/PyPump will support Python 2.x or be stable/mature enough to depend on any time soon, though, so we'd likely have to write some custom Python code ourselves. This shouldn't be too hard. python-twitter depends on python-oauth2, so we can use python-oauth2 without adding an additional dependency. This should make it possible to write a concise method for logging a single message to pump.io.

Shall we make this bug only about Twitter and close it (after we see the first real post using the code you wrote, Ori) and file another one for identi.ca support? Seems cleaner and we'll at least be FIXED RESOLVED for one part....

(In reply to comment #8)

Shall we make this bug only about Twitter and close it (after we see the
first
real post using the code you wrote, Ori) and file another one for identi.ca
support? Seems cleaner and we'll at least be FIXED RESOLVED for one part....

That seems reasonable to me.

(In reply to comment #9)

(In reply to comment #8)

Shall we make this bug only about Twitter and close it (after we see the
first
real post using the code you wrote, Ori) and file another one for identi.ca
support? Seems cleaner and we'll at least be FIXED RESOLVED for one part....

That seems reasonable to me.

Done. See bug 50109 for identi.ca stuff. Once there's a good post from adminbot to twitter, we can RESOLVED FIXED this'un.

Fixed! Thanks Faidon, Ryan, Greg & Antoine for reviewing / testing / packaging / deploying etc.!