Home | Notifications | New Note | Local | Federated | Search | Logout

xz@xz@ebadf.port0.org

Hello again, another attempt at the Fediverse. Please don't expect anything of this account - or me in general. So far, I haven't even chosen a profile picture.

Unix, OpenBSD, Linux, Plan 9 curious, Go, C, awk, {,k,z}sh, low tech, riding my bike, and touching grass.


Languages: DE,EN
Location: Germany
Pronouns: he/him
Joined: 2026-05-22 15:42:54
1 notes, 0 following, 0 followers

xz@xz@ebadf.port0.org (2026-05-21 18:09:00)
One annoyance with my small #snac instance - or any small Fediverse island regardless of the software - is the missing visibility of the rest of the network. For followed hashtags, I am missing out on most posts as I am not federating with most instances.

The usual solution is to use an ActivityPub relay. This, however, resulted in receiving looots of posts, hitting file size and inode limits on this small VM. Thus, I gave up this experiment a while ago.

Now, I just stumbled about https://relay.fedi.buzz/ from @astro@c3d2.social, which allows to only follow certain hashtags, which is kinda exactly what I wanted ❤️

After following the Subscribing to Fediverse Relays section from snac(8), I came up with the following jq(1) command to subscribe each hashtag I am already following on my #snac instance. And yes, this would be way faster to do by hand for those six hashtags in total.

$ # Create multiple snac follow commands for each hashtag the "xz"
$ # user follows. The "data" directory is the $SNAC_BASEDIR.
$ jq -j \
  '.followed_hashtags.[] | "snac follow data relay https://relay.fedi.buzz/tag/",.[1:],"; "' \
  < data/user/xz/user.json
snac follow data relay https://relay.fedi.buzz/tag/openbsd; snac follow data relay https://relay.fedi.buzz/tag/snac; [ . . . ]

If the generated commands are looking not suspicious enough, rerun the command within $() or execute the output manually.

Finally, I am able to doomscroll #biketooter for weird and ridiculously expensive bikes from my instance; yay!