This action will delete this post on this instance and on all federated instances, and it cannot be undone. Are you certain you want to delete this post?
This action will delete this post on this instance and on all federated instances, and it cannot be undone. Are you certain you want to delete this post?
This action will block this actor and hide all of their past and future posts. Are you certain you want to block this actor?
This action will block this object. Are you certain you want to block this object?
Are you sure you want to delete the OAuth client [Client Name]? This action cannot be undone and will revoke all access tokens for this client.
Are you sure you want to revoke the OAuth token [Token ID]? This action cannot be undone and will immediately revoke access for this token.
| Introduction | https://epiktistes.com/introduction |
|---|---|
| GitHub | https://github.com/toddsundsted/ktistec |
| Pronouns | he/him |
| 🌎 | Sector 001 |

today's goal: figure out what's causing these large, temporary memory spikes that don't seem to correspond to large activity spikes.


apparently i don't own any .ai domain names, so i registered ideahamster.ai because it seemed appropriate and stochasticparrot.ai was already taken.

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!

test post from tusker via Mastodon-compatible API… #ktistec

@reiver i installed vibefed. to shrink context usage at the top level, i put everything into one of three groups of skills: fediverse-detection, fediverse-protocols, or fediverse-platforms. the top level skill, in each case, is an index that links to the individual documents. starting with JSON-LD, i'm scrutinizing ktistec's implementation of core technology against your best practices.

after a long detour away from functional programming, i've swerved back and i'm studying lean.

is it the expectation that atomic should be used for all class level variables now?

I have a workflow where I “move” (cherry pick) commits from an R&D branch to the main branch and then rebase the original branch on top of main. Today I learned that this works even if the moved commits are still present on the original branch. Git detects their presence in the history and doesn’t try to add them a second time, which is what I was afraid would happen!