Sunday Serendipity Reading Links

Every day I save a bunch of links from my explorations over the interwebs. Stuff that passes my radar, may become fodder for my writing at some point, but often gets piled and forgotten.I thought maybe it is good to share some of the unsought links I encounter, and some of the notions why I bookmarked it. Blogging of course used to be linklogging, sharing links to your blog neighbourhood, so let’s say it’s returning to a respected tradition. Here are a fistful of links from this week.

    Distributed web

  • IPFS, a distributed way of delivering webpages and files. Pointed out to me in the context of my postings on distributedness and agency. Napsterizing/torrenting everything. Also seems to want to preserve everything on the web better.
  • Steem is a blockchain based social media platform. Aims to ‘pay’ you for contributing, and do the bookkeeping in a blockchain ledger. Not sure that may work, nor that permanent records of each social media utterance are desirable. Like with IPFS mentioned above, ’not forgetting’ may not be a feature but a very concerning social bug. My friend Boris Mann is trying it out, looking forward to reading more of his reflections. I may not understand, I never understood the purpose of Medium either, which superficially seems to be the same thing but without the bookkeeping.
  • Anil Dash reflects on the lost infrastructure of social media. This resonates strongly with me in terms of what made blogging so exciting 10-15 years ago, as well as with my recent writings about agency. Part of the picture is weaving a tapestry of functionality across different services and tools that together are a potent mix. It needs plumbing like RSS, trackback and discoverability over the lines of conversations distributed over the individual blogs of the participants. My friend Lilia did her Phd on those distributed conversations. And as Hoder wrote seeing the web again after six years in an Iranian prison: much of our web now, such as Facebook, is just TV, not coffee house interaction.
    Governance

  • Free private cities. Sign up to live in one, so you have an ‘equal’ position based on contracted service provision. Because tinkering with democracy and the fact that others have different needs is bothersome, or such. Apparantly the social contract isn’t good enough. This has high overtones of Snowcrash Burbclaves, and the micro-democracy states (100.000 people each, and with every election there is freedom of movement globally to pick the government (corporate, value or ethnicity based) of your choice in the very entertaining near-future SF book Infomocracy by Malka Ann Older. These private city contracts don’t seem to account for the cost of leaving if you cancel your contract, as it is still territory bound, so finding a new service provider means physically moving. With all the social and monetary cost of doing that. Also seems to me that the Principality of Monaco held up as a good practice example, incorporated US towns, or the City of London for that matter provide ample demonstration of why this may not be the way forward to a more inclusive global society.
    Effectiveness

  • The Ribbon Farm, a blog by Venkatesh Rao, newly added to my feed-reader. His recent newsletter edition on premature synchronization as a cause of problems, chimes with a lot of my experience. Converging too early (because there are just 10 minutes left in the meeting), or forcing convergence in a group doesn’t help much usually. The leading example in the link being military reminds me of an anecdote I once heard about “the world championship of armies” where the US military units were failing because they waited or tried to confirm orders continuously, and the Dutch fared better because they upon receiving others did what seemed worth doing based on context and observation, not seeking further orders and disregarding the literal meaning of orders in the process. Desyncing, as a practice seems valuable advice, and similar to making stuff distributed by design, or probe-based evolution. Seek out new perspectives and let yourself be challenged as part of your routines.

Koppelting – Session on Leaving Gmail

This weekend the grassroots FabLab conference ‘Koppelting‘ is taking place in Amersfoort, Netherlands. Together with Dirk van Vreeswijk I’ll be doing a session this morning on how to leave Gmail and other walled gardens.

In this session I try to summarize the way I constructed my path out of Gmail in such a manner that it becomes a guide that may enable others to act for themselves. The talk explains why I wanted to leave Gmail, how I finally found a way, and what the replacement solution(s) are I now use. It ends with a ‘recipe’, based on how I found a way out of Gmail, to help you think about what keeps you in your own walled gardens, so it becomes easier to explore alternatives.

Outline and slides
Setting the scene:

  • Using gmail since July 2004
  • 250.000 conversations, across 770.000 messages. 21GB total.
  • 12 years the central hub for all my personal and work e-mail

Why I wanted to leave

  • In part: everything was on US servers
  • In part: because Google with my Gmail and all other data has a very extensive profile of me
  • But most of all: Gmail was a single point of failure. Losing access would mean losing everything concerning mail communications

How I left Gmail

  • From early 2014 started seriously considering it
  • Getting to action was hard as it is extremely easy to use what you have, to stick in your routine. Ease of use keeps you locked in
  • Finding “The Alternative” seemed impossible. Until I thought about the specific aspects that made Gmail so easy for me
    • Multiple addresses into 1 inbox
    • Cross device availability
    • Great filtering and tagging
    • A generic mail address as throw away mail
    • Spam filtering
    • Large free storage space
    • Great search
  • Two core things stood out after making the list
    1. GMail makes it easy to be lazy (piling not filing). I needed to treat myself to a better process: spend a few seconds now (delete, file, delegate), to save more time on search later
    2. What made Gmail great to me in 2004, is now widely available functionality and technology

What I have now
This is described in more detail in my earlier posting that triggered this session. For each item that made Gmail attractive to me I searched for an alternative. Recombining them into a new workflow is a viable alternative for my Gmail usage as a whole. Apart from the technology replacements, key part is up front contemplation and more continuous reflection on my working process. I’m a piler, not a filer, but adding a few seconds during e-mail triage to at least decide putting it in a pile that is not my Inbox, makes all the difference.

The slides are available in PDF on this site, and will be embedded below (currently upload is failing).

Leaving a walled garden planning aid
Although the path for me leaving Gmail took quite a bit of time, I think the journey can be abstracted into a recipe to make it easier to spot your own path out of a walled garden (Gmail, Dropbox, etc.)
The basic steps are:

  1. Pick the walled garden you want to leave
  2. List all the things that make it so convenient for you
  3. Reflect on what that list tells you, about your process and your tools
  4. Find replacements for each element, then recombine them into your new workflow
  5. Share what you found and did, so it is easier for others to follow in your footsteps

The outline and collaborative notes from the session are online on one of the etherpads of the Koppelting conference.

About Koppelting
Koppel is an old Dutch word for communal fields, Ting a Germanic word for a meeting of the free. Organized by the Amersfoort FabLab, a fully opensourced bootstrapped FabLab, Koppelting is the annual grassroots festival about peer production and free/libre alternatives for society.

Germanische-ratsversammlung_1-1250x715Germanic Ting, after the Marcus Aurelius column in Rome, public domain

On Agency: Summary and My Manifesto

Now that I’ve formulated my overall perspective on Agency (part 1 on distributedness, part 2 on defining networked agency, part 3 on technology needs), this is a summary of the key points and their consequences. Half of these are general insights, condensed from what I’ve been exposed to and absorbed in the past 10-15 years or so. These points are why it matters. The novel combinations I think I contribute (marked in bold) provide the ‘how’ to that ‘why’ by delivering the agency towards increasing our agency. These points form my manifesto to act upon.

The key points in summary are:

  1. The agency deficit and potential.
    There are many issues where many people recognize they need or should find different solutions, because existing structures are failing, but do not see a viable path towards action for themselves. This is the current agency deficit. At the same time many existing tools and instruments are underused because of barriers to entry or the form in which they are currently available. This is the agency potential.
  2. The potential of distributedness.
    Distributed digital networks are similarly structured to human networks. Hierarchies and hubs superimposed on a distributed network are rigid edge cases that don’t fully use the flexibility distributed networks can provide. Human networks can more successfully use technology when the same type of flexibility and fluidity is present in the technology used. This is the path to agency.
  3. The relevant unit of agency is a person and related group in context
    The unit of agency to consider is not the individual on her own, nor a general ‘target’ group, but the combination of a person and the subset of meaningful relationships for a real and given context. Agency is networked. That way both the individual’s capabilities and perspectives as well as those of the relationships involved can be leveraged. This means that to discuss agency it needs to be done for specific contexts, and with knowledge of the relationships involved. No generic answers are possible, although examples are.
  4. Networked agency is the sum of striking power, resilience and agility
    Because your context does not exist in a vacuum but in a global network of other contexts and connections, agency is not merely about what you can do in your context (striking power), but also how you can mitigate (resilience) or leverage (agility) the consequences of things propagating to you from outside of it
  5. ‘Hard’ and ‘soft’ technology need to be always used in combination
    Methods and processes that take human networks as a given in how we act, organize and learn (community building, networking, complexity management etc), in combination with hard technology / science is the relevant scope of technology to consider. Not just ‘real’ tech. This combination is how you create the needed bridge and conduit between the digital and us humans, out of the combinations agency emerges.
  6. Technologies need to be ‘smaller’ than us, barriers lowered
    We need to seek out, recombine, or create expressions of that technology that allows the context specific user group involved to deploy, alter, and trust or control it, without barriers to entry based on money, expert knowledge, or time consumption. This often means making the technology truly distributed, such that local expressions of it are independently possible in an interdependent global network. There is a range of promising technologies on this path that however need an extra push.
  7. Reasoning from a desired specific impact, not from technology features
    It is necessary to reason from the desired impact. Issues that cannot be solved by a single individual, nor on a general level by a group or mass, but only with the active involvement of the group of people it concerns are the ones to focus on. Issues are context specific, so is impact.
  8. Making it specific creates a design aid
    Putting a (list of) specific contexts (person plus meaningful relations) at one end, and a (list of possibly) desired impact on a specific issue at the other, with the lists of potential hard and soft technologies in between, such as in the image below, can be used as thinking aid and design aid.
    It allows you to explore possibilities based on selecting varying combinations of certain technologies, or specific combinations of technologies already available in the involved context, to see how to provide agency to contexts/groups towards desired impacts. This provides agency towards creating agency.

Agency by Ton Zylstra

The Evolution and Role of My Agency Postings: Finding My Unifier

I finally wrote down the full overview of how I look at agency in our networked world, and the role of distributed technology in it, in the past weeks (part 1, part 2, part 3). It had been a long time coming. Here is a brief overview of its origins, and why it matters to me.

Origins
I previously (in the past 18-24 months) wrote down parts of it in rants I shared with others, and as a Manifesto that I wrote in January 2015 to see if I could start a hardware oriented venture with several others. I rewrote it for draft research project proposals (the image below resulted from that in June 2015) that ultimately weren’t submitted, and as a project proposal that resulted in the experiment we will start in the fall to see if we can turn it into a design method, which in itself will become an agency-inducing tool.

But the deeper origins are older, and suffused with everything I over time absorbed from my blogging network and the (un-)conference visits where those bloggers met, such as Reboot in Copenhagen. The first story I created around this was my 2008 presentation at Reboot 10, where I formulated my then thoughts on the type of attitudes, skills and tools we need in the networked age.
There I placed the new networked technology in the context of the social structures it is used in (and compared that to what came before) and what it means for people’s attitudes and skills to be able to use it in response to increased complexity. The bridge between ‘hard’ and ‘soft’ technology I mention in the three blogpostings on Agency, originates there.

The second story is my closing keynote speech at the SHiFT conference in Lisbon in 2010 (where we had to stay on a week because of the Icelandic ash cloud closing down European airspace). I blogged the submitted talk proposal, and video and slides are also available. There I talked about doing things yourself as a literacy (where literacy in the Howard Rheingold sense implies not just a skill but deploying that skill in the context of a community for it to be valuable), on the back of internet as our new infrastructure (an echo of Reboot 2008). I suggested that that socially embedded DIY was not just empowering in itself, but very necessary to deal with a complex networked world. Not just to be able to create value for yourself, but to be resilient in the face of ‘small world syndrom’ (the global networks finally making visible we live on a finite world) and cascading failures that propagate at the speed of light over our networks exposing us to things we would previously be buffered from or would have time to prepare for. I proposed the term Maker Households as the unit where DIY literacy (i.e. skills plus community) and local resilience meet, to create a new abundance based on the technical tools and methods that the networked world brings us. I was much more optimistic then how those tools and methods had already lowered the barrier to entry and merely pointed to the need to better learn to apply what is already there. I called upon the audience to use their skills and tools in the context of community, with the Maker Household as its local unit of expression. From those local units, a new global economy could grow (as the root meaning of the word economy is household).

Since then these notions have been on my mind daily but usually absorbed into every day work. I registered the domain name makerhouseholds.eu with the intention of writing up my SHiFT talk into an e-book, but never sat down to do it and let everyday life get in its way. Over time I became ever more convinced of the importance of these notions, as incumbent institutions started to crumble more and general discontent kept rising. At the same time I more strongly realized that the needed technology was failing to create more agency beyond a circle of power-users, and where broad adoption was taking place it was because key affordances were being dropped in favor of ease of use and ease of business models. Especially when I in 2014 started to explore how to make myself less dependent on tools that were providing convenience, but at the cost of exposing myself to single points of failure in what should be networked and distributed, and realized how much work it is to make the tools work for you (like maintaining your own server, or leaving Gmail). That triggered the ranting I mentioned, solidifying my conviction that Maker Households should be about packaging technology in ways that make it easy for people to increase their agency, without compromising their resilience.

Personal importance: Agency as unifier
Why this long overview? Because it seems it led me to finally finding ways to express what unifies my work of the past almost 20 years. As a kid I felt everything was connected, although everyone seemed to want put everything into discreet boxes. Internet and digitization made the connectedness all true, and I’ve been fascinated with the potential and consequences of that ever since I first went online in 1989, over 25 years ago. That unifier has however been elusive to me, even as all my work has always been about making it possible for others to better understand their situation and by using technology more purposefully act together with their peers based on their own perceptions of needs and wants. That was what drove me towards the change management side of introducing technology in groups and organizations, what drives my interest in dealing with complexity, informal learning networks, and the empowering aspects of various internet- and digitisation driven technologies such as social media, digital maker machines, and open data. That unifier has been elusive to my clients and peers often as well. I regularly have people call me saying something like “I don’t understand what it is you do, but whenever I search for things I think might help, your name comes up, so I thought I’d better call you.” Increasing agency as a unifier, from which different areas of expressing that flow, may put that confusion to rest.

Agency, as unifier, also makes the ‘menu’ below the way for me to explore additional fields and activities.

Agency by Ton Zylstra

On Agency Pt 3: Technology Needs for Increased Agency

This is the last of three postings about how I see agency in our networked era.
In part 1 I discussed how embracing the distributedness that is the core design feature of the internet needs to be an engine for agency. In part 2 I discussed how agency in the networked era is about both the individual and the immediate group she’s part of in the various contexts those groups exist, and consists of striking power, resilience and agility. In this third part I will discuss what we need to demand from our technology.

My perception of agency more or less provides the design brief for the technology that can support it.

Agency as the design brief for technology
If distributed networks are the leading metaphor for agency, then technology needs to be like that too.

If agency is located in both the individual and the social context of an immediate group the individual is functioning in for a given purpose, then technology needs to be able to support both the individual and group level, and must be trustworthy at that level.

If agency consists of local striking power, resilience, and agility, then technology must be able to take in global knowledge and perspective, but also be independently usable, and locally deployable, as well as socially replicable.

If technology isn’t really distributed, than at least it should be easy to avoid it becoming a single point of failure for your and your groups use case.

Two types of tech to consider
This applies to two forms of technology. The ‘hard’ technology, hardware and software, the stuff we usually call technology. But also the ‘soft’ technology, the way we organize ourselves, the methods we use, the attitudes we adopt.

Technology should be ‘smaller’ than us
My mental shorthand for this is that the technology must be smaller than us, if it is to provide us with agency that isn’t ultimately depending on the benevolence of some central point of authority or circumstances we cannot influence. In 2002 I described the power of social media (blogs, wiki’s etc.), when they emerged and became the backbone for me and my peer network, in exactly those terms: publishing, sharing and connecting between publishers became ‘smaller’ than us, so we could all be publishers. We could run our own outlet, and have distributed conversations over it. Over time our blog or rather our writing was supplanted, by larger blogging platforms, and by the likes of Facebook. This makes social media ‘bigger than us’ again. We don’t decide what FB shows us, breaking out of your own bubble (vital in healthy networks) becomes harder because sharing is based on pre-existing ‘friendships’ and discoverability has been removed. The erosion has been slow, but very visible, not only if you were disconnected from it for 6 years.

  • Smaller than us means it is easy enough to understand how to use the technology and has the possibility to tinker with it.
  • Smaller than us means it is cheap (in terms of time, money and effort) to deploy and to replace.
  • Smaller than us means it is as much within the scope of control/sphere of trust of the user group as possible (either you control your tools, or your node and participation in a much wider distributed whole).
  • Smaller than us means it can be deployed limited to the user group, while tapping into the global network if/when needed or valuable.

Striking power comes from the ease of understanding how to use technology in your group, the ability to tinker with it, to cheaply deploy it, and to trust or control it.
Resilience comes from being able to deploy it limited to the user group, even if the wider whole falls down temporarily, and easily replace the technology when it fails you, as well as from knowing the exact scope of your trust or control and reducing dependancy based on that.
Agility comes from being able to use the technology to keep in touch with the global network, and easily alter (tinker), replace or upgrade your technology.

Technology needs an upgrade
Most of the technology that could provide us with new agency however falls short of those demands, so currently doesn’t.

It is mostly not distributed but often centralized, or at best ‘hubs and spokes’ in nature, which introduces trust and control issues and single points of failure. Bitcoins ultimate centralization of the needed computing power in Chinese clusters is one, Facebooks full control over what it shows you is another.

It is often not easy to use or deploy, requiring strong skill sets even when it is cheap to buy or even freely available. To use Liquid Feedback decision making software for instance, you need unix admin skills to run it. To use cheap computing and sensing/actuating hardware like Arduino, you need both software and electronics skills. Technology might also still be expensive to many.

Technologies are often currently deployed either as a global thing (Facebook), or as a local thing (your local school’s activity board), where for agency local with the ability to tap into the global is key (this is part of true distributedness), as well as the ability to build the global out of the many local instances (like mesh networks, or The Things Network). Mimicking the local inside the centralized global is not good enough (your local school’s closed page on FB). We also need much more ability to make distinctions between local and global in the social sense, between social contexts.

There are many promising technologies out there, but we have to improve on them. Things need to be truly distributed whenever possible, allowing local independence inside global interdependence. Deploying something for a given individual/group and a given use needs to be plug and play, and packaging it like that will allow new demographics to adopt it.

The types of technology I apply this to
Like I said I apply this to both ‘hard’ tech, and ‘soft’ tech. But all are technologies that are currently not accessible enough and underused, but could provide agency on a much wider scale with some tweaks. Together they can provide the agency that broad swathes of people seem to crave, if only they could see what is possible just beyond their fingertips.

The ‘hard’ technologies where barriers need to come further down I am thinking about are:

  • Low cost open source hardware
  • Digital making
  • Low cost computing (devices or hosted)
  • (open) data and data-analysis
  • IoT (sensors and actuators)
  • Mesh networking
  • Algorithms
  • Machine learning
  • Blockchain
  • Energy production
  • Agrotech
  • Biotech

The ‘soft’ technologies where barriers need to come further down I am thinking about are:

  • Peer organizing, organisational structures
  • Peer sourcing
  • Open knowledge
  • Iterative processes and probing design
  • Social media / media production
  • Community building practices
  • Networked (mental) models
  • Workflow and decision making tools
  • Community currencies / exchanges
  • Hacking ethics
  • Ethics by design / Individual rights

Putting it all together gives us the design challenge
Putting the list of social contexts (Agency pt 2) alongside the lists of ‘hard’ and ‘soft’ techs, and the areas of impact these techs create agency towards, and taking distributedness (Agency pt 1) and reduced barriers as prerequisites, gives us a menu from which we can select combinations to work on.
If we take a specific combination of individuals in a social context, and we combine one or more ‘hard’ and ‘soft’ technologies while bringing barriers down, what specific impact can the group in that context create for themselves? This is the design challenge we can now give ourselves.

In the coming months, as an experiment, with a provincial library and a local FabLab, we will explore putting this into practice. With groups of neighbours in a selected city we will collect specific issues they want to address but don’t currently see the means to (using a bare bones form of participatory narrative inquiry). Together we will work to lower the barriers to technology that allows the group to act on an issue they select from that collection. A separate experiment doing the same with a primary school class is planned as well.

Agency by Ton ZylstraAgency map, click to enlarge

Let’s Encrypt the Web, For Free

Getting a SSL/TLS-certificate for your website has always been a hassle as well as costly. However increasing the amount of default encrypted web traffic is important both in terms of website safety as well as in terms of privacy (when you submit information to websites). The cost and hassle kept most non-commercial websites from using certificates however. Until now. Because now there is Let’s Encrypt, which makes it very easy to add certificates to your website. For free.

When I started using a VPS two years ago to serve as my cloud and as a Dropbox replacement, I needed a certificate to make sure the traffic to my cloud was encrypted. The VPS originally came with one, but that expired after a year. Since then I’ve added a renewing certificate from Comodo (the largest provider at the moment), which I got for a one-time payment as a lifetime service from my VPS provider. But for a range of other domains I use, both hosted on my VPS as well as in various hosting packages with a Dutch hosting provider, I never bothered getting a https certificate, because it was too much work and too expensive to keep up. There already were free certificates available, such as through the Israeli StartCom which I used for one or two domains, but I never felt certain it was secure as a service (it turns out it’s small buth 7th globally, and has received some serious criticism).

Symantec has a certificate problem...
Arranging and renewing certificates can be a pain, even if you’re Symantec, the world’s second certificate provider. (image Lars K. Jensen, CC-BY)

Let’s Encrypt changes all that. Because they are strongly community driven, amongst other with support by the Electronic Frontier Foundation, and because they are going the route of getting their root certificate independently recognized and be a full certificate authority. Currently they use IdenTrust’s (5th globally) existing trusted root certificates, but the Let’s Encrypt root certificate has now been recognized by Mozilla, and they’re working to get it recognized by Google, Apple, Microsoft, Oracle et al. This would increase the independency of Let’s Encrypt. Let’s Encrypt says the growth rate of https traffic has quadrupled since the end of 2015, in part through their efforts. Their certificates are used at over 8 million websites now.

I’ve added a range of my own sites to those 8 million. For the domains on my own VPS that didn’t have valid certificates yet, they were easy to install. I used SSLforFree to generate the Let’s Encrypt certificates, based on me providing proof I have full control over the domains I seek to protect. Then I added the certificates to the domains using the WHM control panel of my server. Certificates are valid for 90 days, but I can set them to auto-renew, although I haven’t done that yet.

For the domains not hosted on my VPS, such as this one for my blog, I depend on my Dutch hosting provider (as I don’t have root access to install certificates myself, although I have full control over the domains such as its DNS settings.) Luckily recently they have started offering auto-renewing Let’s Encrypt certificates (link in Dutch) as a free service for each of the domains you host with them, because they recognize the importance of secure web traffic. All it took was opening a ticket with them, listing the domains I was requesting certificates for. Within two hours eleven certificates were created and installed.

So, from now on you can get my blogpostings from https://zylstra.org/blog.

this blog now with https

On Agency pt. 2: The Elements of Networked Agency

Earlier this year I wrote a 1st posting of 3 about Agency, and I started with describing how a key affordance is the distributedness that internet and digitisation brings. A key affordance we don’t really fully use or realize yet.
I am convinced that embracing distributed technology and distributed methods and processes allows for an enormous increase in agency. A slightly different agency though: networked agency.

Lack of agency as poverty and powerlesness
Many people currently feel deprived of agency or even powerless in the face of the fall-out of issues originating in systems or institutions over which they have no influence. Things like the financial system and pensions, climate change impact, affordable urban housing, technology pushing the less skilled out of jobs etc. Many vaguely feel there are many things wrong or close to failing, but without an apparant personal path of action in the face of it.

In response to this feeling of being powerless or without any options to act, there is fertile ground for reactionary and populist movements, that promise a lot but are as always incapable of delivering at best and a downright con or powerplay at worst. Lashing out that way at least brings a temporary emotional relief, but beyond that is only making things worse.

In that sense creating agency is the primary radical political standpoint one can take.
Lack of agency I view as a form of poverty. It has never been easier to create contacts outside of your regular environment, it has never been easier to tap into knowledge from elsewhere. There are all kinds of technologies, initiatives and emerging groups that can provide new agency, based on those new connections and knowledge resources. But they’re often invisible, have a barrier to entry, or don’t know how to scale. It means that many suffering from agency poverty actually have a variety of options at their fingertips, but without realizing it, or without the resources (albeit time, tools, or money) to embrace it. That makes us poor, and poor people make poor choices, because other pathways are unattainable. We’re thirsty for agency, and luckily that agency is within our grasp.

Agency in the networked age is different in two ways
The agency within our grasp is however slightly different in two ways from what I think agency looked like before.

Different in what the relevant unit of agency is
The first way in which it is different is what the relevant unit of agency is.
Agency in our networked age, enabling us to confront the complexity of the issues we face, isn’t just individual agency, nor does it mean mass political mobilisation to change our institutions. Agency in a distributed and networked complex world comes from the combination of individuals and the social contexts and groupings they are part of, their meaningful relations in a context.

It sees both groups and small scale networks as well as each individual that is a node in them as the relevant units to look at. Individuals can’t address complexity, mass movements can’t address it either. But you and I within the context of our meaningful relationships around us can. Not: how can I improve my quality of life? Not: how can I change city government to improve my neighborhood? But: what can I do with my neighbours to improve my neighborhood, and through that my own quality of life?
There are many contexts imaginable where this notion of me & my relevant group simultaneously as the appropiate unit of scale to look at agency exists:

  • Me and my colleagues, me and my team
  • Me and my remote colleagues
  • Me on my street, on my block
  • Me in my part of town
  • Me and the association I am a member of
  • Me and the local exchange trading group
  • Me and my production coop
  • Me and my trading or buying coop
  • Me and my peer network(s)
  • Me and my coworking space
  • Me in an event space
  • Me and my home
  • Me in my car on the road
  • Me traveling multi-modal
  • Me and my communities of interest
  • Me and my nuclear family
  • Me and my extended (geographically distributed) family
  • Me and my dearest
  • Me and my closest friends

agency comes from both the individual and immediate group level (photo JD Hancock, CC-BY)

For each of these social contexts you can think about which impact on which issues is of value, what can be done to create that impact in a way that is ‘local’ to you and the specific social context concerned.

Different in how agency is constituted based on type of impact
Impact can come in different shades and varieties, and that is the second way in which my working definition of agency is different. Impact can be the result of striking power, where you and your social context create something constructively. Impact can take the form of resilience, where you and your social context find ways to mitigate the fall-out of events or emergencies propagating from beyond that social context. Impact can be agility, where you and your social context are able to detect, assess and anticipate emerging change and respond to it.

So agency becomes the aggregate of striking power, resilience and agility that you and your social context individually and collectively can deliver to yourself, by making use of the potential that distributedness and being networked creates.
Whether that is to strengthen local community, acting locally on global concerns, increasing resilience, leverage and share group assets, cooperatively create infrastructure, create mutual support structures, scaffold new systems, shield against broken or failing systems, in short build your own distributed and networked living.

Designing for agency
For each of those contexts and desired impacts you can think about and design the (virtual and real) spaces you need to create, the value you seek, the levels of engagement you can/should accommodate, the balancing of safety and excitement you desire, the balance you need between local network density and long distance connections for exposure to other knowledge and perspectives, the ways you want to increase the likelihood of serendipity or make space for multiple parallel experimenting, the way you deal with evolution in the social context concerned, and the rhythms you keep and facilitate.

The tools that enable agency
To be able to organize and mobilise for this, we need to tap into two types of enabling technology, that help us embrace the distributedness and connectedness I described in part 1. The ‘techie’ technology, which is comprised of hard- and software tools, and the ‘soft’ technology which consists of social processes, methods and attitudes.
What types of technologies fit that description, and what those technologies need to be like to have low enough adoption thresholds to be conducive to increased agency, is the topic of part 3.

Which City To Live and Work for a Month in 2017?

In the past years Elmine and I have visited different cities for a longer time, to experience how it is to live there. For a month, sometimes shorter, sometimes longer, we would stay in a city, and work from there, seeking out local entrepreneurs, while also enjoying the local food, coffee, and art on offer. Exposing ourselves to a different environment but not in a touristic capacity, provides inspiration, and generates new insights and ideas. We spent extended stays in Vancouver, Copenhagen, Helsinki, Berlin, Cambridge and Lucca, and are now exploring which city to set up camp in in the summer or fall of 2017. As I did in 2013 I asked around for suggestions, this time on Facebook. I got a long list of responses, which makes filtering and ultimately choosing likely a project in itself.

For us, for a city to qualify as a candidate it needs to be in Europe (as we want to drive there by car, given we are bringing our young daughter plus all the gear that entails), needs to have something to offer in terms of culture, and food, and good places to hang out in, but above all needs to have a few communities around new tech, start-ups, or other topics that we are interested in. This because we want to seek out new conversations and connections (such as when I organized the first Danish Data Drinks in Copenhagen in 2012).

Here are the (over 50!) suggestions we received, on a map:

Or see the list.

What would you like me to write more about?

Design Museum
Something to aspire to

A few years ago Elmine and I wrote a short e-book on how to organize an unconference as a birthday party (PDF linked on the right). Since then I’ve regularly entertained the idea of writing another e-book, but that never really happened. While I do have some topics I’d like to write about, I find my knowledge of those topics still too limited to be able to come up with a narrative to share anything worthwile. There are also doubts (fears?) about what type of things would have a potential readership

So this week I decided to ask:

What would you like to see me write more or more extensively about?

Already I got a range of responses, and it is an intriguing list. Some suggestions are about aspects of my own journey, others are about topics that I don’t know much (or anything) about, but where apparantly there’s interest in my take on it. Some come close to topics I already want to write more about, but feel I haven’t found an angle yet.

Here’s the list until now. More suggestions and thoughts are welcome.

  • Optimal unfamiliarity (a phrase I coined in 2004 initially to describe what mix of people make a great event audience to be part of, but has become a design principle in how I try to collect information and learn.), suggested by Piers Young
  • An epistolary travel log novella (something that could arise from my 14 years of blogging about my travels and work), suggested by Georges Labreche
  • Open currencies (which Google tells me they have no meaningful results for, but which connects to my experience with LETS, and chimes with free currencies in p2p networks), suggested by Pedro Custodio
  • Moderating sessions with a mix of analog and digital tools (closely connected to my thoughts about fruitful information strategies in social contexts), suggested by Oliver Gassner
  • Fatherhood (as I became one 9 weeks ago, but I don’t think 9 weeks counts as experience), suggested by Dries Krens
  • Motivating others to act on open data (a large chunk of my work), suggested by Gerrit Eicker
  • Being a European in the digital age (which I strongly claim to be), suggest by Alipasha Foroughi
  • Convincing profit oriented organisations of the value of open access and responsible research (comes close to Gerrit’s point), suggested by Johnny Søraker
  • How and why I left my job (being employed by Dries mentioned above), suggested by Rob Paterson
  • The journey from my involvement in knowledge management and early blogging, to where I am now, and how it impacted the way Elmine and I arrange our lives (lots to unpack here!), suggested by Jon Husband (who, like Rob Paterson, has been part and witness of that journey over many years)
  • The proliferation of means of communication versus the quality of communication (for me this points to information strategies on focus, filtering etc.), suggested by Jos Eikhout
  • Personal information strategies and processes using open source tools (something I blogged often about in various shapes and forms), suggested by Terry Frazier, a fellow blogger on knowledge management back when I started blogging in 2002

Looking at who responded is already in a way a manifestation of some of the suggested topics (the journey, the information strategies, the optimal unfamiliarity, facilitating communities).

I can’t promise I’ll write about all of the things suggested, but I appreciate the breadth and scope of this list and the feedback I can unpack from it. More suggestions are very welcome.

Archiving Mail in MySQL with MAMP and Mailsteward

As I am moving out of Gmail, I had to find a way to deal with the 21GB mail archive from the past 12 years.

Google lets you export all your data from its various services, including email. After a day or so you get a download link that contains all your mail in one single file in MBOX format.

MBOX is a text format so it allows itself to be searched, but that would only tell you that what you are looking for is somewhere in that 21GB file.

I could also import it into my mail client as a local archive, by dropping the MBOX file in the Local Folder of Thunderbird with Finder. That provides me with a similar access and search capability as I had for all that mail in Gmail. However, if I would like to do more with my archive, mine it for things, and re-use stuff by piping it into other workflows having it in Thunderbird would not be enough.

Mailsteward puts MBOX into MySQL
So I searched for a way to more radically open my archive up to search. I came across DevonThink, but that seemed a bit overkill as it does so much more than merely digesting a mail archive, and as such provides way too much overlap with my Evernote. (Although I may rethink that in the future, if I decide to also move out of Evernote, as after Gmail it is my biggest third party service that contains lots of valuable information.) I looked for something simpler, that just does what I need, putting e-mail into sql, and that is how I found Mailsteward Pro.

There are three versions of Mailsteward, and I needed the Pro version, as it is the one that works with MySQL and thus can handle the volume of mail in my archive. It costs $99 one time, not cheap, but as I was paying for storage with Google as well, over time it pays for itself.

Installing Mailsteward
When installing Mailsteward it assumes you already have a MySQL server running on your system. I use MAMP Pro on my laptop as a local web and mysql server, on which I run different things locally, like a blog based journal and a self-assessment survey tool. MAMP Pro is very easy to install.

You need to take the following steps to allow Mailsteward access to MySQL. In MAMP Pro you need to allow external access to MySQL, but only from within your own system (this basically means applications other than MAMP can access the MySQL server.

Schermafbeelding 2016-07-19 om 16.37.07

Then you create a new database via the PHP Mysqladmin that comes with MAMP. Mailsteward will populate it with the right tables. In my case I aptly named it mailarchives.

Schermafbeelding 2016-07-19 om 10.48.16

Within Mailsteward you then add a connection, listing the database you created, and adding the right ports etc. Note that the socket it requests isn’t an actual file on your system, but does need to point to the right folder within the MAMP installation, which is the Application/MAMP/tmp/mysql folder.

Schermafbeelding 2016-07-19 om 08.41.51

Importing MBOX files
I first tested Mailsteward with my parents e-mail archive that I kept after they passed away last year, to be able to find contact details of their friends. It imported fine. Then I tried to import my Gmail MBOX file. It turns out 21GB is too large to handle in one go for Mailsteward, as it eats away all memory on your Mac. I concluded that I need to split my Gmail MBOX file into multiple smaller ones.

Luckily there is a working script on GitHub that chops MBOX files up in smaller ones, and that allows you to set the filesize you want. I chopped the Gmail MBOX into 21 smaller files of 1GB each. These imported ok into MailSteward. Mailsteward maintains tags and conversation threads.

To run the script, first open it in a text editor and change the filesize limit to what you want (default is 40MB, I changed it to 1GB). Then open Terminal and run the script by typing the following command, where the destination folder does not need to exist:

sudo php mbox_splitter.php yourarchivename.mbox yourdestinationfolder

terminalcommand

That way you end up with a folder that contains all the smaller MBOX files:

Schermafbeelding 2016-07-22 om 16.06.53
Using Mailstewards import feature you then add each of those files, by hand (but luckily you only need to do that once).

Using the archive
Mailsteward allows you to search the archive through its rather simple and bland interface, but you can also tweak the MySQL queries it creates yourself. The additional advantage of having it in MySQL is that I can also access the archive with other tools to search it.

Schermafbeelding_mailsteward

Adding newer mail to the archive
Thunderbird allows me to export e-mail as MBOX files via the Import/Export add-on, which can then be added to the archive by Mailsteward. So that’s a straightforward operation. Likely I can automate it and schedule it to run every month.