This has happened before, but I thought I’d write it down this time, because it’s such a lovely story.

After a few years of quietness while I built ib1.org, a month ago I relaunched the Dgen constellation social directory. I need to note here too that Icebreaker One itself grew out of the Dgen constellation in exactly the same way as this. There’s a straight line, except it’s not really a straight line, it’s a constellation line.

Within two weeks over 60 people had reactivated, and one posted a bid in our Signal channel (thanks Matt) – within days a dozen people had expressed their interest and we had two calls, joined a briefing session with the prospect and now have an active and genuinely multidisciplinary group (banking to sound art) and a bid taking shape.

Some of the individuals coming together hadn’t seen each other for over five years (pre-lockdown) and so, of course, the majority of our calls weren’t about the work, but about catching up with each other, sharing stories and was inspiring to hear. The act of people just getting together to make things is always just lovely and we reflected that, unlike COVID, the current global sentiment is a very different shape, and carries a very different kind of weight.

On one level it doesn’t really matter what happens next, I’m just really happy that we’ve continued to build on our many-parts, loosely joined community … to find a way of getting really lovely people together to make new and unpredictable connections. Everything is all anchored on and around people who just love just doing stuff. If we win this particular commission it’d be amazing of course, but it is almost beside the point: the constellation doing what constellations do is the point. The bid is part of the constellation experiment.

The speed in which I was able to do this (I still run IB1) is supported by the tech that I’ve built very specifically around what I need, rather than someone else’s product or beholden to an enshitified product, is part of what we’re building here: tech that doesn’t enables and gets out of the way, doesn’t track or mess with our data in ways we don’t want. Part of the good side of what ai can enable is that we can all now build the tools (not the agents) we want to see in the world, rather than being someone else’s extractive product. I also have had to reflect that the nickname/handle I’ve used online for the last 20+ years (agentGav, thanks to Manu) now has a certain irony to it!

*** UPDATE *** One of our Constellation has just let me know that “One thing that emerged from the constellation is [anonymised] and I getting married. During the pandemic [anonymised] connected over a project and that’s how we met”. Oh my.

A screenshot of part of our Constellation below for reference, just to bring it to life – if you’d like to join, the link and description is here. If you’d like your own Constellation, please get in touch (yes, of course it’s open source).

Hi friends, what have you all been learning?

Many years ago (as captured in my 2017 Thread), I was trying to work out not just what everyone in my fascinating networks of friends, peers and collaborators were doing, but what knowledge they’d gathered.

When you know people over years and decades, it’s easy to lose track of what everyone has learned, what they are interested in, and what unexpected collaborations might exist as a result.

I’m often approached as someone who ‘probably knows someone who does that‘ and wanted to work out how to do that better, and to get out of the way far faster.

I wondered how to better encourage serendipity: part of this was to hold salon-like evenings on M/S Hans to bring dozens of people together in-person and see what just happened. The energy from those events got me thinking about tools that could support everyone in those quite random settings, without creating yet another social network or yet another thing that got in the way more than it helped.

Sign up now

If you’re reading this, it’s likely you already know me, so please feel free to sign up here (and note that the approval process is manual, so it won’t be instant).

Let’s connect on our skills and interests and have fun

The same challenge applies to most networking events, socials, and conferences—there’s a plethora of ‘conference apps’ that are every bit as awful as you’d imagine (Whova, Hopin, Brella et al). But how to connect communities who have ideas, collaboration and work to do together? You might remember someone who you met at an event, half-remember their organisation, might want make an introduction and you can’t quite pull the thread, and everyone’s overwhelmed with social media connections.

For example, in work settings, the usual solution is LinkedIn. However, the usual problem with LinkedIn is that it’s LinkedIn: optimised for broadcasting and monetisation not belonging, and your data is theirs the moment you post it. Most people I know who use LinkedIn to connect after a business event just use its messaging function to get to an email address and then stop using it for that. So, there’s a signal!

To start, how about we do less? (but with more fun)

cl8 is a really small thing: a directory.

I grew up in a village of about 700 people – after a while you’d kind of just know everyone’s phone number, and have a sense of what they did. And, if you rewind a few decades, the person who would definitely know that was…the local telephone operator. One of the last telephone operators was a family friend (thank you Margie Knox), and she knew everyone, everything (and more) about everyone, including how they all connected with each other.

So, can we reboot this in the 2026?

Why not just use something that already exists?

Nothing I’ve found so far quite fills this gap in this way.

I’m sure many have tried and failed (and we may too, but have more fun trying). One pattern I’m sure of though: small things can survive if they stay the right shape.

Looking at alternatives, they tend to fall into three categories: SaaS products that will likely eventually enshittify (Orbit, Luma, and Common Room already did); self-hosted tools that require a lot more faff than the challenge warrants (it needs to be as easy as possible); or shared documents (e.g. Airtable) that go stale because that’s just what happens: the utility or enthusiasm atrophies and, let’s face it, they’re just so desperately dull.

None of them seem to hold the shape of a human network, run by individuals, with communities of overlapping and transitory interests, where skills might cluster and gaps are plentiful. And, of course, all of them involve handing your member data to a platform with rights that seek to keep them, rather than keeping users in control.

I wanted something lightweight enough to actually run myself, curated enough to stay useful, and honest about what it is: more of a social directory rather than a social network. Yes, also looking back to where a lot of social networks began (looking at you, Well), and re-asking if the incentives to ‘keep growing’ were the wrong solutions, and for the wrong reasons (looking at you, FB, Tw*t, Ning, and the rest of you).

On words

cl8 is a compression of “constellation” or “constellate” (as a verb), the name I use for communities of practice, and the (astronomical) language that threads through a lot of my projects.

A constellation isn’t a random scatter of points, it’s more like a pattern that becomes legible when you can work out how to read it. The points were always there: a constellation is what happens when you impose meaning on proximity and cl8 is, perhaps, a type of social telescope. The people were already in the room, more or less: the tool just makes connections visible. Less stuff, more fun.

What it does

You sign in with Google or a verified email, fill in your name, a short bio, and tag yourself with your skills and interests. Ideally not job titles, but rather the things you’d say to someone when meeting them at one of my salon evenings on the boat.

It’s a searchable, private directory where your profile is visible only to other authenticated members of that cl8 instance. Access is granted by whoever runs that community: human curation is part of the design.

It can run on your own server, your community controls the membership, and your data is yours. I’ve built it for my dgen network constellation (you can sign up at d.cl8.io and as its curator it may take me a little while to manually approve you). The first instance is also running for IB1 (Icebreaker One), which is exactly the point: one tool, many communities, each owning their own. You can sign up for that one at ib1.org/constellation.

And yes, you’ll hopefully find some things in all of this that surprise and delight: it’s the start of a journey to doing things differently. It should be fun, so adding in things for your specific, quirky, bonkers community is up to you. Less faff, more fun.

What it doesn’t do

It doesn’t

• reveal any information about you to anyone that you don’t want to share (see https://d.cl8.io/privacy)
• track you (no cookies)
• create more noise in the world

On building it

cl8 is a just few hundred KB of code: a single Node.js file with zero npm dependencies. It mirrors the same architecture as Broadside: copy the file to a server, configure, start a service, done. The data lives in flat JSON. The whole thing was built with AI assistance in the same spirit as the other tools in this stack: it’s been something I’ve wanted for years, and AI has helped me build it in about the same time as it would have taken to evaluate and customise any SaaS alternatives and then sign up for none of them.

It’s meant to be the absolute minimum. A social directory for a few hundred people doesn’t need a database cluster, it does need good session management, solid authentication and security, and enough care in the UI to make filling in your profile feel like something other than homework. Less code, more fun.

If you run a community of practice and you’re tired of it living inside someone else’s product, ping me. It’s open licence, deployable in under an hour, and then the only person looking after your community’s data is you (and them).

A self-hosted social posting tool, ensuring you own your own content

In my ongoing experiments with ai-assisted dev of tools I’d like, I’ve create Broadside to solve a specific irritation. As we all know, “If you aren’t paying for the product, you are the product.” and as all these tools develop their own special enshittifications, it feels like it’s time to have another go at inverting the models.

Also, with the demise of that old-bird-site, things have become more federated and fragmented. I wanted to post across Mastodon, Bluesky, Threads and LinkedIn at the same time, and do so without ‘losing’ what I’d written the moment I hit publish.

Broadside it a small web app that posts to all four simultaneously, keeps a searchable archive of everything locally, and pulls social feeds into one place, including creating useful open things, like an RSS feed. This post is about why I made it, what it does, and the slightly eccentric vocabulary it uses.

You can read all my posts here: https://broadside.dgen.net/bindery/gavin

If you’d like to try it, just ping me (on any channel).

You probably didn’t know LinkedIn is a one-way street

If you post to LinkedIn regularly, you’re building a professional record in a place you cannot back up. They do not let you download your own posts in bulk – the “account data export” doesn’t include posts. You can use their API to POST to the site, but not GET your own content back (without paying).

For the platform most associated with professional credibility where people are documenting their work, sharing hard-won thinking, and announcing things that matter to them, to offer no way to retrieve what you’ve put there is, to be generous, unprofessional.

The same applies across many platforms, to varying degrees and I’ve maintained this website (dgen.net) to be both a business site and a master record of my own works, that I completely control. With music I am addressing a version of this by building a tool to convert my Spotify playlists into a physical record catalogue, because streaming solved discovery but not ‘ownership’. Social media has the same shape: it solved distribution but not possession. Broadside is an attempt to do something about that.

And, yes, of course there are loads of self-publishing tools, but they’re often commercialised into their own SaaS businesses with similar issues of enshittification (looking at you TweetDeck/HootSuite), or too ‘techy’ to actually do yourself. Alternative services, like Mastodon are great but also directly compete with, rather than replace the production flow.

What Broadside does

Broadside runs on my own server (you can host your own too, once I get it on GitHub, open licence of course), and it supports multiple users (so I can enable my constellations and communities to use it for free). It connects social accounts, enables a post to be written in a single compose window, and it posts simultaneously to whichever platforms you select (Mastodon, Bluesky, Threads, LinkedIn, or any combination. Note that Facebook and others don’t allow connections like this). Link previews, image attachments and scheduled posts all work.

It also is keep a copy.

Before anything goes to a social platform, it’s written to an archive on my server. That archive is searchable and downloadable. If any other platform disappears, your posts don’t (nb: if my/your server vanishes, you have backups everywhere else you’ve posted). If you want to find what you said about something three years ago, you can. This useful to me – having a personal, searchable archive of all my public writing is just nice, independently of the cross-posting convenience.

There’s also a feed view, pulling in my Mastodon and Bluesky feeds together into one place (NB: LinkedIn and Threads don’t allow this, and Facebook doesn’t allow anything).

With added AI?

I added an AI-assisted research tool that automatically surfaces related links (e.g. Wikipedia, academic papers, Guardian articles, Hacker News discussions and things I’m experimenting with) for anything I post. This last bit genuinely surprised me with how useful it can be by lowering the ‘friction’ in then googling for references – in an age of fake news, it’s nice to filter on some diverse-yet-trusted sources. The whole thing was built with Claude and, like my other experiments is stuff I wanted but would never have had time to build a decade ago.

And, a white-listed constellation?

Of course, once you’ve got a publishing tool that works well, you can share it with your friends. And then you have something that’s bot-free, curated (h/t haddock), and more akin to the original idea of shared bookmarking and socials. Back to basics, without the tracking (no, really tracking, like LinkedIn scanning all your browser extensions to fingerprint your machine and track you is actually a thing, never mind cookies).

All while not having to switch away from, or shut down, places you like to hangout with other friends and colleagues.

You can probably guess where I might go next with this: not leaving places, but rather connecting them.

On words

Those who know me already know I love finding fun words (e.g. Icebreaker One, AMEE, Tornado) to make using things just feel good. And, of course, design matters deeply to all of this so I’m experimenting with letting people choose their own themes. We love to personalise things.

Note that while I’m using ai for these prototypes, a quick plug for my friends at philpottdesign.com, just because ;).

I’ve given Broadside its own vocabulary because I think it’s more interesting than calling things “dashboard” and “feed”.

Broadside: historically, this is a large sheet printed on one side and distributed as news, proclamations, or verse – one of the original one-to-many formats. It felt right for a tool that takes one piece of writing and to many public spaces at once. Obviously, given my interest in things nautical, broadside is also when all the guns on one side of a warship are fired simultaneously… so quite apt!

The Murmurator: the compose interface. A murmuration is what you see when a flock of starlings moves as one coherent shape. Social media can feel a bit like that and The Murmurator is where you introduce something into the flow.

Murmurings: your own incoming feeds from the people you follow, across the networks.

The Bindery: your personal post archive. The Bindery refers to “a studio, workshop or factory where sheets of (usually) paper are fastened together to make books” [wikipedia] so felt apt for where your own posts are gathered, ordered, and made publicly accessible by default (as a public web page and RSS feed).

Commonplace: As I add people from my constellation into our shared Broadside instance, the Commonplace is our collective archive: everything everyone has posted, in one place (as a public web page and RSS feed). (originally I used Sammelband a German word for a ‘volume that binds together separately published works’ but that was getting a bit too esoteric, even for me).

Addenda: re-establishing control

Stepping aside from all the stupid AI-hype, I think we’re at a fascinating juncture that reminds me of the 1990s early web. The same AI tools that vast platform players are racing to deploy to bind us to them, are equally available to all of us.

We can all now build personalised infrastructure, in hours or days, that would have taken dedicated teams many months or years before. Broadside is an example of this: a small act of reclaiming your relationship with your own writing, from the platforms you publish on and can control.

If we can’t build things for everyone, it won’t work for all of us.

To quote NTK, “THEY STOLE OUR REVOLUTION. NOW WE’RE STEALING IT BACK”