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.

@alexanderadam works!
macro ✂️(str, n)
{{str}}.size > {{n}} ? {{str}}[0, {{n}} - 1] + "…" : {{str}}
end
puts ✂️ "hello, world!", 3 # => "he…"
TIL
The … (the Unicode ellipsis character) works as both a Crystal Language macro and method name, as in:
macro …(str, n)
Ktistec::Util.render_as_text_and_truncate({{str}}, {{n}})
endWhich can be used in a view template as:
= … preview, 120
I'm not saying you should. I'm saying you can.

There are two big features in release v3.1.3 of Ktistec: auto-approve followers and a new image viewer.
Auto-approve followers is conceptually simple ("the server automatically sends an Accept activity when it receives a Follow activity") but it required extensive changes to some of the oldest code in the codebase: the inboxes and outboxes controllers. I refactored inbox and outbox side-effect processing into independent services, which made it possible to support side-effects like auto-approve follow (and also auto-follow back), without having to go through the controllers.
A more significant change for me personally was replacing the lightGallery image gallery (an external dependency) with my own implementation. It's not as slick, and not as full of features—I wrote it in two days—but it is fully free software, and that's important to me.
Added
Fixed
Changed
The OAuth changes set the groundwork for better support of the Mastodon API and the Fediverse clients that depend on it. Stay tuned!

I'm working on federation issues.
👻 Release v3.1.2 of Ktistec improves support for Lemmy and community servers like it that distribute content by wrapping it in Announce activities (FEP-1b12: Group federation support). Ktistec also supports the audience property, although support for that was removed from Lemmy earlier this year.
🎃 This release also adds support for delivering to shared inboxes, which are widely supported by other ActivityPub servers. Despite being federated, the Fediverse is not highly distributed, and this optimization can reduce outbound delivery traffic by 10-20x.
Added
Dislike activity.audience property on activities and objects.Fixed
Announce activities.Changed
Enjoy!

Vacations are wonderful. It is a privilege to be able to travel without worry. It's also wonderful to be home, and to have the time to work on projects I care about. With those thoughts in mind, I present release v3.1.1 of Ktistec, an ActivityPub server written in the Crystal programming language!
This release is a mixed bag of small features and improvements:
Added
Fixed
everything collection.HTTP::Client instances are closed.I added support for multiple users at the beginning of the month. I'm very interested in feedback on how that's working out for anyone using it.


We're reaching for the stars! 🚀✨
Just as 1.18 is released, over 20k users have starred the Crystal repo on GitHub 🌟

This release of Ktistec merges the main_3.x branch into the main branch.
Managing two branches, and two releases, was a lot of work. And sometimes changes were lost in the shuffle, like:
Added
I have about a dozen more features and fixes that are ready for the next release, but to keep things simple, I'm doing the merge first, in its own commit.

Release v2.4.16 of Ktistec... because I forgot to include some critical code in v2.4.15... namely, the menu.
Changed
If you're not planning on adding additional users, you don't need to update!

Experimental support for multiple users landed with Ktistec release v2.4.15. "Experimental" means that it works for me, but hasn't seen enough testing for me to call it "ready for production". With that said, it's unlikely you'll lose your data.
There are lots of intentional design decisions that fit my vision for Ktistec but may surprise you. Here they are:
Every user is an administrator. That doesn't mean users have access to each other's posts and data, but it does mean all users have access to the shared parts of the site—they can change the site description, for example—and they can add new users. So only add people you trust.
If you want to add another user, create an account for them and give them their username and password. There is no self-registration. There are no invitations.
Beyond adding a user, there is no support for user management. You can't even boot a user from your site. Users can delete themselves, however.
There is no support for content moderation. Only add people you trust.
TL;DR Multi-user support in Ktistec is suitable for small teams, families (biological or chosen), and your personal avatars. There are better tools for online communities.
Here's the full set of changes:
Added
Fixed
