I’m an app developer and I used to have my laptop (mainly Mac but also have a Windows one) and a monitor. I would create apps for IOS on my Mac and eventually upgrade it to also work on Android. Now I have 2 monitors, one linked to my Mac and the other to my Windows laptop. This way I can simultaneously develop for both platforms at the same time.

As a data-obsessed golfer trying to get to single digits, I need a tracking app that picks up where Arccos leaves off. So I'm building one: https://shortgamewiz.com (still a bit WIP).

After a few rounds of using it, I already know a few things I didn't before: I suck at right-to-left breaking putts, I baby uphill putts too much, and getting out of bunkers consistently is not good enough if I can't sink the occasional save. So I know what to practice now.

For those who don't want to switch to AI browsers, I built a chrome extension that lets you chat with page, draft emails and messages, fix grammar, translate, summarize page, etc. You can use models not just from OpenAI but also from Google and Anthropic.

Yes, you can use your own API key as well.

https://jetwriter.ai

Feedbacks are welcome.

I made https://poemd.dev/ as an online markdown scratchpad that supports GitHub Flavoured Markdown and stores all data in the URL. This means there are no accounts to work with and everything is basically stored in bookmarks if you choose to.

The persistence model makes documents somewhat sharable, but I do find Open Graph previews to be mixed. In Messenger it renders the whole URL, which is quite long due to encoding, and that kills the conversation view.

The other day I got into some pretty weird territory with Claude, trying to map out what an immortal ASCII cat would look like. Basically an autonomous Tamagotchi.

The idea was to create a quine that runs forever on something like Akash network with its own crypto treasury to support and pay it's bills and try to replicate. It would then talk to an LLM for support and actions on what to do to stay alive.

It got pretty out there. Stored some of the ideas here.

https://github.com/aquaflamingo/catfi

Bor - Linux Desktop policy management ( https://getbor.dev/ ).

In short, it unifies the configuration of different desktop components as policies ( dconf, Kconfig, polkit, Chrome, Firefox, etc.. . It's LGPL.

You can check my slides for the upcoming Tuxconf conference this Friday: https://getbor.dev/publications/tuxcon2026/

Cheers! Blago :)

I've been working on multi agent orchestration

https://github.com/madebywelch/mau

Lately I've been building Aho (https://aho.com) -- an API for verifying age, credentials, and identity using cryptographic proof from digital wallets instead of document inspection.

For context, I built out Playboy's age verification system, and watched as it hurt conversion (nobody wants to upload an ID to an adult website, who would have thought!). Cryptographic signatures from issuing authorities (DMVs, universities, employers, etc) with selective disclosure (e.g. you don't need to upload your full ID, just the fields that matter) is how verification _has_ to work going forward -- AI can fake documents, but not private keys.

I've been working on this 6 months full time, and implemented all the W3C VC, OpenID4VCI/VP, SD-JWT specifications myself.

Would love to get people's thoughts on it!

I am working on mesh (https://growmesh.io) I started working on the topic of human development two years ago and I dived into the topic of how humans have been trained, manipulated, educated or brainwashed. My central idea which I am investigating is that whenever a person is interacting a highly tuneable ML model such as the X/Fb/TikTok feed or chat interfaces with LLMS, does the thinking and development of the human happens more times or less due to the new experience.

I'm working on JRECC, a Java remotely executing caching compiler.

It's designed to integrate with Maven projects, to bring in the benefits of tools like Gradle and Bazel, where local and remote builds and tests share the same cache, and builds and tests are distributed over many machines. Cache hits greatly speed up large project builds, while also making it more reliable, since you're not potentially getting flaky test failures in your otherwise identical builds.

https://jrecc.net