% BIND: % BIND: permissions, questions, transgression, identity, other, separation

% SCION: permissions
% FROM: http://pipelines.local:9001/p/server

	* Setup local server(s) & make your own network infrastructure, rather than "fixing the problems of internet access" by paying for increased bandwidth / data;
	* Prefer "read/write" and negotiable networks to those that "just work";
	* Prefer pocket servers to those in the clouds;
	* Embrace a diversity of network topologies and different scales (machine to machine, local nodes, institutional infrastructure) and consider the implications of working with each; \
	* Rather than a Web 2.0 model where resources must be uploaded onto "a 24/7 Internet" in order to share them; where sharing presupposes acceptance of non-negotiable / non-rewritable Terms of Service defined by market-leading global corporations)
	* Invite participants to look critically at the implications of *any* infrastructural decisions, rather than imagining utopic and/or "killer" solutions; 
	* Aim to make that which is normally hidden and invisible (in contexts that tend to surveillance), explicit and shared (as a gesture of collective authorship), for instance:
		* Instead of caching web resources (silently), imagine services to archive resources and share them locally as cookbooks or a digital library;
		* Rather than logging servers and database accessible only by administrators, imagine (local) logs available for reading / editing by participants and published conditionally.
% [_server_](http://pipelines.local:9001/p/server)

% SCION: questions
% FROM: http://pipelines.local:9001/p/some_thoughts_on_modularity...

How can our questions be our politics. How we build the question, through apparatus.
How can we fail well at politics (because most of our experiments don't work most of the time; RATHER THAN THINKING ABOUT A SUPREME POLiTICS that's always right, we should think about a how do we fail well in politics, so we should accept that this happens, not look for politics that are universally right)
(is this all a quote, and from who?)
% [_some_thoughts_on_modularity..._](http://pipelines.local:9001/p/some_thoughts_on_modularity...)

% SCION: transgression
% FROM: http://pipelines.local:9001/p/a_walk_along_the_zenne

In software, a stack overflow occurs if the stack pointer exceeds the stack bound. The call stack may consist of a limited amount of address space, often determined at the start of the program. The size of the call stack depends on many factors, including the programming language, machine architecture, multi-threading, and amount of available memory. When a program attempts to use more space than is available on the call stack (that is, when it attempts to access memory beyond the call stack's bounds, which is essentially a buffer overflow), the stack is said to overflow, typically resulting in a program crash
% [_a_walk_along_the_zenne_](http://pipelines.local:9001/p/a_walk_along_the_zenne)

% SCION: identity
% FROM: http://pipelines.local:9001/p/QueerOS

% [_QueerOS_](http://pipelines.local:9001/p/QueerOS)

% SCION: other
% FROM: http://pipelines.local:9001/p/anticolonialhacking

the graph, the need to make visible
emerged in a movement .. how to include the layers in the story
colonialist narrative, but simplified through the hacking story. How to bring layers in there?
% [_anticolonialhacking_](http://pipelines.local:9001/p/anticolonialhacking)

% SCION: separation
% FROM: http://pipelines.local:9001/p/modules

Rule of Modularity -> Rule of Separation
% [_modules_](http://pipelines.local:9001/p/modules)