On the side, https://infrabase.ai (hand-verified AI infrastructure directory) launched a Media Generation category, image and video APIs after a run of requests for it. Also the submission spam is way up here latley, been improving the detection here as well. Also seeing real interest in paid listings now, including one that started as a link-buying request I turned down :)

Been doing a lot of AI assisted emailing, so I have started to work on a little review UI for AI generated text, comments on specific words, inline edits, Claude picks up both and revises in place. Like a PR review interface for text. Turns out pretty good workflow with Claude watching the files for new comments, editing and commenting back right away.

It's like a fixed up TypeScript specifically tailored for Wasm GC that can produce very small and fast binaries, but also has features like pattern matching, ownership / borrow checking for resources, pipeline, tail call elimination, multi-value returns, direct WASI component integration and a lot more.

Why? There's no why. The world doesn't need another Markdown editor. I still made one.

Everything is on-device, purposefully human-centric without being anti-AI. I built this because I wanted to work on a project that I could sweat the details unconstrained by deadlines, investors, etc.

I was frustrated with other writing experiences, and like most I gravitated to Apple Notes due to simplicity, but I still missed so many things. As someone that's spent the last 2 years immersed in Cursor, Codex and CC, I wished some of their input behaviors existed in a regular text editor.

For example, you can use / to add styles, or : to add emojis, shortcuts like < 3 for a heart, - > for an arrow, and so on. It honestly feels great.

Is it radically different than other editors? I don't think so. But I think it's well executed across every dimension possible.

Maybe one different thing: multiplayer. It's live editing like google docs, but P2P using WebRTC and strong cryptography. The limitation here is that you can only share a file while having it open yourself.

Great care was taken to performance and portability. This is one of the areas where I spent a ridiculous amount of time simply because I enjoyed pushing the limits of the stack. While using you will notice that rendering, GPU, RAM and bundle sizes were heavily optimized. The Mac app is < 50mb.

Very soon, I'll launch an iOS version with iCloud sync. In the future, I might launch basic AI features. If you miss a great text editor in your life, give it a try.

A programming language which lets you code multiplayer games like singleplayer games. Every program written in Easel is guaranteed deterministic and snapshottable, which is how it can automatically make your game multiplayer automatically using rollback netcode.

My hope is that teenagers who makes games in Scratch might like to make games in Easel because it means they can make games they can play with their friends, without having to deploy a server or learn anything about networking on synchronization. People can literally make a multiplayer game on their first day of coding.

Currently been working on adding tilemaps.

This solves exactly n=1 user's issues: I tend to fall off the workout wagon without public accountability and when I dont get scores to improve on and especially to degrade and dillute my gym trips to the point of ennui.

It's free and public until it breaks:

https://aft.jodavaho.io

My progress

https://aft.jodavaho.io/track/46B8XWPCVK5MVS35R8X53Y8KY5

(heavily helpd by AI on the frontend - I am terrible at it)

My summer project was to challenge existing 2D / 3D visual effect creation tools (touch designer, comfyUI, etc.) with something agentic as the true foundation (not just slapping MCP on top of an existing paradigm).

It also came from the following observations:

- people are making their own coding harness, why not one for realtime visual effects?

- using Claude code or codex to make art and installations is absolutely fantastic, but you usually end up with a lot of friction and paper cuts when it comes to deterministic workflows and concept iteration.

SubjectiveZero is the free and open source project that resulted from it. It’s still following the classic node editor paradigms but making the nodes absolutely more malleable while also combining a user experience flow optimized for ideation and iteration. I definitely invite you to check out the showcase and examples on the website, but basically it feels kind of magical when your editor just “get” what you want, and nudge your exploration into adding more little knobs here and there so using the tool feels more like playing rather than “operating”.

I also liked the emerging concept of an adjustable abstraction ladder, meaning people who are very technical can still get as much granular control as they wish to while people who just want high level concepts and vibes can just use prompts to try things out.

When it comes to determinism, the tool has some neat features like an agent graph to constrain agent workflows, overpowers MCP that drives user interface changes as the agent makes progress, allows the agents to verify their work and coordinate so the usual painful wait for agents to be done is somewhat minimized. There’s also a way to do basic model routing to tweak your intelligence/speed ratio.

I’ve personally used it to make art and fun experiments. Feel free to send feedback or contribute tokens to the project if the concept speak to you!

We created it as an alternative to the price gouging that happened over the last year at various timesheet SaaS companies. The idea is that good software should not cost 10x as much just because 10x as many people use it. In our opinion, software should also be functionally complete. There should be no arbitrary tiers that only exist to force people into more expensive plans.

The stack is Elixir with Phoenix LiveView, deployed on a Talos Kubernetes cluster. This is different from what we normally build on, and honestly quite fun.

Lately we have been thinking hard about the temporal nature of timesheet software. Many things get quite complicated once you factor in historical versions: the need to retire, lock, change, reopen records or rates, and so on. We have been working hard to polish Abejora to make everything accessible, user friendly, and intuitive.

The basic idea is to separate an application's UI semantics from the toolkit that actually renders it. The same application can currently be presented using native Win32, Cocoa/AppKit, Qt6, GTK3, GTK4, Swing, or a web browser. The UI can run locally or be rendered remotely by a client, without the application itself being rewritten for that environment.

I've also been working on a declarative layout format and, lately, a visual designer.

It started as a rewrite of an architecture I worked on many years ago, mostly because I wanted to see how far the idea could be pushed with modern systems. It has turned into a considerably larger project than I expected.

Still private and very much under development, but I'm curious whether other people have run into the same problem: maintaining applications that need to survive changes in GUI toolkits, operating systems, deployment models, or client environments.