Im building serverless hosting for Wordpress (+ serverless mariadb) with the dev tooling I wish Wordpress had.. including mcp and cli that fully exposes the wp cli, mariadb, and all of the underlying infrastructure. So everything you can do through the dashboard, an agent can do via mcp or cli.
For example, if Im debugging a plugin, an agent can just connect to the site, read or modify the code, see what it's writing to disk or db, test it's changes, etc.
And this is standard WP -- this isn't a rewrite like emdash. So the fun part is figuring out how to make it all work without modifying WP, or requiring plugins to be installed, etc.
I'm making a browser-based MMO experience of sorts for the 1999 Dreamcast game Shenmue - it's still pretty rough around the edges but people who like the game have liked it so far:
I'm getting reports of performance issues for TerraSunder from a couple people so if you run into them, submitting a performance report in the settings would help me a lot!
I have some other cool projects listed on my site here, including a browser-based version of EverQuest that plays itself: https://brynnbateman.com/
I'm working on a book starring the 6 Simple Machines. I already did one book called "Simple Machines Made Simple." I'm now doing a follow up book that I'm thinking will likely be titled "Simple Machines Made Complicated" (or maybe Complex). Each page is a working mechanism. Kind of like a book full of fidget toys. So I want to have one page for each simple machine, and some of the progressions to complex are easy i.e. (wheel -> gears), but the one I'm currently stuck on is the pulley. My first book had a compound pulley, but now I'm struggling to figure out a more complex pulley example that I can recreate with less than 5mm for the page thickness. My first idea was to do like a roman blind mechanism with a pinch-stop type thing for the cord, but the more I played with it, the more I felt like this wasn't any different from the first book. I also like the idea of a chain hoist type mechanism, but I'm worried there isn't enough visual pay off for what you put into it. Like you move this chain thing around a bunch, but you only get a very small movement on the other end.
Anyway, that's I'm working on. It might take me another 6 months, but I'm sure I'll figure something out ;)
I've been working on a website monitoring service written in Rust. I had to port from using the reqwest library to libcurl in order to properly capture DNS/connect/TLS/first-byte timing. I basically ran the new engine side by side with the original for a few weeks, running 100k+ checks daily to get a 99.8% agreement. The mismatches were interesting because of the Cloudflare challenge that returned 403 based on the http/2 fingerprint, no matter the user-agent used.
Working on an interactive explainer for code. When agents write most of the code, I find I'm losing the working theory of the code/architecture. Code review had typically served a couple of purposes, two of which are catching errors and disseminating codebase knowledge amongst the team. I find that adversarial agent reviews are good at catching errors, and that I prefer to learn about the architecture before/while I'm designing the next feature, rather than after.
I've also been designing a APL/BQN-like language that uses Korean as a way to compact and compose the meanings of the operations.
Working on an Apple Notes clone, but everything is a local Markdown file.
Currently free, macOS (Silicon + Intel) and Windows. Has tags and priorities, can display many scientific syntaxes (mhchem, most TeX / LaTeX stuff, Excalidraw, PlantUML, Graphviz / DOT, Vega-Lite, and actual Markdown footnotes). Can show notes in vertical lanes like JIRA does. Free iCloud sync too. Still early alpha.
looking at the post dates, there doesn't seem to be a schedule at all. it's posted randomly... posts on 9th through the 30th. Back in 2024, it was even posted regularly on the 1st.
IMO if there isn't a schedule, then posting it on the 1st sounds good.. since that's when the other posts like this are submitted.
I think a biweekly post cadence versus monthly might be beneficial due to the thread locking after 14 days, which would ensure there is always an active thread for folks to share what they're hacking on (and they might not be ready or in a position for a Show HN thread). Otherwise, there is a period of time where you cannot share between the last thread when it closes and the next thread. 1st and 15th of the month, for example. Or perhaps allow these specific threads a longer active window before they close to new comments.
I'm building the Fillvisa: open-Source Alternative to Docketwise
So far, legaltech has mostly been closed-software. I'm building an open source alternative to Immigration tech software.
Github: https://github.com/athos2113/fillvisa-os
Live demo: https://fillvisa.com/demo
Docketwise: https://www.docketwise.com/
Im building serverless hosting for Wordpress (+ serverless mariadb) with the dev tooling I wish Wordpress had.. including mcp and cli that fully exposes the wp cli, mariadb, and all of the underlying infrastructure. So everything you can do through the dashboard, an agent can do via mcp or cli.
For example, if Im debugging a plugin, an agent can just connect to the site, read or modify the code, see what it's writing to disk or db, test it's changes, etc.
And this is standard WP -- this isn't a rewrite like emdash. So the fun part is figuring out how to make it all work without modifying WP, or requiring plugins to be installed, etc.
https://www.agiler.io
I'm making a browser-based MMO experience of sorts for the 1999 Dreamcast game Shenmue - it's still pretty rough around the edges but people who like the game have liked it so far:
https://www.newyokosuka.com/
I'm also close to finishing an browser-based client for the MMOFPS Planetside:
https://terrasunder.net/play/
I'm getting reports of performance issues for TerraSunder from a couple people so if you run into them, submitting a performance report in the settings would help me a lot!
I have some other cool projects listed on my site here, including a browser-based version of EverQuest that plays itself: https://brynnbateman.com/
I'm working on a book starring the 6 Simple Machines. I already did one book called "Simple Machines Made Simple." I'm now doing a follow up book that I'm thinking will likely be titled "Simple Machines Made Complicated" (or maybe Complex). Each page is a working mechanism. Kind of like a book full of fidget toys. So I want to have one page for each simple machine, and some of the progressions to complex are easy i.e. (wheel -> gears), but the one I'm currently stuck on is the pulley. My first book had a compound pulley, but now I'm struggling to figure out a more complex pulley example that I can recreate with less than 5mm for the page thickness. My first idea was to do like a roman blind mechanism with a pinch-stop type thing for the cord, but the more I played with it, the more I felt like this wasn't any different from the first book. I also like the idea of a chain hoist type mechanism, but I'm worried there isn't enough visual pay off for what you put into it. Like you move this chain thing around a bunch, but you only get a very small movement on the other end. Anyway, that's I'm working on. It might take me another 6 months, but I'm sure I'll figure something out ;)
I've been working on a website monitoring service written in Rust. I had to port from using the reqwest library to libcurl in order to properly capture DNS/connect/TLS/first-byte timing. I basically ran the new engine side by side with the original for a few weeks, running 100k+ checks daily to get a 99.8% agreement. The mismatches were interesting because of the Cloudflare challenge that returned 403 based on the http/2 fingerprint, no matter the user-agent used.
Working on an interactive explainer for code. When agents write most of the code, I find I'm losing the working theory of the code/architecture. Code review had typically served a couple of purposes, two of which are catching errors and disseminating codebase knowledge amongst the team. I find that adversarial agent reviews are good at catching errors, and that I prefer to learn about the architecture before/while I'm designing the next feature, rather than after.
I've also been designing a APL/BQN-like language that uses Korean as a way to compact and compose the meanings of the operations.
Working on an Apple Notes clone, but everything is a local Markdown file. Currently free, macOS (Silicon + Intel) and Windows. Has tags and priorities, can display many scientific syntaxes (mhchem, most TeX / LaTeX stuff, Excalidraw, PlantUML, Graphviz / DOT, Vega-Lite, and actual Markdown footnotes). Can show notes in vertical lanes like JIRA does. Free iCloud sync too. Still early alpha.
https://notesplus.io
Laboratory.love, still a one-person side project, and the goal is still to make supply chains transparent with regard to plastic chemicals.
If you eat the same product every morning please consider kicking off a crowdfunding page to get it tested.
Check what's been tested so far here: https://laboratory.love/results
There are posted later in the month. Don't post a new copy on the 1st. The most recent is here: https://news.ycombinator.com/item?id=49686380
looking at the post dates, there doesn't seem to be a schedule at all. it's posted randomly... posts on 9th through the 30th. Back in 2024, it was even posted regularly on the 1st.
IMO if there isn't a schedule, then posting it on the 1st sounds good.. since that's when the other posts like this are submitted.
I think a biweekly post cadence versus monthly might be beneficial due to the thread locking after 14 days, which would ensure there is always an active thread for folks to share what they're hacking on (and they might not be ready or in a position for a Show HN thread). Otherwise, there is a period of time where you cannot share between the last thread when it closes and the next thread. 1st and 15th of the month, for example. Or perhaps allow these specific threads a longer active window before they close to new comments.
(n=1, ymmv)
[flagged]
[dead]