HackerTrans
TopNewTrendsCommentsPastAskShowJobs

rdli

no profile record

Submissions

Security Flaws in DeepSeek-Generated Code Linked to Political Triggers

crowdstrike.com
3 points·by rdli·8 mesi fa·0 comments

Secret Service dismantles telecom threat capable of crippling cell service in NY

politico.com
2 points·by rdli·10 mesi fa·4 comments

comments

rdli
·20 giorni fa·discuss
One thing that wasn't obvious in the post: it's usage (token) based pricing, not including in your existing Claude subscriptions.
rdli
·3 mesi fa·discuss
[dead]
rdli
·5 mesi fa·discuss
Cybersecurity/AI seed startup | Founding AI Engineer | Bay Area | Full-time

We're seed-staged, 3 people, building an AI for cybersecurity, looking for a founding AI engineer who wants to learn/apply SOTA techniques for AI. Ideal background is experience building production agentic AI systems (by this I mean something like Simon's definition: https://simonwillison.net/2025/Sep/18/agents/ definition) who also likes to think about WHAT to build and not just how.

We are a Golang/Python shop (although I'm not sure that matters so much any more).

Email [email protected] with subject HN.
rdli
·6 mesi fa·discuss
I get that but just not entirely obvious how you do that for the Notion AI.
rdli
·6 mesi fa·discuss
Securing LLMs is just structurally different. The attack space is "the entirety of the human written language" which is effectively infinite. Wrapping your head around this is something we're only now starting to appreciate.

In general, treating LLM outputs (no matter where) as untrusted, and ensuring classic cybersecurity guardrails (sandboxing, data permissioning, logging) is the current SOTA on mitigation. It'll be interesting to see how approaches evolve as we figure out more.
rdli
·7 mesi fa·discuss
Nothing super-fancy. We have a common GitHub repo in our org for skills, and everyone checks out the repo into their preferred setup locally.

(To clarify, I meant that some engineers mostly use CC while others mostly use Codex, as opposed to engineers using both at the same time.)
rdli
·7 mesi fa·discuss
This is great. At my startup, we have a mix of Codex/CC users so having a common set of skills we can all use for building is exciting.

It’s also interesting to see how instead of a plan mode like CC, Codex is implementing planning as a skill.
rdli
·8 mesi fa·discuss
Polar Sky | Bay Area | Full-time | Founding AI Engineer

Generative AI is rewriting how organizations use data, and breaking traditional security models in the process. We’re a team of cybersecurity, AI, and systems experts building the foundation for secure, trustworthy AI in the enterprise.

We're looking for a Founding AI Engineer who loves building with AI -- crafting context pipelines, integrating and evaluating LLMs into production systems, and delivering AI-native product experiences. You'll work on all parts of Polar Sky, from the data and eval systems to the reasoning, retrieval, and orchestration systems.

Apply online here: https://ats.rippling.com/polar-sky/jobs/a04ed5b7-6202-45e6-b....
rdli
·10 mesi fa·discuss
Polar Sky | Founding AI Lead | Bay Area/Seattle | Hybrid/Onsite | Full-time

We're a well-funded, pre-seed cybersecurity startup focused on data security. I'm looking for a founding AI lead with experience in fine-tuning LLMs (expertise around RL + reasoning models a big plus). This person would own the full AI stack from data to training to eval to test-time compute.

Who's a good fit:

* If you've always thought about starting a company, but for whatever reason (funding, life, idea), this is a great opportunity to be part of the founding team. We're 2 people right now.

* You enjoy understanding customer problems and their use cases, and then figuring out the best solution (sometimes technical, sometimes not) to their problems.

* You want to help figure out what a company looks like in this AI era.

* You enjoy teaching and sharing knowledge.

Questions, interest, just email [email protected].
rdli
·10 mesi fa·discuss
Polar Sky | Founding AI Lead | Bay Area/Seattle | Hybrid/Onsite | Full-time

We're a well-funded, pre-seed cybersecurity startup focused on data security. I'm looking for a founding AI lead with experience in fine-tuning LLMs (expertise around RL + reasoning models a big plus). This person would own the full AI stack from data to training to eval to test-time compute.

Who's a good fit:

* If you've always thought about starting a company, but for whatever reason (funding, life, idea), this is a great opportunity to be part of the founding team. We're 2 people right now.

* You enjoy understanding customer problems and their use cases, and then figuring out the best solution (sometimes technical, sometimes not) to their problems.

* You want to help figure out what a company looks like in this AI era.

* You enjoy teaching and sharing knowledge.

Questions, interest, just email [email protected].
rdli
·anno scorso·discuss
Seems that OpenAI is acquiring Io for $6.4B in an all-equity deal.
rdli
·anno scorso·discuss
I would think that that the NVidia Dynamo SDK (pipelines) is a big difference as well (https://github.com/ai-dynamo/dynamo/tree/main/deploy/sdk/doc...), or am I missing something?
rdli
·anno scorso·discuss
In this analogy, Dynamo is most definitely not like Django. It includes inference aware routing, KV caching, etc. -- all the stuff you would need to run a modern SOTA inference stack.
rdli
·anno scorso·discuss
This is really interesting. For SOTA inference systems, I've seen two general approaches:

* The "stack-centric" approach such as vLLM production stack, AIBrix, etc. These set up an entire inference stack for you including KV cache, routing, etc.

* The "pipeline-centric" approach such as NVidia Dynamo, Ray, BentoML. These give you more of an SDK so you can define inference pipelines that you can then deploy on your specific hardware.

It seems like LLM-d is the former. Is that right? What prompted you to go down that direction, instead of the direction of Dynamo?