Last modified: 2013-06-25 19:35:16 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T51476, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 49476 - adminbot (morebot) to lose ability to post to Twitter due to API deprecations
adminbot (morebot) to lose ability to post to Twitter due to API deprecations
Status: RESOLVED FIXED
Product: Utilities
Classification: Unclassified
Other (Other open bugs)
unspecified
All All
: High normal (vote)
: ---
Assigned To: Nobody - You can work on this!
http://identi.ca/doc/pumpio
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-06-12 09:43 UTC by Ori Livneh
Modified: 2013-06-25 19:35 UTC (History)
7 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Ori Livneh 2013-06-12 09:43:24 UTC
Identi.ca is migrating to a new distributed social service called 'pump.io'. This was supposed to have happened on June 8th, but details about it are a bit scarce. One of the things entailed in the migration is the deprecation of the current status.net API with adminbot uses to post messages to identi.ca that then get forwarded to Twitter.

Twitter also retired version 1.0 of its API, obsoleting some of the Python Twitter API libraries in Ubuntu Precise.

The future of identi.ca seems rather uncertain and the underlying protocol of the new pump.io API probably has a kink or three. It probably makes sense to ditch it and post to Twitter exclusively. (We have several hundred people following the SAL via Twitter.) We should start by identifying a reliable Twitter API client library that has some established history of following Twitter API changes.

http://identi.ca/doc/pumpio
https://github.com/e14n/pump.io/blob/master/API.md
https://github.com/e14n/pump.io/issues/151
Comment 1 Ori Livneh 2013-06-12 09:49:00 UTC
(Credit to Nemo for noticing this, BTW.)
Comment 2 Nemo 2013-06-12 09:55:18 UTC
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.
Comment 3 Tilman Bayer 2013-06-12 11:20:01 UTC
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.
Comment 4 Ryan Lane 2013-06-12 18:09:08 UTC
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.
Comment 5 Gerrit Notification Bot 2013-06-23 04:15:16 UTC
Related URL: https://gerrit.wikimedia.org/r/70032 (Gerrit Change I18c836dea5d39aff4811780abdedd24a7865d3d7)
Comment 6 Greg Grossmeier 2013-06-23 04:20:31 UTC
(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.
Comment 7 Ori Livneh 2013-06-23 04:32:02 UTC
(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.
Comment 8 Greg Grossmeier 2013-06-23 18:08:26 UTC
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....
Comment 9 Ryan Lane 2013-06-23 21:37:08 UTC
(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.
Comment 10 Greg Grossmeier 2013-06-24 15:55:37 UTC
(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.
Comment 11 Ori Livneh 2013-06-25 19:35:16 UTC
Fixed! Thanks Faidon, Ryan, Greg & Antoine for reviewing / testing / packaging / deploying etc.!

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links