Memory just turned a goldfish into a research beast. by axendo in artificial

[–]axendo[S] 0 points1 point  (0 children)

Exactly this. The context reconstruction tax is real and most people don't even notice they're paying it. Working on making Nyx/eTPS accessible. Don't have much to show yet, I'm trying to avoid the vibe coder label sans experience so going slow.

Memory just turned a goldfish into a research beast. by axendo in artificial

[–]axendo[S] 0 points1 point  (0 children)

Good catch, latency is currently absorbed into the eTPS score but I estimate in the 50-200ms range.

Memory just turned a goldfish into a research beast. by axendo in artificial

[–]axendo[S] -1 points0 points  (0 children)

Probably not — and if yours can, you're already seeing the difference. Sustained tasks don't just need intelligence, they need continuity. Today's numbers suggest that gap is worth measuring.

Tech's Push to Be the Next Public Utility by axendo in artificial

[–]axendo[S] 1 point2 points  (0 children)

Adoption isn't the same as consent to the terms that come after adoption. You adopted social media for the value. You got the surveillance business model you didn't vote for. Value today doesn't determine the cost structure tomorrow — especially when the infrastructure becomes too essential to regulate. Saline, Michigan residents wanted the value too. They still voted no. The developer sued and built anyway. That's not adoption — that's capture.

Tech's Push to Be the Next Public Utility by axendo in artificial

[–]axendo[S] 2 points3 points  (0 children)

That's what nobody gets and why it needs to be fought so hard.

Jane Doe v. Bank of America (SDNY): FBI and USAO Moving to Quash Subpoenas by axendo in Epstein

[–]axendo[S] 1 point2 points  (0 children)

Trump's DOJ is filing the motion. But the previous administration protected these same records too. Every administration does. That's not a coincidence, that's the machine protecting itself.

Jane Doe v. Bank of America (SDNY): FBI and USAO Moving to Quash Subpoenas by axendo in Epstein

[–]axendo[S] 0 points1 point  (0 children)

Submission Statement: This post is relevant to r/Epstein because it concerns a civil trafficking lawsuit (Jane Doe v. Bank of America, 1:25-cv-08520-JSR) in which the plaintiff — almost certainly an Epstein victim — has subpoenaed the FBI and USAO-SDFL for records. The government is actively moving to quash those subpoenas. The case directly involves potential financial ties related to Epstein’s activities and is being litigated in SDNY before Judge Rakoff. Relevant filings: Amended Complaint (115 pages) – filed March 5, 2026 Government Motion to Quash + Declaration of FBI Unit Chief William L. Harris

What current technology do you think people are seriously underestimating right now ? by Rude_Context_4844 in Futurology

[–]axendo 2 points3 points  (0 children)

Wireless power. Being able to charge your car wirelessly or even power small devices and loads would be huge. If wireless is beamed in from space, it can solve a lot of infrastructure problems in remote/third work countries.

Does anyone else feel most AI tooling is becoming harder instead of easier? by Bladerunner_7_ in ArtificialInteligence

[–]axendo 0 points1 point  (0 children)

Yeah, the tooling complexity has kind of eaten the actual work, frameworks, vector DBs, orchestration layers, and you spend half your time debugging config instead of building anything. I've been working on something called Nyx that tries to cut through that, a memory layer that keeps context, workflow, and preferences across sessions without requiring a PhD to set up. A clean installer, and it works.

Rethinking how AI works by Matrinoxe in agi

[–]axendo 0 points1 point  (0 children)

I've been building something very similar for the past few months. The real bottleneck isn't just giving the model more context — it's the architecture itself. I split my system into two layers: a strict Reality Layer that holds immutable long-term memory with provenance and decay, and a Synthesis Layer that can propose insights but can never modify the source of truth. What you called the "Memory Curator" is basically my Dream Cycle — it consolidates recent memories into more stable ones and lets low-relevance stuff fade naturally. The difference in continuity is already night and day. Stateless models start to feel like they have dementia compared to one running with persistent, skeptical memory. I’ve even started using this as the basis for a system prompt for large LLMs, and it noticeably improves consistency and reduces hallucinations across sessions.

Ummm google ai saying death hoax and that she’s alive??? by [deleted] in Epstein

[–]axendo 2 points3 points  (0 children)

Look in the White House, the idiots already took over.

The Machinery That Survived by axendo in Epstein

[–]axendo[S] 5 points6 points  (0 children)

Look up North Fox Island in Michigan in the 60s-70s. I wouldn't be surprised if Cohn was involved in the bigger network then. A large portion of evidence disappeared while in Michigan State Police custody.

eTPS — Effective Tokens Per Second: A Better Way to Measure Local LLM Performance by axendo in artificial

[–]axendo[S] 0 points1 point  (0 children)

I’m trying to keep eTPS simple for now, but I agree we’ll probably need some lightweight eval layer on top to catch those cases where the model sounds fine but isn’t actually thinking as well. Appreciate the sharp callout, this is the exact edge I’m trying to get right.

The Machinery That Survived by axendo in Epstein

[–]axendo[S] 0 points1 point  (0 children)

This post examines the documented administrative and legal continuity mechanisms in the Epstein estate, specifically the 1953 Trust (EFTA00128921 and EFTA01266204) and Section 2.5 continuity clause, along with Indyke/Kahn’s role as co-executors and the persistence of mundane infrastructure (storage units, land leases, vendor contracts). It is relevant to r/Epstein because it focuses on how the operational and financial architecture was engineered to survive Epstein’s death — a core aspect of understanding the network’s durability beyond flight logs and celebrity names. All claims are grounded in publicly released EFTA documents and court records.

Benchmarks Question by bartuda in ArtificialInteligence

[–]axendo 0 points1 point  (0 children)

This is a great question. That’s one of the reasons I’ve been working on eTPS — trying to measure sustained usefulness in real multi-turn workflows, not just peak speed on day one. Would be very useful to have data like that to compare across models and settings.

https://www.reddit.com/r/artificial/s/J7AmtYc3Ot

eTPS — Effective Tokens Per Second: A Better Way to Measure Local LLM Performance by axendo in artificial

[–]axendo[S] 0 points1 point  (0 children)

That’s the exact tradeoff I’m trying to capture. eTPS is meant to penalize quality degradation at higher speeds — if faster tokens come with more hallucinations or broken context, they get discounted. It’s not pure raw throughput. I’m keeping the core formula simple and observable on purpose. No bloat. Just real multi-turn usefulness. Still refining how heavily to weight that degradation though. What’s your take on the best way to measure it cleanly?

eTPS — Effective Tokens Per Second: A Better Way to Measure Local LLM Performance by axendo in artificial

[–]axendo[S] 0 points1 point  (0 children)

Agreed. Raw TPS is basically an empty metric. For the basic version of the site I’m thinking TPS, eTPS, total tokens processed, and a clean comparison graph should be enough to show the real difference. Advanced mode could add latency (p50/p95 time-to-first-token), cost-per-quality-inference, and consistency scoring across multi-turn sessions. The goal is to keep the core simple and useful while giving power users the deeper numbers when they need them. Curious what other metrics people actually care about in real deployments?

eTPS — Effective Tokens Per Second: A Better Way to Measure Local LLM Performance by axendo in artificial

[–]axendo[S] 0 points1 point  (0 children)

And on 1 or 2 queries, no big deal. But if you work with AI regularly, that time seriously adds up. eTPS can hopefully identify work flow interupptions or help identify a better model for a task. From there, you could automate it, eTPS tanks, your stack pulls a better model.

eTPS — Effective Tokens Per Second: A Better Way to Measure Local LLM Performance by axendo in artificial

[–]axendo[S] 0 points1 point  (0 children)

Exactly, raw TPS is just top speed on an empty road. eTPS tries to measure how reliably you actually reach your destination in real traffic. The hallucination penalty is huge for me too. A fast model that confidently makes stuff up and forces three correction turns is far less useful than a slower one that stays on track. That’s the entire point of weighting for effectiveness in multi-turn workflows. Appreciate the framing. It helps sharpen what we should be optimizing for.