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.
made my first connection on #meshtastic at #dragoncon
This release encompasses two broad sets of changes: widening the pool of candidates for feeds and more carefully checking the origin of inbound activities (broadly FEP-fe34, Origin-based security model).
Candidates for feeds were originally limited to posts in the actor's mailboxes. This decision made authorization easy but omitted clearly acceptable posts (for example, posts addressed to the public collection) that arrived via other means (for example, filling in a thread).
Prior to this release, inbox processing did not consistently define an object's origin nor did it apply consistent rules to what it admitted based on the origin.
FEP-fe34 is still not fully enforced, and truth be told, I'm still reviewing some of its mandates, so I'm not yet listing it in Ktistec's federation documentation.
Here's the full list of changes:
Added
Fixed
Create and Update to update objects.Changed
Removed
proxyUrl property from the actor document.I am still working hard on the feed deck. Both notifications and feed ordering now work. It's now my preferred reading interface, and should be ready by the next release!
I left my #meshtastic node on overnight and it found 24 others. my assumption, now confirmed, is that i live in a pretty low coverage area.
flying to atlanta later today. i believe they have a pretty good mesh.
just powered up and connected to my first #meshtastic node. i have no idea what i’m doing…
I found this sticker in a box of miscellany. Based on the things it's stored alongside it's between 10 and 20 years old—I remember being handed it but I don't remember where or when. I'd intended to stick it on my laptop.
I had forgotten that Shepard Fairey was responsible for the original design. You can read more about that here.
Ah, the old days when Mozilla was still cool...
RE: https://mastodon.social/users/Locusmag/statuses/117101769634983338
with a title like this, I just had to buy it...
Explore @garykwolfe’s review of THE THREE COFFIN PROBLEM by @lavietidhar.bsky.social: “Tidhar is obviously having a good deal of fun with real and imagined history.” https://locusmag.com/review/the-three-coffin-problem-by-lavie-tidhar-review-by-gary-k-wolfe/
not attending #worldcon / #laconv this year... it's the week before #dragoncon starts. even sadder, i just realized that worldcon 2027 in montréal is on the exact same dates as dragoncon.
(dragoncon is the annual family vacation, so it's not negotiable)
today i learned that THIS_STYLE_OF_NAMING is called the SCREAMING_SNAKE convention.
years of C, C++, Java, Ruby, etc. etc. etc. and i never knew...
i do sometimes wonder if people on the fediverse know they're on the fediverse 😉
Type-Checking SQL Queries With Crystal Macros
My #crystallang macro powers are unmatched.
https://willhbr.net/2026/08/15/crystal-macro-sql-type-checking/