Social Vacuum

November 20, 2026  |  Publishing  ·  Projects  ·  Philosophy

Picture by Anthony Hortin

Preface

On a personal level, I don’t like social media. When I could afford it, I had none at all.

That said, when you work in public and for the public good, self-isolating yourself from people using your software is not a good idea. The main problem is human nature, and it is a fundamental problem with no clear solution. Here are a few personal examples that motivated me to keep an eye on the “outside world” and participate occasionally.

A Vacuum Craves Filling

Say you created a FOSS Android app. You don’t like Google, so you choose F-Droid and direct distribution over Google Play. That’s nice, and it’s a principled choice. But by doing that, you also created a vacuum.

As your app gets more attention, people hear about it and start searching via their usual means, which you have no control over. That creates an incentive for random scumbags to impersonate your app and push it to Google Play. Sometimes they even sell features which were always free. At a minimum, they add tracking and ads.

That stuff happens all the time. Stopping it requires some unpleasant back and forth and sometimes legal threats. There is a whole breed of malicious people looking for a vacuum to fill, and it shouldn’t be disregarded.

Organic Growth Is a Myth

Or, let’s say you don’t like social media marketing, so you just hope for things to happen “organically”. That is not going to happen. You will just end up with random people impersonating your work for both financial and ego reasons.

The internet does not reward silence. It rewards whoever shows up and answers the question, even if the answer is nonsense. If the author is absent, someone else will happily speak for the project, and their goals might not align with yours.

After the Binary

The good news is that in many cases you don’t need to be terminally online and browse social media all the time. But it is crucial to follow your users, occasionally intervene, and push back on bullshit. An author’s responsibilities don’t end with making a commit or building a release binary.

The code is the beginning, not the end. After it ships, you still have to deal with impostors, takedown fights, and bug and abuse reports from a fork you never wrote.

The Social Contract

To summarize, I would prefer to stay out of social media and walled gardens, but leaving a vacuum is too dangerous.

Can’t say I don’t enjoy Twitter, for example. It is super addictive, and it is hard to control those addictions when you have to check it for project reasons. That is part of a social contract of building public things in public.

So I check in often enough to catch the nonsense early, then go back to the work. The work is public, so the conversation around it is part of the work. The vacuum always finds a way to get filled, and the only question is by whom, and with what.