aurel.eth

Full-stack dev

[aurel.eth @aurel_dev]

@kepano @_thinking_reed Don’t know what he meant but this CLI is only available if you have the Obsidian Desktop. Not with Obsidian headless for our remote agents to use it

[aurel.eth @aurel_dev]

Couldn’t agree more

[Ujjwal Chadha @ujjwalscript]

Unpopular Opinion: We aren't building the future 10x faster with AI. We are just generating legacy code 10x faster.

Everyone is currently bragging about developer velocity. "I built this entire backend in a weekend!" "AI wrote 80% of my codebase!"

But here is the reality check we are ignoring: Code is a liability, not an asset.

If an AI tool spits out 1,000 lines of functional boilerplate in five seconds, that is still 1,000 lines that a human being has to read, review, secure, and maintain when the dependencies inevitably break next year.

We are treating code generation like a pure productivity win, but we are optimizing for the wrong metric. The bottleneck in software engineering was never how fast we could type. The bottleneck has always been comprehension, architecture, and maintenance.

If we don't shift our focus from "generation speed" to "architectural sanity," the tech debt of the next five years is going to be an absolute, unmaintainable nightmare.

[aurel.eth @aurel_dev]

@dsp_ Funnily enough, the MCP spec defines a server definition that could be loaded in the context and have a similar progressive disclosure as Skills.
But MCP clients chose to load all the tools instead 🤷‍♂️

[aurel.eth @aurel_dev]

@juristr - https://t.co/LLEbyvUAAE from @heyandras
- T3 Code

[aurel.eth @aurel_dev]

@jesseproudman @AskVenice Glad to hear, and please update your documentation to state the reality of your privacy

[aurel.eth @aurel_dev]

@ErikVoorhees @AskVenice Not storing is a good thing, but we’ve been asking about who, where and how the AI inference is done.
Your doc says “a network of decentralised providers”, with no mention of guaranteed privacy from these providers.
And yesterday you contradicted it saying you run it yourself

[aurel.eth @aurel_dev]

@ErikVoorhees @milianstx How is it not documented anywhere?
You privacy page mentions a “decentralised network of providers” and now you say you operate it yourself.
Is it TEE? SSL termination in the TEE? Any attestation?
Otherwise it’s just “trust me bro”

https://t.co/CblX7ICRef

[aurel.eth @aurel_dev]

@ErikVoorhees @kenziyuliu @openclaw @steipete Thanks for the reply. You doc still mentions you use decentralized GPU providers, so my question still applies

https://t.co/ELu04xGbrR

[aurel.eth @aurel_dev]

@ErikVoorhees @kenziyuliu @openclaw @steipete For the open source models that you run, you actually use Akash on decentralised GPUs.
What are the guarantees there is no eavesdropping by the actual computer providers there?

[aurel.eth @aurel_dev]

@adamwathan End of an era

[aurel.eth @aurel_dev]

@ErikVoorhees Until you provide the model with some personal data that likely contains PII.
Unless the open models run in TEE can’t be seen by the inference providers?

[aurel.eth @aurel_dev]

@icanvardar We can ask AI to create it for us

[aurel.eth @aurel_dev]

@chrysb @openclaw If only the MCP spec would recommend that clients are only putting the server description into the context and lazily (instead of eagerly) loading the tools when needed, then we would a very similar token efficiency as the skills.
Would not even need “tool search tool”

[aurel.eth @aurel_dev]

@ErikVoorhees To my understanding, your inference is done on Akash by a decentralised network of GPU. Where’s the guarantee the GPU providers don’t look into the data? Are they running in TEEs?

[aurel.eth @aurel_dev]

@Kautukkundan Good insight on the MCP ecosystem. But, MCP is just a spec for the connectivity.
If consumer apps don't allow technical integration it's not MCP fault.
The "Traditional MCP approach" you also describe is not related to MCP but to the AI apps/agents using it

[aurel.eth @aurel_dev]

@JordanLyall But Opus is not a $15/$75 model anymore, it’s $5/$25 since 4.5

https://t.co/4TC59tMHyC

[aurel.eth @aurel_dev]

@udaysy @RhysSullivan It’s because the MCP specification “enforces” both the server and the client to support the different elements for a smooth OAuth flow

[aurel.eth @aurel_dev]

@ctatedev Thanks 🙏
Will definitely give it a try

[aurel.eth @aurel_dev]

@championswimmer @openclaw Why the need to distinguish a token for LLM vs for a “human”?
It represents the ability to do what the human initially consented for

[aurel.eth @aurel_dev]

@pontusab The web has always been rendering server-side before the rise of SPA, I don’t understand people being conceptually against RSC