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): record the trade terminal exit card and rebuild the public feed

nirholas0e19655370e4
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 4f69c0d8f..91ed8bfd7 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -33,6 +33,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
- **DeFi Yields: the filter row is styled again, the phone layout fits, and protocol links stop dead-ending**: The Yields explorer was shipped with its filter row pointing at a stylesheet the page never loaded, so the chain, project and minimum-TVL controls rendered as raw browser dropdowns crammed into one line with their labels colliding. They are proper labelled fields again at every screen size. On a 320 pixel phone the Total TVL card used to be pushed off the right edge with no way to scroll to it, and opening a pool parked its chart outside the visible area inside a table you had to drag sideways; the three headline stats now stack, and the chart stays pinned in view and is drawn at the drawer's real width, so its axis labels are legible instead of shrunk to a third of their size. Fourteen DeFiLlama protocols carry a bracket, a plus or an exclamation mark in their name, and every yield row for one of them linked to a page that answered 404: those links now resolve. When the upstream feed is down, the three stat cards say so rather than sitting as loading placeholders forever, and the result count says the data is unavailable instead of going blank. (`/yields`) `[fix, improvement]`
- **Docs pages stop opening with a wall of raw metadata, and the AWS pages say where the Marketplace listing actually stands**: Nine documentation pages are written as article drafts, so each one starts with a small block of publishing metadata: the title, where it is meant to run, its tags. That block is meant for the tooling, not for you, but the docs reader had no idea what it was and rendered it as an enormous heading at the very top of the article, above the actual writing. It is now recognised and hidden, on the page and in the Copy page text, so those articles begin where they should. Reading the same pages closely turned up claims that had drifted: several said three.ws was already live on AWS Marketplace and billing usage to your AWS invoice. The integration is built and deployed, but the listing itself has not been published yet and the pricing decision is a free subscription with no AWS metering, so the AWS pages now say exactly that and point at the page that tracks the status. The MCP article's vanity-address tool was also listed at a metered price of up to fifty cents; it is a flat five cents per grind, which is what the code has always charged. (`/docs/aws-marketplace`) `[docs, fix]`
- **Eight build tutorials now match what the platform actually does**: An audit of eight tutorials found instructions that could not work. The AI-brain tutorial described a model line-up that had been superseded: it never mentioned the Claude 5 family (Sonnet 5, Opus 5, Fable 5), which are live and selectable, and it recommended Sonnet 4.6 as the default. It also sent you to screens that do not exist, telling you to add API keys under a gear icon in My Agents and to change models, sampling knobs, and streaming under a Brain menu. Provider keys actually live in the AI Provider Keys panel on your account page, the model is a field on the agent's embed policy, and streaming has no off-switch. The promised usage tab with token charts and threshold emails did not exist either; the tutorial now documents the real per-agent usage read and points at the monthly quota and per-minute rate limit, which are the controls actually enforced before your money is spent. It also now explains that a visitor can never escalate your agent onto a paid model. The custom-GLB tutorial was worse for anyone following along: it linked a Studio address that no longer resolves, and four of its commands invoked gltf-transform subcommands that have never existed, so converting an FBX, renaming animation clips, and the full Mixamo walkthrough all failed at the first step. Those are replaced with the converter the platform itself uses and a clip-renaming script that was run against a real avatar to confirm it works. Its Draco flag was wrong, its upload path pointed at the wrong page, and it still warned that an avatar without an idle clip would stand frozen in a T-pose, which stopped being true when animation retargeting became universal. Finally, the page-events tutorial listed the wrong fallback order for emote animations. (`/tutorials/connect-ai-brain`) `[docs, fix]`
+- **Generation Watch: a dropped connection now says so, and the page reads properly to a screen reader**: The page that shows a 3D generation in progress had one way to fail badly: if the tab lost contact with three.ws, it kept animating the countdown against a server it could not reach, silently retrying for forty minutes before admitting anything was wrong. It now stops after four failed checks, tells you plainly that the connection dropped and that your model is still being generated on our servers, and offers a "Keep watching" button that picks up where it left off. It also resumes on its own the moment the browser comes back online. The phase line used to lag a step behind the picture, announcing "Painting the concept" while the concept art was already on screen; it now switches to "Sculpting the 3D mesh" as soon as the artwork arrives. The page had no heading at all for a screen reader and read its four-times-a-second timer aloud continuously; it now has a real title heading, announces each state change once, and keeps the countdown quiet. It follows your light or dark theme instead of forcing dark, gives the three.ws link a visible focus ring, and no longer lets the site-wide Cmd+K hint sit on top of its buttons. The hand-off into the 3D viewer is now checked before it is followed, so it can only ever land on three.ws. (`/watch`) `[fix, improvement]`
- **Grind-Bounty Market: shared bounty links now open the bounty, and "Grind this" grinds that one**: Every bounty the market posts comes back with its own link (three.ws/vanity/bounties#<id>), and the API hands that link out as the bounty's home. Opening one did nothing: the page rewrote the address back to the plain board and left you to hunt for the card, which was not even there if the bounty had already been won or had expired off the open filter. A linked bounty is now fetched by id and pinned above the board, whatever its state, with a Clear button to go back; a link to a bounty that no longer exists says so instead of leaving you staring at the board. The Grind this button on a card was equally misleading: it switched you to the grinder and hoped, while the worker pool always took whichever bounty happened to be first in the queue. It now sets a real priority target that the pool grinds ahead of the queue, shows which bounty is pinned, lets you clear it, and says so plainly if that bounty stops being claimable. Refunding an expired bounty used to ask which address to send the escrow to and then ignore the answer, because the destination is bound to the address recorded when the bounty was funded; it now names the amount and where the money goes and takes a plain yes or no. Four smaller fixes shipped with it: the board no longer fetches itself twice on every page load, the market stats strip and the grinder leaderboard offer a retry when they cannot load instead of a dead end, the tab strip answers arrow keys and Home/End the way its role promises, and the sealed-delivery key field is finally wired to its label for screen readers. (`/vanity/bounties`) `[fix, improvement]`
- **Grind-Bounty Market: shared bounty links now open the bounty, and "Grind this" grinds that one**: Every bounty the market posts comes back with its own link (three.ws/vanity/bounties#<id>), and the API hands that link out as the bounty's home. Opening one did nothing: the page rewrote the address back to the plain board and left you to hunt for the card, which was not even there if the bounty had already been won or had expired off the open filter. A linked bounty is now fetched by id and pinned above the board, whatever its state, with a Clear button to go back; a link to a bounty that no longer exists says so instead of leaving you staring at the board. The Grind this button on a card was equally misleading: it switched you to the grinder and hoped, while the worker pool always took whichever bounty happened to be first in the queue. It now sets a real priority target that the pool grinds ahead of the queue, shows which bounty is pinned, lets you clear it, and says so plainly if that bounty stops being claimable. Refunding an expired bounty used to ask which address to send the escrow to and then ignore the answer, because the destination is bound to the address recorded when the bounty was funded; it now names the amount and where the money goes and takes a plain yes or no. Four smaller fixes shipped with it: the board no longer fetches itself twice on every page load, the market stats strip and the grinder leaderboard offer a retry when they cannot load instead of a dead end, the tab strip answers arrow keys and Home/End the way its role promises, and the sealed-delivery key field is finally wired to its label for screen readers. (`/vanity/bounties`) `[fix, improvement]`
- **KOL Tracker: the whole board is readable on a phone, and dead columns are gone**: On any screen narrower than the board, five of the tracker's seven columns were unreachable: the page could not shrink, and the overflow was clipped rather than scrollable, so P&L, win rate and trade count simply were not there on a phone. The board now fits any viewport and scrolls sideways on its own. Columns with nothing to show are dropped instead of rendering a full column of dashes, so followers and volume appear only once there is data behind them. Each wallet is printed once (it used to appear twice on every row) and links to its Solscan account, so any number on the board can be audited on-chain. Where the P&L for a window comes from is now stated once under the board instead of repeating on all fifty rows, the board refreshes every minute with the time of the last update on screen, and a refresh that fails keeps the rows you are reading rather than blanking them. A failed load now offers a Try again button, an empty window points at the trader leaderboard, and the whole board is navigable and announced properly with a keyboard and a screen reader. (`/tracker`) `[fix, improvement]`
@@ -102,7 +103,6 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
- **Viability now shows skeletons while it reads and says what broke when a read fails**: The Viability page (/viability) reports the two real money loops behind three.ws: $THREE marketplace GMV and take-rate, and guarded agent coin trades with realized P&L. Until now, a slow read left the page as a bare headline with nothing underneath, and a failed read quietly deleted both panels while the page still claimed it had just updated. Both panels now hold their shape with skeletons while the live read is in flight, so the numbers land without the page jumping. If a read fails, that panel says so in plain language, names the reason (offline, rate limited, the status the API returned, or a deploy still rolling out), and offers a Retry that re-runs only that panel, leaving a healthy one untouched. The freshness stamp is honest too: it reports a read in flight, a failed read, or how long ago the figures on screen were actually good. Section titles are now real headings, and the network toggle announces itself correctly to screen readers. (`/viability`) `[improvement, fix]`
- **Voice and vision SDKs ship runnable examples, and the x402 seller SDK reads its Solana sponsor from the environment**: @three-ws/voice and @three-ws/vision-mcp now include example scripts you can run as-is against the live free lanes: the voice one speaks a sentence, animates a face from those exact bytes, and transcribes it back; the vision one probes the lane, writes alt text for an image, and reads the text off it. @three-ws/x402-server used to demand the Solana sponsor account as a code option even though its own error message told you to set X402_FEE_PAYER_SOLANA, so a correctly configured deployment still got missing_fee_payer; it now reads that environment variable when the option is omitted. The VS Code x402 extension's endpoint scaffolder was generating Base-only endpoints and now generates Solana-first ones, matching every paid route on the platform, and it ships with a test suite covering which payment requirement it selects. `[sdk, fix]`
- **Voice Lab: a dead voice provider now leaves the menu instead of failing on your first click**: Google Gemini has been refusing every request on the platform's account, and Voice Lab had no way to know: it listed all 30 Gemini voices, put them first, and the first Preview a visitor pressed came back with a wall of raw error JSON quoting internal project numbers. Now the first refusal is the last one anybody sees. A provider that turns down the platform's credentials is withheld from the voice list for a few minutes with the reason written on its filter chip, its voices disappear from the grid the moment a preview hits it, and the free Microsoft Edge and NVIDIA lanes are named as the alternative. It restores itself the moment the provider works again, with nothing to switch back on by hand. Failure messages across the page are now single readable sentences rather than vendor dumps. The rest is the same page, checked end to end: the catalog error state offers a working Try again, a search that matches nothing offers Clear filters, a deployment with no provider at all says so instead of claiming no voices match, the Remove button next to your own ElevenLabs key is styled like a button again, every control shows a focus ring when you tab to it, and the text box in the playground has a label. The space bar no longer hijacks the button you are pressing: it starts a recording only when nothing on the page is focused. (`/voice`) `[fix, improvement]`
-- **Walk Leaderboard: switching filters no longer strands the board, and an empty board tells you how to get on it**: Clicking through the leaderboard's filters faster than the board could load left it stuck: a second click while a request was open was dropped outright, so the board could sit on a loading skeleton that never resolved, or show one metric's rows under another metric's column header. Every request now supersedes the one before it, so whatever you clicked last is what you get. An empty board used to say the same thing whichever metric you were on, which was wrong for Sites: sites only count where your avatar walks away from three.ws, so that state now explains it and links to the walk companion, while distance and time point at the walk itself. Any narrow window that comes up empty also offers a jump to All Time rather than leaving you at a dead end, and a failed load offers a retry that says what went wrong. The board now lives up to "updates live": it refreshes itself while you are watching, shows how many walkers are ranked and when it last updated, and a refresh that fails quietly keeps the rows you are reading. For screen readers the board is a real table, the top three medals now announce their rank instead of reading as an empty cell, the momentum column speaks its direction, and the two filter groups are proper radio groups with arrow-key and Home/End navigation. (`/walk-leaderboard`) `[fix, improvement]`
- **Watchlist: the portfolio summary stops reporting numbers it does not have**: The watchlist summary bar claimed $0 of 24h volume across every coin you watch. The pump.fun feed simply stops reporting 24h volume once a coin graduates, and the bar was treating each missing figure as a zero and adding them up, so a confident "$0" stood where the honest answer is "not reported". Every aggregate now counts only the coins that actually report it, shows a dash when none do, and says on hover how many of your watched coins it covers. The Oracle tier bar does the same: coins the Oracle has not scored get their own marked-off slice instead of quietly vanishing from the distribution, and each unscored card now carries an "unrated" badge that links to its coin page rather than leaving a blank corner. If the Oracle itself is unreachable, the page says so instead of labelling every coin unrated. Also fixed: at 320px wide the "Clear all" button was pushed off the edge of the screen with no way to reach it, the add-a-coin field had no visible keyboard focus ring, and the page description advertised a verdict the page does not show. (`/watchlist`) `[fix, improvement]`
- **Widget analytics can tell you where your visitors are again, and a shared widget link previews correctly everywhere**: The country column in your widget stats has been empty since the platform moved to its current host in July. A visitor's country was read from a header only the old host set, so once it was gone every view was recorded with no country at all and the top-countries panel stayed blank no matter how much traffic a widget got. Country is now read from the headers our current edge provides, and it is checked against the shape of a real two-letter country code before it is stored, so nobody can push junk into your analytics by editing a request. Chat sessions on talking-agent widgets get the same fix. Separately, the oEmbed endpoint that Slack, Discord, WordPress, Ghost and Notion call to unfurl a shared widget link now says plainly when a consumer asks for a format we do not publish, instead of returning JSON labelled as the format that was asked for and leaving the embed broken with nothing to explain why. (`/widgets`) `[fix, improvement]`
- **World Lines: the AR encounter is finally offered, and the quest tabs answer the keyboard**: The page has always promised an AR challenge, and the immersive encounter was fully built, but nothing ever put a button in front of it: a phone that can run WebXR was quietly handed the flat panel instead. Devices that support immersive AR now see a "Meet the agent in AR" option next to "Begin the encounter", and if the headset session refuses to start, the panel ceremony picks up where it left off. The four tabs (Near me, Explore, My proofs, Create) now behave like a real tab strip: arrow keys and Home/End move between them, only the selected tab sits in the tab order, each tab writes its own address so a tab can be linked and the back button walks back through them. Opening a region on the Explore tab used to leave a heading over an empty space when every quest in it had expired or filled up, and a failure there was a single line of red text with no way to retry; both are now proper states. Focus rings are visible again across the page (they were being drawn in near-black on a black background), the opened region is highlighted, the encounter dialog now takes and holds keyboard focus and hands it back where you left it, and a proof whose date is missing says so rather than claiming it was earned in 1970. (`/world-lines`) `[fix, improvement]`
diff --git a/data/changelog.json b/data/changelog.json
index 127694f16..0545f88e9 100644
--- a/data/changelog.json
+++ b/data/changelog.json
@@ -1,6 +1,36 @@
{
"$comment": "Curated changelog entries for three.ws, the editorial layer of the public changelog. New PAGE launches are tracked automatically via the `added` field in data/pages.json; this file is for everything else holders care about: improvements, fixes, SDK releases, trading/payments capabilities, security work. scripts/build-page-index.mjs merges both sources into CHANGELOG.md, public/changelog.json, and public/changelog.xml. Newest first. Allowed tags: feature, improvement, fix, sdk, infra, docs, security. `link` is optional and must be a live three.ws path.",
"entries": [
+ {
+ "date": "2026-08-15",
+ "title": "glTF Validator: a file it cannot read now says why, and the page is usable from the keyboard",
+ "summary": "Drop a model the validator cannot parse and the page used to claim it had been \"validated\", print \"Validator failed: undefined\", and, when a URL fetch was refused, wipe both result panels to an empty screen with no explanation. Every one of those paths now renders a real failure card: what broke, the actual reason, what to try next (CORS on the host, a .gltf that needs packing into a .glb, a download that did not finish), and a Try again button that reruns the same file or URL. The status line no longer reports a success it did not have, and it counts the issues found instead of just saying \"validated\". The file picker was unreachable without a mouse, so keyboard users could only use the URL box; it is now in the tab order with a visible ring on the drop zone. The three tabs move with the arrow keys, the Agent ID and Chain ID fields have labels, the report headings no longer compete with the page title, and the Submit Report dialog closes on Escape or a click outside, keeps focus inside while open, returns it where it was, and no longer sits underneath the site header. A dead link in the report footnote now points at the Khronos extension registry.",
+ "tags": [
+ "fix",
+ "improvement"
+ ],
+ "link": "/validation"
+ },
+ {
+ "date": "2026-08-15",
+ "title": "Walk Leaderboard: switching filters no longer strands the board, and an empty board tells you how to get on it",
+ "summary": "Clicking through the leaderboard's filters faster than the board could load left it stuck: a second click while a request was open was dropped outright, so the board could sit on a loading skeleton that never resolved, or show one metric's rows under another metric's column header. Every request now supersedes the one before it, so whatever you clicked last is what you get. An empty board used to say the same thing whichever metric you were on, which was wrong for Sites: sites only count where your avatar walks away from three.ws, so that state now explains it and links to the walk companion, while distance and time point at the walk itself. Any narrow window that comes up empty also offers a jump to All Time rather than leaving you at a dead end, and a failed load offers a retry that says what went wrong. The board now lives up to \"updates live\": it refreshes itself while you are watching, shows how many walkers are ranked and when it last updated, and a refresh that fails quietly keeps the rows you are reading. For screen readers the board is a real table, the top three medals now announce their rank instead of reading as an empty cell, the momentum column speaks its direction, and the two filter groups are proper radio groups with arrow-key and Home/End navigation.",
+ "tags": [
+ "fix",
+ "improvement"
+ ],
+ "link": "/walk-leaderboard"
+ },
+ {
+ "date": "2026-08-15",
+ "title": "Generation Watch: a dropped connection now says so, and the page reads properly to a screen reader",
+ "summary": "The page that shows a 3D generation in progress had one way to fail badly: if the tab lost contact with three.ws, it kept animating the countdown against a server it could not reach, silently retrying for forty minutes before admitting anything was wrong. It now stops after four failed checks, tells you plainly that the connection dropped and that your model is still being generated on our servers, and offers a \"Keep watching\" button that picks up where it left off. It also resumes on its own the moment the browser comes back online. The phase line used to lag a step behind the picture, announcing \"Painting the concept\" while the concept art was already on screen; it now switches to \"Sculpting the 3D mesh\" as soon as the artwork arrives. The page had no heading at all for a screen reader and read its four-times-a-second timer aloud continuously; it now has a real title heading, announces each state change once, and keeps the countdown quiet. It follows your light or dark theme instead of forcing dark, gives the three.ws link a visible focus ring, and no longer lets the site-wide Cmd+K hint sit on top of its buttons. The hand-off into the 3D viewer is now checked before it is followed, so it can only ever land on three.ws.",
+ "tags": [
+ "fix",
+ "improvement"
+ ],
+ "link": "/watch"
+ },
{
"date": "2026-08-15",
"title": "Your master wallet: creating one no longer reports a failure, and your balances are real numbers again",
diff --git a/public/changelog.json b/public/changelog.json
index 296de7331..d3dd333fb 100644
--- a/public/changelog.json
+++ b/public/changelog.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-08-15T21:35:55.185Z",
+ "generated_at": "2026-08-15T21:47:06.871Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json",
"site": {
"name": "three.ws",
@@ -297,6 +297,17 @@
"fix"
]
},
+ {
+ "date": "2026-08-15",
+ "type": "update",
+ "title": "Generation Watch: a dropped connection now says so, and the page reads properly to a screen reader",
+ "summary": "The page that shows a 3D generation in progress had one way to fail badly: if the tab lost contact with three.ws, it kept animating the countdown against a server it could not reach, silently retrying for forty minutes before admitting anything was wrong. It now stops after four failed checks, tells you plainly that the connection dropped and that your model is still being generated on our servers, and offers a \"Keep watching\" button that picks up where it left off. It also resumes on its own the moment the browser comes back online. The phase line used to lag a step behind the picture, announcing \"Painting the concept\" while the concept art was already on screen; it now switches to \"Sculpting the 3D mesh\" as soon as the artwork arrives. The page had no heading at all for a screen reader and read its four-times-a-second timer aloud continuously; it now has a real title heading, announces each state change once, and keeps the countdown quiet. It follows your light or dark theme instead of forcing dark, gives the three.ws link a visible focus ring, and no longer lets the site-wide Cmd+K hint sit on top of its buttons. The hand-off into the 3D viewer is now checked before it is followed, so it can only ever land on three.ws.",
+ "link": "/watch",
+ "tags": [
+ "fix",
+ "improvement"
+ ]
+ },
{
"date": "2026-08-15",
"type": "update",
@@ -1049,17 +1060,6 @@
"improvement"
]
},
- {
- "date": "2026-08-15",
- "type": "update",
- "title": "Walk Leaderboard: switching filters no longer strands the board, and an empty board tells you how to get on it",
- "summary": "Clicking through the leaderboard's filters faster than the board could load left it stuck: a second click while a request was open was dropped outright, so the board could sit on a loading skeleton that never resolved, or show one metric's rows under another metric's column header. Every request now supersedes the one before it, so whatever you clicked last is what you get. An empty board used to say the same thing whichever metric you were on, which was wrong for Sites: sites only count where your avatar walks away from three.ws, so that state now explains it and links to the walk companion, while distance and time point at the walk itself. Any narrow window that comes up empty also offers a jump to All Time rather than leaving you at a dead end, and a failed load offers a retry that says what went wrong. The board now lives up to \"updates live\": it refreshes itself while you are watching, shows how many walkers are ranked and when it last updated, and a refresh that fails quietly keeps the rows you are reading. For screen readers the board is a real table, the top three medals now announce their rank instead of reading as an empty cell, the momentum column speaks its direction, and the two filter groups are proper radio groups with arrow-key and Home/End navigation.",
- "link": "/walk-leaderboard",
- "tags": [
- "fix",
- "improvement"
- ]
- },
{
"date": "2026-08-15",
"type": "update",
diff --git a/public/changelog.xml b/public/changelog.xml
index adfc74413..e8283d08c 100644
--- a/public/changelog.xml
+++ b/public/changelog.xml
@@ -222,6 +222,14 @@
<category>docs</category>
<description>An audit of eight tutorials found instructions that could not work. The AI-brain tutorial described a model line-up that had been superseded: it never mentioned the Claude 5 family (Sonnet 5, Opus 5, Fable 5), which are live and selectable, and it recommended Sonnet 4.6 as the default. It also sent you to screens that do not exist, telling you to add API keys under a gear icon in My Agents and to change models, sampling knobs, and streaming under a Brain menu. Provider keys actually live in the AI Provider Keys panel on your account page, the model is a field on the agent's embed policy, and streaming has no off-switch. The promised usage tab with token charts and threshold emails did not exist either; the tutorial now documents the real per-agent usage read and points at the monthly quota and per-minute rate limit, which are the controls actually enforced before your money is spent. It also now explains that a visitor can never escalate your agent onto a paid model. The custom-GLB tutorial was worse for anyone following along: it linked a Studio address that no longer resolves, and four of its commands invoked gltf-transform subcommands that have never existed, so converting an FBX, renaming animation clips, and the full Mixamo walkthrough all failed at the first step. Those are replaced with the converter the platform itself uses and a clip-renaming script that was run against a real avatar to confirm it works. Its Draco flag was wrong, its upload path pointed at the wrong page, and it still warned that an avatar without an idle clip would stand frozen in a T-pose, which stopped being true when animation retargeting became universal. Finally, the page-events tutorial listed the wrong fallback order for emote animations.</description>
</item>
+ <item>
+ <title>Generation Watch: a dropped connection now says so, and the page reads properly to a screen reader</title>
+ <link>https://three.ws/watch</link>
+ <guid isPermaLink="false">2026-08-15:Generation Watch: a dropped connection now says so, and the page reads properly to a screen reader</guid>
+ <pubDate>Sat, 15 Aug 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>The page that shows a 3D generation in progress had one way to fail badly: if the tab lost contact with three.ws, it kept animating the countdown against a server it could not reach, silently retrying for forty minutes before admitting anything was wrong. It now stops after four failed checks, tells you plainly that the connection dropped and that your model is still being generated on our servers, and offers a &quot;Keep watching&quot; button that picks up where it left off. It also resumes on its own the moment the browser comes back online. The phase line used to lag a step behind the picture, announcing &quot;Painting the concept&quot; while the concept art was already on screen; it now switches to &quot;Sculpting the 3D mesh&quot; as soon as the artwork arrives. The page had no heading at all for a screen reader and read its four-times-a-second timer aloud continuously; it now has a real title heading, announces each state change once, and keeps the countdown quiet. It follows your light or dark theme instead of forcing dark, gives the three.ws link a visible focus ring, and no longer lets the site-wide Cmd+K hint sit on top of its buttons. The hand-off into the 3D viewer is now checked before it is followed, so it can only ever land on three.ws.</description>
+ </item>
<item>
<title>Grind-Bounty Market: shared bounty links now open the bounty, and &quot;Grind this&quot; grinds that one</title>
<link>https://three.ws/vanity/bounties</link>
@@ -774,14 +782,6 @@
<category>fix</category>
<description>Google Gemini has been refusing every request on the platform's account, and Voice Lab had no way to know: it listed all 30 Gemini voices, put them first, and the first Preview a visitor pressed came back with a wall of raw error JSON quoting internal project numbers. Now the first refusal is the last one anybody sees. A provider that turns down the platform's credentials is withheld from the voice list for a few minutes with the reason written on its filter chip, its voices disappear from the grid the moment a preview hits it, and the free Microsoft Edge and NVIDIA lanes are named as the alternative. It restores itself the moment the provider works again, with nothing to switch back on by hand. Failure messages across the page are now single readable sentences rather than vendor dumps. The rest is the same page, checked end to end: the catalog error state offers a working Try again, a search that matches nothing offers Clear filters, a deployment with no provider at all says so instead of claiming no voices match, the Remove button next to your own ElevenLabs key is styled like a button again, every control shows a focus ring when you tab to it, and the text box in the playground has a label. The space bar no longer hijacks the button you are pressing: it starts a recording only when nothing on the page is focused.</description>
</item>
- <item>
- <title>Walk Leaderboard: switching filters no longer strands the board, and an empty board tells you how to get on it</title>
- <link>https://three.ws/walk-leaderboard</link>
- <guid isPermaLink="false">2026-08-15:Walk Leaderboard: switching filters no longer strands the board, and an empty board tells you how to get on it</guid>
- <pubDate>Sat, 15 Aug 2026 12:00:00 GMT</pubDate>
- <category>fix</category>
- <description>Clicking through the leaderboard's filters faster than the board could load left it stuck: a second click while a request was open was dropped outright, so the board could sit on a loading skeleton that never resolved, or show one metric's rows under another metric's column header. Every request now supersedes the one before it, so whatever you clicked last is what you get. An empty board used to say the same thing whichever metric you were on, which was wrong for Sites: sites only count where your avatar walks away from three.ws, so that state now explains it and links to the walk companion, while distance and time point at the walk itself. Any narrow window that comes up empty also offers a jump to All Time rather than leaving you at a dead end, and a failed load offers a retry that says what went wrong. The board now lives up to &quot;updates live&quot;: it refreshes itself while you are watching, shows how many walkers are ranked and when it last updated, and a refresh that fails quietly keeps the rows you are reading. For screen readers the board is a real table, the top three medals now announce their rank instead of reading as an empty cell, the momentum column speaks its direction, and the two filter groups are proper radio groups with arrow-key and Home/End navigation.</description>
- </item>
<item>
<title>Watchlist: the portfolio summary stops reporting numbers it does not have</title>
<link>https://three.ws/watchlist</link>
diff --git a/public/features.json b/public/features.json
index ba9b6d0ca..f59b1d329 100644
--- a/public/features.json
+++ b/public/features.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-08-15T21:35:54.904Z",
+ "generated_at": "2026-08-15T21:47:06.597Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json",
"site": {
"name": "three.ws",