Freedomless freedom The beauty of kasuri is received as a gift. As long as the laws of nature are upheld, the beauty of kasuri remains intact. This demonstrates the curious principle that the artisan is deprived of technical freedom but works in the freedom of nature. In this sense, kasuri can be said to be created in a state of freedomless freedom. Yanagi Sōetsu, The Beauty of Kasuri freedomconstraintsnaturemaking
Technological middle age In the automobile's technological middle age, it is hard, if not impossible, to tune or repair one's own vehicle. Technical standardization of cars has occurred, and with it the elimination of the user's access to the machine itself. At the same time, the infrastructures that once served those who did not use automobiles atrophied and vanished. Some may say they were deliberately starved out. Railways gave way to more and more roadways. And thus a technology that had been perceived to liberate its users began to enslave them. Ursula M. Franklin, The Real World of Technology technologyfreedominfrastructure
Why We Build the Wall A Song by Anaïs Mitchell genius.com What do we have that they should want? We have a wall to work upon We have work and they have none And our work is never done And the war is never won The enemy is poverty And the wall keeps out the enemy And we build the wall to keep us free That’s why we build the wall We build the wall to keep us free So that its destruction cannot begin workfreedomcapitalism
How the Blog Broke the Web An Article by Amy Hoy stackingthebricks.com Homepages had a timeless qualityWhen Movable Type ate the blogosphereReverse chronology bias bloggingwww
Homepages had a timeless quality On the early web, there were thousands and thousands more personal homepages than weblogs. Homepages had a timeless quality, an index of interesting or useful or relevant things about a topic or about a person. You didn’t reload a homepage every day in pursuit of novelty. (That’s what Netscape’s What’s Cool was for!) Chronological content was in the minority. indexes
When Movable Type ate the blogosphere Here’s the crux of the problem: When something is easy, people will do more of it. When you produce your whole site by hand, from HEAD to /BODY, you begin in a world of infinite possibility. You can tailor your content exactly how you like it, and organize it in any way you please. Every design decision you make represents roughly equal work because, heck, you’ve gotta do it by hand either way. Whether it’s reverse chronological entries or a tidy table of contents. You might as well do what you want. But once you are given a tool that operates effortlessly — but only in a certain way — every choice that deviates from the standard represents a major cost. Movable Type didn’t just kill off blog customization. It (and its competitors) actively killed other forms of web production. constraintschoicetools
Reverse chronology bias Once you’ve had a taste of effortless updates, it’s awfully hard to back to manual everything. So they didn’t. And neither did thousands of their peers. It just simply wasn’t worth it. The inertia was too strong. The old web, the cool web, the weird web, the hand-organized web… died. And the damn reverse chronology bias — once called into creation, it hungers eternally — sought its next victim. Myspace. Facebook. Twitter. Instagram. Pinterest, of all things. Today these social publishing tools are beginning to buck reverse chronological sort; they’re introducing algorithm sort, to surface content not by time posted but by popularity, or expected interactions, based on individual and group history. There is even less control than ever before. There are no more quirky homepages. There are no more amateur research librarians. All thanks to a quirky bit of software produced to alleviate the pain of a tiny subset of a very small audience. That’s not cool at all. Navigation by shibboleth timequirks