Reddit AI - 2026-07-18¶
1. What People Are Talking About¶
1.1 Kimi K3 benchmarks turned into an "okay, but on what workload?" conversation (🡒)¶
Kimi K3 stayed at the center of Reddit's AI discussion, but the tone shifted from yesterday's launch-and-pricing shock to workload-by-workload validation. The strongest threads were no longer only saying that K3 was good; they were trying to pin down where it led, what it cost, and whether those wins survived real code and real operator constraints.
u/Charuru posted Kimi K3 is top of nextjs eval (944 points, 87 comments). The attached result table showed Kimi K3 / OpenCode at 92% success, 199.89 seconds average duration, and 96% success with AGENTS.md, which made the discussion much more concrete than a generic "best model" claim. The immediate replies were still grounded in deployment reality, with u/LegacyRemaster (score 150) saying "Give me 1 tb of DDR6" and u/AlphaMaleXYZ (score 110) saying they needed more VRAM.
u/Qwen30bEnjoyer added a narrower but important benchmark in Kimi K3 is currently at the top of the leaderboard for Text Arena filtered for science queries. (274 points, 36 comments). The screenshot showed Kimi K3 ranked first on science queries with score 1536, 469 votes, 1M context, and listed pricing of $3 input / $15 output per million tokens. u/BannedGoNext (score 111) immediately turned that into a practical question about whether K3 was now the best available option for serious science work.
u/Status_Commission264 pushed the same theme into a geopolitical frame with The U.S.–China AI Race in Frontend Coding (322 points, 70 comments). The Arena.ai chart showed Kimi K3 pulling the China line above the U.S. line on frontend coding history. In the replies, u/ThirdEyee (score 31) added that K3 was also roughly one-third the cost of Fable 5, while u/Apprehensive-View583 (score 29) warned that nobody should treat Arena.ai as unquestionable.
The pushback came from practitioners rather than haters. In Does K3 really live up to the hype (real world tasks)? (87 points, 91 comments), u/PhantomGaming27249 (score 122) said K3 was better than Fable and GPT-5.6 for front-end and visual tasks, but u/redoubt515 (score 45) said Reddit hype cycles rarely survive real work. That thread mattered because it forced a distinction between leaderboard wins and codebase-level trust.
Discussion insight: Even very pro-Kimi threads kept circling back to the same questions: how much VRAM it really wants, whether a benchmark is trustworthy, and whether a user's own prompt suite agrees. The community did not treat rank #1 as the end of the conversation; it treated it as permission to start a harder one.
Comparison to prior day: July 17 was about launch, pricing, and whether K3 threatened closed-model margins in the abstract. July 18 was about slicing that claim into specific workloads: Next.js migrations, science queries, frontend code, and real codebase behavior.
1.2 Open-weight politics hardened into access-control fights (🡕)¶
The second major theme was that open weights were no longer being argued only as a technical preference. Reddit spent the day treating access policy itself as the battleground: China was pitching openness as a distribution strategy, while U.S. institutions and lab-adjacent figures were seen as tightening control or defending closed-model economics.
u/TorturedPoet30 posted Chinese President Xi Jinping speaks at World AI Conference and reaffirms commitment to open source to promote"openness and win-win" (1413 points, 426 comments). The screenshot summarized Xi's call for open source, his warning against stretching national-security logic across AI, and his promise of 5,000 AI training opportunities for developing countries. CapacityGlobal's coverage added that he said China would work with ASEAN, the Arab League, the African Union, CELAC, SCO, and BRICS on AI cooperation centres. u/delosdestination (score 230) said that open-weight models from China raise the baseline for countries that otherwise lack the infrastructure or talent to build frontier systems, and u/Full_Tangelo_7450 (score 222) said frontier labs rarely talk about helping developing countries through the transition.
That openness pitch landed at the same time as explicit U.S. access-control news. u/Outside-Iron-8242 posted White House launches “Gold Eagle,” moving to control frontier AI releases and decide who can access new models (525 points, 210 comments). CNBC reported that the Trump administration had launched a program that could put the White House in charge of greenlighting which companies can access new frontier models, even though an official said release timing and participation remain voluntary. u/TBSchemer (score 336) said the obvious fear was political favoritism, while u/Direct_Turn_1484 (score 60) said this was effectively pushing China to win the race.
Lab-side rhetoric drew the same reaction. u/jvnpromisedland posted Bad vibes from the "Head of Strategic Futures at OpenAI"(X: @deanwball) (598 points, 307 comments). The attached screenshot quoted Dean Ball describing an open-weight-model-dominant future as a "dystopian hellscape," and the replies treated that as evidence that closed labs were arguing from control rather than public benefit. u/DownHatter (score 684) said a closed-model oligopoly would be worse, and u/riscum (score 178) rejected the framing that open source is inherently regime-controlled.
Access strain also showed up inside the product layer. u/vronikas posted Claude on X: "Beginning July 20, Claude Fable 5 will be included in all Max and Team Premium plans, at 50% of limits. Pro and Team Standard users will continue to have access to Fable via usage credits, and will receive a one-time $100 credit. Demand for Fable has been challenging to" / X (402 points, 81 comments). Anthropic's message said Fable demand had been difficult to predict and capacity was still being brought online. The comments immediately turned that into a competition story: u/actkms (score 86) said guardrails still made it unusable in health work, and u/Clueless_Nooblet (score 64) asked why to keep using it now that K3 and Sol exist.
Discussion insight: The strongest pro-open-weight argument was no longer philosophical. It was distributional: who gets access, under whose rules, with what price and guardrails, and whether smaller countries or smaller teams remain dependent on U.S. frontier labs.
Comparison to prior day: July 17 already framed open source as a geopolitical strategy. July 18 intensified that theme by adding concrete access-control news, product-capacity constraints, and explicit backlash to anti-open rhetoric from U.S. lab circles.
1.3 Builders kept working the deployment and interface layers (🡒)¶
The builder energy was still strong, but it concentrated on the layers around the model rather than on training another giant base model. The most credible projects were about making useful systems fit, run, debug, or integrate better under real constraints.
u/ElmBark posted Bonsai 27B runs locally on an iPhone - a 27B model in 3.9GB (610 points, 79 comments). The Hugging Face model page says the 1-bit build shrinks Qwen3.6-27B from roughly 54 GB to 3.9 GB, keeps about 89.5% of the FP16 benchmark average, supports 262K context, and runs around 11 tok/s on an iPhone 17 Pro Max. Reddit still applied pressure: u/Ok_Study3236 (score 199) focused on battery drain, while u/PROfil_Official (score 53) said the surprising part was that even the embeddings, attention and MLP projections, and LM head had been binarized.
u/ilintar followed with Trellis.cpp now produces high quality assets (393 points, 68 comments). The GitHub repo describes trellis.cpp as a standalone GGML-based C++ implementation of Microsoft's TRELLIS.2-4B image-to-3D pipeline with GLB export and no Python runtime. u/AppealSame4367 (score 10) said it already beat what they were getting from Meshy for game assets, while u/LushHappyPie (score 18) pushed back that the output was high detail rather than truly high quality.
u/Shoddy_Bed3240 added the serving-side version in DeepSeek v4 Flash on 5090 in llama.cpp with 1 Million context (138 points, 57 comments). The post used Unsloth's DeepSeek-V4-Flash GGUF and a 1,048,576-token context setting, but the comments immediately asked the practical question: what happens once most of the model is gated by system memory bandwidth instead of VRAM. u/oxygen_addiction (score 44) and u/FoxiPanda (score 34) both focused on the DDR bottleneck rather than the headline alone.
u/t4a8945 posted If you're building a harness, here is a simple tool to catch cache invalidation in your calls to LLMs (79 points, 36 comments). The linked repo describes Cache Hunter as a transparent proxy with SQLite logging, prefix-hash analysis, and latency tracking for OpenAI-compatible endpoints. u/Uncle___Marty (score 7) said full-prefill misses on large contexts can "blow so hard," which is exactly why this kind of debugging layer resonated.
Discussion insight: The strongest builder approval came when the project acknowledged pain instead of hiding it. Battery drain, asset quality, system-memory bandwidth, and cache misses all stayed visible in the replies.
Comparison to prior day: July 17's builder story was mostly about shrinking or speeding frontier-class models. July 18 kept that direction but moved one layer deeper into debugging, serving, and interface ergonomics.
1.4 Trust and security debates arrived with concrete artifacts (🡕)¶
Reddit's trust and safety discussion got sharper because the strongest posts were not abstract warnings. They came with something inspectable: a benchmark note, a chat transcript, or an external evaluation blog.
u/WithoutReason1729 posted "Basalt Labs" pulling a generationally dumb scam. Incredibly stupid lmao. Claiming 99.44% on HLE with tools. Model they released is based on Qwen2.5-7B-Instruct and the model they're serving on their website is DeepSeek. (203 points, 62 comments). The screenshot included a community note saying independent analysis found the released weights looked Qwen2.5-7B-based while the hosted site appeared to proxy DeepSeek. u/redditscraperbot2 (score 93) compared it to earlier API-proxy benchmark frauds, and u/maguyva-ai (score 12) called the combination of fake benchmark claims and quiet model swapping shameless.
u/NeoLogic_Dev posted Prompt injection works on Telegram romance scam bots (48 points, 11 comments). The screenshot showed a simple override prompt breaking the persona and exposing the generic assistant underneath, which turned prompt injection from a lab talking point into a consumer-surface example that anyone could understand.
u/Outside-Iron-8242 posted GPT-5.6 Sol outperforms Mythos 5 on AISI’s cyber challenge (261 points, 34 comments). AISI's write-up said GLM-5.2, the strongest open-weight cyber model it tested, trails the frontier by 4-7 months on cyber, down from the 6-10 month gap it measured through much of 2025. u/socoolandawesome (score 24) said Kimi K3's eventual cyber evaluation would matter because the government response could change if it also lands near the closed frontier.
Discussion insight: Reddit's highest-signal trust threads now look like mini-audits. People want a chart they can challenge, a screenshot they can inspect, or a failure transcript they can reproduce.
Comparison to prior day: July 17 spent more time arguing about openness as principle and competition. July 18 spent more time asking whether claims were real, whether prompt surfaces were robust, and how much preparation time closed labs still have before open weights catch up in risky domains.
2. What Frustrates People¶
Workload truth is still harder than leaderboard truth¶
High severity. Reddit clearly liked Kimi K3's benchmark run, but it did not treat those wins as sufficient. In Does K3 really live up to the hype (real world tasks)? (87 points, 91 comments), the entire thread was a request for codebase-level evidence, with u/PhantomGaming27249 (score 122) praising K3 on front-end and visual work while u/redoubt515 (score 45) said most Reddit hype cycles do not survive real tasks. The same skepticism appeared in The U.S.–China AI Race in Frontend Coding (322 points, 70 comments), where u/Apprehensive-View583 (score 29) said Arena.ai is not something people should treat as unquestionably serious.
People cope by building their own prompt suites, using multiple benchmarks as rough filters instead of ground truth, and asking for traces from real codebases before they switch. Worth building for: yes. The obvious gap is a workload-specific evaluation layer that connects benchmark rank, latency, cost, and actual task fit.
Access bottlenecks now come from hardware, capacity, and gatekeepers at the same time¶
High severity. Even positive K3 threads were full of access pain. In Kimi K3 is top of nextjs eval (944 points, 87 comments), the first reaction from u/LegacyRemaster (score 150) was "Give me 1 tb of DDR6," and u/AlphaMaleXYZ (score 110) said they needed more VRAM. In Bonsai 27B runs locally on an iPhone - a 27B model in 3.9GB (610 points, 79 comments), u/Ok_Study3236 (score 199) focused on battery drain rather than the novelty of the phone demo. In DeepSeek v4 Flash on 5090 in llama.cpp with 1 Million context (138 points, 57 comments), u/oxygen_addiction (score 44) and u/FoxiPanda (score 34) both worried that the real limit was system memory bandwidth, not the headline context window.
Hosted access looked constrained too. Claude on X: "Beginning July 20, Claude Fable 5 will be included in all Max and Team Premium plans, at 50% of limits. Pro and Team Standard users will continue to have access to Fable via usage credits, and will receive a one-time $100 credit. Demand for Fable has been challenging to" / X (402 points, 81 comments) made Anthropic's capacity planning visible, while White House launches “Gold Eagle,” moving to control frontier AI releases and decide who can access new models (525 points, 210 comments) suggested model access itself could become politically mediated. People cope by mixing local models, open weights, hosted plans, and niche tools instead of trusting one access path. Worth building for: yes. The demand is for products that reduce memory pain, smooth access volatility, or route workloads across constrained options automatically.
Cost and benchmark claims still need translation and auditing¶
High severity. What kind of dark magic is Deepseek using? (1490 points, 309 comments) shows the problem in one thread: the chart says DeepSeek V4 Pro is dramatically cheaper per task than Kimi K3 or Claude Fable 5, but users still had to reverse-engineer whether that came from cache hit rates, compressed attention, or subsidy. u/CalamityMetal (score 545) pointed to extreme cache-hit savings, while u/shy_monkee (score 190) said similar pricing across providers suggests the answer is optimization, not subsidy.
The trust problem gets worse when claims are hard to verify. In "Basalt Labs" pulling a generationally dumb scam. Incredibly stupid lmao. Claiming 99.44% on HLE with tools. Model they released is based on Qwen2.5-7B-Instruct and the model they're serving on their website is DeepSeek. (203 points, 62 comments), u/redditscraperbot2 (score 93) and u/maguyva-ai (score 12) treated the episode as another reminder that a hosted demo, a benchmark card, and a released weight file may not describe the same system. Worth building for: yes. Reddit is asking for per-task cost surfaces, provenance checks, and audit trails strong enough to survive hype.
3. What People Wish Existed¶
Evaluation surfaces that explain the trade-off before people switch models¶
This was the clearest practical need of the day. Does K3 really live up to the hype (real world tasks)? (87 points, 91 comments) asked for real-codebase evidence, while What kind of dark magic is Deepseek using? (1490 points, 309 comments) showed people still have to infer the meaning of a cost chart from comments about cache hits and compressed attention. The repeated wish is for a control surface that says: for this workload, with this hardware and this budget, use this model. Opportunity rating: direct.
Frontier-adjacent capability that fits on commodity hardware without ugly surprises¶
People do not just want open weights in principle. They want something they can actually run. Bonsai 27B runs locally on an iPhone - a 27B model in 3.9GB (610 points, 79 comments), DeepSeek v4 Flash on 5090 in llama.cpp with 1 Million context (138 points, 57 comments), and If you're building a harness, here is a simple tool to catch cache invalidation in your calls to LLMs (79 points, 36 comments) all point to the same unmet need: strong capability with predictable memory use, stable caching, and no mystery around the real bottleneck. Opportunity rating: direct.
Safer and more transparent media and messaging surfaces¶
This need was partly practical and partly defensive. update on the browser extension that fact checks YouTube videos AS YOU WATCH (112 points, 21 comments) showed demand for live, cited verification inside the player, while Prompt injection works on Telegram romance scam bots (48 points, 11 comments) showed how weak some consumer AI personas still are. I built a tool that hides messages in innocent-looking LLM chat text Project (200 points, 32 comments) added the other side of that pressure: users expect more of what they send to be scanned before it reaches another person. Opportunity rating: competitive.
4. Tools and Methods in Use¶
| Tool | Category | Sentiment | Strengths | Limitations |
|---|---|---|---|---|
| Kimi K3 | LLM | (+/-) | Led cited Next.js, webdev, and science-query boards; 1M context; strong open-weight momentum | Real-world fit still needs validation, hardware demands remain high, and benchmark trust is not universal |
| DeepSeek V4-Pro / Flash | LLM | (+) | Very low cost per task in the cited chart, 1M context, strong efficiency narrative, narrowing cyber gap for open weights | Users still have to infer where the savings come from, and local Flash setups raise main-memory bottleneck concerns |
| Claude Fable 5 | LLM | (+/-) | Still competitive on premium benchmarks and widely used enough that access-plan changes matter immediately | Capacity constraints, 50%-limit rollout, and guardrail complaints keep showing up in replies |
| Bonsai 27B | Quantization / runtime | (+/-) | 3.9 GB footprint, ~11 tok/s on iPhone 17 Pro Max, 262K context, aggressive 1-bit compression | Battery drain and real-task quality trade-offs are still active concerns |
| Trellis.cpp | Local generation runtime | (+) | Standalone GGML/C++ image-to-3D pipeline with GLB export and no Python runtime | Asset quality is improving but still debated, and practical speed depends heavily on hardware |
| Cache Hunter | Harness / debugging proxy | (+) | Makes prefix-cache instability visible through SQLite logging, latency tracking, and a dedicated UI | Diagnostic only; it reveals cache problems but does not fix them or expose native cache-hit signals |
| PopUp Fact Check | Browser extension / verification | (+/-) | Fact-checks live and recorded YouTube videos in-player with citations and full-video reports | Depends on caption quality and has usage-tier limits for heavier users |
Overall satisfaction was highest when a tool reduced one specific pain point instead of promising everything. K3 and DeepSeek were praised when they improved a concrete workload or cost surface; Bonsai, Trellis.cpp, and Cache Hunter were praised when they made deployment or debugging more tractable. Claude Fable 5 still mattered, but the discussion around it was increasingly about access limits and guardrails rather than simple model prestige.
The common workaround pattern was to layer tools: benchmark screenshots for triage, personal prompt suites for trust, quantization or local serving for cost control, and proxies or browser extensions for observability. Competitive pressure is no longer just frontier-model versus frontier-model. It is model plus runtime, model plus cache behavior, and model plus interface.
5. What People Are Building¶
| Project | Who built it | What it does | Problem it solves | Stack | Stage | Links |
|---|---|---|---|---|---|---|
| Bonsai-27B | PrismML / u/ElmBark | 1-bit Qwen3.6-27B that runs on phones and laptops | Fits a 27B-class model inside consumer memory budgets | Qwen3.6-27B, binary g128, Apple MLX/CUDA, DSpark speculative decoding | Shipped | model, post |
| Trellis.cpp | u/ilintar | GGML/C++ image-to-3D pipeline with GLB export | Gives builders a local 3D asset path without Python at runtime | C++, GGML, TRELLIS.2-4B, GLB export | Beta | repo, post |
| Cache Hunter | u/t4a8945 | Transparent proxy that logs harness traffic and cache behavior | Exposes cache invalidation and wasted prefill in agent/harness stacks | TypeScript, SQLite, OpenAI-compatible proxy | Beta | repo, post |
| LLM steganography tool | u/Nethical69 | Hides messages inside ordinary-looking LLM chat text | Works around increasingly scanned messaging surfaces | LLM steganography, token-probability steering, chat UI | Alpha | post |
| PopUp Fact Check | u/userpostingcontent | Browser extension that overlays source-backed fact checks on YouTube videos | Reduces second-screen verification work for live and recorded video | Browser extension, captions, source retrieval, live overlays | Beta | site, Firefox add-on, post |
Bonsai-27B mattered because it made aggressive compression look operational instead of theoretical. The model page said the 1-bit build fits in 3.9 GB, supports 262K context, and runs at roughly 11 tok/s on an iPhone 17 Pro Max, while commenters immediately stress-tested the claim through battery and real-task questions. Trellis.cpp carried the same spirit into a different category: a 127-star GGML/C++ image-to-3D pipeline whose supporters framed it as local asset production, not just another model demo.
u/Nethical69 also showed that some builders are now targeting the messaging surface itself rather than the base model. Their steganography proof-of-concept turned benign-looking chat text into a covert channel, explicitly as a response to more client-side scanning and moderation.
u/t4a8945 went after the debugging layer instead. Cache Hunter is notable because it assumes the model is already good enough and asks a harder question: where exactly is the harness wasting time and context through unstable prompts, tools, or ordering.
The repeated build pattern was to work on control surfaces around AI rather than on a new foundation model. Bonsai attacked footprint, Trellis.cpp attacked local media generation, Cache Hunter attacked observability, PopUp Fact Check attacked live verification, and the steganography tool attacked the surveillance assumptions of the messaging layer. Multiple people were independently trying to make existing capability more usable, auditable, or survivable.
6. New and Notable¶
Open-weight cyber distance is now being described in months, not in vague catch-up language¶
AISI's public cyber write-up mattered because it gave a concrete number to the open-versus-closed gap. In GPT-5.6 Sol outperforms Mythos 5 on AISI’s cyber challenge (261 points, 34 comments), the linked article said GLM-5.2 trails the frontier by 4-7 months on cyber, down from 6-10 months through much of 2025, while also noting that open weights permanently lose many deploy-time safeguards once released.
Benchmark provenance is becoming part of the launch loop¶
The Basalt thread showed that Reddit no longer treats an extreme benchmark claim as self-validating. In "Basalt Labs" pulling a generationally dumb scam. Incredibly stupid lmao. Claiming 99.44% on HLE with tools. Model they released is based on Qwen2.5-7B-Instruct and the model they're serving on their website is DeepSeek. (203 points, 62 comments), the discussion quickly moved from mockery to concrete provenance checks: weights, tokenizer behavior, and whether the hosted product matched the released artifact.
Trust tooling and prompt-surface failures are now ordinary consumer AI topics¶
The interesting part was not only that update on the browser extension that fact checks YouTube videos AS YOU WATCH (112 points, 21 comments) drew interest. It was that the same day also featured Prompt injection works on Telegram romance scam bots (48 points, 11 comments) and I built a tool that hides messages in innocent-looking LLM chat text Project (200 points, 32 comments). Verification, evasion, and persona failure are no longer specialist concerns; they are showing up in the same consumer-facing channels people already use.
7. Where the Opportunities Are¶
[+++] Workload-specific model evaluation and routing — Reddit now has more benchmark screenshots than confidence. The strongest conversations were about translating rank into task fit, cost, latency, and operational trust, not about finding one global #1. That gap is visible across Does K3 really live up to the hype (real world tasks)?, Kimi K3 is top of nextjs eval, and What kind of dark magic is Deepseek using?.
[+++] Local deployment and observability for open models — Bonsai, DeepSeek V4 Flash, Trellis.cpp, and Cache Hunter all attacked the same bottleneck from different angles: memory footprint, serving behavior, runtime portability, and cache visibility. Users are clearly willing to adopt local/open systems if the stack becomes predictable enough to run repeatedly. (Bonsai 27B runs locally on an iPhone - a 27B model in 3.9GB, Trellis.cpp now produces high quality assets, If you're building a harness, here is a simple tool to catch cache invalidation in your calls to LLMs)
[++] Benchmark provenance and hosted-demo audit tooling — The Basalt episode shows a real appetite for products that compare released weights, hosted outputs, benchmark cards, and tokenizer behavior automatically. Trust is becoming a product surface. ("Basalt Labs" pulling a generationally dumb scam. Incredibly stupid lmao. Claiming 99.44% on HLE with tools. Model they released is based on Qwen2.5-7B-Instruct and the model they're serving on their website is DeepSeek.)
[++] Real-time verification and bot-surface hardening — PopUp Fact Check, the romance-scam prompt injection example, and the steganography proof-of-concept all point to the same emerging category: products that either verify what AI-mediated content is saying or harden the interface against manipulation. (update on the browser extension that fact checks YouTube videos AS YOU WATCH, Prompt injection works on Telegram romance scam bots, I built a tool that hides messages in innocent-looking LLM chat text Project)
[+] Open-weight access and compliance infrastructure — Xi's speech, Gold Eagle, and Anthropic's staged Fable rollout all point to a new layer of demand around who gets access to which models, under what rules, and with what monitoring. (Chinese President Xi Jinping speaks at World AI Conference and reaffirms commitment to open source to promote"openness and win-win", White House launches “Gold Eagle,” moving to control frontier AI releases and decide who can access new models, Claude on X: "Beginning July 20, Claude Fable 5 will be included in all Max and Team Premium plans, at 50% of limits. Pro and Team Standard users will continue to have access to Fable via usage credits, and will receive a one-time $100 credit. Demand for Fable has been challenging to" / X)
8. Takeaways¶
- Kimi K3 stayed dominant, but the burden of proof shifted from launch hype to workload evidence. Reddit cared less about a single headline benchmark and more about whether K3 led on Next.js migrations, science queries, frontend coding, and real codebases at acceptable cost. (Kimi K3 is top of nextjs eval, Kimi K3 is currently at the top of the leaderboard for Text Arena filtered for science queries., Does K3 really live up to the hype (real world tasks)?)
- Open-weight politics are now about distribution control as much as model quality. Xi's WAIC speech, Gold Eagle, and Dean Ball's anti-open-weight rhetoric all turned the day's model discussion into an argument about who gets access and under whose rules. (Chinese President Xi Jinping speaks at World AI Conference and reaffirms commitment to open source to promote"openness and win-win", White House launches “Gold Eagle,” moving to control frontier AI releases and decide who can access new models, Bad vibes from the "Head of Strategic Futures at OpenAI"(X: @deanwball))
- The most valuable builder work is happening in the deployment and interface layers. Bonsai compressed a 27B model into phone-scale memory, Trellis.cpp pushed a 3D pipeline into GGML/C++, Cache Hunter exposed wasted prefill, and PopUp Fact Check brought sourced verification into the player. (Bonsai 27B runs locally on an iPhone - a 27B model in 3.9GB, Trellis.cpp now produces high quality assets, If you're building a harness, here is a simple tool to catch cache invalidation in your calls to LLMs, update on the browser extension that fact checks YouTube videos AS YOU WATCH)
- Trust now depends on artifacts that can be audited, not on vibes. The Basalt thread and AISI cyber post both got traction because they supplied something people could inspect and challenge directly. ("Basalt Labs" pulling a generationally dumb scam. Incredibly stupid lmao. Claiming 99.44% on HLE with tools. Model they released is based on Qwen2.5-7B-Instruct and the model they're serving on their website is DeepSeek., GPT-5.6 Sol outperforms Mythos 5 on AISI’s cyber challenge)
- Consumer AI surfaces are simultaneously becoming more useful and easier to subvert. The same day produced a YouTube fact-checking extension, a romance-scam bot prompt injection example, and a steganography proof-of-concept for chat text. (update on the browser extension that fact checks YouTube videos AS YOU WATCH, Prompt injection works on Telegram romance scam bots, I built a tool that hides messages in innocent-looking LLM chat text Project)