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 |

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

I think one of the strangest things about "application software development" is that an essential skill in the development process consists of taking requirements expressed in human language and manually translating them into cryptic (to most people) programming language syntax.
Of course this isn’t desirable, and we've tried so many things to change that over time: programming languages are themselves abstractions over lower-level machine language, we invented disciplines like CASE (Computer Aided Software Engineering) and methodologies like Shlaer-Mellor to assist with or automate the creation of the source code, we invented categories of products like low-code and no-code tools to change the building blocks themselves. None of that really changed the nature of application software development.
Now, we find ourselves in 2025 contemplating/confronting the literal opportunity/challenge/threat of telling a machine what we want in a human language and having them build the application. The fact that we are here surprises me. That it works at all surprises me.
That the state of the art comes down to “prompt engineering” and trying to jury-rig business requirements to satisfy an LLM does seem a little weird though.

I was planning on adding support for custom themes in release v2.4.13 of Ktistec. That turned out to be difficult, so I implemented post visibility instead—which then also turned out to be difficult. C'est la vie.
The editor now includes radio buttons for controlling post distribution and visibility. In particular, you can now send messages directly to mentioned users without sending them to all of your followers.
You can also mark posts as sensitive using the content warning checkbox in the editor. Sensitive posts are hidden behind a summary that readers can click to reveal the content.

This release of Ktistec includes RSS feeds and RSS feed discovery. RSS feeds are currently available for the site home page and account pages.
Here's the full changelog:
Added
Changed
Fixed

this is a direct message for @toddsundsted (now updated)

a dependent type itself depends
on Agda, Idris, and Lean.
a list of three, on three itself
depends recursively.


Servers
- Mbin v1.8.4
- Ktistec v2.4.12
- PeerTube v7.3.0
- Lemmy v0.19.13
- gancio v1.28.0
- Misskey v2025.9.0
- NeoDB v0.12.2.1
- tootik v0.19.0
- Gush! v0.0.21
- PieFed v1.1.7
- Trunk & Tidbits, August 2025 (Mastodon)
- Introducing quote posts (Mastodon)
Clients
- IceCubesApp v2.0.0
- Mangane v1.17.2
- Aria v1.3.9
- Photon v2.0.2
- Blorp v1.9.22
For developers
- fediverse-pasture-inputs v0.3.2
- Fedialgo v1.1.38
Protocol
- FEP-11dd: Context Ownership and Inheritance
- Bite activity
Articles
-----
#WeekInFediverse #Fediverse #ActivityPub
Previous edition: https://mitra.social/objects/01991bd7-ffbb-3059-0160-12d3c53fb8aa

i’m pretty excited to have discovered @LIGO@scicomm.xyz

RSS feeds are in the works...


I'm going to make a backwards-incompatible change to the dropdown values for the range input on the metrics page, switching from calendar-based periods to duration-based periods. I thought beginning of week, beginning of month, and beginning of year would be sensible ranges, but I almost always adjust the range in the query string by hand to be last seven days, last thirty days, or last 365 days, so it makes sense to make those the options.

new word of the day:
  desiderata/desideratum
something that is wished for or desirable...