{"resolved":true,"match_type":"uuid","source_type":"original_book","book_id":"24410bf1-91f1-4e6b-9613-e64f0132d341","title":"The Stack On Software and Sovereignty","author":null,"edition":null,"publisher":null,"year":null,"isbn":"9780262029575","requested_by":"printed_page","book":{"source_type":"original_book","book_id":"24410bf1-91f1-4e6b-9613-e64f0132d341","id":"24410bf1-91f1-4e6b-9613-e64f0132d341","uuid":"24410bf1-91f1-4e6b-9613-e64f0132d341","title":"The Stack On Software and Sovereignty","normalized_title":"thestackonsoftwareandsovereignty","author":null,"edition":null,"publisher":null,"year":null,"isbn":"9780262029575","isbns":["9780262029575"],"parsed":true,"ai_readable":true,"document_type":"book","page_count":517,"navigation_url":"https://workshop.closeclaw.top/ai/book/24410bf1-91f1-4e6b-9613-e64f0132d341","title_url":"https://workshop.closeclaw.top/ai/title/The%20Stack%20On%20Software%20and%20Sovereignty","fixed_page_url_template":"https://workshop.closeclaw.top/ai/book/24410bf1-91f1-4e6b-9613-e64f0132d341/page/{printed_page}","path_api_url_template":"https://workshop.closeclaw.top/api/ai/book/24410bf1-91f1-4e6b-9613-e64f0132d341/page/{printed_page}","read_url":"https://workshop.closeclaw.top/api/ai/read/24410bf1-91f1-4e6b-9613-e64f0132d341","page_url":"https://workshop.closeclaw.top/api/ai/books/24410bf1-91f1-4e6b-9613-e64f0132d341/page","search_url":"https://workshop.closeclaw.top/api/ai/books/24410bf1-91f1-4e6b-9613-e64f0132d341/search"},"page":{"printed_page":338,"pdf_page":352,"physical_index":352,"physical_index_base":0,"printed_page_status":"recognized","page_sha256":"79d81577b442fd1ffffc78a2423a349ec79de18dd819a442018bf3144e1a454b"},"chapter":"Fheck The Stack |On Software and Sovereignty Benjamin H. Bratton","content":"As computation becomes more deeply ubiquitous and the agency of the User is shared by any addressable thing or event, then for many people, the world may become an increasingly alien environment in which the privileged position of everyday human intelligence is shifted off-center. To my thinking, this strongly recommends this program. As discussed in the Interface chapter, one of the chief functions of the GUI ’ s reductions is the simplification and narration of all possible interactions to a understandable set of options for the User to easily manage. Long before we achieve anything like a deep address hypermaterialism, the design of any sufficiently advanced Internet of Things infrastructure will have to deal with ongoing complexity issues for human Users and, it is hoped, will do so in ways more imaginative that simple physical skeuomorphisms for which an object “ looks like ” what it does (i.e., tiny models that are synced with their full-size counterparts elsewhere, like little tanks on a big war gaming table). As designers learn to accommodate nonhuman Users, those kinds of correspondences may or may not prove useful, but the basic function of the interface, graphical or objective, will persist: to reduce the complexity of systems by presenting some selfreferential closure that will allow for directed entry into that system and into how that system differentiates itself from its own environment. <sup>66</sup>\n\n338\n\nThe Stack to Come","previous_page":337,"next_page":339}