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.
#ktistec 166 hashtags

The two big features in release v3.2.7 of Ktistec are back end support for creating polls (the front end is coming in the next release) and advanced theming support—specifically, a rich vocabulary of CSS class values and data attributes on which to build a theme. The full set is documented in the README. I'll post more on how I'm using these later this week.
Here is the full set of notable changes:
Added
Fixed
Question ID.Changed



I took a detour and worked on alt text editing in release v3.2.6 rather than continuing with the polls backend. I also continued to fix bugs and to add polish. Here's the full set of changes:
Added
Fixed
figcaption elements.Changed
(I'm editing this post in Markdown—the new feature in the last release!)

Would it be useful to customize the rendering and presentation of posts by actor?
I follow a lot of actors and I get a lot of posts, and I'd like the posts from some actors to stand out, and I'd like the posts from others to be more inconspicuous. Or maybe I want to use color to help visually categorize posts from actors I follow, based on subject matter.
Does this sound like a useful feature?


I rolled out a lot of features over the last several weeks and created a lot of bugs in the process. Release v3.2.5 of Ktistec is mostly about fixing those bugs. I did implement two requested features, however: support for editing posts in Markdown and support for Open Graph metadata. Here's the full list of new features:
Added
🎄 I'm working on support for poll creation and management now. It's also time for a performance improvement pass or two.

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 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!