Something that strikes me as odd in addressing fake news, is that it’s almost exclusively focused on the information production and distribution. Not on the skills and strategies of the entity taking information in. Partly this is understandable, as forcing transparency on how your information might have been influenced is helpful (especially to see if what you get presented with is something others / everyone else is presented with). But otherwise it’s as if those receiving information are treated as passive consumers, not as agents in their own right.

“Our best defense against hostile influence, whatever its vector, is to invest in critical thinking skills at all levels of the population so that outlandish claims are seen for what they truly are: emotional exploitation for political or monetary gain”, wrote Nina Jankowicz on how Finnish society instills critical thinking skills.

The question of course is whether governments truly want to inoculate society, or merely want to deflect disinformation and manipulation from specific sources. Then it’s easier to understand where the focus on technology oriented solutions, or ones that presume centralised efforts come from.

In networks smartness needs to be at the endpoints, not in the core. There’s a lack of attention for the information strategies, filtering and interpreting tactics of those receiving information. Crap detection skills need to be developed for instance, and societies have a duty to self-inoculate. I think the obligation to explain* applies here too, showing others what you do and how.

Here’s a list of postings about my information habits. They’re not fixed, and currently I’m in the process of describing them again, and taking a critical look at them. What are your information habits, have you ever put them into words?

*The obligation to explain is something I’ve adopted from my friend Peter Rukavina: “The benefits of a rich, open pool of knowledge are so great that those who have learned have an obligation to share what they’ve learned.

From the recent posting on Mastodon and it currently lacking a long tail, I want to highlight a specific notion, and that’s why I am posting it here separately. This is the notion that tool usage having a long tail is a measure of distribution, and as such a proxy for networked agency. [A long tail is defined as the bottom 80% of certain things making up over 50% of a ‘market’. The 80% least sold books in the world make up more than 50% of total book sales. The 80% smallest Mastodon instances on the other hand account for less than 15% of all Mastodon users, so it’s not a long tail].

To me being able to deploy and control your own tools (both technology and methods), as a small group of connected individuals, is a source of agency, of empowerment. I call this Networked Agency, as opposed to individual agency. Networked also means that running your own tool is useful in itself, and even more useful when connected to other instances of the same tool. It is useful for me to have this blog even if I am its only reader, but my blog is even more useful to me because it creates conversations with other bloggers, it creates relationships. That ‘more useful when connected’ is why distributed technology is important. It allows you to do your own thing while being connected to the wider world, but you’re not dependent on that wider world to be able to do your own thing.

Whether a technology or method supports a distributed mode, in other words is an important feature to look for when deciding to use it or not. Another aspect is the threshold to adoption of such a tool. If it is too high, it is unlikely that people will use it, and the actual distribution will be very low, even if in theory the tools support it. Looking at the distribution of usage of a tool is then a good measure of success of a tool. Are more people using it individually or in small groups, or are more people using it in a centralised way? That is what a long tail describes: at least 50% of usage takes place in the 80% of smallest occurrences.

In June I spoke at State of the Net in Trieste, where I talked about Networked Agency. One of the issues raised there in response was about scale, as in “what you propose will never scale”. I interpreted that as a ‘centralist’ remark, and not a ‘distributed’ view, as it implied somebody specific would do the scaling. In response I wrote about the ‘invisible hand of networks‘:

“Every node in a network is a scaler, by doing something because it is of value to themselves in the moment, changes them, and by extension adding themselves to the growing number of nodes doing it. Some nodes may take a stronger interest in spreading something, convincing others to adopt something, but that’s about it. You might say the source of scaling is the invisible hand of networks.”

In part it is a pun on the ‘invisible hand of markets’, but it is also a bit of hand waving, as I don’t actually had precise notions of how that would need to work at the time of writing. Thinking about the long tail that is missing in Mastodon, and thus Mastodon not yet building the distributed social networking experience that Mastodon is intended for, allows me to make the ‘invisible hand of networks’ a bit more visible I think.

If we want to see distributed tools get more traction, that really should not come from a central entity doing the scaling. It will create counter-productive effects. Most of the Mastodon promotion comes from the first few moderators that as a consequence now run large de-facto centralised services, where 77% of all participants are housed on 0,7% (25 of over 3400) of servers. In networks smartness needs to be at the edges goes the adagium, and that means that promoting adoption needs to come from those edges, not the core, to extend the edges, to expand the frontier. In the case of Mastodon that means the outreach needs to come from the smallest instances towards their immediate environment.

Long tail forming as an adoption pattern is a good way then to see if broad distribution is being achieved.
Likely elements in promoting from the edge, that form the ‘invisible hand of networks’ doing the scaling are I suspect:

  • Show and tell, how one instance of tool has value to you, how connected instances have more value
  • Being able to explain core concepts (distribution, federation, agency) in contextually meaningful ways
  • Being able to explain how you can discover others using the same tool, that you might want to connect to
  • Lower thresholds of adoption (technically, financially, socially, intellectually)
  • Reach out to groups and people close to you (geographically, socially, intellectually), that you think would derive value from adoption. Your contextual knowledge is key to adoption.
  • Help those you reach out to set up their own tools, or if that is still too hard, ‘take them in’ and allow them the use of your own tools (so they at least can experience if it has value to them, building motivation to do it themselves)
  • Document and share all you do. In Bruce Sterling’s words: it’s not experimenting if you’re not publishing about it.

stm18
An adoption-inducing setting: Frank Meeuwsen explaining his steps in leaving online silos like Facebook, Twitter, and doing more on the open web. In our living room, during my wife’s birthday party.

Just quickly jotting some thoughts down about bookmarking, as part of a more general effort of creating an accurate current overview of my information strategies.

Currently I store all my bookmarks in Evernote, by storing the full article or pdf (not just the url, removing the risk of it being unavailable later, or behind a paywall). I sometimes add a brief annotation at the start, and may add one or more tags.

I store bookmarks to Evernote from my browser on the laptop, but also frequently from my mobile, where I pick them out of various timelines.
There are several reasons I store bookmarks.

  • I store predictions people make, to be able to revisit them later, and check on whether they came true or not.
  • I store news paper articles to preserve how certain events were depicted at the time they happened (without the historic reinterpretation that usually follows later)
  • I store pages for later reading (replacing Instapaper)
  • I store bookmarks for sharing in (collated) blogposts, or on Twitter, or to send to a specific person (‘hey, this looks like what you were looking for last week’)
  • I store bookmarks around topics I am currently interested in, as resource for later or current desk research, or for a current project.
  • I store bookmarks as reminders (‘maybe this restaurant is a place to go to sometime when next in Berlin’, ‘possible family trip’, ‘possible interesting conference to attend’)

In the past, when I still used Delicious, when it had a social networking function, I also used bookmarking for discovery of other people. Because social tools work in triangles (as I said in 2006) I would check in Delicious who else had also bookmarked something, and with which tags they did so. The larger the difference in tags (e.g. I’d tag ‘knowledge management’ and they’d tag ‘medication’) or difference in jargon (me ‘complexity’, they ‘wicked_problem’, another ‘intractable’), the likelier someone would be part of different communities than me, but focusing on the same things. Then I’d seek out their blog etc, and start following their rss feeds. It was a good way to find people based on professional interests and extend my informal learning network. A way to diversify my inputs for various topics.

Visualization of my del.icio.us bookmarks
A visualisation of Kars Alfrink’s Delicious bookmarks, based on usage of tags, 2006, CC-BY

Looking at that list of uses, I notice that it is a mixture of things that can be public, things that can be public to some, and things that are just for my eyes. I also know that I don’t like publishing single bookmarks to my blog, unless I have an extended annotation to publish with it (more a reflection or response to a link, than just bookmarking that link). Single bookmarks posted to a blog I experience as cluttering up the timeline (but they could be on a different page perhaps).
The tagging is key as a filing mechanism, and annotation can be a helpful hint to my future self why I stored it, as much as a thought or an association.

When I think of ‘bringing bookmarking home’ in the sense of using only non-silo tools and owning the data myself, several aspects are important:

  • The elements I need to store: URL, date/time stored, full article/pdf, title, tags, notes. Having a full local copy of a page or PDF is a must-have for me, you can’t rely on something being there the next time you look at an URL.
  • The things I want to be able to do with it are mostly a filtering on tags I think (connecting it to one or more persons, interests, projects, channels etc.), and then having different actions/processes tied to that filtering.
  • I’d want to have the bookmarks available offline on my laptop, as well as available for sharing across devices.
  • It would be great if there was something that would allow the social networking type of bookmarking I described, or make it possible in decentralised fashion

When I look at some of the available open source bookmarking tools that I can self-host I notice that mostly the ability to save full pages/documents and the offline functionality are missing elements. So maybe I should try and glue together something from different building blocks found elsewhere.

What do you use for bookmarking? How do you use bookmarks?

In just over a week I will be joining the Nuremberg IndieWebCamp, together with Frank Meeuwsen. As I said earlier, like Frank, I’m wondering what I could be working on, talking about, or sharing at the event. Especially as the event is set up to not just talk but also build things.

So I went through my blogpostings of the past months that concerned the indie web, and made a list of potential things. They are of varying feasibility and scope, so I can probably strike off quite a few, and should likely go for the most simple one, which could also be re-used as building block for some of the less easy options. The list contains 13 things (does that have a name, a collection of 13 things, like ‘odd dozen’ or something? Yes it does: a baker’s dozen, see comment by Ric below.). They fall into a few categories: webmention related, rss reader related, more conceptual issues, and hardware/software combinations.

  1. Getting WebMention to display the way I want, within the Sempress theme I’m using here. The creator of the theme, Matthias Pfefferle, may be present at the event. Specifically I want to get some proper quotes displayed underneath my postings, and also understand much better what webmention data is stored and where, and how to manipulate it.
  2. Building a growing list of IndieWeb sites by harvesting successful webmentions from my server logs, and publish that in a re-usable (micro-)format (so that you could slowly map the Indieweb over time)
  3. Make it much easier for myself to blog from mobile, or mail to my blog, using the MicroPub protocol, e.g. using the micropublish client.
  4. Dive into the TinyTinyRSS datastructure to better understand. First to be able to add tags to feeds (not articles), as per my wishlist for RSS reader functionality.
  5. Make basic visualisation possible on top of TinyTinyRSS database, as a step to a reading mode based on pattern detection
  6. Allow better search across TinyTinyRSS, full text, to support the reading mode of searching material around specific questions I hold
  7. Adding machine translation to TinyTinyRSS, so I can diversify my reading, and compare original to its translation on a post by post basis
  8. Visualising conversations across blogs, both for understanding the network dynamics involved and for discovery
  9. Digging up my old postings 2003-2005 about my information strategies and re-formulate them for networked agency and 2018
  10. Find a way of displaying content (not just postings, but parts of postings) limited to a specific audience, using IndieAuth.
  11. Formulate my Networked Agency principles, along the lines of the IndieWeb principles, for ‘indietech’ and ‘indiemethods’
  12. Attempt to run FreedomBone on a Raspberry Pi, as it contains a range of tools, including GnuSocial for social networking. (Don’t forget to bring a R Pi for it)
  13. Automatically harvest my Kindle highlights and notes and store them locally in a way I can re-use.

These are the options. Now I need to pick something that is actually doable with my limited coding skills, yet also challenges me to learn/do something new.

Saturday I visited the Maker Faire in Eindhoven. Jeroen of the Frysklab team invited me to come along, when their mobile FabLab was parked in our courtyard for Smart Stuff That Matters. They had arranged a touring car to take a group of librarians and educators to the Maker Faire, and invited me to join the bus ride. So I took a train to Apeldoorn and then a taxi out to a truck stop where the bus was scheduled to stop for a coffee break, and then joined them for the rest of the drive down south.

The Maker Faire was filled with all kinds of makers showing their projects, and there was a track with 30 minute slots for various talks.
It was fun to walk around, meet up with lots of people I know. Lots of projects shown seemed to lack a purpose beyond the initial fascination of technological possibilities however. There were many education oriented projects as well, and many kids happily trying their hand on them. From a networked agency point of view there were not that many projects that aimed for collective capabilities.

Some images, and a line or two of comment.

Makerfair Eindhoven
En-able, a network of volunteers printing 3d-printed prosthetics, was present. Talked to the volunteer in the image, with his steam-punk prosthetic device. They printed 18 hands and arm prosthetics for kids in the Netherlands last year, and 10 this year until now. Children need new prosthetics every 3 to 6 months, and 3d printing them saves a lot of costs and time. You even get to customise them with colors, and your favourite cartoon figure or super hero.

Makerfair Eindhoven Makerfair Eindhoven
3d printing with concrete, a project in which our local FabLab Amersfoort is involved. Didn’t get to see the printer working alas.

Makerfair Eindhoven Makerfair Eindhoven Makerfair Eindhoven
Novelty 3d printing of portraits.

Makerfair Eindhoven Makerfair Eindhoven
Building your own electronic music devices.

Makerfair Eindhoven Makerfair Eindhoven
Bringing LED-farming to your home, open source. Astroplant is an educational citizen science project, supported by ESA.

Maker Faire Eindhoven Maker Faire Eindhoven
Robot football team versus kids team. Quite a few educational projects around robotics were shown. Mostly from a university of applied sciences, but with efforts now branching out to preceding education levels. Chatted to Ronald Scheer who’s deeply involved in this (and who participated in our Smart Stuff That Matters unconference).

Maker Faire Eindhoven Maker Faire Eindhoven
A good way to showcase a wide range of Microbit projects by school children. I can see this mounted on a class room wall.

Maker Faire Eindhoven Maker Faire Eindhoven
20180929_123913
An open source 3d-printed, arduino controlled android. But what is it for? Open source robotics in general is of interest of course. There were also remote controlled robots, which were quite a lot of fun, as the video shows.

Maker Faire Eindhoven Maker Faire Eindhoven

20180929_134053

At the fringe of the event there was some steam punk going on.

Maker Faire Eindhoven Maker Faire Eindhoven
Building with card board boxes for children. Makedo is an Australian brand, and next to their kits, you can find additional tools and elements as 3d printable designs online.

Maker Faire Eindhoven
The Frysklab team presented the new Dutch language Data Detox kit, which they translated from the English version the Berlin based Tactical Tech Collective created.

I plan to dedicate some learning time in the coming 12 weeks to better understand the protocols that drive the independent web, or IndieWeb. During our STM18 birthday unconference Frank Meeuwsen presented his experiences on the IndieWeb. Frank, Peter and I have formed an impromptu triade to explore the IndieWeb in the past months. In one of his slides Frank conveniently listed the relevant protocols. I’ll plan for 24 hours to explore 6 protocols. Some of them I already understand better than others, so I’ll start with the ones I feel less knowledgeable about.

The ones I want to explore in more detail, in planned order, are:

  • ActivityPub / OStatus, a decentralized networking protocol (as this ties into my Mastodon experiments as well, this comes first)
  • Micropub, publish on your own domain with 3rd party tools
  • Microsub, own your feed-subscriptions (although I already run my own TinyTinyRss instance)
  • Microformats, markup for data, text, people, events (already used on my blog, but curious to see how I can extend that to more types of data)
  • Indieauth, federated login protocol to sign in with your own domain on other services (already active on my blog, but interested in where else I could use it)
  • Webmentions, respond to a blogpost through your own site (already active on my site, but strongly wish to better format and style it on my site)

Last week the 2nd annual Techfestival took place in Copenhagen. As part of this there was a 48 hour think tank of 150 people (the ‘Copenhagen 150‘), looking to build the Copenhagen Catalogue, as a follow-up of last year’s Copenhagen Letter of which I am a signee. Thomas, initiator of the Techfestival had invited me to join the CPH150 but I had to decline the invitation, because of previous commitments I could not reschedule. I’d have loved to contribute however, as the event’s and even more the think tank’s concerns are right at the heart of my own. My concept of networked agency and the way I think about how we should shape technology to empower people in different ways runs in parallel to how Thomas described the purpose of the CPH150 48 hour think tank at its start last week.

For me the unit of agency is the individual and a group of meaningful relationships in a specific context, a networked agency. The power to act towards meaningful results and change lies in that group, not in the individual. The technology and methods that such a group deploys need to be chosen deliberately. And those tools need to be fully within scope of the group itself. To control, alter, extend, tinker, maintain, share etc. Such tools therefore need very low adoption thresholds. Tools also need to be useful on their own, but great when federated with other instances of those tools. So that knowledge and information, learning and experimentation can flow freely, yet still can take place locally in the (temporary) absence of such wider (global) connections. Our current internet silos such as Facebook and Twitter clearly do not match this description. But most other technologies aren’t shaped along those lines either.

As Heinz remarked earlier musing about our unconference, effective practices cannot be separated from the relationships in which you live. I added that the tools (both technology and methods) likewise cannot be meaningfully separated from the practices. Just like in the relationships you cannot fully separate between the hyperlocal, the local, regional and global, due to the many interdependencies and complexity involved: what you do has wider impact, what others do and global issues express themselves in your local context too.

So the CPH150 think tank effort to create a list of principles that takes a human and her relationships as the starting point to think about how to design tools, how to create structures, institutions, networks fits right with that.

Our friend Lee Bryant has a good description of how he perceived the CPH150 think tank, and what he shared there. Read the whole thing.

Meanwhile the results are up: 150 principles called the Copenhagen Catalogue, beautifully presented. You can become signatory to those principles you deem most valuable to stick to.

Heinz Wittenbrink, who teaches content strategy at the FH Joanneum in Graz, reflected extensively on his participation in our recent Smart Stuff That Matters unconference.
We go back since 2006 (although I think we read each others blog before), when we first met at a BarCamp in Vienna. Later Heinz kindly invited me to Graz at several occasions such as the 2008 Politcamp (a barcamp on web 2.0 and political communication), and the 2012 annual conference of the Austrian association for trainers in basic education for adults.

He writes in German, and his blogpost contains a lot to unpack (also as it weaves the history of our interaction into his observations), so I thought I’d highlight and translate some quotes here. This as I find it rather compelling to read how someone, who’s been involved in and thinking about online interaction for a long time, views the event we did in the context of his and my work. And that some of what I’m trying to convey as fundamental to thinking about tools and interaction is actually coming across to others. Even if I feel that I’ve not yet hit on the most compelling way to formulate my ideas.

Heinz starts with saying he sees my approach as a very practice oriented one.
“Ton engages on a very practical level with the possibilities of combining the personal and personal relationships with the wider contexts in which one lives, from the local community to global developments. He has a technical, pragmatic and practice oriented approach. Also he can explain to others who are not part of a digital avantgarde what he does.”

And then places the birthday unconferences we did in that context, as an extension of that practice oriented approach. Something I realise I didn’t fully do myself.

“The unconference of last week is an example of how one can do things from a highly personal motivation – like meeting friends, talking about topics you’re interested in, conversing about how you shape your new daily routines after a move – and make it easy for others to connect to that. What you find or develop you don’t keep for yourself, but is made useful for others, and in turn builds on what those others do. So it’s not about developing an overarching moral claim in a small context , but about shaping and networking one’s personal life in such a way that you collectively expand your capabilities to act. Ton speaks of networked agency. Digital networking is a component of these capabilities to act, but only embedded in networks that combine people, as well as locations and technical objects.”

Speaking about the unconference he says something that really jumps out at me.

To list the themes [….of the sessions I attended…] fails to express what was special about the unconference: that you meet people or meet them again, for whom these themes are personal themes, so that they are actually talking about their lives when they talk about them. At an unconference like this one does not try to create results that can be broadcast in abstracted formulations, but through learning about different practices and discussing them, extend your own living practice and view it from new perspectives. These practices or ways of living cannot be separated from the relationships in which and with which you live, and the relationships you create or change at such an event like this.

Seeing it worded like that, that the topics we discussed, theorised about, experimented around, are very much personal topics, and in the context of personal relationships, hits me as very true. I hadn’t worded it in quite that way myself yet. This is however exactly why to me digital networks and human networks are so similar and overlapping, and why I see your immediate context of an issue, you and your meaningful relationships as the key unit of agency. That’s why you can’t separate how you act from your relationships. And why the layeredness of household, neighbourhood, city, earth is interwoven by default, just often not taken into account, especially not in the design phase of technology and projects.

Heinz then talks about blogging, and our earlier silent assumptions that novel technology would as per default create the right results. Frank’s phrasing and Heinz’s mention of the ‘original inspiration’ to blog resonate with me.

It’s probably not a coincidence that the people I had the most intensive conversations with have been blogging for a long time. They all stuck with the original inspiration to blog. Frank in his presentation called it “to publish your own unedited voice”. The openness but also the individuality expressed in this formulation was clearly visible in the entire unconference.

For me blogging was a way of thinking out loud, making a life long habit of note taking more public. The result was a huge growth in my professional peer network, and I found that learning in this networked manner accelerated enormously. Even if my imagined audience when I write is just 4 or 5 of people, and I started blogging as a personal archive/reflection tool, I kept doing it because of the relationships it helped create.

Continuing on about the early techno-optimism Heinz says about the unconference

The atmosphere at the unconference was very different. Of the certainties of the years shortly after 2000 nothing much remains. The impulses behind the fascination of yesteryear do remain however. It’s not about, or even less about technology as it was then, it’s about smart actions in themselves, and life under current conditions. It’s about challenging what is presented as unavoidable more than producing unavoidability yourself.

Only slowly I understand that technologies are much deeper embedded in social practices and can’t be separated from them. Back then I took over Ton’s concept of ‘people centered navigation’. Through the event last week it became clearer to me what this concept means: not just a ‘right’ efficient way to use tools, but a practice that for specific needs deliberately selects tools and in doing so adapts them.

People centered navigation is not a component of better more efficient mass media, but navigating information in reference to needs and capabilities of people in localised networks. Where above all the production of media and content in dialogue with a limited number of others is relevant, not its reception by the masses. Network literacies are capabilities to productively contribute to these localised networks.

Just like practice is inseparable from our relationships, our tools are inseparable from our practices. In networked agency, the selection of tools (both technology and methods) is fully determined by the context of the issue at hand and the group of relationships doing it. As I tried to convey in 2010 in my Maker Households keynote at SHiFT and indeed at the earlier mentioned keynote I gave at Heinz’s university on basic literacy in adult learning, networked literacies are tied to your personal networks. And he’s right, the original fascination is as strong as before.

Heinz finishes with adding the work of Latour to my reading list, by his last remark.

The attempt to shape your local surroundings intelligently and to consider how you can connect them in various dimensions of networks, reminds me of the localised politics in fragile networks that Bruno Latour describes in his terrestrial manifest as an alternative to the utopies and dystopies of globalisation and closed national societies. Latour describes earth as a thin layer where one can live, because one creates the right connections and maintains them. The unconference was an experiment to discover and develop such connections.

Thank you Heinz for your reflection, I’m glad you participated in this edition.

At our birthday unconference STM18 last week, Frank gave a presentation (PDF) on running your own website and social media tools separate from the commercial silos like Facebook, Twitter etc. Collected under the name IndieWeb (i.e. the independent web), this is basically what used to be the default before we welcomed the tech companies’ silos into town. The IndieWeb never went away of course, I’ve been blogging in this exact same space for 16 years now, and ran a personal website for just under a decade before that. For broader groups to take their data and their lives out of silos it requires however easy options out, and low-threshold replacement tools.

One of the silos to replace is Twitter. There are various other tools around, like Mastodon. What they have in common is that it’s not run by a single company, but anyone can run a server, and then they federate, i.e. all work together. So that if I am on server 128, and you are on server 512 our messages still arrive in the right spot.

I’ve been looking at running a Mastodon instance, or similar, myself for a while. Because yes, there are more Mastodon servers (I have accounts on mastodon.cloud and on mastodon.nl), but I know even less about who runs them and their tech skills, attitudes or values than I know about Twitter. I’ve just exchanged a big silo for a smaller one. The obvious logical endpoint of thinking about multiple instances or servers, is that instances should be individual, or based on existing groups that have some cohesion. More or less like e-mail, which also is a good analogy to think of when trying to understand Mastodon account names.

Ideally, running a Mastodon instance would be something you do yourself, and which at most has your household members in it. Or maybe you run one for a specific social context. So how easy is it, to run Mastodon myself.

Not easy.

I could deploy it on my own VPS. But maintaining a VPS is rather a lot of work. And I would need to find out if I run the right type of operating system and other packages to be able to do it. Not something for everyone, nor for me without setting aside some proper time.

Or I could spin up a Mastodon instance at Amazon’s server parks. That seems relatively easy to do, requiring a manageable list of mouse clicks. It doesn’t really fit my criteria though, even if it looks like a relatively quick way to at least have my own instance running. It would take me out of Twitter’s software silo, but not out of Amazon’s hardware silo. Everything would still be centralised on a US server, likely right next to the ones Twitter is using. Meaning I’d have more control over my own data, but not be bringing my stuff ‘home’.

Better already is something like Masto.host, run by a volunteer named Hugo Gameiro who’s based in Portugal. It provides ease of use in terms of running your own instance, which is good, but leaves open issues of control and flexibility.

So I’d like a solution that either can run on a package with my local hosting provider or figure out how to run it on cheap hardware like Raspberry Pi which can be connected to my home router. The latter one I’d prefer, but for now I am looking to learn how easy it is to do the former.

Mastodon and other similar tools like Pleroma require various system components my hosting provider isn’t providing, nor likely to be willing to provide. Like many other hosters they do have library of scripts you can automatically install with all the right dependencies and settings. In the section ‘social media’ it doesn’t mention Mastodon or any other ‘modern’ varity, but they do list GnuSocial and its predecessor StatusNet. GnuSocial is a script that uses the same protocols like Mastodon, OStatus and ActivityPub. So it should be able to communicate with Mastodon.

I installed it and created an account for myself (and myself as administrator). Then I tried to find ways to federate with Mastodon instances. The interface is rather dreadful, and none of the admin settings seemed to hint at anything that lies beyond the GnuSocial instance itself, no mention of anything like federation.

The interface of GnuSocial

However in my profile a button labelled “+remote” popped up. And through that I can connect to other people on other instances. Such as the people I am connected to on Mastodon already. I did that, and it nicely links to their profiles. But none of their messages show up in my stream. Even if it looks I can send messages to them from my GnuSocial instance as I can do things like @someotheruser, they don’t seem to arrive. So if I am indeed sending something, there’s no-one listening at the other end.

I did connect to others externally

And I can send messages to them, although they do not seem to arrive

So that leaves a number of things for next steps to explore. Also on Mastodon in conversation with Maarten I noticed that I need to express better what I’m after. Something for another posting. To be continued.

Our event meant bringing together some 45 people. They all know at least one of us two, but mostly don’t know each other. Some type of introduction is therefore useful, but you don’t want to take much time out of the day itself for it, as often intro-rounds are dreary and meaningless exercises that sap energy and of which you don’t remember much immediately after. So we’ve aimed for our events to have a first activity that is also an intro-round, but serves a bigger purpose for the event.

Previously we’ve done 1-on-1 intro conversations that also produced a hand drawn map of connections or of skills and experiences in the group, to be re-used to find the right people for subsequent sessions. We’ve done groups of 5 to 6 to create Personas, as the first step of the design process to make something yourself. This time we settled on an idea of Elmine, to do what can best be described as Anecdote Circles Lite. Anecdote circles are a process to elicit experiences and stories from a group as they reveal implicit knowledge and insights about a certain topic (PDF). You group people together and prompt them with one or more questions that ask about specific occasions that have strong feelings attached to it. Others listen and can write down what stands out for them in the anecdote shared.

The starting point of the unconference theme ‘Smart Stuff That Matters’ was our move to Amersfoort last year. It means getting to know, find your way in, and relate to a new house, a different neighbourhood, a different city. And do that in the light of what you need to fulfill your needs to be at home and feel supported in the new environment. But in a broader light you can use the same questions to take a fresh look at your own environment, and make it ‘smarter’ in being at home and feeling supported. Our opening exercise was shaped to nudge the participants along the same path.

In my opening remarks, after singing a birthday song together for Elmine, I sketched our vision for the event much as in the previous paragraph. Then I asked all participants to find 3 or 4 others that you preferrably do not know, and find a spot in the house or garden (inviting them to explore the house/garden on their own that way too, giving them permission to do so as it were). The question to prompt conversation was “Think back to the last time you moved house, and arrived in a new environment. What was most disappointing to you about your new place/live? What was pleasantly surprising to you about your new place/live?” With those questions and pen & paper everybody was off to their first conversations.

stm18

The thoughts and observations resulting from the intro-round

Judging by Peter’s description of it, it went well. It’s quoted here in full as it describes both the motivation for and the layeredness of the experience quite well. I take Peter’s words as proof the process worked as intended.

The second highlight is an event that preceded Oliver’s talk, the “icebreaker” part of the day that led things off. I have always dreaded the “everybody introduce yourself” part of meetings, especially meetings of diverse people whose lives inevitably seem much more interesting than my own; this, thankfully, was dispensed with, and instead we were prompted to gather with people we didn’t yet know and to talk about our best and worst moves in life.

What proceeded from this simple prompt was a rich discussion of what it’s like to live as an expat, how difficult it is to make friends as an adult, and the power of neighbourhood connections. Oliver and I were in a group with Heinz and Elja and Martyn, and we talked for almost an hour. I have no idea what any of the others in our group do for a living, but I know that Martyn mowed his lawn this week in preparation for a neighbourhood party, that Heinz lives in an apartment block where it’s hard to get to know his neighbours, and that Elja has lived in Hungary, the USA and Turkey, and has the most popular Dutch blog post on making friends.

During the event Elja shared her adagio that the best way to get to know people after moving to a new environment is to do something together (as opposed to just sitting down for coffee and conversation). It’s pleasantly recursive to see a statement like that as the result of a process designed to follow that adagio in the first place.

I will transscribe all the post-its and post (some of) it later.

Some images from previous activities-as-intro-rounds we used in previous editions:

IMG_6973IMG_7015

Persona creation / Using the hand drawn skills cards

Drawing the Sociogram

Drawing a map of connections, dubbed sociogram, between participants

Google Reader five years dead

Five years ago, on July 1st 2013, Google killed their Google Reader. It was then probably the most used way to keep track of websites through RSS.

RSS allows you to see the latest articles from a website, and thus makes it easier to keep track of many different blogs and sites all at once. RSS is a very important part of the plumbing of internet.

I used to read everything through RSS, but over time people migrated to FB, stopped blogging, fell silent. Services like Twitter stopped providing RSS, website owners forgot it was a standard feature. Google Reader stopping meant that many casual users stopped reading the web with RSS. Browsers stopped visibly supporting it.

Five years on, Dave Winer writes, Google Reader centralised a decentralised technology. We should have been more alert, choose an independent tool to read, and not hand it to a silo. Frank Meeuwsen says similar things, that removing the biggest RSS reader made room for new growth and variety.

Therefore:

Long Live RSS

Aral Balkan, timed with the 5th anniversary of Google Reader’s demise, blogged “Reclaiming RSS“, explaining what it does. RSS is an important part of letting the web be what it is best at, a decentralised space where all can read and write. Earlier in April Wired called for a RSS Revival as well.

How I read RSS
I interact with people, I don’t follow sites. That is how I shape and perceive my RSS reading, having all the feeds named after their authors, and grouping them in my reader roughly along my perceived social distance. From a group of people closest to me, to people I know well, not very well, to strangers whose writing I came across. Roughly following Dunbar-like group size levels. See the image below. This is because I see blogging as distributed conversations: you write something, I respond with some of my own writing. Blogposts building upon blogposts. So I set up my feedreader to reflect that conversational aspect. I use ReadKit currently, as I prefer an offline reader.


Screenshot of part of my RSS reader, in rough groups of social distance

You can find the link to my blog’s RSS feed in the right side column (with the orange icon). Any feedreader should also be able to automatically detect my blog’s feed if you point it to my web address.
I also publish which feeds I am reading. On the right hand side you see a link to ‘OPML Blogroll‘ which is a file of all the feeds I currently read that machines can read (the list is a bit out of date, but I update it every month or so). Any feed reader should be able to import that file.

In 2005 I described how I read RSS then, in response to Lee Lefever asking about people’s RSS reading routines. The current ‘grouping by social distance’ way of reading I have is the result of the search I mention at the end of that blogpost, on how to deal with a larger number of feeds.

How do you read RSS feeds?

Thirteen years on, I’m curious how you use RSS. How many feeds, what (daily) routine, what topics? How do you read RSS feeds?
I look forward to reading your take on it in my feedreader.

When Hossein Derakshan came back on-line after a 6 year absence in 2015, he was shocked to find how the once free flowing web ended up in walled gardens and silo’s. Musing about what he presented at State of the Net earlier this month, I came across Frank Meeuwsen’s posting about the IndieWeb Summit starting today in Portland (livestream on YT). That send me off on a short trip around the IndieWeb and related topics.

I came across this 2014 video of Tantek Celik. (he, Chris Messina and Andy Smith organised the first ever BarCamp in 2005, followed by a second one in Amsterdam where I met the latter two and many other fellow bloggers/techies)

In his talk he looks back at how the web got silo’d, and talks from a pure techie perspective about much the same things Hoder wrote about in 2015 and talked about this month. He places ‘peak open web’ in 2003, just before the web 2.0 silos came along. Those first silo’s (like Flickr, delicious etc) were ‘friendly silo’s’. We knew the people who built them, and we trusted their values, assumed the open web was how it was, is and would remain.

The friendly silos got sold, other less friendly silos emerged.
The silos have three things that make them hugely attractive. One ‘dark pattern’ which is adding functionality that feeds your dopamine cravings, such as like and heart buttons. The other two are where the open web is severely lacking: The seamless integration into one user interface of both reading and writing, making it very easy to respond to others that way, or add to the river of content. And the ability to find people and walk the social graph, by jumping from a friend to their list of friends and so on. The open web never got there. We had things like Qumana that tried to combine reading and writing, but it never really took off. We had FOAF but it never became easy.

So, Tantek and others set out in 2011 to promote the open web, IndieWeb, starting from those notions. Owning your data and content, and federating to participate. In his slides he briefly touches upon many small things he did, some of which I realised I could quickly adopt or do.
So I

  • added IndieAuth to my site (using the IndieAuth WP plugin), so that I can use my own website to authenticate on other services such as my user profile at IndieWeb wiki (a bit like Facebook Connect, but then from my own server).
  • added new sharing buttons to this site that don’t track you simply by being displayed (using the GDPR compliant Sharrif plugin), which includes Diaspora and Mastodon sharing buttons
  • followed Tantek’s notion of staying in control of the URLs you share, e.g. by using your own URLs such as zylstra.eu/source/apple-evernote-wordpress to redirect to my GitHub project of that name (so should GitHub be eaten alive after Microsofts take-over, you can run your own Gitnode or migrate, while the URLs stay valid).
  • decided to go to IndieWeb Camp in Nuremburg in October, together with Frank Meeuwsen

My stroll on the IndieWeb this morning leaves me with two things:

  • I really need to more deeply explore how to build loops between various services and my site, so that for all kinds of interactions my site is the actual repository of content. This likely also means making posting much easier for myself. The remaining challenge is my need to more fluidly cater to different circles of social distance / trust, layers that aren’t public but open to friends
  • The IndieWeb concept is more or less the same as what I think any technology or method should be to create networked agency: within control of the group that deploys it, useful on its own, more useful federated, and easy enough to use so my neighbours can adopt it.

A good quote from Thomas Madsen Mygdal

4 billion dollar ico yesterday.
Seen a generation and tech with big potential end up in ipo games, greed, speculation and short term thinking – “saw the beast of capitalism directly in it’s eyes” is my mental image of the dotcom bubble.
A natural consequence of any technology cycle I rationally know, but just sad to see generations repeating previous mistakes over and over.

In the comments Martin von Haller Grønbaek points to what happened after the dotcom bubble burst, a tremendous wave of innovation. So blockchain tech is set to blossom after the impending ICO crash.

I remember once reading an article that if you ask people across cultures to draw their ideal landscape they all prefer the same elements: a woodland, bordering on a grass land, in which some large animal is visible. Water flowing. And a man-made structure.

Based on conversations earlier this week I am trying to find a reference to it. But I can’t find it. I think after initial searches, the right search term is canonical landscapes.

Do you have some notion as to where I should look?

Over the years there have been several things I’ve automated in my workflow. This week it was posting from Evernote to WordPress, saving me over 60 minutes per week. Years ago I automated starting a project, which saves me about 20 minutes each time I start a new project (of whatever type), by populating my various workflow tools with the right things for it. I use Android on my phone, and my ToDo application Things is Mac only, so at some point I wrote a little script that allows me to jot down tasks on my phone that then got send to Things. As Things now can process email that has become obsolete. I have also written tiny scripts that allow me to link to Evernote notes and Things items from inside other applications.

I’m still working to create a chat based script in my terminal that takes me through my daily starting routine, as well as my daily closing routine. This to take the ‘bookkeeping’ character away, and make it easier for me to for instance track a range of lead-indicators.

I know many others, like Peter Rukavina or Frank Meeuwsen also automate stuff for themselves, and if you search online the sheer range of examples you can find is enormous. Yet, I find there is much to learn from hearing directly from others what they automate, how and why it is important to them, as the context of where something fits in their workflow is crucial information.

What are the things you automate? Apart from the the full-on techie things, like to start a new virtual server on Amazon, I mean. The more mundane day to day things in your workflow, above key board shortcuts? And have you published how you do that somewhere online?