3,771 karma · joined November 15, 2010
If you’re not upgrading your deps and rebuilding your rust project this morning, you’re pretty likely exposed to eMudhra. If your project was “done” a few years ago that’s likely not going to be easy.
It's hard to hold an LLM accountable for anything.
But I recently looked into self hosting and several things each wanted their own Postgres container. Immich wants a Postgres and a redis instance.
If you’re building apps targeted at self hosters, SQLite is really all you need.
The actual sources for this (that actually list the 19 car brands) are: https://news.northeastern.edu/2026/09/29/connected-car-priva...
https://www.consumerreports.org/electronics/personal-informa...
I believe Cloudflare is the only FaaS that offers that. It makes it fantastic for putting a light weight layer in front of a few upstream API, like say inference providers.
This is why the sidewalks next to city parks take forever to get shoveled after a big snow storm.
It seems like most other options for self-hosted S3 (Garage/SeaweedFS/RustFS) want to hide my files away in some sort of custom format.
Many companies fulfill the intent of the law. They run a real hiring process — where they advertise online and interview people with work authorization/citizens and people who would require sponsorship.
But if someone requiring sponsorship was the best candidate for the job, then they have to run an additional “fake” process that fulfills these requirements, since no one actually hires tech workers from the newspaper.
One recommendation, if you want to take the class but aren’t planning on doing it professionally (and have any interest in outdoor activities), take a Wilderness First Responder class. I found I learned a lot more in that class, and much it is practical in many circumstances, not just riding on an ambulance. It’s also a lot more fun, as you spend a lot of time running around in the woods learning to macguyver splints out of all kinds of stuff.
The other thing I found was that to really be good at it/feel confident treating anything beyond the most basic patients, you’re going to have to work on an ambulance full time in an urban setting. And in most places, to do that professionally, you’re going to have to become a paramedic.
His publisher also said the original draft was submitted in 2019, though they’ve also become lukewarm in their backing of the author lately (he was also just accused of classic plagiarism for an unrelated short story).
So hard to say this one is settled.
If I have to gather and tag data to fine-tune Jev, I can probably just train an "old school" classifier model and make it even cheaper, faster, and just as accurate.
Imagine a world where you could:
* Configure your favorite harness/chat client with any OpenAPI spec for an API that supports Oauth2.
* The harness would walk you through the Oauth flow and securely store the token.
* And then insert some tools for discovering the API methods and making requests in to the context.
* The agent could then formulate a request, call the request tool, and the harness would 1) makes sure it's allowed to make a request to that API, and 2) insert the Auth Token into the request.
It would be basically exactly the same way MCP is setup today, except all you would need is an OpenAPI spec. You wouldn't have setup a server for a janky new standard that's half implemented slightly differently by every harness/chat client.
OP wasn’t even actually critical of LLMs, they were just saying that plan mode was helpful to stop the model from making incorrect assumptions when you want you don’t specify everything you should.
However, now I live in New York, where they seem to go out of their way to make it difficult. The registration cutoff is several weeks before the election and for at least one election, I found myself wrongfully expunged from the voter roles.
I think it may just be how corrupt the state government is.
In that case, when the docs are not associated with a code change, you want to make getting those improvements into the docs as frictionless as possible, otherwise the changes aren't going to get made.
Personally, I've found that making docs updates incredibly fast + easy to be far more valuable than anything you get from forcing doc changes through the full SDLC process. If someone has feedback on your docs changes they would have shared in a review, they can just update the docs instead.
Instead they invented something new/weird/complex standard, and then every client implemented slightly differently (and different parts of it).
But you’re right, since clients don’t have a nicely sandboxed “make api request” tool, it’s basically the way to go for a lot of use cases.
I think the real value of MCP is that it allowed companies to say “we’re doing AI!” When they built an MCP server. Just saying “use our api” was a lot less exciting.
Giving it a different name probably also helped cut through politics at companies where non-technical people didn’t want to open up user data with an API, but they did want to do AI.
Though for cc you are correct, using it with your sub draws from extra usage.