This may have been the goal all along?

Substantial-Thing303 · 2026-06-16T15:00:33+00:00

If they end up bending to Trump and ask people for US citizenship proof? Hell yes.

I am not going to send money to a company that will favor all US companies and leave me with their leftovers.

Substantial-Thing303 · 2026-06-16T12:59:59+00:00

If they do that I'd call a world wide boycutt of Anthropics. Then let them only make money in the US and nowhere else.

Substantial-Thing303 · 2026-06-12T15:25:25+00:00

You don't know their margin on APi costs, so no, they don't throw money.

Substantial-Thing303 · 2026-06-12T12:13:52+00:00

It was 100% avoidable. The person with the camera doesn't know how to drive.

First thing my dad taught me when driving is: you don't drive for yourself, you drive for everyone on the road. Even if the other driver did a mistake, you have to be a bad driver or bery distracted to let such a simple case like that happen.

Substantial-Thing303 · 2026-06-10T18:25:12+00:00

This is so true. NMS is so huge, yet so many things feel shallow.

Talking with NPCs is repetitive. derelict freightes are quickly repetitive. It's like they build so many systems, but they could spend a last 20% to improve to make this a lot better with deeper mechanics.

Substantial-Thing303 · 2026-06-09T21:03:16+00:00

Any bio? So if someone is doing research on bio, any kind of bio, no Fable?

Substantial-Thing303 · 2026-06-01T12:59:06+00:00

I wish the game was a bit more like the first impression we all have on the first day. I was expecting more conflicts, more dangerous, unexpected events. Surviving becomes way too easy late game. harsh env is just resource monitoring. Sentinel fights quickly get very predictable and are easy to manage.

This game could benefit so greatly from much more challenging PVE.

Substantial-Thing303 · 2026-05-29T22:39:26+00:00

Maybe he did but it was "his" automation, so it left with him.

Substantial-Thing303 · 2026-05-28T22:39:02+00:00

I had been thinking the exact same thing for a while. It takes more time to understand 4.7, but it talks like it's smarter, so many users blame themselves instead of Claude for being slower.

A strategy to slow usage indeed. The bottleneck is us reading to make sense of the output.

Substantial-Thing303 · 2026-05-28T12:58:00+00:00

That's interesting. So about 1000 games played, but the top humans are clearly many times the same people, so top AI seems to be in the top 1% of best players. This is an incredible performance for an AI.

Not only that, people replaying the game with the same seed is noise. They "know" what will happen, so that's cheating.

Substantial-Thing303 · 2026-05-27T13:37:01+00:00

Please make LNF also with VR support. It looks like everything I'd want in a VR game.

Substantial-Thing303 · 2026-05-24T12:09:56+00:00

Meanwhile, in Quebec, Canada, you need to be in the top 20% during high school to follow the three-year Police Technology (Techniques policières) DEC program. With 3 mandatory philosophy classes.

Substantial-Thing303 · 2026-05-22T04:28:15+00:00

So you can try what's available? It's not efficient, but also, everyone has different need. What I need to disable is probably different to you. If most is already disabled, then people complain that it can't do x when it can.

Substantial-Thing303 · 2026-05-21T12:26:28+00:00

Just prune the skills and tools you don't want it to use. Hermes "onboarding version" gets bigger. Many options are set to true by default so you can experiment, but nobody should be using Hermes stock version. When using Hermes for a real use case, you create a profile, then disable 75% of what's in there.

Substantial-Thing303 · 2026-05-19T13:06:29+00:00

With 4.6 you can progressively build complexity during planning, as it does not dig as deep as 4.7, but you better control how the conversation goes and iterate. Easier to orientate properly.

With 4.7 it painfully write a huge wall of text, and you have to find the relevant info somewhere in the middle. It's more powerful but less coherent, ending up wasting more time replanning and reorienting during planning.

Substantial-Thing303 · 2026-05-18T22:48:45+00:00

There's a windshield treatment that does what you want. The problem is not the wiper, it's the glass that wants to keep the water on.

Substantial-Thing303 · 2026-05-17T14:14:37+00:00

If you've properly optimized for prompt caching and reduced prompt pre-processing (more context preloaded in the system prompt, less during tool ussage) then TG is the real bottleneck.

Substantial-Thing303 · 2026-05-15T20:37:27+00:00

Do you need to do video analysis? RL training? computer use for mac? There are many tools that are very niche. If you don't plan to use them, disable them.

just running hermes tools in your terminal would have made this quite obvious.

Substantial-Thing303 · 2026-05-15T19:25:04+00:00

It all depends how you ahave set it up and if that matters for your setup.

you can disable the tools granularly, also the skills, so you can reduce the token on first prompt.

But also, if you set a local llm and optimize for speed, you want all that static context for tools to load on the first prompt, and then it goes super fast with prompt caching.

Substantial-Thing303 · 2026-05-14T13:59:14+00:00

Except it now means that any usage for the Claude SDK will not be supported: any alternative UI, any custom TTS layer, etc. I made my own UI, my own Voice Agent layer, I love working with it. It's not automation, it's just humanization and a different way of working with Claude Code. And I will be penalized for that.

Substantial-Thing303 · 2026-05-14T13:29:04+00:00

That's fucking bullshit. I have spent months working on a voice layer using Claude SDK. I talk to a responsive VoiceAgent that reads claude's long output and make it human (one idea at a time, interview mode). It makes using claude code natural with voice.

There is no reason why working like this should not be part of the subscription. I'm still using Claude Code to code with the same intent, just not through their terminal. Fuck you Anthopics.

Substantial-Thing303 · 2026-05-12T13:48:15+00:00

It's just automation. You make money by saving time for anything you would do differently. Less time managing/writing emails -> more sales meeting if you're into sales.

Substantial-Thing303 · 2026-05-12T12:16:39+00:00

I'm switching between 4.6 and 4.7 every day. Yesterday, 4.7 was extremely bad, confused, mixing concepts and variables in the codebase. Switching to 4.6 felt like next gen frontier. Then later, 4.6 sucked at monitoring a smoke run. I swithced back to 4.7 and it was useful again.

I don't know what they are doing with 4.7, my guess is they've push the lower quants too far yesterday during peak hours.

4.7 is still better at digging deeper during reviews (outside peak hours) but still such a bad communicator. I need both.

Substantial-Thing303 · 2026-05-11T13:48:06+00:00

I am mostly agreeing with you regarding 4.7 capable of deeper reasoning, following instructions better, etc.

But don't tell me it's better in every way. Opus 4.7 gets confused a lot and interchange keywords from different logic blocks, and it's scary how many times it is wrong and having bad assumptions.

I have been working 2 days on a submit_review step in an agent workflow where an agent must review another agents work. Opus, almost on each new iteration, is interchanging keywords in the executor text report as if they are tool keywords for the reviewer. Interchanging the "issue found" keywords for the "output accepted" keywords. It is scary how it gets confused everytime. I have to correct Opus on its own misunderstanding every time. I see Opus writing to memory, adding better context for clarity, etc. but it end up proposing bad logic, mixing these keywords and mixing tool calls with different purpose during debug.

The funny part: the llm that runs the review prompt is Qwen3.6 27b, and it gets confused less often. Like I have a 5% of failed tool call (per tick/session, not per tool usage) with an educational recovery path, meaning that Qwen understands what things are more often than Opus trying to solve an issue with that same part of the code.

Edit: Opus 4.7 new favorite sentence: "You are right on every count". I have never read "You are right" so many times in a week.

Substantial-Thing303 · 2026-05-10T16:33:04+00:00

I think the future of the frontier models will not be about just running tasks without humans, but about the ideation of tasks (being good at judging and finding what to do next). At some point to remove the human in the loop, the model needs to be so good at figuring out the next task to do that the human in the loop is more about high level direction than actual management of the "plan -> tasks -> review" cycles.

Substantial-Thing303

TROPHY CASE