Pay attention to what it forgets, and start telling it to proactively note down those things into nominated files while it works, e.g. indexing topics covered by each chapter/section/page of each paper/material. GPT-5.6 is really good at finding context again, if given the smallest hint where to start looking.
You can also ask it to read your past sessions, find places where it was wrong after compaction, and figure out a strategy to persist the most important summary information.
I have several Hermes threads that have each had >10 compactions with a 200k context limit, and with the right instructions on note-taking, they require at most a "double-check that against our past decision records" to be put back on track after a slip-up.
It's a solvable problem if you're willing to throw more tokens at it. Frontier models have gotten very good at cleaning up their own messes. You just need the right skills/loops, and to stick to models that consistently follow instructions (i.e. GPT-5.5/GPT-5.6-Sol).
There is a third case where the other party doesn't realize that the asker lacks the relevant experience to discern good LLM answers from bad answers for that topic.
Same solution as case one though - don't be afraid to say "Claude said X but that doesn't sound right".
As a current free-tier user, this price & transition plan seems completely reasonable. I'll upgrade when the nudge comes. I've got at least that much utility from it so far.
Very glad this isn't a subscription.
I have found Claude to be especially unpredictable. I've mostly switched to GPT-5.4 now - although it's slightly less capable, it's massively more reliable.
Some of the flak is that issues are often only acknowledged once a fix is in place, and the partial fixes are presented as if they solve the whole problem.
The near-instant transition from "there is no problem" to "we already fixed the problem so stop complaining" is basically gaslighting. (Admittedly the second sentiment comes more from the community, but they get that attitude after taking the "we fixed all the problems" posts at face value.)
Childhood, at least IME, does a bad job of preparing people for this: fault and blame rarely matter in real interactions. When no teacher is around to play judge, all that matters is that you get a favorable outcome. That's something you need to figure out, usually in the heat of the moment, how to get. It takes active effort to understand the other side.
It works for me Firefox's Cloudflare DNS over HTTP.
For clarity, the recent issue[0] likely wasn't intermittent. Cloudflare's malware blocking DNS server now blocks those archive.today sites. Doesn't affect the non-malware-blocking DNS server (1.1.1.1).
This could be an explanation for the drama - LLMs are trained to learn and emulate correlations in text.
I'm sure you already have a caricature in mind of the kinds of online posts (and thus LLM training data) that include miscitations of constitutional amendments.
It's not perfect but it does have a few opt-in security features: running all tools in a docker container with minimal mounts, requiring approvals for exec commands, specifying tools on an agent by agent basis so that the web agent can't see files and the files agent can't see the web, etc.
That said, I still don't trust it and have it quarantined in a VPS. It's still surprisingly useful even though it doesn't have access to anything that I value. Tell it to do something and it'll find a way!
I'm working in AI, but I'd have made this anyway: Molty is my language learning accountability buddy. It crawls the web with a sandboxed subagent to find me interesting stuff to read in French and Japanese. It makes Anki flashcards for me. And it wraps it up by quizzing me on the day's reading in the evening.
All this is running on a cheap VPS, where the worst it has access to is the LLM and Discord API keys and AnkiWeb login.
Ratio/quantity is important, but quality is even more so.
In recent LLMs, filtered internet text is at the low end of the quality spectrum. The higher end is curated scientific papers, synthetic and rephrased text, RLHF conversations, reasoning CoTs, etc. English/Chinese/Python/JavaScript dominate here.
The issue is that when there's a difference in training data quality between languages, LLMs likely associate that difference with the languages if not explicitly compensated for.
IMO it would be far more impactful to generate and publish high-quality data for minority languages for current model trainers, than to train new models that are simply enriched with a higher percentage of low-quality internet scrapings for the languages.
It requires tax increases, and the average earner's UBI will typically balance out the tax increase, meaning they don't directly profit.
UBI isn't about giving everyone free money. It's about giving everyone a safety net, so that they can take bigger economic risks and aren't pushed into crime or bullshit work.
The upper half of society will only see the indirect benefits, like having greater employment/investment choices due to more entrepreneurialism.
That discussion also makes me worry that they may try to use LLMs or LLM-based metrics to measure the size of the gap as a proxy for value of the content.
The landlord of the marketplace should probably not dabble in the appraisal of products, whether for factuality or value.
As a content consumer, I'm also hoping to be part of the ecosystem. I already use Patreon a lot as "AdBlock absolution", but it doesn't fix the market dynamics. Major content platforms tend to stagnate or worsen over time, because they prefer to sell impressions to advertisers than a good product to consumers.
What makes you think the secrets are small enough to fit inside people's heads, and aren't like a huge codebase of data scraping and filtering pipelines, or a DB of manual labels?
Please consider also describing the business model on the website, even if hidden away on a FAQ. I've so much subscription fatigue now, I just don't try things out if needing a subscription is an inevitability. I'm happy to pay for good products, just not happy to be forced to pay a fixed rate for continued access even if my usage dwindles.
If you are thinking of adding a one-off-donation-style purchase method, consider giving annual reminders to renew it. At least in my case, I'm not unwilling to pay repeatedly if development continues, just unwilling to make an upfront ongoing commitment.
I don't think retrofitting existing languages/ecosystems is necessarily a lost cause. Static enforcement requires rewrites, but runtime enforcement gets you most of the benefit at a much lower cost.
As long as all library code is compiled/run from source, a compiler/runtime can replace system calls with wrappers that check caller-specific permissions, and it can refuse to compile or insert runtime panics if the language's escape hatches would be used. It can be as safe as the language is safe, so long as you're ok with panics when the rules are broken.
It'd take some work to document and distribute capability profiles for libraries that don't care to support it, but a similar effort was proven possible with TypeScript.