u/Firereign

I’m not sure if it’s intentional, nor if it changed in the 3.9 update, but I accidentally discovered yesterday that Frame will connect to the Machine’s internal 6GHz access point if the dongle is not plugged in.

My Machine is connected to my network via Ethernet, so its internal Wi-Fi is not being used for anything otherwise. Hence why I’m not sure whether this is accidental; it might not happen if the internal Wi-Fi is connected to a standard network.

That attitude? Right there? Yeah, that’s that point about you.

You could’ve used the opportunity to learn how to make better use of the tools that you’re paying hundreds a month for, instead of entrenching yourself in cognitive surrender.

This sub? Inane shit like this plagues most of Reddit at this point.

Anthropic is so full of themselves.

Less so than the clueless sheep that bleat on Reddit whenever they hit a stumbling block that would take more than a second of effort to overcome. Especially if it risked learning something.

Because it's obviously all Anthropic's fault. It can't possibly be a skill issue.

Meanwhile, I've thrown over 100b tokens at a reverse-engineering project over the last 6 months. Claude's happy to work on it.

I'd be kinder about your lack of ability, because I didn't have the faintest fucking clue what I was doing when I started my project, but I didn't choose to bitch on Reddit and point fingers elsewhere every time I hit a stumbling block. Your comments make it quite clear that you aren't interested in learning.

Sure. But I don't need it.

I mean, it would be fun to be able to say "I use Mythos", but what does it gain me over Fable? Again, my main point is that I'm not having issues with refusals or classifiers.

I'd never heard of Ghidra when I started this project. I told Claude what I wanted to do, and it suggested Ghidra. It installed it, it runs Ghidra headlessly to analyse and export functions, it organises the snippets that come out, it makes inferences and documents the results.

Classifiers were trigger-happy with Fable 5 early on if one session spent too long thinking about memory offsets. It was more than happy to chuck Opus agents at it. And Fable 5.1 has spent plenty of time and tokens deep in this stuff without classifier intervention.

I've not twisted or lied about what I'm doing. At no point has it stopped to question legality or ethics. My project CLAUDE.md states exactly what we're working with, and Claude is well aware that having the original assets in decrypted form in the first place necessitates a DMCA violation.

So, I'm still left wondering WTF people are asking Claude to do when it refuses to reverse-engineer something.

For me, the only topic where it "locks down all the time" is anything involving unauthorised decryption.

Working with Ghidra? Trawling through a binary? Reimplementing someone else's program? It's happy to do all of that in my usage.

I'm not a super-special person with privileged access. I'm a random nobody with a Max plan. I'm using the same models, and going through the same classifiers, as the next nobody.

So: what are you doing with it that's causing it to "lock down all the time"?

Because I’m a random individual with a personal Max plan doing this on my own time for fun and personal development. They’re not about to give me access to Mythos.

Besides, I’m having zero issue chucking Fable and Opus at the project. That was kinda the point I was making.

Because REA is trending, people who don't have the faintest understanding about any of this stuff are trying to use it. Which, in and of itself, is fine - I had no fucking clue what I was doing when I started my project.

The difference is, I started it as a learning experience, expecting it to take months (and hundreds of hours of my own time), using it to both learn about RE and about agentic engineering. Getting a neat end result out the other side is a bonus.

On the other hand, a ton of people have installed REA, thrown Claude at "reverse-engineering" a bit of software, gotten annoyed when it won't one-shot it for whatever reason (classifiers or otherwise), and then bitched about it on Reddit or elsewhere.

Nope. Claude Code, Max 20x plan.

I average ~5-6bn a week. Doubled this week as I pushed to use the one-time reset before it expired.

Rarely, and not in a while. I can't remember the last time I've seen a classifier intervene on this project.

I don't do anything to work around them. My CLAUDE.md states pretty plainly what the project is. I don't need to reframe what it's doing, nor coerce it into using specific wording.

Despite the incessant whining claiming that Anthropic are trying to lock things down, the classifiers are a lot less trigger-happy than they used to be. I started the project right when Fable 5 (first) launched, and it would hit classifiers if one session spent too long delving into the original binary.

Meanwhile, I've chewed through a further 12 billion tokens over the last week, across Opus 5.5 and Fable 5.1, on a months-long reverse-engineering project, with no issues.

Said sessions over the last week have included using Ghidra to export functions, attempting to infer what they do based on the resulting pseudocode, driving and iterating on a harness around the original binary to test inferences, documenting said inferences in great detail, expanding on and fixing up the reimplementation, and pre-screening visual test cases in the reimplementation. Largely autonomously. In a project that makes no attempt to hide what it's doing.

When I see people complaining that it's nerfed or can't do anything, I really wonder what the fuck they're talking about. One nice upside is that it helps to assuage my fears over job security.

You are technically correct. Coolant is warmer after exiting a component block. Where your understanding falters is on the thermodynamics.

Water has a very high heat capacity. It takes about 4.2kJ to heat 1kg of water by 1C. That's why boiling water takes a lot of energy.

If you were running a fairly slow loop flow rate of 120 L/h - i.e. 120 kg/h - that's 1kg passing through a part of the loop every 30 seconds. (120 L/h is about 0.5 GPM, for those who use silly units.)

If you have a component dumping, say, 140 watts into the coolant, that's 4.2kJ of energy every 30 seconds. So, 4.2kJ into 1kg - i.e. a 1C rise.

So, if you had a monster GPU chugging through 720 watts, and a low flow rate, you'd be seeing a 5C change. Most loops aren't going to see that kind of heat load.

The maths is the same for radiators, dissipating heat instead of dumping it into the coolant.

Why have a radiator then, just run a loop through all components.

The coolant is transporting heat to the radiator. It just doesn't need to change in temperature by much to do it.

My first Fable 5 session had an estimated API rate cost of about $800. (Subscription plan, so I - thankfully - don’t pay API rates.)

Fable 5.1 dropped the cached read cost from $1/MTok to $0.25/MTok. Sounds minor at a glance, next to the $50/MTok output cost.

So, I went back and calculated how that change would’ve impacted that first session. It would have cut the “cost” by almost half.

Long sessions, with many rounds, in my experience, are dominated by cache reads. It’s not unusual for me to see ~500x as many cache read tokens as output tokens.

So, I went back again and recalculated what that first would’ve “cost” with caching disabled. Rough estimate: $4,500.

To be clear: I’m talking length in terms of round-trips. This does not necessarily mean running to long context lengths. One round might input 100k tokens through a bunch of reads. It might input 100 tokens from a simple tool call.

Your gatekeeper is an idiot.

Edit: Thought I’d take a look at the session I have open right now. It’s not done much. Fable 5.1 sitting at 124k context. 50 rounds, 5M cache read, 100k cache writes, 40k output, no cache misses. $5 at API rates. If caching was turned off and each of those cache reads was a fresh input, the cost would be $50 in input tokens alone.

...Really? Like, once it started hitting you with congestion fees, you'd have been plugged in for, what, another 10 minutes? Just suck it up and pay the extra fiver, for goodness' sake.

Or just unplug at ~85%, and find a different charger closer to the cabin if you really need extra juice. You're not exactly in the middle of nowhere. If I check Zap-Map, there are >=100kW fast chargers in every direction. Going to Land's End? There are 175kW Shell chargers at Hayle, and 160kW Instavolt units at Helston.

The steering wheel is physically quite small, and the steering rack has a very fast ratio, so you’re likely moving your hands a lot less than you’re used to. If you haven’t already, play around with the steering weight/assistance in the options to find what you’re most comfortable with; I prefer it in the heaviest/least assisted setting.

Eh...the fastest car in the world can only go so fast because speed limits and traffic exists.

And yet I still find plentiful opportunities to enjoy my car's acceleration - and for that matter, its handling - while staying safe and on the right side of the speed limit.

If the vast majority of your time driving is spent stuck in stop-and-go traffic then, yeah, it makes a lot less sense.

you know what's not fun? Replacing those damn tires every 10K miles

My stock PZeros have 5mm of tread left after 13k miles.

Instant torque doesn't just permit breakneck acceleration. It gives precise control over power delivery, and changes in power delivery.

Turns out that, when you're not hammering the car, using that control over power delivery to drive smoothly - and to stop smoothly, instead of driving right up to the lights then slamming on the anchors - does wonders for wear.

I’ve had my HD800S for…something like 8 years at this point? I’ve not treated them with the care that most would. They’ve sustained multiple drops. Headband is absolutely fine, as is the rest of the headphone, aside from a spot of paint wear.

To relate kW and kWh to the way you’re probably used to thinking about petrol/diesel:

“kWh” is a unit of energy. Think of it like the quantity of fuel - you’re probably used to thinking of litres or gallons of petrol.

“kW” is a unit of power. Or, the rate at which energy is moving around. You’re probably used to thinking of miles per gallon; “kW” is similar to thinking of “gallons per hour”. (So, the amount of fuel added or used per period of time.)

Now, here’s the neat trick: one “kWh” is the amount of energy you get from one kW over one hour. It’s slightly different to the petrol terminology, because the time part isn’t where you’re used to: saying “I drew one kW, for one hour, so I used one kWh” is like saying “I consumed one gallon per hour, for one hour, so I used one gallon in total”.

A domestic wall socket supplies 2.3kW at maximum. Charging isn’t perfectly efficient, so call it 2kW - this makes the maths easier too.

The car’s battery is approx. 60kWh. A full 0% to 100% charge would take 60kWh divided by 2kW: about 30 hours.

In practice, you’re probably not going to be charging from 0% to 100%. If you plug in for, say, 7.5 hours overnight, that’s about 25% of the battery. That’s a decent amount of daily driving covered.

It's two completely different experiences, that appeal in different ways, to different people.

Yeah, the Cayman is slower. It's not designed for straight-line speed. And if the speed is part of the thrill for you, a Cayman is never going to satisfy.

I have a Highland 3P, and I just can't imagine anything out there suiting me like this car does. The instant torque and throttle mapping give me a feeling of control over power output that I find engaging and satisfying, no matter the situation, and I love that it can go from calm and smooth to ludicrous rocket ship, and back again, in an instant.

Others find the lack of theatre to be very dull. They get tired of getting a few seconds of breakneck acceleration here and there, with no noise and no mechanical engagement. They'd rather take longer to accelerate while rowing through the gears and taking a flat-6 to the redline. They'd rather have to use all three pedals and a gearstick as they go through the twisties, in a lighter car, with a steering setup that communicates more about what's going on between tyres and tarmac.

Both perspectives are valid. Just because /r/cars loves to circlejerk about steering feel, lightness, manual gearboxes, and "slow car fast", doesn't mean that you are going to find joy in it.

Try a few different lightweight sports cars and see if any of them click with you.

Most of these have been discussed to death, as you’d be able to find through a basic search.

Yes, the auto-wipers are shit. The “why” is because of a core philosophy to avoid having redundant parts, so they rely on the front-facing cameras for detecting water instead of adding a dedicated rain sensor.

Auto-park isn’t included because the standard auto-park behaviour sucks, and the “improved” branch builds on the rest of the FSD software stack. They can’t be decoupled, and Tesla deems that they can get £100/mo for it. (I’d never trust it. To each their own.)

A speed limiter is one feature I do miss. The “why” is because facilitating it with the rest of their UI/UX philosophy would be… difficult. To say the least.

No CarPlay/Android Auto because they want you using their services, which facilitates data collection. Data is valuable. Same reason they push you to use their navigation. For which there are practical benefits: it’s very good at estimating energy usage on long trips, and is designed to plan charging stops for you and to make the “EV ownership experience” easy. Given how awful it can be with other brands, this is understandable. But if you look closely at the screen, you’ll notice that the actual map data comes from Google.

No 360 view because the car’s cameras aren’t positioned to facilitate it, and they don’t want to add dedicated cameras for it. I find it very easy to judge, with the car’s excellent front visibility and multiple high-res camera feeds. To each their own.

If you’re asking open questions like that, without providing context, and without doing your own research, then here’s the advice: don’t.

Custom watercooling is complex. If you need someone to tell you these things, then it’s not for you.

Yeah, that ain’t accurate in 2026.  Phones have been pushing sensor sizes ever higher.

An iPhone 17 Pro has a sensor that matches the Go Ultra in size, exceeds that of the Ace Pro 2 and any DJI Action, and isn’t far off the Luna Ultra and Osmo 3/4.

Furthermore, most action cameras have a very wide FoV. Similar is true of vlogging cameras. Chuck on dewarp and you’ve thrown that sensor size advantage away. If you’re shooting a shot that’s better framed by the FoVs typical of the main cameras on high-end smartphones, they’re putting a lot more of their sensor area on the subject.

Really, these are different devices with different use cases. Action cameras have their niche - it’s in the name. The gimbal-head cameras are very versatile. But, if someone just wants to point a device at something and get high-quality video? High-end smartphones have been very good at that for a few years now.

That’s disappointing, and a very real concern that Tesla should absolutely be criticised for.

That said, the latch failing to disengage in normal use - when the electronics should be operating normally - is not the same as whether they fail-open in a severe crash, where I’d expect unexpected loss of low-voltage power, perhaps combined with an accelerometer signal, to fire a backup release.

I’d hope the engineers were sufficiently considerate and intelligent to make the latches fail-safe on loss of power, given the safety focus across the rest of the car.

People will quote reports of people stuck in their cars after a collision, to which I’d point out that a collision severe enough to knock out power to the door switches and latches is not unlikely to have deformed the frame in such a way that the door is jammed shut, irrespective of whether the latch is operable.

To be clear: it’s a bad design, they are an issue, and I’d welcome a revision. I’m just inclined to think that the odds of it mattering are vastly smaller than most of the loud critics suggest: there’s been a severe crash, power is lost, doors failed latched instead of safe, passengers need to get out before emergency responders can assist, but they are sufficiently unharmed and sound-of-mind to make egress possible, and the passenger cell is sufficiently intact that the latch is the only blocker?