Like everyone in the world working from home during the pandemic, we saw a sudden switch to intensive use of video conferencing for the past eight weeks.
Daily stand-ups with clients, coffee chats with colleagues, meetings, on and on, up to the point you feel you’re only in video calls the entire day. It was such a sudden increase that it now feels suddenly odd to have an actual phone call, without video.

I want to jot down some of our experiences with various video conferencing tools these past weeks, and how it compares to ‘before’. It’s a good thing meanwhile to keep in mind that phones, sms, mail etc also still exist.

One of the first things that stood out for my company at the start of the lock down was that while we did have regular video conferences previously, we didn’t host them ourselves. It was mostly at the invitation of clients or others, using their solutions such as Webex, and Skype for business. Amongst ourselves we used Skype, but usually made regular phone calls. Within my World Bank projects we used Skype as well.

Our cloud tool, NextCloud offers NextCloud Talk, supported with a STUN and a TURN server. We tested this and it works reasonably well for up to 4 people. Our first experiences were however not convincing enough to want to use it for larger groups or as a default for client interaction. We did however use it with one client reliably with 3 to 4 people.

Next to our existing NextCloud we added Zoom, with 4 hosts. Zoom works very well, also with a few dozen participants, and we have been using it for our own all-hands meetings, weekly check-ins and daily coffee times. We also used Zoom for an online workshop, including the use of break-out rooms and that worked very well. Zoom however has been the subject of a lot of privacy and data security criticism, which have only in part been addressed. Various clients of ours do not allow Zoom. Specifically the use of the Zoom client is seen as problematic, some do allow their people participating in a Zoom call through their browser.

Meanwhile our clients operating within the Microsoft silo speeded up their switch to Microsoft Teams, which meant that our interaction with them takes place through Teams’ video conferencing. This for us reduced the need for being the host of a range of meetings, and our need for Zoom.

Still we wanted another video conferencing option for ourselves, that supports larger groups, and is within our own scope of control. We arranged for a managed Jitsi server for our company’s use. This at first glance looked like it might be an expensive solution (as it meant a bespoke service as no regular hosting offers were to be found), but in the end our existing cloud hoster provided us with our own Jitsi server geared to use for larger groups against low costs. Our experiences with Jitsi are somewhat mixed. It works best if everyone is on Chrome browsers, but that in itself is not really desirable nor even easy to ask of every participant. Jitsi does not allow for scheduling or planning a call, as you can only login as a host after starting a call. Jitsi also does not support break out rooms, nor is it on the current development agenda it seems. We’ve used Jitsi reliably in various settings, both with others and amongst ourselves, including a group of 8 people from different organisations. In that case being able to offer to use Jitsi on our own server made the call possible in the first place, as several participants were adamant about not wanting to use other tools such as Zoom.

So the current reality is that we use Nextcloud Talk, Jitsi, Teams, Zoom all in parallel, depending on context and participants, while we also still participate in Hangouts, Webex and Skype for Business meetings. The only thing that has seen a reduction of use is regular phone calls, which upon reflection is an odd effect, as no-one set out to replace or try to improve upon those. Maybe it’s because all the video conferencing tools bring the conversations into the device you have in front of you working from home all day anyway: your computer screen.

The Britsh Museum is chock full of fascinating artefacts, even if the sourcing of some of those artefacts means their ownership of them is disputed. While that sourcing happened in different times perhaps (which doesn’t mean our current perspective can’t be different), in these times echoes of that can be heard in the form of digital appropriation.

Earlier this week the British Museum announced they had revamped their website. Part of the revamp is providing more and better digital images of artefacts. Digitising artefacts well is a lot of work and effort, and making them available to the public is very laudable. Especially as the British Museum says, since we’re now only capable of visiting from home.

Director Hartwig Fischer in the museum’s communication is quoted saying

We hope that these important objects can provide inspiration, reflection or even just quiet moments of distraction during this difficult time

Inspiration, cool. Let’s do. Jason Kottke wrote about it and posted some beautiful images.
I went to the BM’s site as well and browsed. Then I came across this artefact:

Screenshot of the British Museum showing a 1725 etching, with copyright claim

I didn’t know the British Museum had a print of the water gates in my hometown!

Then I noticed an oddity: a ‘(c) Trustees of the British Museum’ statement on it. I have the image (remixed with a Mondriaan painting, by E after my idea) on my wall. This as the etching by A. Rademaker is also in the collection of the Rijksmuseum, and they too have digitised their collection and made it available. At the Rijksmuseum that image however is public domain.

The British Museum also allows downloading images. For ‘my’ image at least that download is of distinctly lower resolution than the Rijksmuseum download (the BM’s download is 365Kb, the Rijks’ 2.8MB). Here you see them side by side, BM on the left, Rijks on the right.

‘high-ish’ res BM image on the left, higher res Rijks image on the right

Moving on from inspiration to reflection then, as per the director’s words: What’s up with that copyright claim? The etching itself, being from the 18th century, is clearly in the public domain. Are they saying making a photo of an artefact is creating a new copyright? As Cory Doctorow also noted, that is a wild claim to make. Making a photo of an artefact to show just that artefact is not considered a creative act, and thus not protected under copyright rules, in the UK (PDF) and the EU.

The actual licensing terms attached by the British Museum to a downloaded image are Creative Commons BY NC SA, meaning only non-commercial use is allowed, if the results are shared under the same conditions and the British Museum is mentioned as the source. This is not an open license. It means that Jason Kottke who, inspired as hoped by the BM’s director, put images on his site is in breach of this license, as he also sollicits membership payments through his blog. Appropriate would be a CC0 license, or public domain mark. Claiming copyright on an image that actually is in the public domain because its subject matter is in the public domain on the other hand is digital appropriation.

A second question is why would the British Museum do this? A clue is the information shown when you want to download an image:

BM allows download for non-commercial use, but for commercial use requires a request

The distinction between commercial and non-commercial forms of use, I suspect, may have something to do with the effort of digitisation. Digitisation is generally very costly. Museums fall under the EU PSI Directive on the re-use of public information. In that Directive a possibility exists to temporarily make the exploitation of digitised material exclusive to a certain party as reward for help with the digitisation. Under this exemption tech companies can enter into agreements with museums and libraries to digitise their collections and have a handful of years before the results become generally available to the public. The fact that the BM publishes some images for the general public, at lower quality, is another potential clue. It’s my speculation, but it may mean that the BM tries to provide at least some publicly available material, while the exclusive exploitation rights for whoever is paying for the digitisation still exist. In other countries we’ve seen that material isn’t published until those rights expire, and it would indeed be a useful step to find a way of providing at least some access.

However, none of that has any relation to copyright, as the digitisation itself does not create new rights to license. It would I think better be solved by providing lower quality material as public domain material, while higher quality material is made available as part of the exclusive exploitation deal. If this is what is happening, again it’s just my assumption, using a restrictive CC license is the wrong instrument. If it has nothing to do with the digitisation process and surrounding contracts, but only to create revenue for the museum, then using Creative Commons licenses to do so is just plain wrong and digital appropriation that should be corrected.

Het NRC meldt dat er een spoedwet komt om de noodmaatregelen tegen de pandemie juridisch beter te borgen. Na een korte uitwisseling (via Mastodon) met Remkus de Vries hierover, schrijf ik mijn gedachten er bij maar eens uit.

Tot nu toe gold ‘nood breekt wet’: de momenteel afgekondigde maatregelen zijn bij wijze van noodverordening ingevoerd. Daarin staan dingen die strijdig zijn met de grondwet (zoals samenkomstverboden) en verschillende rechten in de praktijk opschorten. Dergelijke noodverordeningen zijn door de 25 veiligheidsregio’s ingesteld, onder coördinatie van ministeries. De veiligheidsregio’s worden bestuurd door de burgemeesters van de gemeenten in die regio, en zij zijn het die de verordeningen invoeren. Ik heb een aantal van die verordeningen gelezen, en hoewel er wel doelbinding in staat (de verordening is direct gekoppeld aan de pandemie), stond er geen einddatum in. Daarnaast is er geen parlementaire controle op deze gang van zaken, want langs die weg komt het niet tot stand. Verder maakte ik me niet heel veel zorgen over die noodverordeningen, juist omdat het de ongeveer 400 burgemeesters zijn die het instellen. Zoveel anti-democraten staan er niet tegelijk op in ons land, en als er maar een enkeling daarvan publiekelijk zijn steun terugtrekt valt het geheel vanzelf in duigen.

De nieuwe wet moet nu de noodverordeningen gaan vervangen. Dat is op zich logisch, die verordeningen zijn bedoeld voor de korte termijn tijdens een acute crisis. In die eerste chaotische fase houd je rekening met verschillende mogelijkheden, zo waren er in 2000 na de vuurwerkramp bij ons in Enschede het eerste weekend blokkades op de snelwegen om ramptoerisme te voorkomen, en staan sinds het begin van de pandemie mariniers stand-by in Doorn om binnen 6 of 12 uur ingezet te worden voor het bewaken van de openbare orde.
Na een eerste vaak wat chaotische fase ontstaat er een nieuw plateau waarin je voor de middellange termijn de boel moet regelen. Van acute crisis naar langere uitzonderlijke situatie. Dan is er behoefte aan stabielere regels en onderbouwing daarvan, omdat de medewerking en het vertrouwen van ons als burgers anders terecht afnemen naarmate de tijd vordert. Die fase is nu duidelijk aangebroken, de eerste piek van de epidemie in ons land wordt langzaam gepasseerd, en het is helder dat totdat er een vaccin of behandeling is, danwel we allemaal het virus gehad hebben, we rondom het evenwichtspunt maatregelen moeten op- en afschalen om te zorgen dat het zorgsysteem kan blijven functioneren. Die periode duurt nog wel een jaar, of misschien wel twee. Er wordt gekozen voor een nieuwe wet, in plaats van een nu al wel mogelijk zwaarder middel, het verkondigen van de noodtoestand. Dat zwaardere middel is door zijn zwaarte ook ongerichter, en de steun er voor zal eveneens snel afbrokkelen als men die noodtoestand niet om zich ook zo voelt zoals in de eerste chaos van een crisis.

Die nieuwe wet wordt nu aangekondigd als tijdelijk en gericht op de pandemie. Maar de ervaring leert dat wat als tijdelijk wordt aangekondigd en gestart lang niet altijd tijdelijk blijft. De ervaring leert ook dat een langzaam kruipende scope, leidend tot het gebruik van regelingen voor doeleinden waarvoor die regelingen niet tot stand zijn gebracht, niet ongebruikelijk is (anti-terreurwetgeving is er een mondiaal voorbeeld van).

In complexe situaties kun je weinig voorzien, ervaring van eerder heeft geen voorspellende waarde voor de toekomst. Daarom zijn heldere grenzen en waarden noodzakelijk. Dat doe je voor kinderverjaardagsfeestjes (niet van de oprit af! blijf met je tengels uit de drankkast! niet met schoenen aan naar binnen rennen!), en dat moeten we ook doen voor een spoedwet als deze. Dat het een spoedwet is wil niet zeggen dat het ok is om je principiële afwegingen opzij te zetten, omdat je denkt dat je dat later wel kunt repareren. Juist andersom, bij een spoedwet moet je zeer strikt zijn met je voorwaarden, zodat je daarbinnen bewegingsruimte hebt om situationeel te schakelen naar wat nodig is. (Dat zagen we afgelopen weken ook met de Corona-apps. Daar werden principiële uitgangspunten opgesteld, maar vervolgens niet gehanteerd bij het filteren van kandidaten. Dan krijg je “Ja privacy heel belangrijk, dat lossen we straks wel op”, met als gevolg dat geen van de uiteindelijk voorgestelde apps door de beugel kon. Dat had je ook kunnen weten voor de ‘appathon’ begon, bij die allereerste filtering omdat je daar je uitgangspunten al losliet.)

Wat mij betreft zijn lakmoesproeven voor een spoedwet*:

  • De wet is gekoppeld aan de Corona epidemie. De wet kan niet worden gebruikt voor zaken die niet bijdragen aan de bestrijding van de epidemie. Elke getroffen maatregel op basis van deze wet moet gemotiveerd worden op basis van de epidemie.
  • Er staat een einddatum in de wet, waarop deze zijn geldigheid verliest. Alleen aangeven dat het een ‘tijdelijke’ wet betreft is niet genoeg. Een einddatum is nodig.
  • Die einddatum is dichterbij gesteld dan dat we nu denken dat de pandemie duurt. Dus niet over 2 jaren, maar over maximaal een paar maanden.
  • De wet kan alleen worden verlengd als het parlement voor verlenging stemt onder vaststelling van een nieuwe einddatum die wederom hooguit enkele maanden in de toekomst ligt.
  • Naast een einddatum waarop de wet zonder verlenging buiten kracht raakt, is ook opgenomen wat de maximale termijn is waarna verlenging door het parlement niet meer mogelijk is. Daarmee is gegarandeerd dat vooraf bekend is wanneer de wet uiterlijk buiten werking treedt.
  • Het is niet voldoende dat het parlement niet tegen verlenging gestemd heeft. Het parlement moet voor verlenging stemmen. Als er geen stemming plaats heeft gevonden bijvoorbeeld dan vervalt de wet op de dan geldende door het parlement vastgestelde einddatum.
  • De wet geeft een limitatieve opsomming van onder de wet mogelijke maatregelen die grondwettelijke rechten geheel of gedeeltelijk opschorten. Wat niet in die opsomming staat is niet mogelijk als maatregel. Het parlement kan bij verlenging de limitatieve opsomming inkorten.
  • De maatregelen worden alsnog via verordeningen in de veiligheidsregio’s, met de zelfde einddatum als de wet, van kracht. Die verordeningen bevatten de motivatie voor de inzet van elke specifieke maatregel. Dit maakt regionale variatie mogelijk, en dwingt tot motivatie van maatregelen in regionale context. Wat nuttig is voor Noord-Brabant is dat wellicht niet voor Friesland. Wat passend is voor de kust of de Amsterdamse binnenstad is dat niet automatisch ook voor de Drentse hei of het grensgebied met Duitsland. En vice versa.
  • Burgers staat de gang naar de rechter vrij om de toepassing van een maatregel en de motivatie daarvoor op basis van het eerste uitgangspunt te laten beoordelen.
  • De nationale ombudsman is daarnaast aangewezen voor het ontvangen van klachten over de inzet van maatregelen, en doet verslag daarover aan het Parlement en het algemeen publiek op zijn minst voor elke stemming over verlenging of zoveel vaker als de ombudsman daar het belang van ziet. De overheid voert gedurende de looptijd van de wet actief campagne om mensen op de mogelijkheid tot klachten indienen te wijzen. De aantallen ontvangen klachten en de aard van de klachten worden doorlopend actief openbaar gemaakt door de ombudsman. De spoedwet mag niet de werking van artikel 78a van de Grondwet inperken (die de ombudsman en andere Hoge Colleges van Staat regelt).
  • De wet stelt niets over benodige of gewenste dataverzameling, noch stelt het het algemeen belang van openbaarheid buiten werking of ter discussie. Integendeel, de wet eist actieve openbaarmaking door betrokken overheden van alle documentaire informatie die betrekking heeft op de ten uitvoerlegging van de spoedwet. Het bijzondere karakter van de wet maakt actieve volledige transparantie van het gebruik van die wet noodzakelijk.

Met dergelijke voorwaarden maakt nood met meer waarschijnlijkheid een redelijke wet, en breekt de nood niets onvervangbaars.

Ik vertrouw er op dat de liberale premier niet genegen zal zijn om het werk van Thorbecke ongedaan te maken. Maar er zitten meerdere anti-democraten in het parlement, en er komen verkiezingen. Het is riskant om op enig moment uit gevoelde nood ambigue wetten aan te nemen zonder op voorhand een uiterste houdbaarheidsdatum, andere harde grenzen en volledige transparantie over het gebruik van de wet daarin vast te leggen.

Zodra het wetsontwerp naar de Tweede Kamer gaat zullen we zien of het kabinet op zoek is naar een voldoende stevig hek, of alleen lippendienst bewijst aan tijdelijkheid en proportionaliteit.

*Ik ben geen jurist. De opsomming is dus een mening, ongeacht wat wel en niet mogelijk is in ons wetgevingsproces. De opsomming is gebaseerd op omgang met complexiteit: het trekken van zo duidelijk mogelijke grenzen, die nodig zijn om in een complexe situatie te kunnen handelen. Naast duidelijk, moeten die grenzen proportioneel zijn en eenmaal geplaatst absoluut (als je een paard in een weiland wil houden zet je een hek om het weiland, niet om de polder waarin het weiland ligt, en niet willekeurig op verschillende plekken midden in het weiland.). Met die grenzen mag niet gemarchandeerd worden (Als het hek eenmaal om het juiste weiland staat verplaats je het niet), want dat leidt van complexiteit snel terug naar chaos, in plaats van naar meer voorspelbare stabiliteit op termijn.

Yesterday I participated in, or more accurately listened in on, a IndieWeb conversation on wikis and their relationship to blogs (session notes).

I didn’t feel like saying much so kept quiet, other than at the start during a (too long) intro round where I described how I’ve looked at and used wiki personally in the past. That past is almost as long as this blog is old. Blogs and wikis were to me the original social software tools.

  • Between 2004 and 2010 I kept a wiki as the main screen on my desktop, sort of like how I used The Brain in years before that. In it I kept conversation notes, kept track of who’s who in the projects I worked on etc. This after a gap in turn got replaced by Evernote in 201210
  • Between 2004 and 2013 I had a public wiki alongside this blog (first WakkaWiki, then WikkaWiki). In those years at one or two points I recreated it from scratch after particular intensive waves of automated spam and vandalism
  • Between 2004 and 2010 I had a wiki covering all the BlogWalk Salons I co-organised from 2004-2008
  • I had a script that let me crosspost from this blog to the wiki alongside it, so I could potentially rework it there. I don’t think that happened much really.
  • At one point I glued blogs, wiki and forum software together as a ‘Patchwork Portal‘ for a group I worked with. Elmine and presented about this together on BlogTalk Reloaded in 2006, showing the co-evolution of a budding community of practice and the patchwork portal as the group’s toolset. Afterwards it was used for a while in a ‘wiki on a stick’ project for education material by one of the group’s members.
  • Two years ago I re-added a wiki style section of sorts to this blog. As I’m the only one editing anyway, I simply use WordPress pages, as when I’m logged in everything has an edit button already. The purpose is to have a place for more static content, so I can refer to notions or overviews more easily, and don’t need to provide people with a range of various blogposts and let them dig out my meaning by themselves. In practice it is a rather empty wiki, consisting mostly of lists of blogposts, much less of content. A plus is that Webmentions work on my pages too, so bidirectional links between my and someone else’s blog and my wiki are easy.
  • With clients and colleagues over the years I’ve used Atlassian as a collaborative tool, and once created a wiki for a client that contained their organisation’s glossary. Current items were not editable, but showed sections directly below that which were. Colleagues could add remarks, examples and propose new terms, and from that periodically the glossary would be changed.

Stock versus flow, gardening and streams
Neil Mather, who has a really intriguing wiki as commonplace book since last fall, mentioned he writes ‘stream first’. This stock (wiki) and flow (blog) perspective is an important one in personal knowledge management. Zettelkasten tools and e.g. Tiddlywiki focus on singular thoughts, crumbs of content as building block, and as such fall somewhere in between that stock and flow notion, as blogging is often a river of these crumbs (bookmarks, likes, an image, a quote etc.) Others mentioned that they blogged as a result of working in their wiki, so the flow originated in the stock. This likely fits when blog posts are articles more than short posts. One of the participants said his blog used to show the things from his wiki he marked as public (which is the flip side of how I used to push blog posts to the wiki if they were marked ‘wikify’).
Another participant mentioned she thinks of blogs as having a ‘first published’ date, and wiki items a ‘last edited’ date. This was a useful remark to me, as that last edited date in combination with e.g. tags or topics, provides a good way to figure out where gardening might be in order.
Ultimately blogs and wikis are not either stock or flow to me but can do both. Wikis also create streams, through recent changes feeds etc. Over the years I had many RSS feeds in my reader alerting me to changes in wikis. I feel both hemmed in by how my blog in its setup puts flow above stock, and how a wiki assumes stock more than flow. But that can all be altered. In the end it’s all just a database, putting different emphasis on different pivots for navigation and exploration.

Capturing crumbs, Zettelkasten
I often struggle with the assumed path of small elements to slightly more reworked content to articles. It smacks of the DIKW pyramid which has no theoretical or practical merit in my eyes. Starting from small crumbs doesn’t work for me as most thoughts are not crumbs but rather like Gestalts. Not that stuff is born from my mind as a fully grown and armed Athena, but notes, ideas and thoughts are mostly not a single thing but a constellation of notions, examples, existing connections and intuited connections. In those constellations, the connections and relations are a key piece for me to express. In wiki those connections are links, but while still key, they are less tangible, not treated as actual content and not annotated. Teasing out the crumbs of such a constellation routinely constitutes a lot of overhead I feel, and to me the primary interest is in those small or big constellations, not the crumbs. The only exception to this is having a way of visualising links between crumbs, based on how wiki pages link to each other, because such visualisations may point to novel constellations for me, emerging from the collection and jumble of stuff in the wiki. That I think is powerful.

Personal and public material
During the conversation I realised that I don’t really have a clear mental image of my wiki section. I refer to it as my personal wiki, but my imagined readership does not include me and only consists of ‘others’. I think that is precisely what feels off with it.
I run a webserver on my laptop, and on it I have a locally hosted blog where very infrequently I write some personal stuff (e.g. I kept a log there in the final weeks of my father’s life) or stream of consciousness style stuff. In my still never meaningfully acted upon notion of leaving Evernote a personal blog/wiki combo for note taking, bookmarking etc might be useful. Also for logging things. One of the remarks that got my interest was the notion of starting a daily note in which over the course of the day you log stuff, and that is then available to later mine for additional expansion, linking and branching off more wiki-items.

A question that came up for me, musing about the conversation is what it is I am trying to automate or reduce friction for? If I am trying to automate curation (getting from crumbs to articles automagically) then that would be undesirable. Only I should curate, as it is my learning and agency that is involved. Having sensemaking aids that surface patterns, visualise links etc would be very helpful. Also in terms of timelines, and in terms of shifting vocabulary (tags) for similar content.

First follow-ups

  • I think I need to return to my 2005 thinking about information strategies, specifically at the collecting, filtering stage and the actions that result from it. and look again at how my blog and wiki can play a bigger role for currently underveloped steps.
  • Playing more purposefully with how I tie the local blog on my laptop to the publlic one sounds like a good experiment.
  • Using logging as a starting point for personal notetaking is an easy experiment to start (I see various other obvious starting points, such as bookmarks or conversations that play that role in my Evernotes currently). Logging also is a good notion for things like the garden and other stuff around the home. I remember how my grandmother kept daily notes about various things, groceries bought, deliveries received, harvest brought in. Her cupboard full of notebooks as a corpus likely would have been a socio-economic research treasure

Tom Critchlow last week wrote about a decentralised format for shareable bookshelves he came up with. I like the concept, it’s like the FOAF of old but for books, BOAF maybe? Like he mentions in the updates, while providing JSON is probably more fitting technology for the now, there is a world of RSS and OPML out there that might mean a more ready made environment. After all RSS can have very different payloads, as podcasting shows.

I’ve been writing here every now and then since a year or so about (not all of) the books I read. Like Tom says, there’s no getting around the dominance of Goodread and its owner Amazon, other than doing something yourself. I started writing here about my reading, not for the first time in the past two decades, precisely because I don’t want to add my effort to Goodreads. Although I do post affiliate links to Amazon here, as there is not reliable other way to link to books so that it makes sense for most readers. No way to dynamically link a book to your ‘local’ bookstore. Maybe I should just stop doing that, linking to Amazon. People can search a book in their own preferred way easily enough.

RSVPed Attending Gardens and Streams: Wikis, blogs, and UI — a pop up IndieWebCamp session

This sounds like a good conversation to have. I have been and am experimenting with the blog / wiki combination basically since the start of this blog. And I dislike the disconnect between that and my note taking system, as well as the always manual creation of wiki content (though I used to have a script that pushed blog content to the wiki for further evolution way back in 2004)