Live data from Hacker News

Viewing profile — eoskx

eoskx

HN member
Joined
Sun, Jan 21, 2018, 3:52 AM UTC
HN karma
1,190
Public activity
77 items

About eoskx

No profile information was provided.

Recent public activity

  1. comment
    Comment #48279608

    Claude's style is now overuse of sentence fragments, which this "article" has in spades. Fragments are the new emdash or "delve".

  2. comment
    Comment #48279590

    AI generated slop. Why would anyone waste the time to read this if you won't take the time to thoughtfully write something?

  3. comment
    Comment #48174471

    It is unfortunate because the content and subject matter isn't actually bad, but yes, there are definite AI-generated tells here.

  4. comment
  5. comment
    Comment #48165359

    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 g…

  6. comment
    Comment #48164543

    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 bri…

  7. comment
    Comment #48036168

    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 …

  8. comment
    Comment #47641056

    Interesting, but cannot run CUDA or more to the point `nvidia-smi`.

  9. comment
    Comment #47504118

    Also, not surprising that LiteLLM's SOC2 auditor was Delve. The story writes itself.

  10. comment
    Comment #47503274

    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…

  11. comment
    Comment #47502715

    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, An…

  12. comment
    Comment #47502698

    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 …

  13. comment
    Comment #47502678

    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, Ant…

  14. comment
    Comment #47502652

    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 Op…

  15. comment
    Comment #47502619

    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 th…

  16. comment
    Comment #47222107

    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 Passwor…

  17. comment
    Comment #47219395

    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 …

  18. story
  19. comment
    Comment #47212912

    "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 c…

  20. story
  21. comment
    Comment #47210205

    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 afterno…

  22. comment
    Comment #47209505

    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 governmen…

  23. comment
    Comment #47209463

    "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 Pen…

  24. story
  25. comment
    Comment #47209261

    Correct URL: https://archive.ph/WEcM4