Trader implementation: appear regularly at the tavern selling materials for crafting.
Adventurers implementation: Have a quest and can be booked into rooms. When the embark on a quest after their stay.
Reworked items: previously I had an enum to distinguish between different items. This would become infeasible once I start adding more items. Rework to have a generic item struct.
Reworked recipes: similar to items, each recipe is now a struct. The recipe defines the ingredient requirements and a function to generate the resulting item.
Implementing scheduled publishing with #ActivityPub requires some effort. Until now my blog only had draft/published as states of entries. The AP service would just send out the requires requests immediately. With the possibility of setting the publishing date into the future this is no longer possible. I have to somehow trigger these after the publishing date.
Pull systems are so much easier than push systems.
I've built an #ActivityPub integration for my blog. Likes, boosts and replies are also shown below blog posts. Together with #webmention it serves as the comment/feedback mechanism for my blog.