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 13 hashtags


The latest release ("walk the walk") of Ktistec completes the RFC 9421 work—the server now retries an outbound request with an RFC 9421 signature when its draft-cavage signature is rejected—and adds support for using private labels as feed criteria and replacing the default timeline with any published algorithmic feed.
I annotate posts with private labels to mark content I want to see (or don't want to see) and—now that I can use them as custom feed criteria—to group posts into topical reading lists, presented as feeds.
Being able to replace the default timeline with a custom feed is the closing chapter of a long-running desire of mine to separate the kind of posts I want to read (what people do) from the "hot takes" (what people say) that are part and parcel of social media 😀.
Here's the full changelog:
Added
Fixed
figcaption in the image viewer's caption.Changed
I've shipped a lot of new features lately. The next few releases will focus on polishing them.


Since v3.13.0, Ktistec has supported custom feeds.
A custom feed is a collection of posts selected by a set of rules called a judge. Any post Ktistec has cached that is public, or was sent to you, is a candidate. The judge's job is to decide which posts are in the feed and which posts are out.
Ktistec comes with one built-in judge called the criteria judge. It also supports any number of fully custom external judges—judges implemented as external scripts the server can call on candidate posts.
I use the criteria judge for most of my custom feeds. This post explains how it works. Later posts will dive into external judges.
The Criteria Judge
The criteria judge allows you to define feeds by flexibly matching on keywords, hashtags, and mentions. You can filter candidates to those posts that contain any of one set of keywords, hashtags, or mentions, all of a second set, and none of a third.

Keywords match anywhere in a post's text, summary, or title, ignoring case—even inside words, so "art" also matches "party". Hashtags and mentions match exactly: #art matches only posts tagged #art. Use a hashtag when you want precision. Use a keyword when you want reach.
Once you've settled on terms, you can preview the feed. To keep it fast, the preview returns up to 20 matches from the 100 most recent candidates—just enough to give you a feel for what it will look like. "Create Feed" publishes the feed and starts a task that backfills the last 30 days of posts. (Feeds are private, though—only you can see them.)
After it is published, the feed is available in the deck—the column-oriented feed reader. The deck shows up to 12 feeds side by side, and you can reorder them.

Matching is fast. I have feeds with 20+ keywords and hashtags, and there is no perceptible processing delay when a new post arrives.


if you're using #ktistec and you're on an older version, i would be very happy to help you upgrade. there are a few instances running older versions, and there are enough improvements in usability, performance, and security that it is worth moving to the latest version.

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

Since all my websites and web-tools use the phenomenal #SimpleCSS framework, I thought it would also make sense to create a theme for #ktistec using those exact colours. Of course, this is also available from my ktistec-tweaks, next to the old purpleish-theme, which I had before.
Also new is the separation of the card-style post theming, which is also shown in the screenshot below, in its own CSS file.


Yesterday, I implemented #CSS rules in my "purpleish theme" within my #ktistec tweaks that change the display of posts in card style, similar to other social media. Also adds some very subtle shadow, which gives it a very slight 3D effect. This looks a lot more modern now, I think: https://src.jayvii.de/pub/ktistec-tweaks/commit/136cc0629bd23df71cc4969e23e6c252f847a9c6.html


Trying to mass-delete older posts and shares on my #ktistec instance without prior backup turned out to be a bad idea
The docker container running on my tiny 1 vCPU, 1GB RAM VPS suddently started crashing and restarting every few seconds.
Turns out, ktistec is doing some(?) tasks in the background now, hogging the CPU and loads of RAM, which eventually leads to crashing the container. Creating a swapfile stabilized the situation until the cleanup(?) tasks are done. We will see whenever it finishes.
Remember: never start fiddling without doing prior backups...

I am actually really happy about how my mobile-tweaks for #ktistec turned out. There was a lot of #CSS hacking involved, but I am pretty happy with the results :)
Here's a little video of how it looks:

Started working on some tiny #ktistec end-user hacks: https://src.jayvii.de/pub/ktistec-tweaks
For now only a user #CSS theme i dupped "purple-ish": https://src.jayvii.de/pub/ktistec-tweaks/file/css/purpleish.css.html
Maybe more to come in the future. Or not, we'll see :)

This was actually a nice read!
While I would probably not go for a "dumb" or feature phone at the moment (particularly for messaging; SMS is an insecure technology that needs to die already), the overall sentiment does resonate a lot with me.
I've read a bunch of insightful blogposts, articles and long-reads over the past few months about this topic. I did switch my habits a fair bit, especially after reading this post by amolith, which I also enjoyed a lot as well: https://secluded.site/pull-vs-push-intentional-notifications/
What I concluded for me personally is, that I want to be a lot less online to "kill time". This especially affects social media (in my case, that means the #fediverse) and doom-watching YouTube videos.
I intentionally selfhost an ActivityPub server that has few bells and whistles and is overall somewhat geared towards a slower feed (it's called #ktistec, check it out and leave some warm words for its developer!). I check in once a day or every other day. Still have some nice interactions and interesting thoughts to read, but nothing dragging me back every few minutes or notifications popping up constantly.
I enjoy reading interesting articles and blogposts and of course news about hobby interests, software developments & releases, discussions and A LOT about international, European and German politics. I use mostly #RSS for that. Again, this also follows the idea of "pull, not push". My preferred RSS client #miniflux just sits there and keeps collecting all my neatly compiled sources. And whenever I get around to it, I pull it up and start reading what's interesting and discard the rest. It does not notify me, it does not stress me: pull, not push.
Lastly, I started to use the Do Not Disturb mode of my phone and computer very liberally. Mostly on a timer during most of the day (during work and from 8PM until waking up), allowing only phone calls to get through and only from people in my contact list. I told family and friends to call me, when they need something from me immediately or for important issues. Messages on #signal can take several hours (sometimes days) until I see them.
This has gotten me in a better place, I think. Still, there are some "left-over issus" I am still unhappy about, such as YouTube/VOD consumption, which is still way more than I would like. And also the fact that i constantly have my phone on me and often times also in my hand, rarely even during conversations, which is horrible!
But I decided to not stress myself about that too much and work on minor changes in a consistent manner, as I have during the past months and years. It is all a process.