I just released v2.4.0 of Ktistec. This release encompasses a few things that I've been working on for a while: improved support for operating without JavaScript available/enabled and support for running scripted automations.

Except for a few items, Ktistec now works without JavaScript. Obviously, things like WYSIWYG editing of HTML don't work—I plan to add support for Markdown to compensate. Running in Lynx is a stretch, but...

Since the early days, most controller actions supported both text/html and application/json.  I cleaned up support for the latter and have officially documented the Ktistec API in the README.

In addition, I've added support for running bots/automations (prior announcement). The Ktistec server will periodically run any executable script in the etc/scripts directory. These scripts have access to the Ktistec API and can post, follow, share, like, etc. This is experimental and obviously introduces an attack surface, though that shouldn't be a problem on correctly configured hosts.

Here's the full changelog:

Added

• Support running scripted automations.
• "Fetch Once" button on hashtag and thread pages. (fixes #108)
• Support navigation to a post's threaded view. (fixes #108)
• Add support for post name and summary.

Fixed

• Improve support for operating without JavaScript available/enabled.
• Only enforce CSRF protection on "simple" requests.

Changed

• Replace use of multi-action controller with formaction. (fixes #101)

Other

• API usability improvements.

#ktistec #fediverse #activitypub #crystallang

for reasons i don't understand, some restarts of epiktistes result in huge memory usage spikes—reported both by the garbage collector and the operating system. what's interesting is heap size and free memory move roughly in tandem (though the difference isn't constant), which implies that there is free memory, but perhaps it's too fragmented to be useful?

a restart typically fixes the problem...

#ktistec #crystallang