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

                    1. The open web is to content agnostic user experiences as network neutrality is to content agnostic network pipes.
                      Permalink On twitter.com Twitter logo Chronotope’s avatar ♻️ 2 Retweets ❤️ 2 Favorites Mood 0
                  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.
                    Permalink On twitter.com Twitter logo Chronotope’s avatar ♻️ 2 Retweets Mood 0
                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
                  Permalink On twitter.com Twitter logo Chronotope’s avatar ♻️ 2 Retweets Mood -1 🙁
              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.
                Permalink On twitter.com Twitter logo Chronotope’s avatar ♻️ 3 Retweets ❤️ 1 Favorite Mood 0
            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.
              Permalink On twitter.com Twitter logo Chronotope’s avatar ♻️ 3 Retweets ❤️ 1 Favorite Mood -5 🙁
          1. …in reply to @Chronotope
            History you ask? Let's take an obvious example related to me by an open source historian...
            Permalink On twitter.com Twitter logo Chronotope’s avatar ♻️ 3 Retweets Mood 0
        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.
          Permalink On twitter.com Twitter logo Chronotope’s avatar ♻️ 3 Retweets ❤️ 1 Favorite Mood 0
      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...
        Permalink On twitter.com Twitter logo Chronotope’s avatar ♻️ 3 Retweets ❤️ 1 Favorite Mood +1 🙂
    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.
      Permalink On twitter.com Twitter logo Chronotope’s avatar ♻️ 2 Retweets Mood +3 🙂
  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...
    On twitter.com Twitter logo Chronotope’s avatar ♻️ 1 Retweets ❤️ 2 Favorites Mood 0
    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.
      Permalink On twitter.com Twitter logo Chronotope’s avatar ♻️ 1 Retweets ❤️ 1 Favorite Mood -2 🙁
      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.
        Permalink On twitter.com Twitter logo Chronotope’s avatar Mood -8 🙁
        1. …in reply to @Chronotope
          Humanity doesn't do quite so well when it comes to working around lost history.
          Permalink On twitter.com Twitter logo Chronotope’s avatar ❤️ 1 Favorite Mood -3 🙁

Search tweets' text