user43928

The crypto economy isn't real, it's a pointless wealth redistribution scheme.

Anyway, that and your question are hardly relevant to the fact that Binance and their cabal own the crypto exchanges and consequently could manipulate the price to reduce the size of their obligation denominated in crypto rather than currency or stable coins.

Surely with all their security programs, they would run testing on the ChatGPT implementation.

I speculate that the AI didn't find this and that human effort and intuition for where to look were needed to find this vulnerability.

Crypto isn't foreign currency. The price may fluctuate wildly based on sentiment and action taken by exchanges such as Binance, which would directly impact their obligation here.

Comparing crypto to actual currency typically connected to large, real economies is not relevant here.

It's an important distinction.

$3.5B stolen was "stable coins", which you could equate to a piece of paper with a dollar amount written on it.

Those are largely freezable by the issuer of the paper.

Then we have $2.4B in Bitcoin and ETH stolen. Those are not directly freezable.

However, if that does create a liquidity challenge for these exchanges, what if the price just so happens to drop by 60% after trading is restricted? That liability might shrink in actual value.

Only tangentially related, but recently when I was working on a feature using iCloud, I noticed that it's just using Google storage APIs. I read Apple uses AWS S3 too.

Supposedly Apple holds the encryption keys on their own infra, but I still found it interesting how they are just reselling Google Cloud storage here.

Cursor made Grok Bot and is working on the Grok models.

I wouldn't say it's obviously unsuccessful.

More of whatever you had in mind.

Clearly there are few limits to what you can implement with AI agents today.

Depending on the complexity, you will spend a lot of time QA testing, giving feedback, and iterating.

One can take shortcuts such as porting existing software, as you mentioned. Many are just content publishing crappy novel software that they barely tested.

You don't need to do that. No one is forcing you not to QA test and iterate until you have a good product.

That's a fair point, and with newer package managers, at least the dependencies no longer automatically execute build scripts on install.

There were a few common sources of large runtime dependencies in the past. Like the browserify Node polyfills, babel-polyfill and runtime with core-js, React -> fbjs, Material UI -> JSS and plugins, styled-components.

It's also not trivial to tell whether a dependency you listed under devDependencies is actually imported and consequently bundled into your production build.

Since today we no longer need polyfills and the modern stack with Vite etc. doesn't have a sprawling dependency tree, I think things are now looking much better.

Interesting. The Grok Bot computer connects to your box via SSH and using herdr it can work well with Claude Code and Codex there?

I started using Grok Bot a few days ago and I have seen zero screwups.

I don't know what I'd need a channel for, creating bots/personas seems more natural.

Adding credentials is essential, contrary to what the author of the article said. I gave it my library login and it can fetch newspapers for me instead of me clicking through the app every day.

When I had to provide a GitLab token, it nicely spawned a box for me to save the credential.

  - What did not work well -

Voice calls. The quick responses are often dumb while the proper model does the thinking, and in the middle of talking to me it would stop to do work or searches. It did not feel realtime.

Permission settings. There is a form where you can automatically allow actions you describe in natural language. I tried to allow it to run Claude on my computer or Send certain emails automatically, but the settings achieved nothing.

Coding. I wasn't able to make it use Claude, and its own work is worse than me using Opus 5.5 in Claude Code.

  - What worked well -

Planning flights, accessing newspapers from my online library, checking stock in online stores, sending regular summaries of events and weather to plan activities.

No, because contrary to keeping Daylight Savings Time as it is, that would come with other tradeoffs.

Probably at a point where my worries will be when my team of construction robots finishes my villa, rather than whether companies are prepared to ditch source code.

That's simply not true.

Until spec files can be worked with so efficiently that we can just regenerate the binaries from them for every change, what you said makes little sense.

You're going to need an intermediate portable form of storing the program. It so happens that all the tools and AI are optimized to work with source code.

Then you probably haven't worked much with JS.

The Jest test runner alone has 250 dependencies in its latest version, and v25 had over 500.

Spy seems inappropriate if you can only read information stored in this side channel intentionally.

We'd first need to establish that this side channel leaks usable information during regular use.