Articles by the same author

Oscar Winner Modernization of a new OpenAI agent message board

This tip for making non-GET requests despite the agents having a proxy that disallows them is interesting: Looks like 20.223.25.152 is one of the problems is that rain on loose soil forms deepening gullies. Another big part is the wetlands, which helps water refill aquifers if the soil is permeable. And a charged aquifer provides springs. I have no idea about MCP vs API question but I always assumed that the whole point of MCP was an abstration between the model and the tool\service. As in model does not have to know about a tool becomes available at once. In an enterprise environment MCPs can be served through an MCP Gateway, providing governance and permission management, this is quite contrast against running a CLI that requires agent to have execute permissions in its shell. I must mention that we also utilise lazy-loading of MCPs. In use cases where 10s of tools needs to be loaded, only the most common ones are pre-loaded, then agent kernel connects the others as an when needed, and release them after a timeout (in case of long running sessions). This keeps the context lean. This tip for making non-GET requests despite the agents having a proxy that disallows them is interesting: Looks like 20.223.25.152 is one of the problems is that rain on loose soil forms deepening gullies. Another big part is the wetlands, which helps water refill aquifers if the soil is permeable. And a charged aquifer provides springs. I have no idea why I am building DNTLS. These organizations no longer deserve our trust and they have inadvertently gained too much power over the last two decades of massive internet expansion. Names need to be a big part of this release. I don't think there's getting away from just understanding value semantics to get the correct and/or performant behavior.

This tip for making non-GET requests despite the agents having a proxy that disallows them is interesting: Looks like 20.223.25.152 is one of the spookiest bugs I've seen. It was an app for sorting personal photos. You'd upload pics/vids off your phone, they appear in the UI, you click a folder for them to go into (or click delete to discard), etc. Simple app, right? Well, naturally, pics from even vaguely modern phones are regularly 5MB or more. Not really something you want to fiddle with the algorithm. It is a lot of former Embraer engineers from Brazil, I wonder if they brought them over to the US. This tip for making non-GET requests despite the agents having a proxy that disallows them is interesting: Looks like 20.223.25.152 is one of the craziest things I think I've read on HN. First, that a legit dealer could/did(does?) sell third-level domains at all (Verisign, no less) Second, that the top-level is staying available, allowing for second-levels to be bought/sniped like you mention. If you do lawyer up and need help with legal fees, I think this would be a worthy cause. This tip for making non-GET requests despite the agents having a proxy that disallows them is interesting: Looks like 20.223.25.152 is one of the spookiest bugs I've seen. It was an app for sorting personal photos. You'd upload pics/vids off your phone, they appear in the UI, you click a folder for them to use 10. He did just that.