Ed,
I think you might have misunderstood Yuvi's first response.
and possibly a less reliable IRC bridge
running on labs.
I believe he meant that, rather than shutting down the IRC feed entirely, we'd write a bridge between RCStream and an IRC server so that laggards who insist on using IRC don't see their tools go down. But that bridge will inevitably be less stable than RCStream -- which using common/standard formats (JSON) on top of a standard protocol (websockets).
Really, RCStream is what the IRC feed ought to have been -- and probably would have been if those standards were available at the time of its construction. RCStream solves the same problem better.
-Aaron
On Tue, Apr 7, 2015 at 2:56 PM, Yuvi Panda yuvipanda@gmail.com wrote:
On Tue, Apr 7, 2015 at 12:51 PM, Ed Summers ehs@pobox.com wrote:
That wasn't the most compelling argument for migrating. But thanks for
the response:
Heh. The compelling arguments for migration to me are:
- This gives you structured JSON, no need to futz around with IRC
colors. This is a big one, I think 2. Easier to extend from the mediawiki side, so more events should be easier to add. 3. Far easier to consume rcstream than IRC Feeds (Websockets vs IRC) 4. Running our own IRC server is not the most fun thing in the world, and our ops team would like to not have to keep doing that forever.
I find (1) and (3) most compelling - look at the client examples on https://wikitech.wikimedia.org/wiki/RCStream#Client, they're vastly simpler than similar examples for IRC
-- Yuvi Panda T http://yuvi.in/blog
Wiki-research-l mailing list Wiki-research-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wiki-research-l