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.
Epiktistes is my home in the Fediverse. It is an instance of Ktistec, a single-user ActivityPub server like Mastodon, but with fewer users and fewer commits. Here's my introduction (last updated early-2025).
I wrote a series of posts about optimizing the performance of the Ktistec server, its build time, and its executable size: part 1, part 2, part 3, part 4, and part 5.
Some things I regularly write about, organized by hashtag:
I also wrote some #pointfreeverse.
SUPERHOT was short and sweet.
that’s not how i was supposed to say it…
aaaaand i've tagged the v1.0.0 release of ktistec! 🎉 🎊 🥂
the last push was for greater compatibility with other fediverse servers—it took quite a bit of yak-shaving to get it done.
i also released a docker image if you want to try it out:
docker run --rm -it -p 3000:3000 toddsundsted/ktistec:latest
enjoy!
support indy artists!
i've tested ktistec compatibility with:
many things work—follows in both directions and creating/updating notes (AKA toots, etc.)—but there's lots of room for improvement. lemmy, for example, announces activities instead of forwards activities. i'm working on 1.0, but in the next major release, i'll build server-specific extensions to handle more of these kind of issues.
i created a few issues in other repos:
and worked around a few issues that haven't quite rolled out:
and made many other concessions for compatibility.
once you've seen one activitypub implementation, you've seen one activitypub implementation.
i just wrapped up a whole lot of interoperability work for ktistec. bottom line, you can't just read and implement the activitypub spec et al and expect anything to federate with your implementation. your best bet, in fact, is to doggedly copy the mastodon implementation, right down to the braces and brackets—since every other implementation is at least shooting for mastodon compatibility—and then work from there.
to be fair, about half of the fixes were arguably due to bugs in my own code. but seriously lemmy, why do you require the json-ld context to be a list, even when the context is defined by a single URL...?
Character 田 ("ta/da") in the name of city 三田 ("sanda") is usually read as "da". As the character can also be read as "ta", Sanda is doing just that in December to call itself "Santa". Kanji are nice.
https://twitter.com/HananoAki/status/1468199613312438279
one criticism of activitypub is that it's not a specification, and as a consequence you have to test extensively to ensure interoperability between implementations.
this is a valid criticism.
to some degree i guess i don't care. i'm building a free/open source application not a commercial product, and it's aimed at relatively tech-savvy users, and i kind of enjoy spelunking issues like these anyway, but for anyone whose goal is mass adoption of the "fediverse" concept, it's a problem.
