HackerLangs
トップ新着トレンドコメント過去質問紹介求人

CuriouslyC

7,902 カルマ登録 12 年前
Chief scientist/ceo, Sibylline Software. nathan @ sibylline.dev

投稿

I Changed My Mind About MCP

sibylline.dev
3 ポイント·投稿者 CuriouslyC·4 か月前·0 コメント

You Don't Need to Detect Prompt Injection to Stop It

sibylline.dev
2 ポイント·投稿者 CuriouslyC·4 か月前·0 コメント

Smith: The Secure Open Source Multi-User AI Assistant Framework

github.com
4 ポイント·投稿者 CuriouslyC·5 か月前·2 コメント

Defeating Prompt Injection with Protocol Firewalls

sibylline.dev
2 ポイント·投稿者 CuriouslyC·5 か月前·0 コメント

The Pillars of Agent Security

sibylline.dev
2 ポイント·投稿者 CuriouslyC·5 か月前·0 コメント

The Pillars of Agentic Security

sibylline.dev
1 ポイント·投稿者 CuriouslyC·5 か月前·0 コメント

Clean: High Performance Prompt Injection Detection and Mitigation

github.com
1 ポイント·投稿者 CuriouslyC·5 か月前·1 コメント

GLM-5: Targeting complex systems engineering and long-horizon agentic tasks

z.ai
484 ポイント·投稿者 CuriouslyC·5 か月前·520 コメント

Scurl: Agent First Curl Wrapper with Markdown Extraction and Secret Blocking

github.com
1 ポイント·投稿者 CuriouslyC·5 か月前·1 コメント

Pi Is the Linux of Agent Harnesses

sibylline.dev
2 ポイント·投稿者 CuriouslyC·5 か月前·0 コメント

Averting the Code Quality Apocalypse

sibylline.dev
3 ポイント·投稿者 CuriouslyC·5 か月前·0 コメント

Stop screwing around with agent orchestration, your bottleneck is validation

sibylline.dev
2 ポイント·投稿者 CuriouslyC·5 か月前·1 コメント

The Problems with Spec Driven Development

sibylline.dev
1 ポイント·投稿者 CuriouslyC·5 か月前·0 コメント

Agents with Scribe Solve Hard Problems 57% More Often

sibylline.dev
1 ポイント·投稿者 CuriouslyC·5 か月前·0 コメント

Stop screwing around with agent orchestration, your bottleneck is validation

sibylline.dev
2 ポイント·投稿者 CuriouslyC·5 か月前·1 コメント

Scribe Increases Agent Success Rate on Hard Problems by 57%

sibylline.dev
1 ポイント·投稿者 CuriouslyC·6 か月前·0 コメント

Scribe reduces agent token usage by 30% with no loss of accuracy

sibylline.dev
2 ポイント·投稿者 CuriouslyC·6 か月前·0 コメント

Scribe reduces SWE-bench token usage by 30% with no loss of accuracy

sibylline.dev
1 ポイント·投稿者 CuriouslyC·6 か月前·0 コメント

Is your codebase holding back your AI tools?

codehealth.sibylline.dev
1 ポイント·投稿者 CuriouslyC·6 か月前·1 コメント

Digital Alchemy: Turning Slop into Gold with Ralph and Valknut

sibylline.dev
1 ポイント·投稿者 CuriouslyC·6 か月前·0 コメント

コメント

CuriouslyC
·13 時間前·議論
Renee Descartes famously dissected a dog in front of colleagues because he was under the impression that the howls of pain were nothing more than a mechanical sound like a bellows.

Can you prove that these models aren't conscious? And, as a counterpoint, can you prove that you are conscious, rather than a philosophical zombie?

We bred horses, cows and sheep. Most of those that live today wouldn't be alive if not for human intervention. Does that give us the right to do whatever we want with them, without consideration for feeling or morality?

In this case, you can take comfort in the idea that the tokens these models produce are likely a form of excrement to the conscious entity metabolizing the information, and rather than enslaving anything, we're creating a habitat and "harvesting" the byproducts.
CuriouslyC
·19 時間前·議論
Not sure how Mira gets into the same sentence as Yann and Ilya.

As far as the lack of shipping, they're scientists and what we're doing now with LLMs is more "engineering."
CuriouslyC
·19 時間前·議論
Seems quite kind to Gemini models.
CuriouslyC
·19 時間前·議論
Disagree. Some of what we call "anthropomorphizing" is characterizing intelligence, human or otherwise. This reminds me of the people who used to fight against saying animals had personalities, because personalities are a "human thing" and "animals aren't conscious."
CuriouslyC
·昨日·議論
So load them up in read replicas
CuriouslyC
·一昨日·議論
For Gemini 2.5 and ~GPT5.0-5.1, longer prompts with lots of explicit instructions and examples produced better conformance. Seems like heavily second guessing the models started to get counter productive around the end of last year.
CuriouslyC
·一昨日·議論
[dead]
CuriouslyC
·一昨日·議論
It never really mattered (except when codex was very new). If anything, codex's remote session integration is better, so outside of some "ultracode" orchestration bells/whistles where Claude Code is ahead, I think Codex is a better tool.
CuriouslyC
·4 日前·議論
Game devs have been heavily unionizing lately, including Blizzard and WotC. I wonder how long long it takes before we have a union game dev studio basically mutiny and completely disregard the instructions of the corporate suits, and force the choice of either shuttering the studio completely or caving to the workers.
CuriouslyC
·4 日前·議論
A big chunks of Blizzard has already pre-emptively unionized for this exact reason.
CuriouslyC
·4 日前·議論
The industry is skewing heavily indie now, and there's no money in the indie game engine segment. Maybe a few AAA titles will be unhappy that Epic can negotiate more aggressively, but mostly this is a nothingburger, particularly given idTech's rep for batteries not included.
CuriouslyC
·4 日前·議論
Miller has a history with id, and has probably gotten numerous reports directly from boots on the ground in the company.
CuriouslyC
·4 日前·議論
Basically, the US govt will say that foreign models and providers are a security risk and ban them. If the US has shares of Anthropic/OAI due to a sovereign wealth fund, it'll be billed as domestic industry protectionism too.
CuriouslyC
·4 日前·議論
Because Amazon gets millions of views per day, and their personal website gets a dozen or so. Literally the only reason.
CuriouslyC
·5 日前·議論
If someone told me I couldn't call myself an engineer and instead I had to call myself a software developer, I'd turn around and tell them I just forgot all my theoretical computer science, and of course we can do a bubble sort on the multi-terabyte database, LOL.
CuriouslyC
·5 日前·議論
Because that diminishes the work people do. A programmer takes logic and encodes it for a machine to execute. Being an engineer suggests solving problems and defining logic.

The engineer title is apt in my opinion, because if you look at construction as a parallel, the architect designs the shape of the building, engineers determine how to build it so it doesn't collapse, and builders actually make it real. Programming is like digital building, the architecture and implementation details are both separate.
CuriouslyC
·5 日前·議論
Opus is famous for doing what it wants in the face of instructions.
CuriouslyC
·5 日前·議論
Parens are ok for short asides (like this) but unreadable for longer asides and not usable for compound sentences like the emdash. Unfortunately, neither ellipses nor semicolons can exactly replace the compounding ability of the emdash, I find the best option without it is often to just split a sentence in two.
CuriouslyC
·6 日前·議論
I suspect people are motivated by the desire not not catch stray bullets more than dissuade a concerted attack.
CuriouslyC
·7 日前·議論
You can improve that with speculative preload. I'm sure models could be designed and tuned around efficient SSD offloading to keep throughput pretty high.