Dear Diary (Homelab edition)

Dear Diary (Homelab edition)

7 Oct 2026

I wanted to do a dear diary post before too much more time goes past. I’ve been working on several projects that have been published, such as Activity Relay and Activity Relay Directory, and I have a couple WordPress plugins that about ready to be published as well.

With feedback from my parents, who are on a slower internet connection, I used AI to build a plugin that renders raw video into much more streaming friendly formats – the ArgentWolf Video Processor (AWVP) plugin. Version 1.0 does all of the rendering on server, so for if you are self hosted like myself, it’s nice to use your hardware to do the rendering and it doesn’t require any API tokens or subscriptions.

The next level, and continuing my efforts to explore the Fediverse (a term that refers to open, free, and distributed social media), is leveraging PeerTube. I set up a PeerTube instance at https://video.argentwolf.org, where you can check out recent videos that I’ve uploaded to the blog. PeerTube has a couple nice features, such as automatic captions, transcoding, better streaming options, and the ability to use ‘runners’ to do these jobs. Runners are clients on various computers that do a job and part of the processing, and now that we have a couple additional computers around for the kids, I’ve set up runners on their workstations, so when they are idle, which is most of the time, they can be useful for other things.

You will notice that the videos here recently are served up a bit differently. They are embedded from the PeerTube instance, and not WordPress’ native video interface. AWVP 2.0 allows me to do all my video uploads through WordPress, configure the metadata, and send it to the runners for transcoding without leaving WordPress’s editor interface. AWVP 2.0 is in the Release Candidate (RC) status right now, and as I get through my backlog of posts and test it a bit more, I expect to publish the new version soon, perhaps this weekend or next week.

Work continues on another plugin, Argent Wolf Post Notifier, which will fill a gap I have of properly notifying users of new posts, again in a proper self hosted manner without external services.

One of the annoying things about WordPress, and enabling user registration is the spam bots hammmering your site. So, time for another plugin! Argent Wolf Access Guard is designed to thwart these bot attempts. No captchas or other things necessary. So far, it has blocked nearly 1,000 attempts to create a spam account on the site. This protection also leverages my Argent Wolf Email Verification Plugin, which, if a spam account does register, it is prevented from fully activating the user until a verification email is clicked. And since they don’t use real email addresses, they never verify, and the accounts are deleted after seven days.

This will also tie into the over watch program, Argent Sentinel (not a WordPress Plugin), which can block the offending IPs at the firewall automatically on configured servers. This is a self learning and protecting methodology across all protected hosts to defend against malicious IPs/hosts.

The home network continues to grow and be refined. I have set the kids up with workstations on Ubuntu connected to a SAMBA domain controller, and leveraging ZFS, they can log into any computer and have their profile and home directory synchronized via ZFS snapshots. The practical effect is that they can go to any workstation, log in, and it is transparent to them which computer they are on, compared to my experience with Windows machines where the profiles didn’t truly roam and when you saved things on a computer, they didn’t necessarily follow you unless you saved it on your embarrassingly small network drive.

I’ve also gotten into the Minecraft hosting business. A client wanted a Minecraft server set up for their group, so I had some extra capacity on the server, and set that up for them. I also set up a family Minecraft server using Pterodactyl and Wings. Pterodactyl is the control plane and Wings are the ‘nodes’ that run the server. I put the family Minecraft server on one of the workstations, and that has been working out well. That way the kids can leverage what I set up for the infrastructure, without impacting the server. I bought the workstations bit higher spec just for this purpose.

With the software releases I’ve been doing, I make announcement posts. When the posts on the blog are reshared by my Friendica (https://friendica.argentwolf.org/profile/alan/conversations), the server gets a lot of traffic in a big burst. Friendica (and PHP) didn’t handle that so well, so yesterday I, with the help of my AI tech support, set up caching on Nginx which has greatly reduced that problem. We had to make sure that the caching only affected some of the Friendica endpoints, and not the other parts which should not be cached. This allowed me to unblock the GoToSocial clients which, for whatever reason, really liked to hammer the instance and previously caused PHP timeouts/overloads.

GitHub had an outage on their runners a while back, so not to be deterred, I now have my own Forgejo instance (a self hosted GitHub replacement), which I am slowly migrating all of the projects over to it. One of the nice things, is that like PeerTube, it uses runners to do the jobs and can take advantage of the additional available workstations to quickly process jobs in parallel and much faster than what is provided by GitHub (for free, anyway) to do the various code actions and build the packages.

I’ve also taken to making a couple tweaked docker images for Jellyfin. Jellyfin is the media server software that allows us to stream our videos and music to devices. There are two issues that have come up. One is that with a relatively large library, the SQLite version of Jellyfin tends to crash and get hung up, which is inconvenient and it only does that when I’m away and the wife needs it to work so the kids will leave her alone. Switching to the experimental PostgreSQL edition, a much more robust database back end, fixed that problem. FFMPEG, which Jellyfin uses, recently had a security vulnerability, which while fixed in newer editions of Jellyfin is still present in the operational PostgreSQL editions. So I made some images that use a fixed (I’d say patched, but we just disabled the offending codec which caused the remote code execution CVE). Then there is a bug having to do with time precision, where PostgreSQL is more precise than the SQLite version, resulting in every library scan to reflect several thousand updates when nothing actually changed. This was fixed in later editions, 12.2, but that version isn’t ready yet with the PostgreSQL integration. So I backported that fix to 10.11.11 and built an image with all the fixes. Those can be found here: https://github.com/thystra/jellyfin-security-images The awsec2 images currently have those fixes in them.

I have a couple other projects in work – a maintenance tracking app for Nextcloud and a home school management program, but those are still early. Right now I’m focusing on finishing the infrastructure build out and protective measures for the spam bots and performance tuning.

So, the work continues and I’m now working through my backlog of posts while getting through these infrastructure updates, here at the homelab of Theseus. Between the homelab, homeschool, homesteading, sports, Scouts, and other activities, dull moments are rare around here!

That’s about it for now. My journaling time is done, and I have a bunch of chores and things to do! Until next time!

Activity Relay 3.0.1 maintenance release

30 Sep 2026

Activity Relay 3.0.1 has been released to fix a couple bugs caused by invalid follower states blocking relay operation.

https://github.com/thystra/Activity-Relay/releases/tag/v3.0.1

Activity-Relay 3.0.1 is a focused reliability release for follower-state handling and relay fan-out.

Fixed

  • Prevent stale mutual-follow responses from recreating incomplete Redis follower records.
  • Validate follower state before persistence.
  • Ignore malformed persisted follower records when loading relay state.
  • Isolate invalid or unplannable delivery targets so one bad receiver cannot abort healthy fan-out.
  • Keep queue reservations and remaining-delivery counts aligned with deliveries actually planned.
  • Harden manual follower acceptance ordering.
  • Update Forgejo container/release CI for Debian Trixie’s split Docker client packages.

No configuration or data migration is required.

The 3.0.1 candidate was production-tested on relay.argentwolf.org, including real WordPress fan-out to healthy Friendica and Mastodon receivers while an independently failing receiver continued through its isolated retry path.

Container: ghcr.io/thystra/activity-relay:3.0.1

See docs/releases/v3.0.1.md and CHANGELOG.md for complete details.

The attached files are the exact canonical artifacts produced and accepted by the Forgejo release workflow.

If you find this useful, please consider leaving a tip on my Ko-Fi – https://ko-fi.com/thewolfandtheraven

Activity Relay 3.0.0 and Activity Relay Directory 1.0.0 Released!

I am pleased to announce that Activity Relay 3.0 and Activity Relay Directory 1.0 are released! This brings a conclusion to this passion project. I’ve been dabbling in the Fediverse for a while, and have, for some years, wanted to run my own relay. Of course, there were never very many good relay packages, and of what there were, were incomplete or incompatible with Friendica (or WordPress!, which was what I wanted to use as my platform of choice.

You can get them here:

https://github.com/thystra/Activity-Relay
Operational Example: https://relay.argentwolf.org

https://github.com/thystra/activity-relay-directory
Operational Example: https://directory.argentwolf.org

So, now having access to AI, I forked the Yukimochi Activity Relay and spent some time directing AI to fix and modernize the Relay software. 3.0 now supports RFC 9421 HTTP Message Signatures and RFC 9530 Digest Fields – a big thanks to @julian for turning me onto that. A docker image and a .deb package is provided. An optional front end website is also part of it, which can be disabled or otherwise configured with your own custom front end for the statistics.

The most significant addition to this is the link to Activity Relay Directory (ARD). Once I had my relay server up and running, I wanted to advertise it. I messaged the 4 or 5 current list of relays that I could find. I never heard back from any of them, if they even had a way to message them. So how does one advertise a Relay? Thus, the Directory was born.

Relay operators can opt in to have their Relay auto report to a Directory and indicate that it is up. Directory operators can set their Directory to open or closed, and no manual intervention is required. An example can be seen at https://directory.argentwolf.org. Other Relay implementations can use the Protocol to talk to the Directory Server as well.

I am also committing to maintain a list where Relay operators can find other Directories to list their Relay in.

Of course, as the human in charge, all faults are mine. So if there is an issue, please log a bug against the appropriate package. If you have an instance, I’d love to see you connect to the relay. If you host a Relay, please try the directory server.

This was something I’ve wanted for a while, and I’m happy to give back to the Fediverse community.

@alan

Activity-Relay v2.5.0 is released!

Activity-Relay v2.5.0 is now released!

  • Added signed authorized-fetch support for secure-mode Mastodon servers.
  • Improved Friendica and NodeBB interoperability while preserving the existing relay identity and public key.
  • Added reliable Redis-backed claims and recovery for interrupted work.
  • Added per-receiver retries, retained payloads, and detailed delivery diagnostics.
  • Added receiver-health tracking, Prometheus metrics, and private health/readiness endpoints.
  • Migrated to the maintained Redis-only Machinery v2 fork.
  • Published a native Debian package and multi-architecture container images for AMD64 and ARM64.

Activity-Relay Server 2.5.0 is now live at https://relay.argentwolf.org as an example server.

If you find it useful, please star it on GitHub! Thank you!

Changelog

Please help me out with connecting and testing! If you have any issues, please let me know! You can reach me at @alan, or open an issue on https://github.com/thystra/Activity-Relay

#activitypub #friendica #mastodon #fediverse #nodebb #relay #relayserver #relayservers #relaytest

Activity-Relay Server 2.5.0 RC2 pushed

Activity-Relay Server 2.5.0 RC 2 is now live at https://relay.argentwolf.org

Please help me out with connecting and testing! If you have any issues, please let me know! You can reach me at @alan, or open an issue on https://github.com/thystra/Activity-Relay

RC2 enhancements include:

  • Reliable delivery retries: Each relay fan-out target now receives one initial attempt plus five delayed retries.
  • Bounded Fibonacci backoff: Retry delays occur at approximately 8, 13, 21, 34, and 55 seconds.
  • Longer activity retention: Shared activity bodies remain in Redis for 15 minutes, covering the full retry window with additional margin.
  • Correct terminal accounting: remain_count is reduced only after successful delivery or final retry exhaustion—not after every failed attempt.
  • Protection against premature payload deletion: A temporary failure from one receiver can no longer delete the activity needed by its own retry or other pending receivers.
  • Structured delivery diagnostics: Logs now include task UUID, activity storage ID, activity/object/actor identifiers, origin domain, receiver domain, attempt number, remaining retries, and body SHA-256.
  • Delivery timing details: Each attempt records elapsed processing time and the scheduled time or delay for the next retry.
  • Improved HTTP failure evidence: Logs capture HTTP status codes, classified error types, and bounded response text from receivers, including useful errors such as 424 Failed Dependency.
  • Safer diagnostic logging: Raw activity bodies, HTTP signatures, private keys, and unbounded remote responses are not written to logs.
  • At-least-once recovery: A receiver that finishes processing after the relay times out may receive the same activity again during retry, allowing recovery from ambiguous timeout outcomes.
  • Receiver-health tracking across retries: Successful and failed attempts update per-receiver delivery statistics and consecutive-failure state.
  • Regression coverage: New tests verify retriable failure retention, successful later delivery, terminal cleanup, retry timing, metadata extraction, and bounded response handling.
  • Operational observability: RC2 supports private health, readiness, and Prometheus metrics endpoints, now enabled locally in production on 127.0.0.1:9090.
  • Preserved upgrade state: Deployment validation confirmed that the relay actor identity, private key, configuration, website settings, and all Redis logical data remained intact during the RC1-to-RC2 upgrade.

Changelog

Activity-Relay Server v2.5.0 RC1 is now live

Activity-Relay Server 2.5.0 RC 1 is now live at https://relay.argentwolf.org

Please help me out with connecting and testing! If you have any issues, please let me know! You can reach me at @alan, or open an issue on https://github.com/thystra/Activity-Relay

What’s new in Activity-Relay v2.5.0-rc1

  • Adds relay-signed actor and object fetches for Mastodon authorized-fetch and secure-mode compatibility.
  • Publishes the relay actor as an ActivityStreams Application, allowing current Friendica versions to discover and register the relay while preserving the existing actor ID, endpoints, and public key.
  • Uses a shared, exact-authority HTTP-signature implementation for both authorized fetches and outbound delivery.
  • Adds durable per-receiver delivery-health tracking through /status.json schema version 4.
  • Adds an optional private observability listener for Prometheus metrics, process health, and Redis-backed readiness checks.
  • Adds bounded Redis-backed operational metrics shared across the API and worker processes.
  • Migrates asynchronous delivery to the maintained Redis-only Machinery v2 fork.
  • Adds leased in-flight task claims and at-least-once recovery, preventing silent task loss after an abrupt worker or host failure. A duplicate delivery remains possible if the remote server accepts a request immediately before the worker terminates.
  • Preserves the existing actor key, actor address, queue data, delayed retries, configuration names, and Redis database through the tested upgrade path.
  • Includes extensive package, rollback, Redis-failure, worker-interruption, Mastodon, Friendica, NodeBB, container, race-test, and production validation.

Full RC changelog: Activity-Relay v2.5.0-rc1 changelog

Full release notes and downloads: Activity-Relay v2.5.0-rc1 release

Known limitation: NodeBB 4.14.2 may return HTTP 424 when it performs an unsigned follow-up fetch from an origin that requires signed GET requests. The relay-delivered request itself remains properly signed. (Bug Report)


If you find this project useful, please give it a star on GitHub! Any tips and/or support contributions are appreciated!

Activity-Relay server 2.4.0 released

29 July 2026

Activity-Relay server 2.4.0 is released.
Github: https://github.com/thystra/Activity-Relay

Notable changes and features:

  • Debian (.deb) and docker compose installation methods.
  • Optional Caddy example reviewed from the idea in upstream PR 60, implemented as documentation rather than a runtime dependency.
  • Standard actor outbox, followers, following, and shared-inbox metadata.
  • Friendica and standards-style server-actor follow compatibility.
  • NodeBB reciprocal follow, public-key, HTTP Host signing, and embedded Announce interoperability.
  • Public connected, receiving, and publisher status information.
  • Open signed publisher ingestion with policy enforcement.
  • Bounded queue, fan-out, remote response, and concurrency controls.
  • Multiple explicit daily-summary slots and resilient mail handling for reports to the server administrator.
  • Configurable Cache size limits in the config.yml.
  • Upgrade-safe optional website customization.
  • Native package identity preservation and inactive-by-default services.

Changelog

Future roadmap

You can see a live install at: https://relay.argentwolf.org – Please try to connect and let me know of any issues!

If you have any issues, please let me know at alan@friendica.argentwolf.org, on github, or here!

Fediverse Relay server updated

I’ve updated the relay server back end to properly support wordpress clients pushing content to the relay. If you have a server you wouldn’t mind pointing at the relay, I’d love to get some more sites on it to test it out.

The address is: https://relay.argentwolf.org

If you have any issues, please let me know at alan@friendica.argentwolf.org thanks!

If you are interested in trying the server out, you can get it here. Version 2.4.0 is in testing and will be released soon!

https://github.com/thystra/Activity-Relay