At first I was stoked to have a two letter domain, but then I looked into it and learned these companies will get you hooked with a low initial price, then jack up the prices as the domain becomes established.
Quite the grift. My plan is to tread lightly on that domain and be ready to back away from it when the rent seekers move in.
You’d think there would be some sort of rules to the neutrality of these TLD administrators, but nope.
The second time around I wised up and go ogplus.net for an API domain instead of ogplus.media. I’ll take neutrality over vanity any day.
I’m super early stages with this project and exploring what it would look like agents were just unix programs running securely along side other Unix programs. A big benefit of that is I can pipe one agents output into another agents input.
Another idea I’m exploring is having agents write code for simple tasks. First example, if you run “hello world” with agent script, the first time an agent reads the text file, understands its simple, then writes a static memory.js file. When the program runs again, it hits that file and never invokes the agent.
Where things get interesting are the cases where a script works for some cases, but not all. When that happens, the memory.js script can call agent.resume() during a static run so the agent can take over.
I remember thinking Google paid an absurd and ridiculous sum of money when they acquired YouTube. I couldn’t have been more wrong, what an incredible acquisition.
I’ve been working on https://og.plus, a service that creates unique Open Graph images per page on a website.
It does this by taking a screenshot of the page, but before it does that, you can modify what’s displayed in the screenshot with CSS, tailwind classes, meta tags, or HTML templates.
If you connect your website to it, the only thing you need to deploy to your web app are a few meta tags. The OG+ servers do the heavy lifting of processing the meta tags to setup the page, take a screenshot of it, and serve it up to the consumer.
The other cool thing it does is generate a different Open Graph images per social network so they all get an image for the exact size they works best in their previews. The CSS or HTML templates are aware of this too so you can display different content to specific social networks.
I'm beginning to put together that party-lines are strictly about gaining and holding power at all costs. Irony disappears through that lens and the way people act makes much more sense.
I shot the Phlex on Rails video course outside last summer with a glossy screen and barely notice reflections or glare, mainly because I setup shop under the shade of large oak trees. The bigger issue with direct sunlight is the glare off the chassis and heat, even when it’s 75F/24C outside.
It’s “Hotwire for command-line apps”, meaning you can ship a CLI in a Rails app without building an API. The dream is to make it work for all major web frameworks.
Terminalwire streams stdio, browser launch commands, and a few more things needs to ship a CLI for a SaaS quickly.
The best part is when you want to ship a feature for the CLI, you don’t have to worry about pushing out updates to clients and making sure it’s compatible with your API.
A more interesting development are companies that are using it as a replacement for MCP in AI stacks. They’re reporting less token usage and better overall results.
Also, water is wet and the sky is blue.