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.
#crystallang 96 hashtags

After I release a new version of ktistec, I build the server commit-by-commit to see which commits increase the server executable size and build time the most. I do this because I’ve learned that small implementation details (inlined code, small methods, using blocks) can have large impacts on these numbers.
Here's the output:
Commit Size Time ======== ========== ======= ===== ======= 248850b1 36426264 10.3 47268073 36425688 -0.00% 10.5 +1.60% 344de272 36425688 +0.00% 10.8 +3.24% ef561f52 36425944 +0.00% 10.8 -0.08% 8ae2cbd4 36429128 +0.01% 10.8 -0.01% 3e425f3b 36429128 +0.00% 10.8 +0.22% 1487d903 36427704 -0.00% 11.0 +1.42% 935c9ceb 36427016 -0.00% 11.0 +0.14% de37dc6a 36427016 +0.00% 10.9 -0.97% a660a326 36427016 +0.00% 10.8 -1.12% ff3d990e 36427016 +0.00% 10.8 +0.54% 5724a58d 36523192 +0.26% 11.0 +1.78% 7b5057d4 36523640 +0.00% 11.0 -0.44% 30ca6a3f 36541352 +0.05% 11.6 +5.73% e2327eea 36671592 +0.36% 11.0 -5.36% ad0d76eb 36671592 +0.00% 10.9 -0.48% d388e74f 36671592 +0.00% 11.4 +4.59% dacea7ad 36671592 +0.00% 11.0 -3.76% 03d5dfd8 36671592 +0.00% 10.8 -1.63% 79d9d89f 36671576 -0.00% 11.0 +1.82% b65d292f 36792376 +0.33% 11.1 +0.95% 0ef53365 36808904 +0.04% 11.6 +4.88% b3766e7b 36808904 +0.00% 11.1 -4.50% 56ba79ce 36825416 +0.04% 11.1 -0.50% 4824df58 36825736 +0.00% 11.1 +0.31% c4705143 36837544 +0.03% 11.1 -0.03% e3d37ef7 36837768 +0.00% 11.5 +3.52% 4509fa0d 36837768 +0.00% 11.0 -3.83% 0ff9237b 36837768 +0.00% 11.0 -0.55%
Overall, the server executable size increased by about 1.1% and the build time increased by about 6.8%. Maybe that's not too bad for a major feature, but let's dig in.
It's nice to see that three commits account for almost all of the increase in server executable size:
But, compare 5724a58d to 8ae2cbd4 (Add `language` to `Account`). It added +22 loc but didn't increase the server executable size as much.
In any case, I'll look at e2327eea first. I'd like to understand why this relatively small change adds 130,240 bytes to the server executable size!

Ktistec release v2.4.3 supports language translation.

Inspiration for this feature comes from Mastodon.
In order to enable translation, you need an API key for either DeepL or LibreTranslate. These are the only services Ktistec supports at this time.
Posts from properly configured accounts on supported servers, like Mastodon, include the content language. On posts like these, Ktistec will display a button to translate the content if the language differs from your language.
Unfortunately, not all Fediverse/ActivityPub servers explicitly support language (I mean, Ktistec didn't until just now). And not all users correctly set their posts' language, so ymmv... but it has been hugely useful for me.
I'm going to focus on site customization next (colors, etc.).

Release v2.4.2 fixes a few more bugs. Only one is a regression—I found the others while testing. In this release:
Fixed
del, ins, and s elements in sanitized HTML.redirect_after_auth_path on browser navigation.FileUtils.mv to move uploaded files. (fixes #117)Thanks to @jayvii for help with troubleshooting the last one!

Eh, I didn't test enough and released v2.4.0 of Ktistec with a few annoying regressions. Release v2.4.1 fixes them! ☹️ 😠 😡 🤬
Fixed

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
Fixed
Changed
formaction. (fixes #101)Other

And we have a new release: Crystal 1.14.0 🚀
Read about the highlights in https://crystal-lang.org/2024/10/09/1.14.0-released/
Happy Crystalling!

have i told you all i love spectator? i love spectator!

I just released v2.3.0 of Ktistec. It fixes a few bugs introduced in the previous release. In particular, it handles a case I've observed a few times in production where the fetching of followed content hangs. The fix adds a monitor that periodically checks for "running" tasks without a backing fiber and sets socket timeouts to ensure requests eventually terminate (I believe the latter actually fixes the problem, but belts and suspenders...)
#ktistec #crystallanguage #crystallang #activitypub #fediverse

Today we celebrate the 12th anniversary of Crystal!
The initial commit was on September 4, 2012 🎉
https://github.com/crystal-lang/crystal/commit/220bb8c736381d5beda5e7bc36c8d7f0d59badf6

I just released v2.2.0 of Ktistec. A lot of code was written but the main user-visible change is streaming timeline updates to the web client using server-sent events. The back-end pub/sub framework will also make it easier to decouple some components down the road.
I want a visual indicator that new posts are in my timeline. I appreciate that not everyone feels the same way—if there's interest I may make it switchable.
And now, off to #worldcon!