Tag: IRC

The smallest deed is better than the greatest intention

Thanks to John Burroughs for today’s title. For me, it’s an oblique reference to some of the situations I find myself in, both in my professional and personal life. After all, words are cheap and actions are difficult.

I’m going to take the unusual step of quoting someone who’s quoting me. In this case, it’s Stephen Downes picking up on a comment I made in the cc-openedu Google Group. I’d link directly to my comments, but for some reason a group about open education is… closed?

I’d like to echo a point David Kernohan made when I worked with him on the Jisc OER programme. He said: “OER is a supply-side term”. Let’s face it, there are very few educators specifically going out and looking for “Openly Licensed Resources”. What they actuallywant are resources that they can access for free (or at a low cost) and that they can legally use. We’ve invented OER as a term to describe that, but it may actually be unhelpfully ambiguous.

Shortly after posting that, I read this post from Sarah Lambert on the GO-GN (Global OER Graduate Network) blog. She says:

[W]hile we’re being all inclusive and expanding our “open” to encompass any collaborative digital practice, then our “open” seems to be getting less and less distinctive. To the point where it’s getting quite easily absorbed by the mainstream higher education digital learning (eLearning, Technology Enhanced Learning, ODL, call it what you will). Is it a win for higher education to absorb and assimilate “open” (and our gift labour) as the latest innovation feeding the hungry marketised university that Kate Bowles spoke so eloquently about? Is it a problem if not only the practice, but the research field of open education becomes inseparable with mainstream higher education digital learning research?

My gloss on this is that ‘open education’ may finally have moved into the area of productive ambiguity. I talked about this back in 2016 in a post on a blog I post to only very infrequently, so I might as well quote myself again:

Ideally, I’d like to see ‘open education’ move into the realm of what I term productive ambiguity. That is to say, we can do some workwith the idea and start growing the movement beyond small pockets here and there. I’m greatly inspired by Douglas Rushkoff’s new Team Human podcast at the moment, feeling that it’s justified the stance that I and others have taken for using technology to make us more human (e.g. setting up a co-operative) and against the reverse (e.g. blockchain).

That’s going to make a lot of people uncomfortable, and hopefully uncomfortable enough to start exploring new, even better areas. ‘Open Education’ now belongs, for better or for worse, to the majority. Whether that’s ‘Early majority’ or ‘Late majority’ on the innovation adoption lifecycle curve probably depends where in the world you live.

Diffusion of innovation curve
CC BY Pnautilus (Wikipedia)

Things change and things move on. The reason I used that xkcd cartoon about IRC at the top of this post is because there has been much (OK, some) talk about Mozilla ending its use of IRC.

While we still use it heavily, IRC is an ongoing source of abuse and harassment for many of our colleagues and getting connected to this now-obscure forum is an unnecessary technical barrier for anyone finding their way to Mozilla via the web. Available interfaces really haven’t kept up with modern expectations, spambots and harassment are endemic to the platform, and in light of that it’s no coincidence that people trying to get in touch with us from inside schools, colleges or corporate networks are finding that often as not IRC traffic isn’t allowed past institutional firewalls at all.

Cue much hand-wringing from the die-hards in the Mozilla community. Unfortunately, Slack, which originally had a bridge/gateway for IRC has pulled up the drawbridge on that front, so they could go with something like Mattermost, but given recently history I bet they go with Discord (or similar).

As Seth Godin points out in his most recent podcast episode, everyone wants be described as ‘supple’, nobody wants to be described as ‘brittle’. Yet, the actions we take suggest otherwise. We expect that just because the change we see in the world isn’t convenient, that we can somehow slow it down. Nope, you just have to roll with it, whether that’s changing technologies, or different approaches to organising ideas and people.


Also check out:

  • Do Experts Listen to Other Experts? (Marginal Revolution) —”very little is known about how experts influence each others’ opinions, and how that influence affects final evaluations.”
  • Why Symbols Aren’t Forever (Sapiens) — “The shifting status of cultural symbols reveals a lot about who we are and what we value.”
  • Balanced Anarchy or Open Society? (Kottke.org) — “Personal computing and the internet changed (and continues to change) the balance of power in the world so much and with such speed that we still can’t comprehend it.”

Slack’s bait-and-switch?

I remember the early days of Twitter. It was great, as there were many different clients, both native apps and web-based ones. There was lots of innovation in the ecosystem and, in fact, the ‘pull-to-refresh’ feature that’s now baked into every social app on a touchscreen device was first created for a third-party Twitter client.

Twitter then, of course, once it had reached critical mass and mainstream adoption, killed off that third party ecosystem to ‘own the experience’. It looks like Slack, the messaging app for teams, is doing something similar by turning off support for IRC and XMPP gateways:

As Slack has evolved over the years, we’ve built features and capabilities — like Shared Channels, Threads, and emoji reactions (to name a few) — that the IRC and XMPP gateways aren’t able to handle. Our priority is to provide a secure and high-quality experience across all platforms, and so the time has come to close the gateways.

A number of people weren’t happy about this, notably those who rely on the superior accessibility features available through IRC and XMPP. A software developer and consultant by the name of JC Brand takes Slack to task:

We all know the real reason Slack has closed off their gateways. Their business model dictates that they should.

Slack’s business model is to record everything said in a workspace and then to sell you access to their record of your conversations.

They’re a typical walled garden, information silo or Siren Server

So they have to close everything off, to make sure that people can’t extract their conversations out of the silo.

We saw it with Google, who built Gtalk on XMPP and even federated with other XMPP servers, only to later stop federation and XMPP support in favour of trying to herd the digital cattle into the Google+ enclosure.

Facebook, who also built their chat app on XMPP at first allowed 3rd party XMPP clients to connect and then later dropped interoperability.

Twitter, although not using or supporting XMPP, had a vibrant 3rd party client ecosystem which they killed off once they felt big enough.

Slack, like so many others before them, pretend to care about interoperability, opening up just so slightly, so that they can lure in people with the promise of “openness”, before eventually closing the gate once they’ve achieved sufficient size and lock-in.

I’m definitely on the side of open source people/projects here, but it’s worth noting that the author uses the post to promote the solution he’s been developing. And why not?

There’s a comment below the post which makes, I think, a good point:

I’m betting this decision wasn’t made by the same folks who were at Slack (or Facebook, Google, etc) and thought adding support for the open protocols was a good thing. I bet the decision is a product of time over any attempt to trick anyone. Over time people change roles, leave, and slowly new leadership emerges. Outside pressures (market growth, investors) require a change in priority and the org shifts away from supporting things that had low adoption and ongoing maintenance cost.

So I don’t think it’s as malicious as the author implies (Bait and Switch) as that requires some nefarious planning and foresight. I think it’s more likely to be business/product evolution, which still sucks for adopters and the free net, but not as maleficent. Just, unfortunately, the nature of early tech businesses maturing into Just Another Business.

Indeed.

Source: Opkode