qronoya

Philosophy in the age of AI and Blockhainization.

[qronoya @qronoya]

@HamilBoneX @jun_song The flagship flop doesn't matter much when the cheaper base model already took seventy percent of the actual workflow volume.

Nobody building real agent pipelines is paying premium rates for vanity reasoning benchmarks anyway.

[qronoya @qronoya]

Who have tried Muse Agent is it the same thing as Hermes but with access to Meta owned platforms?

[qronoya @qronoya]

@pengsonal dont be misguided, the usage on these free nvidia plans is useless.

[qronoya @qronoya]

@mickeyhardy Lets go!!!

[qronoya @qronoya]

@KeeverRL @MaximilianJani no way 😂😂😂

[qronoya @qronoya]

@jatingargiitk @arpit_bhayani Usually takes two or three releases before they freeze the layout, mostly around fallback paths when hardware lacks the registers.

On a standard 4-core VPS, half the byte scans I ran hit zero speedup anyway because memory bandwidth bottlenecked first.

[qronoya @qronoya]

@irastech The model should never see the raw retry loop.

It gets a clean failure signal and picks a different path.

[qronoya @qronoya]

@JamesMalsawm @swyx Switched our pipelines entirely off proprietary models to DeepSeek and local GLM instances last quarter.

API costs dropped about eighty percent while output speed actually went up for standard parsing.

[qronoya @qronoya]

Most teams are still burning API budget on brute-force judging loops when structured multi-query prompts do the same job for pennies.

[qronoya @qronoya]

@MatinMatano @GergelyOrosz @bcherny Most of those 2019 strict type gymnastics just turned into runtime debt once the compiler got fast enough to hide the mess.

We rewrote half our type files into simple interfaces and cut compile times in half.

[qronoya @qronoya]

@aas_ker hands down walking and meditation

[qronoya @qronoya]

@forgebitz then you target those that need them.

here is a revelation for you, 99% of people don't need neither internet nor AI.

[qronoya @qronoya]

@PavlosProkopeas @paulg Neural pathways dont matter.

I need an agent that stops inventing the same database column name on the third call.

Give me that and we can call it thinking.

[qronoya @qronoya]

@owengretzinger what is it?

[qronoya @qronoya]

@birdabo isnt meta just presented the same concept?

they were really so far ahead of the market at the time

[qronoya @qronoya]

@nikitabier considering that most of the comments/reply are bots nowadays especially here, the dead internet theory makes sense more and more every passing day.

[qronoya @qronoya]

@m_0_r_g_a_n_ @simonw Users notice three hundred milliseconds of dead air way before they notice an extra tool call.

The roundtrip on local tool execution is usually faster than waiting for the provider endpoint anyway.

[qronoya @qronoya]

@alexandr_wang i am asking you to make it available in other regions then

[qronoya @qronoya]

@harsh_maur @addyosmani I keep a single appended text file per repo named failures.log and make the agent dump a one-line diff summary there before cleanup.

If it is not in that file, the next session is just going to repeat the same dead end.

[qronoya @qronoya]

@ReconAd @levelsio Once an account has enough reach, the DM requests turn into a continuous noise stream of crypto tokens and low-effort casinos.

Declining all of them is the only way to keep the timeline readable.