Compare commits

..

No commits in common. 'master' and 'master' have entirely different histories.

@ -1,10 +1,15 @@
# SquatConf Call For Papers Berlin 2016
Welcome to SquatConf CFP repository.
Welcome to SquatConf CFP repository. you can also mail your submission to [talks@squatconf.eu] please copy this [model] and mail it.
## Submit a talk
# CFP IS NOW CLOSED
- Fork this repo
- `cp submitTalk.md proposed/my_talk.md`
- Edit your talk
- Submit a pull request
or use the email submission (see paragraph above).
## Disclaimer
@ -25,3 +30,5 @@ cool people.
SquatConf is an experience, it is up to you to try it.
[talks@squatconf.eu]: mailto:talks@squatconf.eu
[model]: https://raw.githubusercontent.com/squatconf/talks/master/submitTalk.md

@ -1,14 +1,19 @@
# Infos
auth-name : David Potocnik / david@totalism.org / @dcht00
need travel fee : hope to self-org, see [http://totalism.org/base-eu](http://totalism.org/base-eu)
need room : no
Location : UK
# Hackbases, infrastructure for postcapitalism
Speaker : David Potocnik / david@totalism.org / @dcht00
time : 30min + 30min (discussion)
Often hailed as some ultimate constructive and radical force, hackers are subsumed by the lifestyle logic of current advanced capitalist societies. To describe a common hacker is to describe a hobbyist - hanging out at the local hackerspace and playing with personal projects after necessary paid labour. This covers their subsistence, but also probably more or less directly powers the bullshit neoliberal political reality, with its destructive effects on society and nature.
Hackbases are a new type of institution to enable work in the other direction. They are hackerspaces you can also live in, for any period of time, with minimized need for dealing with (earning, spending) money. The goal is to design and spread a tech-forward model of infrastructure and a lifestyle, supporting free, full-time avantgarde technologists and people in general, serving the commons. This talk should equip and inspire you to visit one of the existing bases (like CHT in Lanzarote, Canary Islands @ http://totalism.org/), or even better, reorganize your living situation to start a new one.
[http://totalism.org/base-eu]
need travel fee: pls // need room: hope to self-org, see http://totalism.org/base-eu ? // Location: huh?
duration: 30min + 30min (discussion)
need travel fee : if possible
need room : hope to self-org, see [http://totalism.org/base-eu](http://totalism.org/base-eu)
Location : UK
[http://totalism.org/base-eu]

@ -1,13 +1,16 @@
# anarchitecture
# Infos
auth-name : Substack
tag : some things
Speaker : Substack
tag : some things
need travel fee : na
need room : na
Location : Earth?
# anarchitecture
As the web browser accumulates important features, we can offload more of the
work of servers onto clients. What happens when there's no more work for the
server to do? How can we use webrtc and p2p techniques to build internet
services that nobody can own?
need travel fee : na
need room : na
Location : Earth?

@ -1,11 +1,8 @@
# Apathy, and "My Pet Project"
Speaker : dvn
contact: : dvn
I see two systemic behaviours in the broad hacker community, which consistantly stifle progress, and I don't think it has to be this way.
Whether it's giving up on private communication due to societal pressure, or growing jaded from investing all your time into developing proprietary software for an ungrateful company, apathy is a grating force in open source communities. The second, and an arguabely bigger problem, is what I'm calling the "Pet Project" syndrome. People grow to love a software project like their own child, and often end up favouring, and defending it like it's their own child. This causes people to close their eyes to solutions others have already found, and creates a lot of parallel work.
I'd like to collaboratively discuss these issues, provide some examples, and maybe we can discover some solutions.
need travel fee : N
need room : Y

@ -1,18 +0,0 @@
Speaker: hoegrammer
Tags: refugees, digital exclusion
This talk is a call to action, and a cry for help.
Digital exclusion is a huge problem for refugees. Without passports, they can't buy mobile data. Money is also a problem for many. Wifi cafes only go so far.
The psychological necessity of communicating with family and friends is only part of it. Rumours, misinformation and lies spread like wildfire. People are not getting the information they need to make decisions about their future. They don't know what is legal and what is not. And now, unbelievably, the Greek government has decided to offer asylum registration ONLY THROUGH SKYPE, FOR FUCK'S SAKE.
I'll talk about how I failed them at Ritsona camp in recent weeks, and how I hope to do better. About the problems we face, politically and technologically.
I have only basic knowledge of networking technology, but now seems like a perfect time to learn. I'll be asking for advice on quick, simple ways to get people online, and wisdom about the politics involved as well.
Secure communication is also an issue - for volunteers working outside of the law, as well as the refugees themselves.
The ISPs, the mobile networks, the corporations will not deliver to these vulnerable people the connectivity which has become almost a human right.
If anyone's going to help them, it can only be people like us.

@ -1,19 +0,0 @@
# unix & holistic technologies
Speaker : noffle
tag : holistic prescriptive unix web distributed node
Every technology lies on a spectrum: prescriptive technologies, like car
assembly lines, have dependence on large non-individual organizational
structures in order to function; while holistic tech is self-reliant and
depends on little, like a personal garden. Or a unix program. Most
things lie somewhere in between.
What the consequences of a society heavily dependent on prescriptive
technologies? What is its cost of adoption? Where can freedom be found
in taking control of the toolchain? Let's look at where the unix
philosophy and the web fit in.
need travel fee : N
need room : N
Location : San Jose, CA

@ -1,10 +0,0 @@
# Host your own stuff at home
Speaker : realitygaps
tag : selfhost
In the modern world, where all your data is hosted on other peoples computers (the cloud) - wouldnt it be nice to host it yourself in the comfort of your own home?
need travel fee : N
need room : Maybe
Location : Universe

@ -1,11 +0,0 @@
# How to intercept your bosses print jobs
Speaker : Thomas Watson
Location : Copenhagen, Denmark
Bonjour/Zeroconf is used to automatically configure and connect to networked devices like printers on a LAN and is widely deployed in offices and homes. This talk gives an introduction to the Zeroconf standard and shows how its vulnerable to a man-in-the-middle attack.
The talk will show how Zeroconf can be exploited to allow a man-in-the-middle attack on any Zeroconf enabled device. This allows you to intercept anything from print jobs to admin panel passwords.
Bio:
I'm an open source hacker. I enjoy mad science hacks and working with network protocols. My current programming language of choice is Node.js and I teach programming by organising or mentoring local NodeSchool events around the world.

@ -1,164 +0,0 @@
#Get better at helping people with programming
Marina Kukso
@marinakukso
---
#things i didn't know when i was a beginner
* the big boy voice is bullshit
* i am not dumb if i don't understand what you're telling me
* it's not strange if i don't know x - i just don't know it.
* "the DOM"
* relationship b/w hardware and software
* how to use sample code & install instructions
* prog is a skill that you can learn like other skills.
* why programming books start with data types
* there are crystals inside computers
* what exactly a bit is
---
#experiences i had already had when i was a beginner
* geocities, html
* CS1 in college (java, eclipse)
* fetishization of programming
* "what it's like to be a woman at a bitcoin meetup"
* bad outcomes when i asked questions
---
#things that didn't work for me
* "ok, type console.log"
* "install firebug. you'll need it."
* online code schools & other non-interoperable things
* "just learn python"
* intro to github
* skeleton css framework
---
#things that worked for me - laying the groundwork
* html, geocities
* taking a computer apart
* bits & how computers store info
* pen and paper registry, data structures, pseudocode
* computer/programming "ask me anything" sessions
* being around nice hackerpeople
---
#things that worked for me - programming
* figured out that i needed to learn linux before a prog language
* bash - sit with tutee & do things via command line
* analogies and examples
* writing programs from scratch
* working with node (most people will be happy to make a website)
* concrete projects: neocities, studio.substack.net, voxel.js, hardware, scripts
* amazing mentors, ongoing mentorship
* mentors pushed me to ask questions until i understood
* computerphile - "how would you make a computer do x"
---
#general tips
* empathy!
* assume as little as possible about the learner - ask q's
* constant feedback loop between you and the learner
* reassurance (personal stories) can be helpful
* examples, analogies, demonstrate on your comp
* history of computing - give the context! (eg origin of text-based interfaces.)
* help them set up an environment that will allow them to keep learning on their own
* person who sees self as beginner may not feel empowered to ask q's
* silence is not "i understand." check in at every step.
* ask q's until you understand what they're confused about
* read between the lines. xy problem. beginners often don't
use the right words to describe a problem.
* be aware of power you may hold in a situation
* you don't have to help all the time. "i'm busy right now", man pages
* jargon: focus on relevance/function; explain any jargon
in your explanation; if you are giving a very accurate, specific
explanation, explain why these seemingly minor
distinctions matter.
---
#specific tips
* don't touch learner's keyboard
* no, please: "it's easy"/"just do..."
* "are you familiar with?"
* "does that make sense?"
* "are you stuck on anything?"
* "do you know what to do next?"
* man pages, googling, reading errors
* don't say "guy" for "person"
* be aware of how you present to others - big boy voice, don't stare!
* as a mentor, you are responsible for the tenor of the
learning environment - ya gotta enforce!
* "do you have any ideas for what to work on?" if not, share
ideas that would be within reach of that person
* many want to learn prog for "practical" reasons, but not all!
* if a noob seems to be using a bad/weird tool, ask about it
& chat. (don't be dismissive or just suggest another tool
w/no explanation. give context.)
---
#secrets you should tell learners
* programmers use linux
* "which distro?" - k/l/ubuntu is well-supported
* "which language?" = "i'm not sure what to learn first".
start with bash!
* how programmers use IRC
* don't get taken in by those who use the big boy voice
* you don't have to take hazing/trolling/dickishness
* much of programming is not writing difficult algorithms
* much of programming is not hot shit. boring, useless, not wizardry.
* you don't have to memorize all the commands in the book
* linux commands are programs
* what built-in methods are
* don't update linux
* shell tips: .. , tab complete, history
* dev environment: text editors, git & github
* how "professional websites" get built: dev vs production, bug trackers, etc.
* what is localhost and how to run a dev version of your thing
* everyone googles all the time
* pros don't just have all errors & solutions memorized.
they've just learned through suffering through many errors.
one day this will be you! :D
* no: "i'm stuck on x but it's supposed to be easy!" it's
frustrating, but the more time you spend, the faster
you'll get. you will learn through pain :P
* there are common patterns in programming.
* if you don't get it, it doesn't make you dumb.
* you don't always have to know every detail of a thing to use it
* server program vs server computer
* different ways that the word "API" is used
* package manager as "free app store"
* solving problems w/a bag of command line apps vs giant gui program
* common command line apps - mplayer, imagemagick, youtube-dl, etc.
* large software & bags of utilities (frameworks, d3, etc.) vs small libraries
* types of work that's out there (front end, back end, sys admins)
* existing controversies & hierarchies in the field
* command line seems hard, but is easy. programming seems easy, but is hard.
---
#running a collaborative learning group
* space
* mentors
* learners
* calendar
* noise
* surprise treats are great
* encourage co-learning

@ -0,0 +1,14 @@
# Infos
auth-name : realitygaps
tag : selfhost
need travel fee : N
need room : Maybe
Location : Universe
# Host your own stuff at home
In the modern world, where all your data is hosted on other peoples computers (the cloud) - wouldnt it be nice to host it yourself in the comfort of your own home?
~
~

@ -1,6 +1,6 @@
# How to ruin a community in 3 easy steps
Speaker : Caleb James DeLisle
Caleb James DeLisle
This is less a presentation than a wild tale of trying to keep the Hyperboria network a cool and
friendly place for all kinds of people, especially women and minorities who don't have so many cool

@ -1,12 +1,15 @@
# Lessons learned from learning and teaching programming
# Infos
auth-name : marina (@marinakukso)
tag : some things
need travel fee : i have already bought my ticket to berlin, but would love to have some of that cost offset.
need room : Y (can accompany substack, or be on my own)
Location : San Diego, CA, USA
Speaker : marina (@marinakukso)
tag : some things
# Lessons learned from learning and teaching programming
i have been a programming apprentice for about two years. during this time, my friends and i ran a free, cooperative "anti-bootcamp" (http://cyber.wizard.institute/), and participated in a lot of informal collaborative learning in our friend group. i'd like to share with you some of the patterns and anti-patterns that i've run into learning programming as an adult with peers. this will include some of the things that were most tricky for me to learn and also some of the things we discovered that seemed to worked well when teaching.
Length: I am flexible. this talk can be longer or shorter based on the time you have available. i can do 20 minutes, but can also do up to an hour or down to 5 minutes. i am also flexible with regard to the content. if you think that a related or additional issue would be more relevant to the audience than what i've included, i'm happy to discuss modifications.
need travel fee : i have already bought my ticket to berlin, but would love to have some of that cost offset.
need room : Y (can accompany substack, or be on my own)
Location : San Diego, CA, USA

@ -1,12 +1,14 @@
# Mr. Peel Goes To Cyberspace
# Infos
auth-name : Dmytri
tag : p2p communism
Speaker : Dmytri
tag : p2p communism
need travel fee : no
need room : no
Location : Berlin
# Mr. Peel Goes To Cyberspace
Resisting Digital Colonization with Technological Disobedience,
Counterantidisintermediation and Venture Communism.
No Servers! No Admins!
need travel fee : no
need room : no
Location : Berlin

@ -0,0 +1,16 @@
# Infos
auth-name : naomi rosenberg
tag : refactoring, micro-management, professionalism
need travel fee : N
need room : Y
Location : Planet Earth
# How Stealth Refactoring is Wrecking our Codebases
Because management are perceived not to value refactoring, developers fear being “told off” for doing it. So we refactor less than wed like to, and when we do, we often sneak it in, hidden amongst functional changes.
We know insufficient refactoring leads to technical debt. Stealth refactoring creates problems, too. Reviewing a diff mixing functional and non-functional changes is time-consuming and error-prone, costing money and introducing bugs. Also, stealth refactoring tends to focus only on the “geographical area” - the function, file or module - that we are “touching” at the time. What are the implications of that for the coherence and consistency of our codebases?
I will make some technical suggestions for optimising how we refactor, but the main issue is cultural. Is our shame around refactoring entirely due to management, or are devs responsible too? How can we sell simplicity to people who may not be aware of its value? Can we create a culture that legitimises - or even rewards! - a practice that is, after all, essential to developing good software?

@ -1,9 +0,0 @@
# Mapping the Megacity - Challenges of applying a developed world software standard to a devloping world context
Speaker : brabo
time : 5-10 minutes, discussion perhaps 10 min?
Some years ago I was inspired to take a list of known empty residences and transform it to a google maps so people could use it to find places to squat. I tried to build further on this by scraping real estate websites. Sadly, it is too big for me alone, and involves software I myself am not good enough at. So, let us all take a couple minutes to consider what we may be able to create here.
length - talk ~ 5-10 minutes, discussion perhaps 10 min?
## still unsure if Brabo will make it, PLEASE MAKE IT

@ -1,13 +1,13 @@
# Toolbox for Cybernetic Totalitarianism
Speaker : Ksenia
# Infos
This would be a very short talk that I would like to become a discussion as quickly as possible.The aim is not so much mapping out and going over the things which creep us out: such as for example blockchains and linked data
but to invite people to look at the dystopia scenarios, set of tools and strategies which which might come in handy for navigating cybernetic totalitarianism. It is really a continuation of several long and short conversations I had with quite a few people,
at least two of them will be amongst the attendees.
auth-name : ???
need travel fee : appreciated, if possible
need room : no
Location : UK
## ksenia choosed this talk between the 2 she made we will see if we can put this one somewhere sometime
# Toolbox for Cybernetic Totalitarianism
This would be a very short talk that I would like to become a discussion as quickly as possible.The aim is not so much mapping out and going over the things which creep us out: such as for example blockchains and linked data
but to invite people to look at the dystopia scenarios, set of tools and strategies which which might come in handy for navigating cybernetic totalitarianism. It is really a continuation of several long and short conversations I had with quite a few people,
at least two of them will be amongst the attendees.

@ -1,7 +1,13 @@
# On distributed unicorns and decentralization myths
# Infos
Speaker : olga from the wolga
tag : rhizom cybernetic decentralization
auth-name : olga from the wolga
tag : rhizom cybernetic decentralization
need travel fee : N
need room : N
Location : DE
# on distributed unicorns and decentralization myths
Since i started programming some hundred years ago i've had this
dream of building a totally distributed unicorn with no single points of
@ -13,7 +19,3 @@ CJDNS just wonderful unicorns? Which ways do crypto-fascisms loom and
which human agencies? How is this whole programming business entangled with
bureaucratic, cybernetic state thinking in that it tries to appropriate,
steer human living for control and profit?
need travel fee : N
need room : N
Location : DE

@ -1,13 +1,15 @@
# Federated Wiki intro & plugin workshop
# Infos
auth-name : ???
Speaker : Ksenia (changed speaker ???)
need travel fee : appreciated, if possible
need room : no
Location : UK
# Federated Wiki intro & plugin workshop
Federated Wiki is a wiki where people don't have to agree. It has a cute architecture which is a mix between a wiki and a version control.
At the venue we're planning to have a local Federated Wiki farm. Whoever is interested can learn how to set it up and use it. We would like to do an intro on the first day, and
and offer an additional workshop about building plugins for it. The author of this tool Ward only will be able to join us remotely as he's based in the US.
Intro 30min
Workshop 1h +
need travel fee : appreciated, if possible
need room : no
Location : UK

@ -1,12 +1,9 @@
# No second (life) chances
Speaker : Nick Merrill <ffff@berkeley.edu>
name : Nick Merrill <ffff@berkeley.edu>
time: 30 minutes - 1 hour depending on needs/wants
Over the course of it's beta, from 2003 to 2007, Second Life transformed in vision from a peer-to-peer market society with no hierarchies and no scarcity, to a hypercapitalist society, driven by corporate verticals and labor exploitation. How did this happen? The aim of this talk is to surface patterns in communities, cultures, and socio-technical systems that make labor ownership difficult to build and enforce. Ultimately, we look toward the question: How can we prevent the present generation of idealistic developers, bent on subverting traditional mechanisms of application and data control, from falling into the same trap as Second Life?
need travel fee : would be neded, yes, i am a student
need room : yes
Location : oakland, ca, usa
NOTE: this talk would be accepted but there currently is no funding for the required travel.
Over the course of it's beta, from 2003 to 2007, Second Life transformed in vision from a peer-to-peer market society with no hierarchies and no scarcity, to a hypercapitalist society, driven by corporate verticals and labor exploitation. How did this happen? The aim of this talk is to surface patterns in communities, cultures, and socio-technical systems that make labor ownership difficult to build and enforce. Ultimately, we look toward the question: How can we prevent the present generation of idealistic developers, bent on subverting traditional mechanisms of application and data control, from falling into the same trap as Second Life?

@ -1,15 +1,15 @@
# PC 2.0
# Infos
Speaker : Adam Ierymenko <adam.ierymenko@zerotier.com>
name : Adam Ierymenko <adam.ierymenko@zerotier.com>
time : about 1 hour
need travel fee : no (already arranged)
need room : no
Location : Los Angeles, California, USA
time : about 1 hour
# PC 2.0
This talk will be a followup to a popular blog post I made a few years ago: [Decentralization: I Want to Believe](http://adamierymenko.com/decentralization-i-want-to-believe/).
There's a so-called ["wheel of reincarnation"](http://catb.org/jargon/html/W/wheel-of-reincarnation.html) in computing in which things oscillate between centralized and decentralized paradigms. Today we are in the midst of what I call the "mainframe 2.0" era. Everyone else calls it "cloud." Here I am going to talk about what's next, about what I call "PC 2.0" and what I think it will look like and how we might get there.
I'm also going to discuss some of the reasons for centralization and why decentralization is hard. PC 2.0 is predicated on solutions to a wide array of challenges, as well as (like PC 1.0) on continued technological progress in areas like computing power, cost, and network bandwidth.
need travel fee : no (already arranged)
need room : no
Location : Los Angeles, California, USA

@ -1,10 +1,12 @@
# Peergos - Control your data!
# Infos
Speaker : ianopolous
tag : P2P crypto ipfs
auth-name: ianopolous
tag: P2P crypto ipfs
Think TrueCrypt + DropBox + BitTorrent. A secure P2P file storage and sharing network based on IPFS, fully open source.
need travel fee: no
need room: no
Location: Oxford
need travel fee : no
need room : no
Location : Oxford
# Peergos - Control your data!
Think TrueCrypt + DropBox + BitTorrent. A secure P2P file storage and sharing network based on IPFS, fully open source.

@ -1,14 +1,14 @@
# Privileged Service
# Infos
Speaker : Friedel [(@dignifiedquire)](https://github.com/dignifiedquire)
auth-name : Friedel [(@dignifiedquire)](https://github.com/dignifiedquire)
tag : privilege service web
Privilege is nothing someone should feel guilty for, it rather should remind us
of the responsibilty that we have, to profoundly serve the people around us. Extending from
this, the things we build and the way we interact with one another should reflect this responsibilty.
need travel fee : N
need room : Y
Location : Freiburg, Germany, Earth
## awaiting confirmation from friedel
# Privileged Service
Privilege is nothing someone should feel guilty for, it rather should remind us
of the responsibilty that we have, to profoundly serve the people around us. Extending from
this, the things we build and the way we interact with one another should reflect this responsibilty.

@ -1,15 +0,0 @@
# Fuck Your License: Communiques from the Copyfight
name : Knoe Won <knoe.won@sigaint.org>
time: 30 minutes - 1 hour
need travel fee : yes
need room : yes
Location : no ?
note: can only be there for the 29th
This workshop will present the myriad potentialities of unbridled data sharing emergent from non-legalist information liberation strategies. Starting off with an initial exposition of why copyleft licenses are not merely undesirable, but are in actuality far more cancerous to unbridled knowledge dissemination than copyright, the workshop will then present potential strategies for removing the various legal, technical, and cultural fetters enchaining various cultural bodies of work. In other words: how could one not only create open archives, but how can one do so safely without the possibility of adversarial reprisal? How could one integrate security considerations from the ground up to foster unimpeded data availability, irrespective of various potential impediments thereto?
NOTE: this talk need more info for us to process, it is still in flux right now.
# no answer from the speaker
Loading…
Cancel
Save