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

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.

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.



The major feature in v3.2.0 of Ktistec is thread analysis. The previous release, v3.1.2, added support for viewing threads from Lemmy communities. I follow the Open Source community, which leads to many large threads. The thread on FFMpeg and Google has 112 posts and is still growing.
Thread analysis helps me navigate these extensive conversations. It includes: top contributors, a timeline histogram, and notable branches.
The analysis applies several heuristics to identify interesting branches of the main thread. “Interesting” is subjective, but the algorithm currently looks for sudden bursts of activity and highlights those areas. Ktistec uses this to create a table of contents that links directly to those branches. Clicking on one of these links takes you to a branch-only view that focuses on the selected part of the thread.
It's fast—I anticipated needing to cache analyses, but analyzing a thread with over 400 posts takes only about 50 milliseconds on my production server.

This release also addresses an object visibility regression that was introduced in a previous version.
Full Changelog
Added
analyze_thread and get_threadFixed
Changed


I love a good discussion, but navigating large threads is difficult, and filtering the dross to find the silver and gold is tedious. I am working on thread analytics and an improved thread header to make it easier to identify the interesting bits and to quickly navigate to them.
Here's a peek:

In addition to top contributors, the thread header now includes a timeline histogram showing periods of engagement, and a table of contents with notable branches and direct links to those branches.
This feature is still under development, so expect changes and refinements before the next release.


centralization always leads to the same destination. that’s why I built #ktistec and why it only supports one user*
*okay, soon to support a small number of users, but the point still stands


RSS feeds are in the works...

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: