Release v3.2.0 of Ktistec
General Discussion
1
Posts
1
Posters
11
Views
-
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.
Figure 1: Screenshot of the final design. Notable branches link to subsets of the thread. This release also addresses an object visibility regression that was introduced in a previous version.
Full Changelog
Added
- Thread analysis that displays key participants, a timeline histogram, and notable branches
- New MCP tools:
analyze_threadandget_thread - Focal point rendering support for image attachments
Fixed
- Regression in object visibility affecting replies to threads
Changed
- Enhanced MCP tool details for likes, dislikes, and announces
- Improved cookie security.
-
undefined stefano@mastodon.bsd.cafe shared this topic on
Feed RSS
Gli ultimi otto messaggi ricevuti dalla Federazione
-
Right, which ActivityPub.Space follows and auto categorizes, which ends up as a way for microblog content to make its way into the threadiverse. @strypey@mastodon.nzoss.nz
@silverpill@mitra.social sorry for interjecting 😁
-
-
> @strypey@mastodon.nzoss.nz said:
>
> We could instead try to agree on a separate place for all discussions about fediverse coordination (would it rub anyone up the wrong way if I described this as fediverse governance?). But it does makes sense to discuss a federated network in a federated network, rather than a separate, centralised forum.I keep harping on this one point because it just makes so much sense that it'd be silly not to. The new blood (new software devs implementing AP) always appear on fedi, not some third-party site, first.
To your main point, fedi on Mastodon is all just everybody talking in the same room. Certainly that's why it seems like there's so much meta-discussion about AP.
This isn't the case on the threadiverse, where discussions are segregated/categorized by community.
-
@mariusor awesome! ♥️
-
@pfefferle I added a PKCE task to my todo list:
-
@pfefferle if I'd come up with a scheme for them they would be related to pairs of activityType:objectType entries (instead of a global write), or maybe just the activityType
Ie, Create:Note, Create:Image, Undo, Delete.
-
@mariusor yea, I think the scopes and the PKCE part was the issue!
but finally... 😊
-
@pfefferle love it! 💗
GoActivityPub doesn't really do "scopes" because I couldn't think of a way store the permissions on the server side in a way that doesn't require custom logic to interact with vanilla ActivityPub objects.
