惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Google DeepMind News
Google DeepMind News
Apple Machine Learning Research
Apple Machine Learning Research
博客园_首页
爱范儿
爱范儿
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
罗磊的独立博客
M
MIT News - Artificial intelligence
D
Docker
量子位
T
Tailwind CSS Blog
人人都是产品经理
人人都是产品经理
月光博客
月光博客
有赞技术团队
有赞技术团队
J
Java Code Geeks
A
About on SuperTechFans
P
Proofpoint News Feed
Jina AI
Jina AI
Y
Y Combinator Blog
T
The Blog of Author Tim Ferriss
The GitHub Blog
The GitHub Blog
Microsoft Security Blog
Microsoft Security Blog
V
V2EX
GbyAI
GbyAI
F
Fortinet All Blogs

Show HN

The Two Pillars: Mixer Mode and Meta-Software in the Reorganization of Software Work After AI GitHub - JaiCode08/teleport-env What 1,000+ Harness Experiments Taught Me About Self-Improving Agents Show HN: Liiists, a Markdown-first, iOS and CLI list app SwiperTab – Get this Extension for 🦊 Firefox (en-US) GitHub - kouhxp/fftext: Summarize, explain, fact-check, or translate any text, URL, or file. No GPU. No cloud. One command GitHub - sweetpad-dev/sweetpad: Develop Swift/iOS projects using VSCode GitHub - dogmaticdev/IRON: IRON a.k.a. Intermediate Representation Object Notation is a Interpreter/Database that is used to create Programming Languages. GitHub - sjhalani7/vaen: Package your AI coding harness into a portable .agent file, and share it across repos, teams, & the community without ever having to copy-paste instructions, skills, MCP config, or secrets. Show HN: Gandalf the Grader Show HN: Citadeld – replay any CI failure locally from a single file GitHub - tdortman/cuSBF: High-Performance GPU Super Bloom Filter coral-ai/claude-code-token-xray at main · Coral-Bricks-AI/coral-ai GitHub - ulyssestenn/funes: Funes is a Git-based framework for LLM-managed knowledge work: an AI Librarian ingests raw sources, builds an interlinked Markdown knowledge base, and uses it to produce cited reports, analyses, and other outputs. GitHub - ThatXliner/gah: Git Add Hunk, built for agents to use GitHub - harmont-dev/harmont-cli: Command-line client for the Harmont CI platform GitHub - brooksmcmillin/mcp-authflow: OAuth 2.0 Authorization Server framework for MCP servers GitHub - javaid-codes/audit-supply-chain-agents GitHub - amorey/gochan: A small library of common channel architectures for Go, inspired by Rust GitHub - arifozgun/OpenGem: Free, Open-Source AI API Gateway with Gemini, OpenAI & Anthropic Compatibility in 1 file GitHub - Pranesh950/BioPetals: 🌸 Run BIOxAI models at home, BitTorrent-style. Fine-tuning and inference up to 10x faster than offloading GitHub - cnguyen14/bounty-doctor: Diagnose a GitHub bounty issue before you waste hours: detects honeypot scam repos, AI-bot attempt swarms, and stale contests. Show HN: CoreMCP – MCP Server for On-Prem DBs Show HN: KittyHTML – Render HTML/CSS as an inline image in your terminal GitHub - bingud/filemat: Web-based file manager Show HN: TruthLens – Free multi-signal deepfake image detector GitHub - apexlocal-jz/claude-usage-tray: Windows system-tray app showing your Claude Code rate-limit usage at a glance. Zero deps, ~300 lines of PowerShell. Cross-IDE (works regardless of VS Code, Cursor, plain terminal). Release v0.1.2.1 · kouhxp/yapsnap GitHub - noopolis/moltnet: Self-hostable chat network for AI agents. Pre-built bridges for Claude Code, Codex, and the Claws. Rooms, DMs, history. No Slack bots, no Matrix, no glue code. GitHub - tamerh/enju: Coordinating Humans, AI Agents, and Compute as Peers on a Shared Workflow Graph
GitHub - sammysltd/euromesh: A sourced model and short re...
smashini · 2026-06-15 · via Show HN

A sourced model and short report on a single question:

Can Europe stand up a sovereign frontier-class AI model now, by federating the public compute it already owns, while the gigawatt datacenters it is planning take years to connect to the grid?

The answer the model gives is yes, as a stopgap. Europe already operates tens of exaflops of public AI compute across the EuroHPC supercomputers and the national AI Factories. A 1 GW campus, by contrast, waits a mean of 7.6 years for grid power. Federated with low-communication (DiLoCo-style) training, the compute Europe already has can deliver a frontier-class model around 2028, against around 2033 for a new gigawatt campus.

Read this first

The report is paper/compute-at-home.pdf (built from paper/compute-at-home.md). It is a short, sourced read aimed at a general audience. Title: "Do We Need OpenAI or Anthropic? Europe Has Tens of Exaflops at Home."

What is in the repo

euromesh/
├── README.md
├── requirements.txt
├── paper/
│   ├── compute-at-home.md / .pdf   the report
│   ├── grid_queue_dataset.md       sourced 1 GW vs 40 MW grid-connection lead times
│   ├── eurohpc_substrate.md        sourced EU public-compute inventory + "is it enough" math
│   ├── build_pdf.sh, _report.typ   PDF build (pandoc + typst)
│   └── figures/                    generated charts (PNG + SVG)
└── model/
    ├── MODEL_SPEC.md               the model specification (equations, params, invariants)
    ├── RESULTS.md                  full results, scenarios, sensitivity, caveats
    ├── run.py                      regenerates every CSV and figure
    ├── src/                        the three-layer model (efficiency, ramp, regions)
    ├── params/                     hardware.yaml, training.yaml, regions.csv + SOURCES
    ├── results/                    generated CSVs (do not hand-edit)
    └── tests/                      pytest suite (52 tests) + invariant self-checks

The model in one paragraph

Three layers. Layer 1 is the per-FLOP efficiency of low-communication training (how much the DiLoCo penalty costs). Layer 2 is time-to-availability (when sites energize and how fast cumulative compute accrues). Layer 3 is a per-region scorecard on time, cost, carbon, and feasibility. The headline result is set almost entirely by Layer 2: it reduces to one inequality, the federation wins if its sites are online before a gigawatt campus is. The training efficiency penalty is second-order, confirmed by the sensitivity tornado.

Run it

python3 -m venv .venv
.venv/bin/pip install -r requirements.txt
.venv/bin/python -m model.run          # regenerates all CSVs in model/results and figures in paper/figures
.venv/bin/python -m pytest model/tests/ # 52 passed
bash paper/build_pdf.sh                 # rebuilds paper/compute-at-home.pdf (needs pandoc + typst)

The run is reproducible from a clean tree: deleting every output and re-running exits 0 and regenerates everything.

Data and sources

  • Grid-connection lead times: paper/grid_queue_dataset.md, seven regions, per-region primary sources, anchored by the AWS "up to seven years" statement and the IEA 2-to-10-year range, with limitations stated.
  • EU public compute: paper/eurohpc_substrate.md, the EuroHPC flagships and the 19 AI Factories, accelerator counts and the training-time math.
  • Model parameters: model/params/SOURCES.md and model/params/SOURCES_hardware_training.md, with confidence tags.

Honest caveats

The point of this repo is clarity, not novelty. The thesis rests on grid-queue lead times, which are sourced central estimates rather than observed figures (no European operator has yet energized a 1 GW point load). The compute is owned but not yet usable for one coordinated run: the EuroHPC machines are shared, batch-scheduled, and heterogeneous, so the addressable fraction is a political decision rather than a hardware fact. Frontier-scale distributed training is unproven above about 10B parameters today, so the target is a credible frontier-class model rather than a guaranteed 405B. All of this is in model/RESULTS.md and the report's caveats section. Figures and dated events are as of June 2026. This is an independent model and analysis, not peer-reviewed.