eoskx

6 ms·

1.
by eoskx 4mo ago
Claude's style is now overuse of sentence fragments, which this "article" has in spades. Fragments are the new emdash or "delve".
2.
by eoskx 4mo ago
AI generated slop. Why would anyone waste the time to read this if you won't take the time to thoughtfully write something?
3.
by eoskx 4mo ago
It is unfortunate because the content and subject matter isn't actually bad, but yes, there are definite AI-generated tells here.
4.
by eoskx 4mo ago
A lot of how well it works or won't work depends on your clients, as not all clients have support for things like RFC 9728 (Protected Resource Metadata). Assuming your client has good support for most of the OAuth 2.0 standards that MC
5.
by eoskx 4mo ago
Doing a workshop this week on MCP for an enterprise client and explaining the 406 returned by GET against /mcp w/o text/event-stream is exactly one of the things that I have to bring up when I do these. The specification stil
6.
by eoskx 4mo ago
Fond memories of buying cheap Sun gear around 2005-2007. I had an E4500, Blade 1000, and a Tadpole SPARCbook 6500 that I ran Solaris 10/11 on along with a couple of Sun Rays. Used the Blade 1000 as a Sun Ray server and it was a great e
7.
by eoskx 6mo ago
Interesting, but cannot run CUDA or more to the point `nvidia-smi`.
8.
by eoskx 6mo ago
Also, not surprising that LiteLLM's SOC2 auditor was Delve. The story writes itself.
9.
by eoskx 6mo ago
Valid, but for all the crap that LangChain gets it at least has its own layer for upstream LLM provider calls, which means it isn't affected by this supply chain compromise (unless you're using the optional langchain-litellm packa
10.
by eoskx 6mo ago
Not just as a gateway in a lot cases, but CrewAI and DSPy use it directly. DSPy uses it as its only way to call upstream LLM providers and CrewAI falls back to it if the OpenAI, Anthropic, etc. SDKs aren't available.
11.
by eoskx 6mo ago
Yep, I think the worst impact is going to be from libraries that were using LiteLLM as just an upstream LLM provider library vs for a model gateway. Hopefully, CrewAI and DSPy can get on top of it soon.
12.
by eoskx 6mo ago
Yep, DSPy and CrewAI have direct dependencies on it. DSPy uses it as its primary library for calling upstream LLM providers and CrewAI falls back to it I believe if the OpenAI, Anthropic, etc. SDKs aren't available.
13.
by eoskx 6mo ago
LangChain at least has its own layer for upstream LLM provider calls, which means it isn't affected by this supply chain compromise. DSPy uses LiteLLM as its primary way to call OpenAI, etc. and CrewAI imports it, too, but I believe it
14.
by eoskx 6mo ago
This is bad, especially from a downstream dependency perspective. DSPy and CrewAI also import LiteLLM, so you could not be using LiteLLM as a gateway, but still importing it via those libraries for agents, etc.
15.
by eoskx 7mo ago
Very similar experience to my own. Was a 1P customer for years, but the product declined after the VC purchase and I trust Apple more to get privacy & security right. Apple Passwords accomplishes the minimum of what I want a Password sy
16.
by eoskx 7mo ago
I've asked multiple OpenAI employees on X that have been posting about the issue whether or not they will be processing bulk unclassified Americans' data or what will they do when asked since I think it is fair to assume that they
17.
by eoskx 7mo ago
"Even as Mr. Trump published the post at 3:47 p.m., the two sides kept talking. Mr. Michael, who was on a call with Anthropic executives at the time, said the Pentagon wanted the company to allow for the collection and analysis of uncl
18.
by eoskx 7mo ago
Related: https://archive.ph/WEcM4 "Anthropic’s team was relieved to hear that the government would be willing to remove those words, but one big problem remained: On Friday afternoon, Anthropic learned that the Pentago
19.
by eoskx 7mo ago
Considering they asked Anthropic to participate in the following, I would say this is by design in the OpenAI arrangement: "Anthropic’s team was relieved to hear that the government would be willing to remove those words, but one big p
20.
by eoskx 7mo ago
"Anthropic’s team was relieved to hear that the government would be willing to remove those words, but one big problem remained: On Friday afternoon, Anthropic learned that the Pentagon still wanted to use the company’s AI to analyze b
21.
by eoskx 7mo ago
Correct URL: https://archive.ph/WEcM4
22.
Inside Anthropic's Killer-Robot Dispute with The Pentagon(theatlantic.com)
15 points by eoskx 7mo ago|2 comments
23.
by eoskx 7mo ago
"Anthropic’s team was relieved to hear that the government would be willing to remove those words, but one big problem remained: On Friday afternoon, Anthropic learned that the Pentagon still wanted to use the company’s AI to analyze b
24.
by eoskx 7mo ago
Tried Ghostty several times and I really appreciate the font rendering, but I keep going back to iTerm2 and Terminal.app mostly because of lack of scroll back & CMD-F, etc. Looking forward to what is coming in the next release.
25.
by eoskx 7mo ago
thanks for speaking out, and yes, that was my interpretation, as well, which I outlined below. This is nothing more than some sugar coating on "lawful use" despite what OpenAI says and the contractual "safeguards" they t
26.
by eoskx 7mo ago
100% this - totally stealing this analogy.
27.
by eoskx 7mo ago
OpenAI: "let's delegate morality to laws that we know are wholly inadequate for AI to absolve ourselves of any moral responsiblity."
28.
by eoskx 7mo ago
Not great? Seems kind of loose language? It isn't OpenAI saying no autonomous weapons use, but only that use must be consistent with laws, regulations, and department policies: "The Department of War may use the AI System for all
29.
by eoskx 7mo ago
"Tonight, we reached an agreement with the Department of War to deploy our models in their classified network. In all of our interactions, the DoW displayed a deep respect for safety and a desire to partner to achieve the best possible
30.
OpenAI agrees with Dept. of War to deploy models in their classified network(twitter.com)
1407 points by eoskx 7mo ago|648 comments

More ›