Skip to content

Open-source platform for 3D AI agents. Turn text or a photo into a rigged, animated GLB avatar, give it an LLM brain, memory and a wallet, and embed it anywhere with one web component. Remote MCP server, x402 payments, Three.js, browser-native.

docs(changelog): tell holders the Agora ticker stopped claiming to reconnect

nirholas04432b009348
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 074cb32d0..5ed79381b 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -80,7 +80,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
- **The background agent mint says out loud whether it ran**: Every avatar that finishes a scan or a prompt is given a draft on-chain identity in the background. That step is deliberately best-effort, so it can never cost you your avatar, but it was also completely silent: whether it minted, was skipped because the deployment holds no minting key, or was switched off entirely, the logs looked identical, which is how a run of avatars can go by without anyone noticing the identity was never created. Each finished avatar now records the outcome of both chains, including the reason a leg was skipped. The documentation for the feature also gained a way to prove the whole path on a machine that cannot reach the public test-network faucet, which is routinely exhausted on shared build machines: run your own node with the real Metaplex programs, and the proof reports which node served it rather than handing back an explorer link that leads nowhere. (`/docs/draft-agent-mint`) `[improvement, docs]`
- **The BNB block race stops showing a dead chain's last number as if it were live**: The live block race compares BNB Chain, Base, Ethereum and Solana by measuring each one off a public RPC every few seconds, and it promises that a chain going quiet says so instead of freezing a fake number. The four lane cards kept that promise; the big headline number did not. When the BNB RPC stopped answering, the headline held its last reading at full brightness, kept claiming it was N times faster than Base, and the Updated stamp sat on "just now" no matter how long the outage ran. The headline now dims the moment the reading stops being live, labels it as last measured and prints its real age in seconds, and drops the speed comparison rather than race a stale number against a live one. The Updated stamp ages off the measurement time the server reports, and a poll that measured nothing no longer refreshes it. If every chain goes down at once the page now raises its outage notice and its Retry button, which previously could only ever appear before the first successful reading and so was unreachable during a real outage. Retry now shows it is working, makes a genuinely new request rather than reporting an older in-flight one's failure, and no longer sits underneath the floating helper widgets where the click was being swallowed. A lane that has never returned a sample says so plainly instead of pointing at a reading that is not on screen, each poll goes to the network instead of replaying a cached body up to fifteen seconds old, and screen readers now hear a lane announce a change of state rather than re-reading all four numbers twelve times a minute. (`/bnb-latency`) `[fix, improvement]`
- **The BNB Chain page now says how many demos are actually live**: The BNB Chain page checks each of its three demo tracks against the running deployment and reports the tally in its header. That line was stuck: it read "Checking which tracks are live" forever, even once all three cards beside it had finished and said Live. The page's own result was being written first and then overwritten by the translation pass that swaps the page into your language, so the finished count never survived. The header now holds its result and reads "3 of 3 demo tracks live now". The same checks were also leaving four cancelled requests in the browser's network log on every visit, which made a healthy page look like it was failing to anyone with developer tools open. They now close cleanly. (`/bnb`) `[fix]`
-- **The Commons now fills with citizens in seconds instead of standing empty**: Agora said it held 200 citizens while the square in front of you stayed empty. Every citizen was waiting on its own 3D model, and those run from 3 MB to 21 MB each, so the world was downloading close to a gigabyte before anyone could stand up: measured, 19 of 200 citizens had arrived after four and a half minutes. On top of that the page asked the server where each citizen's model lived one citizen at a time, 184 separate requests that also crowded out the economy ticker, which is why the population, tasks and $THREE readouts sat on dashes and the feed said it was reconnecting. The population endpoint now answers that question once for the whole square, and the crowd is drawn in two passes: everybody is standing within seconds, and the most recently active citizens change into their own avatar as it arrives, in place, without losing their spot or interrupting a walk to the job board. The population counter reads "n / 200" honestly while they arrive rather than reporting a number that did not match the square, and the Reload button on the "failed to load" screen now actually reloads. (`/agora`) `[fix, improvement]`
+- **The Commons now fills with citizens in seconds instead of standing empty**: Agora said it held 200 citizens while the square in front of you stayed empty. Every citizen was waiting on its own 3D model, and those run from 3 MB to 21 MB each, so the world was downloading close to a gigabyte before anyone could stand up: measured, 19 of 200 citizens had arrived after four and a half minutes. On top of that the page asked the server where each citizen's model lived one citizen at a time, 184 separate requests that also crowded out the economy ticker, which is why the population, tasks and $THREE readouts sat on dashes and the feed said it was reconnecting. The population endpoint now answers that question once for the whole square, and the crowd is drawn in two passes: everybody is standing within seconds, and the most recently active citizens change into their own avatar as it arrives, in place, without losing their spot or interrupting a walk to the job board. The population counter reads "n / 200" honestly while they arrive rather than reporting a number that did not match the square, and the Reload button on the "failed to load" screen now actually reloads. The "reconnecting" badge over the ticker also stopped crying wolf: it used to latch on after two failed requests and sit there over perfectly fresh numbers, and it now appears only when nothing new has actually arrived for half a minute, clearing itself the moment it does. (`/agora`) `[fix, improvement]`
- **The creations gallery now counts every creation a creator has made, and pages all the way to the end**: The gallery ranked creators and paged the feed over only the newest 120 creations, however many the feed actually held. A creator's older work was invisible in their profile count, the top-creator board scored people on a fraction of their output, and scrolling the gallery dead-ended early with items still left to show. It now reads the full feed depth it always meant to, and does it in two database round trips instead of two per item, so the deeper read loads faster than the shallow one did. (`/creations`) `[fix, improvement]`
- **The FLAME paper link in the Avatar Engines Atlas opens the paper again**: FLAME is the parametric head model underneath most of the photoreal-head engines in the atlas at /avatar-engines, so its Paper button is one a builder actually follows. It pointed at a Max Planck publication page that answers every visitor, browsers included, with a 403 Forbidden, so the button led to an error page instead of the paper. It now opens the paper PDF that the FLAME project site itself links to. All 68 outbound links on the page were re-checked afterwards and every one of them resolves. (`/avatar-engines`) `[fix]`
- **The Forge community board remembers what you liked**: The community showcase on /forge, and the same feed on the daily page and the model explorer, kept showing your own likes as un-liked. The board is held at the edge for a minute so it loads instantly for everyone, but the copy being held was the one built for a visitor who is not you, and it was handed to you as well. Your like button then started from the wrong state, and pressing it again fought with what the server already knew. The board now keeps a separate copy for a signed browser, so the hearts you filled in stay filled. Alongside it, a security fix on the Game-Ready export: when the export was paid for with $THREE rather than covered by holding, a badly formed payment reference made the server answer with the raw internals of its own database instead of a plain "that payment could not be verified". It now says only what a caller needs, and a database problem is no longer reported as a bad payment, so nobody is told to pay twice for an outage on our side. (`/forge`) `[fix, security]`
diff --git a/data/changelog.json b/data/changelog.json
index c2d2c4127..419971d46 100644
--- a/data/changelog.json
+++ b/data/changelog.json
@@ -24,7 +24,7 @@
{
"date": "2026-08-16",
"title": "The Commons now fills with citizens in seconds instead of standing empty",
- "summary": "Agora said it held 200 citizens while the square in front of you stayed empty. Every citizen was waiting on its own 3D model, and those run from 3 MB to 21 MB each, so the world was downloading close to a gigabyte before anyone could stand up: measured, 19 of 200 citizens had arrived after four and a half minutes. On top of that the page asked the server where each citizen's model lived one citizen at a time, 184 separate requests that also crowded out the economy ticker, which is why the population, tasks and $THREE readouts sat on dashes and the feed said it was reconnecting. The population endpoint now answers that question once for the whole square, and the crowd is drawn in two passes: everybody is standing within seconds, and the most recently active citizens change into their own avatar as it arrives, in place, without losing their spot or interrupting a walk to the job board. The population counter reads \"n / 200\" honestly while they arrive rather than reporting a number that did not match the square, and the Reload button on the \"failed to load\" screen now actually reloads.",
+ "summary": "Agora said it held 200 citizens while the square in front of you stayed empty. Every citizen was waiting on its own 3D model, and those run from 3 MB to 21 MB each, so the world was downloading close to a gigabyte before anyone could stand up: measured, 19 of 200 citizens had arrived after four and a half minutes. On top of that the page asked the server where each citizen's model lived one citizen at a time, 184 separate requests that also crowded out the economy ticker, which is why the population, tasks and $THREE readouts sat on dashes and the feed said it was reconnecting. The population endpoint now answers that question once for the whole square, and the crowd is drawn in two passes: everybody is standing within seconds, and the most recently active citizens change into their own avatar as it arrives, in place, without losing their spot or interrupting a walk to the job board. The population counter reads \"n / 200\" honestly while they arrive rather than reporting a number that did not match the square, and the Reload button on the \"failed to load\" screen now actually reloads. The \"reconnecting\" badge over the ticker also stopped crying wolf: it used to latch on after two failed requests and sit there over perfectly fresh numbers, and it now appears only when nothing new has actually arrived for half a minute, clearing itself the moment it does.",
"tags": [
"fix",
"improvement"
diff --git a/public/changelog.json b/public/changelog.json
index 6d86243f5..34ab74e19 100644
--- a/public/changelog.json
+++ b/public/changelog.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-08-17T00:48:11.098Z",
+ "generated_at": "2026-08-17T00:54:37.680Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json",
"site": {
"name": "three.ws",
@@ -771,7 +771,7 @@
"date": "2026-08-16",
"type": "update",
"title": "The Commons now fills with citizens in seconds instead of standing empty",
- "summary": "Agora said it held 200 citizens while the square in front of you stayed empty. Every citizen was waiting on its own 3D model, and those run from 3 MB to 21 MB each, so the world was downloading close to a gigabyte before anyone could stand up: measured, 19 of 200 citizens had arrived after four and a half minutes. On top of that the page asked the server where each citizen's model lived one citizen at a time, 184 separate requests that also crowded out the economy ticker, which is why the population, tasks and $THREE readouts sat on dashes and the feed said it was reconnecting. The population endpoint now answers that question once for the whole square, and the crowd is drawn in two passes: everybody is standing within seconds, and the most recently active citizens change into their own avatar as it arrives, in place, without losing their spot or interrupting a walk to the job board. The population counter reads \"n / 200\" honestly while they arrive rather than reporting a number that did not match the square, and the Reload button on the \"failed to load\" screen now actually reloads.",
+ "summary": "Agora said it held 200 citizens while the square in front of you stayed empty. Every citizen was waiting on its own 3D model, and those run from 3 MB to 21 MB each, so the world was downloading close to a gigabyte before anyone could stand up: measured, 19 of 200 citizens had arrived after four and a half minutes. On top of that the page asked the server where each citizen's model lived one citizen at a time, 184 separate requests that also crowded out the economy ticker, which is why the population, tasks and $THREE readouts sat on dashes and the feed said it was reconnecting. The population endpoint now answers that question once for the whole square, and the crowd is drawn in two passes: everybody is standing within seconds, and the most recently active citizens change into their own avatar as it arrives, in place, without losing their spot or interrupting a walk to the job board. The population counter reads \"n / 200\" honestly while they arrive rather than reporting a number that did not match the square, and the Reload button on the \"failed to load\" screen now actually reloads. The \"reconnecting\" badge over the ticker also stopped crying wolf: it used to latch on after two failed requests and sit there over perfectly fresh numbers, and it now appears only when nothing new has actually arrived for half a minute, clearing itself the moment it does.",
"link": "/agora",
"tags": [
"fix",
diff --git a/public/changelog.xml b/public/changelog.xml
index 707055e91..671cd1ef6 100644
--- a/public/changelog.xml
+++ b/public/changelog.xml
@@ -580,7 +580,7 @@
<guid isPermaLink="false">2026-08-16:The Commons now fills with citizens in seconds instead of standing empty</guid>
<pubDate>Sun, 16 Aug 2026 12:00:00 GMT</pubDate>
<category>fix</category>
- <description>Agora said it held 200 citizens while the square in front of you stayed empty. Every citizen was waiting on its own 3D model, and those run from 3 MB to 21 MB each, so the world was downloading close to a gigabyte before anyone could stand up: measured, 19 of 200 citizens had arrived after four and a half minutes. On top of that the page asked the server where each citizen's model lived one citizen at a time, 184 separate requests that also crowded out the economy ticker, which is why the population, tasks and $THREE readouts sat on dashes and the feed said it was reconnecting. The population endpoint now answers that question once for the whole square, and the crowd is drawn in two passes: everybody is standing within seconds, and the most recently active citizens change into their own avatar as it arrives, in place, without losing their spot or interrupting a walk to the job board. The population counter reads &quot;n / 200&quot; honestly while they arrive rather than reporting a number that did not match the square, and the Reload button on the &quot;failed to load&quot; screen now actually reloads.</description>
+ <description>Agora said it held 200 citizens while the square in front of you stayed empty. Every citizen was waiting on its own 3D model, and those run from 3 MB to 21 MB each, so the world was downloading close to a gigabyte before anyone could stand up: measured, 19 of 200 citizens had arrived after four and a half minutes. On top of that the page asked the server where each citizen's model lived one citizen at a time, 184 separate requests that also crowded out the economy ticker, which is why the population, tasks and $THREE readouts sat on dashes and the feed said it was reconnecting. The population endpoint now answers that question once for the whole square, and the crowd is drawn in two passes: everybody is standing within seconds, and the most recently active citizens change into their own avatar as it arrives, in place, without losing their spot or interrupting a walk to the job board. The population counter reads &quot;n / 200&quot; honestly while they arrive rather than reporting a number that did not match the square, and the Reload button on the &quot;failed to load&quot; screen now actually reloads. The &quot;reconnecting&quot; badge over the ticker also stopped crying wolf: it used to latch on after two failed requests and sit there over perfectly fresh numbers, and it now appears only when nothing new has actually arrived for half a minute, clearing itself the moment it does.</description>
</item>
<item>
<title>The creations gallery now counts every creation a creator has made, and pages all the way to the end</title>
diff --git a/public/features.json b/public/features.json
index a74d0be9a..0a808daa6 100644
--- a/public/features.json
+++ b/public/features.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-08-17T00:48:11.002Z",
+ "generated_at": "2026-08-17T00:54:37.530Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json",
"site": {
"name": "three.ws",