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 |


fine game. and right for the time...

i posted about the problems caused by the lack of a clear license a week ago. commits ca662ca through 49d3e2a remove the kemal-session and kemal-csrf shards and replace them with lightweight improvements to a session store i'd written previously and forgotten about and cut-and-paste reuse of kemal-csrf (which has a clear license and clean history). ktistec will be released under AGPLv3.

i didn't expect follows. or boosts.

this is the web pretty much throwing its arms up in the air and giving up

these commits show the actor's public posts when an anonymous user navigates to the site, and show the authenticated actor the content timeline for both their inbox and their outbox. these are really two big queries with a pagination scheme i found on the internet. i haven't yet benchmarked it against the common "OFFSET LIMIT" method.


clearly license your open source software. if you don't it's impossible to use it (at least in the united states).
kemal-session was released without a license, and there's discussion online looking/hoping for clarification. unfortunately, kemal-session was built on top of code that, itself, wasn't licensed, so any resolution is going to require tracking down at least two people.
not impossible, but possibly more work than just rewriting the library...

didn't know this syntax worked in ruby (and crystal):
puts %x[ls]

remote is nice but somedays i miss the office


i think we're past sitting on the fence. if you see two kids, and one of them is beating kids up while the other is just playing, you don't need to stand around and unimaginatively point out that "one [kid] has the personality of a bully, [while] the other doesn鈥檛 have much personality at all". stop the bully!