Warming up the new Microwave!

by

Wednesday, 5 August 2026

Checking on the remaining mama turkey. She has taken up residence behind our A/C compressor. I’ve been checking on her the past few days. I haven’t seen any eggs hatch, a couple have popped (gone bad). And at this point, I’m not confident any of these eggs are viable any longer.

Read more

Attic Adventures!

by

30 July 2026

Morning time, Chore time!

Checking on the mama turkey who is still sitting on an egg. She’s been pretty dedicated and made a nest in the tall grass. It was rather difficult to find her, you would not know she was there unless you walked up on her!

Garrett wanted a chess lesson. I gave him a good lesson in the basics. We used his new set that Granny sent.

I sucked it up and went back up into the attic to make some progress on the bathroom project. I found the vent for the downstairs hall bathroom, venting directly to the attic. I’ll add that to the list of things to fix.

I had left an A/C duct disconnected, so I went up to fix that. I also cleared out some insulation around the existing fan and made a hole in the ceiling, so I can access the area from the bottom. I need to rewire the fan and light on to their own circuit. Also, as you can see, it also vents directly to the attic space, so that’s my next trick, to install a roof vent and properly escape the humid air.

The heat has been crazy, but its cooled off a bit and both Meagan and I were in a bit of a funk. But we’ve been getting out of that, and now back at it with the projects!


Thanks for reading! Sign up here on the blog or on our Patreon to know when posts get published! I share these automagically to the Journey of the Wolf and Raven Facebook page if you prefer that. You can also follow me on the fediverse via @alan@www.wolfandraven.blog, or on Friendica at @alan

Activity-Relay v2.5.0 is released!

by

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

by

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

Making the cut!

by

29 July 2026

Arya has been doing try out for the last three days, being called back each time. She found out she made the middle school team! This is a big deal for her, as last year they only took two sixth graders! Quite the accomplishment for her! This also means early practices, 5 days a week. So we will see how it goes!

Congratulations, Arya!


Thanks for reading! Sign up here on the blog or on our Patreon to know when posts get published! I share these automagically to the Journey of the Wolf and Raven Facebook page if you prefer that. You can also follow me on the fediverse via @alan@www.wolfandraven.blog, or on Friendica at @alan