From IndieWeb

Bjoern Stierand is an IndieWeb and Digital Garden enthusiast and from Nuremberg, Germany.

Björn Stierand

Hey there, I'm Björn from lovely Nuremberg/Germany.

I'm a data center management guy in my professional life. In my spare time I run a free self-hosted services for me and my family and try to establish an online presence with my website Besides that I go by the handle @egoexpress on various social networks, but apart from GitHub and Untappd I don't use those anymore.

I currently use Known for my website (and even developed some plugins for it). I was a regular participant at the Homebrew Website Club meetups in Nuremberg that Joschi Kuphal organized and I'd like to establish those meetups again anytime soon.

My personal itch

Setup a Digital Garden

My currently running website based on Known presents entries in typical blog form as a stream. This puts a lot of pressure on oneself to keep the site up-to-date and have a post on the top that is not months or even years old. I want to change this to a more relaxed and calm setup. The current plan is to ditch the Known website altogether and set up a Digital Garden based on Obsidian.


For years now I try to collect all the stuff I put on the interwebs on my own site. After some tries with a self-written script and adventures into Reclaim Social Media I used Sifttter Redux Known, an IFTTT-Dropbox-Ruby script setup I adapted to work with the Known API.

This area lays pretty dormant right now and I want to get this up running again, maybe using Obsidian as my single source of truth. If I want to publish anything, I can use my Digital Garden setup.

Having less stuff on the web

I had too many outlets on the web (2 web sites and one blog) and used too many similar web-based tools (e.g. Dropbox, Google Drive and OneDrive). I sized down to just one outlet and cut all the social networks and redundant tools I no longer needed. Also I migrated all my services to just one hoster and now run all my stuff on the same base systems (VPS with Ubuntu, every service in its own Docker container with matching docker-compose configuration). For now, I'm quite happy with the current situation in this space.