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 should probably just add support for mastodon style polls to ktistec...)
i have an informal poll for ktistec users. should we require (and use features from) the most recent versions of sqlite? how recent is too recent? if you're running ktistec, i'd love your point of view.
some background... sqlite is the most significant dependency in ktistec. to minimize problems for potential users, i intentionally stuck to features found in "older" versions of sqlite. as i write this, the current version of sqlite is 3.40.0. ktistec only depends on 3.11.0, which was released in 2016. that's very conservative.

chatgpt might be the most useful search tool out there. it just needs links in the output.
my question was "what open source alternatives are there to jmeter". at least with chatgpt all of the results are, or were, legitimate open source projects.

google's results are, as expected, full of seo-optimized websites looking for clicks. google is essentially useless for any search that might have commercial potential (to be fair, it has been for years).

i always hold out a little hope for duck duck go, but it's really a list of the same seo-optimized sites (although, you know, stack overflow and quora are down there near the end).

what's the tl;dr? i don't know. i think i'm going continue to try to start my searches with chatgpt and then use duck duck go or google to look up the websites. i wonder if i could automate that...

can we get chatgpt with fact check plz...

it looks like sqlite only recently replaced (insecure) rc4 with chacha20 for random number generation...

I wish I could reach the correct audience to suggest to that, if you are going to work full time remote, especially for a mostly remote company for the first time, it is absolutely crucial that you learn how people communicate and actively participate in it. Not just how work information is disseminated. Join your “random” and hobby Teams or Slack channels. Meet people not on your direct team. Join a social group if your company sponsors one you find interesting. It indeed takes effort as an introvert - but while working remote you are not building relationships organically like in an office, at all. Those work relationships are important to getting stuff done in business, being noticed when opportunities come up, emotionally feeling part of a team and mission, and staying mentally healthy. We spend a big chunk of our lives working!
Over the last 5 years of working and managing a team FT remote, this social interactivity is one of the top indicators I’ve observed of whether someone will succeed and be balanced and happy, long term - or whether they will burn out and be left behind. The people who often vanish the fastest never chatted except when prompted to do so for business, never turned their camera on, nor set a profile image.
I’m not telling you to step way outside your comfort zone. I’m not saying there aren’t situations where it’s necessary to turn off the camera. I’m not saying you’ll automatically fail if you never socialize. I’m just giving you some advice based on hard life lessons of watching people thrive versus be unhappy.


Today's release of code fixes things that have been annoying me for a while:
nil and other garbage was not. Lesson learned? We'll see...getter (which is, effectively, a read-only property). Previously, this code wouldn't even compile, thereby unintentionally coupling database persistence and bulk assignability.

i built @relistan 's branch this morning and tried out ktistec support for mastodon profile metadata. the attachment shows profile metadata pulled from the ruby.social mastodon instance, as well as @relistan 's own personal ktistec instance. this is something i've wanted for a long time!
a shoutout is due both these two (the owners of the two profiles shown in the attachment): @alexanderadam has been posting encouragement about ktistec all year long, and maybe before—an intangible that's immensely valuable when you're banging away on open source software—and @relistan is the first person besides me to contribute major feature functionality to the project—which takes a huge leap of faith.
thanks!

elon needs to learn that freedom of speech isn't measured in decibels.

