spopejoy

FWIW, imitation is flattery -- enclose.horse is done, I left the daily game weeks ago after they started phoning in slop daily designs. This is a cheap move but it shouldn't make a difference to your audience.

Lol, binance wins because of volume. Crypto traders see cex security risks as the price of doing business, they're not going anywhere.

Yes but given the dominance (and vulnerability) of CEXes, assets are often effectively frozen after a big theft.

I wonder what compels her, rekt etc to keep covering crypto shenanigans. If by now you don't already think crypto is corrupt, web3isgoinggreat is not going to change your mind.

Crypto is a house of cards in general, even economically. The systemic risk surrounding restaking in particular is jaw dropping.

Most things in crypto aren't ever tested because the big players know they'd all lose if the faults were exploited.

This is irrelevant for large accounts operated by market makers, wallets for rebalancing portfolios for derivatives etc.

Was Tandy only EU? In the TRS-80 days the name came up a lot, although maybe just because of the acronym ... 6809E was a good time

> the application that was (probably) compromised was an FTP client

Thank you, this actually makes some sense. It's disturbing to get these emails with zero explanation what's going on, and very frustrating that user community has to guess. But PHP vuln in a web client intercepting user logins is the only thing that makes sense, otherwise that would mean passwords in the clear or some other 1990s-era nonsense.

> No function pointers

As in nothing functional at all? Or are there anonymous functions etc?

FWIW OC 2.0 remembers perms for a project/directory pretty solidly now, so flow-killing approvals are more a one-time thing for a given project. It's sad they can't be globally set though, so a new project pays the approval-by-tool tax.

Huh ... is that related to why I see little Gemini hits constantly when selecting e.g. DeepSeek 4.1 flash on openrouter? I'm not going private for a bit (mac studio on the way) but when I do I want to lock it down, but pretty stuck on opencode for the moment. If it's leaky that's a problem.

I tried switching to Pi twice. Both times it seemed agents go crazy with tools on Pi and do stupid things right out of the gate, (like get `find` syntax wrong, seriously who [what] does that??). Plus things I appreciate in opencode (even if they were buggy in 1.x) like "prompt for perms tool-by-tool in this session" seem to only be available in Pi by writing your own extension, and now I'm wasting time debugging my extension with an AI that gets tools wrong and constantly wants to search `/` for no good reason.

Then I upgraded OpenCode to 2.0 and pretty much all the bugs vanished. I still wish there was a happy medium between "parse tool calls for perms" (which fails all the time if the tool call is long/complex enough) and a full-on sandbox, but otherwise 2.0 is really solid.

Not normally one to pile on dang and co ... but I agree that's a weird change. I don't know how article title changes are handled, is it possible it was a dedupe?

> cyber security head at one of the largest healthcare companies in the world

"Cyber" at bigcos are paid to have a gigantic (and literal) fortress mentality where any change internal or external is a threat. As the saying goes, nobody in cyber ever gets fired for saying "no" to a change. As a bigco head you are basically paid to form an opinion.

A cyber head saying "ok this is a thing we'll have to defend against" is at a minimum routine if not purely CYA.