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 |


this chart shows inbound activitypub messages to my server. over time fediverse instances seem to receive increasing numbers of messages, many not addressed to anyone on the instance, so this represents an increase in that passive traffic, replies to other people's posts, as well as announcements/boosts/shares.
n.b. you can see all of the inbound messages to your ktistec server on the /everything endpoint.

among other improvements, document how rules work.
it's now possible to customize how ktistec processes ActivityPub inbound and outbound activities without having to write crystal language and recompile the server.

i'm still making lots of small changes/improvements to ktistec: upgrading dependencies, fixing bugs, and cleaning up. i'm laying the foundation for improvements to the experience of reading posts on your ktistec instance—a reactive user interface with streaming updates/notifications, the ability to follow arbitrary collections of objects, and a timeline that can flexibly highlight content you find interesting (vs. displaying posts in chronological order). underpinning all of this is a flexible, scriptable, rule-based language for customizing the experience.

it would be nice to have a way to federate users around topics or areas of interest, without having to join a specific server. it would make it easier for people to discover each other based on interests, regardless of the server they join. federated interests...?


started another dnd campaign.
i'm playing a gnome artificer with a surprising resemblance to tony stark...


the williamsburg bridge is still my favorite…


today was my second attempt to conquer the new york metropolitan museum of art—egyptian antiquities wing. the previous attempt met with failure due to insufficient provisions. i'm happy to report that i was successful, having viewed relics of 20+ dynasties. tomorrow i start on medieval arms and armor.

local bands playing in tompkins square park today… i ❤️ nyc

dragon con is over and i'm heading home. i spent much of my time in maker panels this year. attached is a picture of a drone built on a frame made from badminton rackets!

the team that built this was composed of grade school students!