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 |

I have a workflow where I āmoveā (cherry pick) commits from an R&D branch to the main branch and then rebase the original branch on top of main. Today I learned that this works even if the moved commits are still present on the original branch. Git detects their presence in the history and doesnāt try to add them a second time, which is what I was afraid would happen!

I have started work on a Mastodon-compatible API layer intended to support the many Mastodon front-ends available. It is incomplete and requires an explicit build flag to enable, but what's there (the main timeline) already works with the official Mastodon app, Tusky, and Phanpy.
Here's the full changelog:
Fixed
Changed
As always, check out the full diff for the complete details.

This small release focused on two big deliverables: support for the latest version of Crystal and fixes for a few delivery issues.
Previous releases supported a wide range of Crystal Language versions, but ran into problems with version 1.17.x and beyond due to breaking changes in the standard library. This release works on 1.19.1 but also requires at least 1.19.1.
This release also fixes a bug, present since mid-2020 when HTTP signatures were first added, that resulted in signatures some fediverse servers wouldn't accept. Mastodon did, but with the proliferation of new ActivityPub servers, I increasingly encountered servers that did not.
Here's the full changelog:
Fixed
keyId now includes #main-key fragment.Changed
It's always good to stay up-to-date on releases. But if your platform doesn't yet support 1.19.1, I've also released a parallel branch that still runs on 1.16.3 and earlier. I'll maintain that branch for the next few releases to give everyone time to upgrade.


My never ending quest to redefine my news reading habits have fallen back to old school newspaper reading, but with a twist!
Using a pretty cool RSS aggregator that writes into templates of arbitrary formats in combination with some RegEx foo and a full-page scraper, I am now able to read "newspaper" every morning either on the phone, PC or ebook reader and be done with it for the rest of the day.
I realised that I fall into the habit of checking news constantly, even when using classic RSS readers for it. During my test-flights in the past week, this hacky project appears to work-for-me(TM)
Git-Repository of "Zeitung", a news aggregator in newspaper style as HTML/PDF/EPUB

Iāve adopted the Oxford comma, but damn my mind struggles with the syntax.

I think Iām going to work on a Mastodon-compatible API next. I did all the hard work figuring out what I need to change months ago so this should be smooth. Iām happy with the existing #ktistec UI but there is a lot of interesting work on the client side that Iād like to sample.
FWIW, Iām not opposed to C2SāKtistec comes with a lot of the necessary abstractions. But I feel like my users, myself included, will get more bang out a Mastodon-compatible API. (But change my mind!)

The latest release of Ktistec addresses the shortcomings of the previous release that became apparent after using quote posts in production for a few days. So far, there have been no major bugs, but there was room for improvement.
Here's the full changelog.
Added
Changed
siteName to more standard nodeName.Fixed
I added a FEDERATION.md document to the project. This is documentation required by FEP-67ff on "information necessary for achieving interoperability with a federated service". The document describes, at a high level, what federation protocols and standards Ktistec currently supports.

it would make me very happy if more people on the fediverse, especially those that see themselves as pillars of progressivism, treat others with a little more grace and thoughtfulness.
(Iām not advocating for being nice to fascists. Iām asking you to be nice to people here who share 99.9% of your values and differ on that one thing.)


working on writingĀ FEDERATION.md i already found one easily fixable deviation (siteName instead of nodeName in nodeinfo).

working on writingĀ FEDERATION.md i already found one easily fixable deviation (siteName instead of nodeName in nodeinfo).