Despite the holidays, we’ve been busy.

1. What we shipped

We migrated our front-facing website (kanka.io) from Netlifly to Cloudflare. We’ve consistently had multiple issues with Netlifly’s hosting, leading to us wasting a lot of time fixing non-issues. This doesn’t impact app.kanka.io, just the “what’s Kanka and why it’s the best collaborative worldbuilding tool in existence” website.

The new campaign-wide connections graph got a handy little “Save (PNG)” button, suggested by a user in Discord, so that you can quickly export the whole graph to use in other tools or offline.

2. What we’re working on next

We’ve disabled inactive account purging and are thinking of better ways to still allow for inactive, “just tested Kanka” accounts from not filling up our database servers. We’ll make announcements when those changes go live.

We are also working on allowing characters to have multiple locations, similar to how custom modules and some other modules has that feature. Currently, each module has it’s own system, but we want to merge it into a singular module, so that we aren’t repeatedly making our lives more difficult. This is a huge refactoring effort.

3. Behind the scenes

On the 25h of December, 8:43pm México time, I started getting hundreds of alerts that something with Kanka was wrong. Turns out the database servers were filling themselves up with logs due to a config mismatch between the main and replica servers. My script to catch a 90% full disk didn’t trigger (something to figure out sooner rather than later). Thanks Santa!

---

Hopefully you enjoyed this little peek at what we’re working on. We plan to keep these short but frequent. If you want even more tea on upcoming updates, consider joining our Discord.