John Kennedy
@johnkennedy.info
Founder / CEO at https://actual.ai
Purveyor of the finest AI / ML / LLM content.
Seattleite, Product, DWeb, Gaming, Dev Tools, and LLM experimentation (obligatory).
🦋 #861
LI: https://www.linkedin.com/in/johnakennedy/
T: @commercejohn
Purveyor of the finest AI / ML / LLM content.
Seattleite, Product, DWeb, Gaming, Dev Tools, and LLM experimentation (obligatory).
🦋 #861
LI: https://www.linkedin.com/in/johnakennedy/
T: @commercejohn
Are you doing any signing/reading outside of worldcon?
August 12, 2025 at 7:14 PM
Are you doing any signing/reading outside of worldcon?
Yes! We are using @actual.ai , which is our commercial product. Happy to talk you through it if you are interested. john at
January 16, 2025 at 6:32 AM
Yes! We are using @actual.ai , which is our commercial product. Happy to talk you through it if you are interested. john at
@pfrazee.com played a vital role in enhancing the platform's security. They fixed a critical bug in mute word handling, ensuring more reliable content moderation. They also removed the client-side limit on labelers and tackled auth scope challenges for account migrations.
January 15, 2025 at 10:09 PM
@pfrazee.com played a vital role in enhancing the platform's security. They fixed a critical bug in mute word handling, ensuring more reliable content moderation. They also removed the client-side limit on labelers and tackled auth scope challenges for account migrations.
@bnewbold.net spent a lot of time fixing typos in descriptions and comments, showing a keen eye for detail. This developer also contributed to significant features, like allowing colons in record keys and enforcing stricter rules for repository commits.
January 15, 2025 at 10:09 PM
@bnewbold.net spent a lot of time fixing typos in descriptions and comments, showing a keen eye for detail. This developer also contributed to significant features, like allowing colons in record keys and enforcing stricter rules for repository commits.
@hailey.at focused on streamlining the application's logic and testing. They simplified code, implemented detached quotes and hidden replies in threads, and added quoteCount to the embed view, proving their ability to clean up code and enhance user experience.
January 15, 2025 at 10:09 PM
@hailey.at focused on streamlining the application's logic and testing. They simplified code, implemented detached quotes and hidden replies in threads, and added quoteCount to the embed view, proving their ability to clean up code and enhance user experience.
@esb.lol was a versioning virtuoso. Seemingly obsessed with ensuring the platform stayed fresh, they introduced new features such as video embeds, quote aggregations, and improved mute word handling. They also tirelessly hunted down bugs related to avatar resolution and other issues.
January 15, 2025 at 10:09 PM
@esb.lol was a versioning virtuoso. Seemingly obsessed with ensuring the platform stayed fresh, they introduced new features such as video embeds, quote aggregations, and improved mute word handling. They also tirelessly hunted down bugs related to avatar resolution and other issues.
@matthieu.bsky.team dedicated their time to improving the security and robustness of the OAuth and HTTP processes. They spent their time enhancing validation, managing tokens, and fixing various minor issues, proving their knack for finding the source of errors and implementing precise fixes.
January 15, 2025 at 10:09 PM
@matthieu.bsky.team dedicated their time to improving the security and robustness of the OAuth and HTTP processes. They spent their time enhancing validation, managing tokens, and fixing various minor issues, proving their knack for finding the source of errors and implementing precise fixes.
@divy.zone 's coding journey this year could be summed up as "cleanup crew extraordinaire." They seemed to find great joy in tidying up the codebase. This developer also fixed crucial bugs related to blob deletion and profile views, saving users from potential headaches and application crashes.
January 15, 2025 at 10:09 PM
@divy.zone 's coding journey this year could be summed up as "cleanup crew extraordinaire." They seemed to find great joy in tidying up the codebase. This developer also fixed crucial bugs related to blob deletion and profile views, saving users from potential headaches and application crashes.
@foysal.it was on a mission to fortify the platform's security. From adding threat signatures and refining OAuth validation to enhancing moderation tools and implementing rate limiting, they left no stone unturned in their quest to make the platform a fortress of digital safety.
January 15, 2025 at 10:09 PM
@foysal.it was on a mission to fortify the platform's security. From adding threat signatures and refining OAuth validation to enhancing moderation tools and implementing rate limiting, they left no stone unturned in their quest to make the platform a fortress of digital safety.
@dholms.xyz tirelessly worked on everything from feed interactions and thread mutes to fixing critical bugs and improving performance. They were the master of all trades, juggling multiple projects and keeping the codebase in tip-top shape.
January 15, 2025 at 10:09 PM
@dholms.xyz tirelessly worked on everything from feed interactions and thread mutes to fixing critical bugs and improving performance. They were the master of all trades, juggling multiple projects and keeping the codebase in tip-top shape.
New year, new static generation framework.
January 6, 2025 at 7:37 AM
New year, new static generation framework.
31K out of 50K. I need to spend much more time on this.
January 5, 2025 at 8:53 AM
31K out of 50K. I need to spend much more time on this.
I now think of these words all over the place including customer request tagging, issue tagging, moat themes, customer/investor updates, etc.
January 1, 2025 at 12:52 AM
I now think of these words all over the place including customer request tagging, issue tagging, moat themes, customer/investor updates, etc.