Chronotope’s avatarChronotope’s Twitter Archive—№ 57,388

            1. The open web is to content agnostic user experiences as network neutrality is to content agnostic network pipes.
          1. …in reply to @Chronotope
            In both data counts, but is not counted. They *are* different cases. Which is how a tech co.s can be pro-network neutrality & anti-open web.
        1. …in reply to @Chronotope
          Slack, for example, couldn't afford a freemium model w/o network neutrality but they don't allow external services to access or archive them
      1. …in reply to @Chronotope
        Slack, therefore, would probably be impossible without network neutrality, but is absolutely anti-open web. So is Twitter. Same reasons.
    1. …in reply to @Chronotope
      In the end, limitations on either side of the equation are potentially terrifying in the scale they restrict access, and destroy history.
  1. …in reply to @Chronotope
    History you ask? Let's take an obvious example related to me by an open source historian...
    1. …in reply to @Chronotope
      WordPress's community once heavily relied on IRC, which was constantly archived. The archives could be searched, abstracted into data, DLed.
      1. …in reply to @Chronotope
        Now, like many open source projects, they are on Slack. Slack's structure and TOS prevent archiving, external DL and search...
        1. …in reply to @Chronotope
          WordPress's community is therefore now opaque to the greater web. And the growing, important(!) history of the project? Probably to be lost.
          1. …in reply to @Chronotope
            This is sad. Also important, because WordPress writes the web (25% of it). And the same is happening in many open source projects...
            1. …in reply to @Chronotope
              There are sure to be consequences to this beyond the academic, ones we can't predict. That's the danger of the closed web.
              1. …in reply to @Chronotope
                I honestly think it might be more dangerous than network neutrality issues. Bad networks are terrible, but we can route around them.
                1. …in reply to @Chronotope
                  Humanity doesn't do quite so well when it comes to working around lost history.


Search tweets' text