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.
| Introduction | https://epiktistes.com/introduction |
|---|---|
| GitHub | https://github.com/toddsundsted/ktistec |
| Pronouns | he/him |
| 🌎 | Sector 001 |

the only thing more annoying than a test failure in a test suite that only occurs when you randomize the order of the test suite, is a test failure that also only happens occasionally despite running the randomized suite with the same seed! 😡

I wonder if you could use/abuse Mastodon polls (FEP-9967) to distribute posts that provide near-real-time status updates (I'm thinking about severe weather alerts but I'm sure there are other use cases)?
Create a poll with an expiry far in the future and a token set of options (ideally just one—"Do you opt in?"—but poll implementations seem to require at least two).
Nothing seems to prevent the content of a poll from changing—and this is the key insight. The FEP says, "The type of a poll (single choice / multiple choices) and its options might be changed at any time. In that case the author of the poll MUST reset the vote counts." So broadcast updates via the content.
It would be a lightweight way to follow a single item without following the actor, built on top of implementations that already exist.Â

Ktistec now generates a table of contents for all posts with canonical (pretty) paths (/about-the-name-epiktistes rather than /objects/6QNom799BYc).
One of the original goals I had for Ktistec was blogging. At some point, I lost track of my "blog posts". I added this to make it easier to see what I've published.

The table of contents is currently only visible to authenticated users.
Apologies in advance for the flood of updates as I add canonical paths to older posts!

i'm "pretty sure" i have litestream backing up my epiktistes sqlite database, but getting it running was surprisingly fiddly...

I have Markdown editing working in Ktistec!
Which post was written in Markdown?

Voilà !

This is an often requested feature. It also makes Ktistec usable in browsers when JavaScript is disabled. The Markdown editor supports autocomplete and autosave, just like the rich text editor. Expect this to show up in the next release.

The big feature in release v3.2.4 of Ktistec is support for viewing and voting on Mastodon polls (AKA FEP-9967: Polls). This feature took a surprising amount of work. Some of the effort was due to my struggles with visual design, but getting the behavior right was also tricky. For example, a "vote" is just an ActivityPub Note, but unlike other notes, it shouldn't appear in a poll's replies (it could, but that would be redundant and confusing). So I had to add exceptions throughout the code to deal with this. A custom Vote object type would have been nice in the original implementation.
Added
Fixed
title attributes are now preserved.Changed
Thank you @jayvii for the build fix!

‘Twas a beautiful day for a ren faire…

I don't love the food, but I do enjoy the people… and the merchandise. There are a few makers who really pour heart and soul into making and selling something interesting and unique. And musicians who find an audience for niche songs about dragons, or being lost at sea. And where else are you going to encounter a hurdy gurdy?

And the weather—it was 75°F in December.

After thrashing through several attempts to add a smooth transition to the poll partial after the user votes, I realized that the best solution was hiding in plain sight. Turbo already sets the busy attribute on a turbo-frame element while the request is in progress, and adds a complete attribute when the request is complete. The only thing required was the styling!


Just cooked up a quick Mastodon theme for #ktistec :)Â https://src.jayvii.de/pub/ktistec-tweaks/file/css/mastodon.css.html

Polls are rendering!

I'm working to get all of the little visual elements available across the Fediverse to render in a usable way on Ktistec. When released, users will also be able to vote on polls.