Bookmarked Gopher: When Adversarial Interoperability Burrowed Under the Gatekeepers' Fortresses by Cory DoctorowCory Doctorow (Electronic Frontier Foundation)

The Gopher story is a perfect case history for Adversarial Interoperability. The pre-Gopher information landscape was dominated by companies, departments, and individuals who were disinterested in giving users control over their own computing experience and who viewed computing as something that took place in a shared lab space, not in your home or dorm room.

Rather than pursuing an argument with these self-appointed Lords of Computing, the Gopher team simply went around them, interconnecting to their services without asking for permission. They didn't take data they weren't supposed to have—but they did make it much easier for the services' nominal users to actually access them.

Paul Linder‘s retweet of a post by Cory Doctorow ()
Read Gopher: When Adversarial Interoperability Burrowed Under the Gatekeepers' Fortresses by Corey Doctorow (Electronic Frontier Foundation)
When Apple's App Store launched in 2008, it was widely hailed as a breakthrough in computing, a "curated experience" that would transform the chaos of locating and assessing software and replace it with a reliable one-stop-shop where every app would come pre-tested and with a trusted seal of...

The Gopher story is a perfect case history for Adversarial Interoperability. The pre-Gopher information landscape was dominated by companies, departments, and individuals who were disinterested in giving users control over their own computing experience and who viewed computing as something that took place in a shared lab space, not in your home or dorm room.
Rather than pursuing an argument with these self-appointed Lords of Computing, the Gopher team simply went around them, interconnecting to their services without asking for permission. They didn’t take data they weren’t supposed to have—but they did make it much easier for the services’ nominal users to actually access them. 

Annotated on February 23, 2020 at 08:39AM

Today’s Web giants want us to believe that they and they alone are suited to take us to wherever we end up next. Having used Adversarial Interoperability as a ladder to attain their rarefied heights, they now use laws to kick the ladder away and prevent the next Microcomputer Center or Tim Berners-Lee from doing to them what the Web did to Gopher, and what Gopher did to mainframes. 

Annotated on February 23, 2020 at 08:40AM

Legislation to stem the tide of Big Tech companies’ abuses, and laws—such as a national consumer privacy bill, an interoperability bill, or a bill making firms liable for data-breaches—would go a long way toward improving the lives of the Internet users held hostage inside the companies’ walled gardens.
But far more important than fixing Big Tech is fixing the Internet: restoring the kind of dynamism that made tech firms responsive to their users for fear of losing them, restoring the dynamic that let tinkerers, co-ops, and nonprofits give every person the power of technological self-determination. 

Annotated on February 23, 2020 at 08:42AM

Read webmentions and microsub (gopher.floodgap.com)

This phlog is about web stuff. Specifically it's about Indyweb things and microformats.

I use my website https://tomasino.org as an IndieAuth [0] portal. When logging into sites that understand the IndieWeb concept, I provide my "Home" URL as an identifier. Then the site scrubs through all the various links I have on that page and picks out those that it can understand for authentication. In most cases I get GPG and GitHub hits, though occasionally a site will support more. I oAuth in, and bam... identified. It's pretty neat and requires very little effort on my side.

IndieWeb with Gopher. Not sure if this will send a Webmention correctly though…
Read Replied to a post on gopher.floodgap.com by Johan BovéJohan Bové (Johan's Known)

James Tomasino wrote about his experience with implementing Webmentions on his Gopher blog.

To bridge my webmention from HTTP to Gopher, I'm web-mentioning his post through the Floodgap Gopher proxy. If you're using Lynx or another Gopher-capable browser, open his post here: gopher://gopher.black:70/phlog/20191223-webmentions-and-microsub

Read a post by Daniel Goldsmith (View from ASCRAEUS)

I’ve been happily noodling around the interstices of the web of late.

I’m still super happy with my nanoreader and using it everyday has reminded me of the beauty of plaintext. Text is content.

In that spirit, I’ve gone back to using gopher. I’ve finally got what I missed when I wrote about this three years ago - text doesn’t need to be the web! Text can just be itself, text should just be itself. My previous effort missed this fundamental principle, and looking back now, I can see that this was largely to blame for my walking away from that experiment.

Coming back to the idea of gopher, with that in mind, has been liberating.

Some of my content (not my microposts) is available on gopher, as this post will be. I’ve been doing this for a few weeks now, feeling my way into an area I once knew well, and I’m satisfied with the results.

I’d love to hear from anyone else who’s using gopher, or who’s using older text-focused network systems in interesting ways. I still want to love the web. I still want to find communities working to deliver on the promise there once was in this technology.

I seem to be seeing a lot of resurgence around Gopher in the past couple of months…