The Mastodon-compatible API is at a stable stopping point, so I have removed the gating with_mastodon_api build flag and made it generally available.
I use the API daily via a couple different client apps. What works, works. There are known limitations, most of them rooted in architectural differences between Mastodon and Ktistec. For example, Mastodon and Ktistec manage media differently. In Ktistec, there is no simple way to upload and manage media apart from creating a post. That difference will take some work to bridge.
Here's the full changelog for this release:
Added
/api/v1/accounts/api/v1/accounts/lookup/api/v1/accounts/:id/api/v1/accounts/:id/statuses/api/v1/accounts/:id/following/api/v1/accounts/:id/followers/api/v1/accounts/relationships/api/v1/follow_requests/api/v1/polls/:id/votes/api/v1/preferencesFixed
keyId from Signature header for inbox verification.Changed
Credit goes to this thread for inspiring me to review my signature verification. There is now one more correct implementation. 😉
The next release will focus on cleaning up the internals. Ktistec is just under 100,000 lines of code, 307 source files, and 195 spec files (7030 tests). With one maintainer, the only way to stay sane is by ruthlessly refactoring and paying down the debt!
@[email protected] tell me that when Fedify is validating an HTTP Signature you load the key identified by the `keyID`, get its `owner`, and then load the owner ActivityPub object. 🙏🏼
Time flies! It's already 5 years since the release of Crystal 1.0.
We're going to celebrate that! Meet the Core Team and community members looking back at that milestone, what happened since then, and what's coming next.
You can tag your questions with #Crystal2026AMA
Friday, 27 March 2026 16:00 UTC
Video Call: https://man.as/crystal2026ama-zoom
Live Stream: https://man.as/crystal2026ama
More info: https://forum.crystal-lang.org/t/5-years-anniversary-of-crystal-1-0/8801
Release v3.3.4 of Ktistec is available.
This release adds Mastodon-compatible client support for publishing posts. Just like the previous release, however, all Mastodon API support is behind a build flag (-Dwith_mastodon_api). It's still experimental, so opt in only if you're happy to work with rough edges.
Beyond that, I focused on cleanup and refactoring throughout the codebase. Here's the full changelog:
Added
/api/v1/statuses endpoint for status posting./api/v1/timelines/public endpoint.Fixed
Changed
npm audit, test, and caching.npm ci in Dockerfile for reproducible builds.🏋️ Mastodon API support is coming along—more in the next release!
is it the expectation that atomic should be used for all class level variables now?