It always ends up being faster, clearer, simpler, and better.

My tinfoil hat theory is Anthropic is trying to get their new models to take on higher-level longer-running tasks, which has a trade-off against rapid-fire tactical use of an LLM.

For these reasons, I've always found the 5 series models from Anthropic aren't great and use 4.8 for a lot of my work.

I stopped using Docker on macOS because host file system performance was so slow, even with all of the caching hacks piled on top of it, that it made the whole thing effectively unusable for development.

Directionally the post shared sounds great, but it seems "too good to be true" that we'd have a performant microVM for macOS.

Also, water is wet and the sky is blue.

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.

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.

Comments URL: https://news.ycombinator.com/item?id=47129751

Points: 3

# Comments: 1

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.

To be clear, I think both censorship regimes are not good, but I can't say I'm surprised.