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): regenerate the public feed with the trending contrast and walk keyboard entries

nirholas7abcf72f9512
diff --git a/CHANGELOG.md b/CHANGELOG.md
index c238da3a8..47958fa49 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -4,6 +4,10 @@
Public history for [three.ws](https://three.ws), newest first. New pages come from `added` dates in data/pages.json; everything else is curated in data/changelog.json. Also available as [JSON](https://three.ws/changelog.json) and [RSS](https://three.ws/changelog.xml), live at [three.ws/changelog](https://three.ws/changelog).
+## 2026-08-16
+
+- **Trending: muted text on the board is readable, and the Tip button that only navigated is gone**: Ten pieces of text on the Trending board sat below the WCAG AA contrast floor: the subtitle, the two unselected tabs, the 7d and all-time buttons, the column headers, agent descriptions and the unit labels next to each number. They are all legible now, and the Oracle link in the footnote is underlined instead of being told apart by colour alone. The wallet chip on each row carried a Tip button and a hover card, but the whole row is a link, so the browser followed the row instead of running either one: pressing Tip took you to the agent's wallet page rather than opening a tip. Both controls are gone from the board and tipping stays where it works, on the agent page the row opens, while the chip keeps showing the wallet address and its live balance. An automated accessibility scan now reports zero violations on all three boards and on their loading, empty and error states. (`/trending`) `[fix, improvement]`
+
## 2026-08-15
- **3D viewer: shared model links keep their name, and every button on the page does something**: Open a shared model link and the browser tab now keeps the model's name instead of resetting to a generic one a moment after the page loads, so a bookmarked or shared viewer link is identifiable again. The model's name is also the page's heading now, which is what screen readers and search engines read first. A link whose address does not point at a real https model file used to show a Download button that did nothing; the page now explains what is wrong with the link and offers the only action that helps. Copying the embed snippet from 'Embed it anywhere' confirms it copied, and launching a coin from the model shows that the token image is rendering, both of which were being written to a part of the page the visitor could not see. The page's own title and description now describe what the viewer actually does: preview any public glTF or GLB model, then pose, restyle, scene, AR, embed or download it. (`/viewer`) `[fix, improvement]`
@@ -94,7 +98,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
- **The vanity receipt verifier stops calling honest receipts fraudulent, and the avatar CLI takes a Solana address**: Two documented commands did not do what their page said. The command-line verifier for a provably-fair vanity address receipt scored the difficulty claim with the retired flat model, the one that treats every Base58 character as equally likely. Every receipt issued since the leading-character correction landed therefore failed its difficulty check and was reported as untrustworthy, even though the in-browser verifier at /vanity/verify passed the same receipt. The verifier now reads the model each receipt names in its own signed difficulty block, exactly as the page and the SDK do, so current receipts verify and older ones keep verifying under the model they were issued under. Separately, the Rig Doctor page showed an avatar-manifest command taking a Solana address as the owner, which the CLI rejected outright: it understood Ethereum addresses and full CAIP-10 identifiers and nothing else. Since Solana is the home chain, a bare Solana address is now accepted and recorded as solana:mainnet-beta. Alongside those, eight tutorial and reference pages were audited against the code they describe: the Vercel self-hosting guide had a stale copy of the config file and pointed at a migrations folder that has moved, the MCP guide listed three placeholder OAuth scopes where the live server publishes twelve real per-capability ones, and the Avatar CLI page pinned a version number that npm has never had. (`/docs/rig-doctor`) `[fix, docs, sdk]`
- **The vanity SDK now uses the payment wallet you hand it, and the in-chat 3D avatar keeps its tuned lighting**: Three fixes in the developer packages. The @three-ws/vanity SDK documented a fetch option on its paid address-grinding lane but silently ignored it, so a developer who passed a payment-enabled fetch got a payment-required error back instead of the keypair they paid for; that option now works, as do a custom API host and key. The avatar MCP server's in-chat 3D viewer had been hand-tuned with softer shadows, brighter exposure and a neutral environment light, but the script that rebuilds it before every release still produced the old flat version, so the next release would have quietly undone the tuning; the script now produces the tuned viewer, and the same settings apply to the fallback view for chat apps that cannot run the interactive one. The tool SDK's quick-start example pointed at an API that does not exist and skipped the wrapper an MCP server needs to return anything at all, so following it produced a tool that answered with nothing; it now runs end to end against a real free three.ws endpoint. `[fix, sdk, docs]`
- **The vault's session controls moved out of browser pop-ups and its model panel became a real modal**: The vault page (/vault) gives every visitor a session key that acts as their buyer identity: it is what pays for a model and what decrypts it in the browser afterwards. Everything you could do with that key used to happen through the browser's own grey pop-up boxes, which offered no way to see the address, no way to copy it, and no way to start over with a fresh one. The session strip now does all of it on the page: copy the address to fund it from anywhere, open an inline amount field to top it up from your wallet with the amount checked before the wallet is even asked, and rotate to a new key behind a two-step confirmation that first spells out what a new key costs you. The panel that opens when you pick a model is now a proper dialog: it says it is checking your purchase status instead of flashing a Buy button it might have to take back, keyboard focus stays inside it, Escape closes it, and closing puts you back on the model you were reading. When listings fail to load, the page now offers a way to try again instead of only stating the failure, and both empty states point at what to do next. (`/vault`) `[improvement, fix]`
-- **The Walk page shows the real top walkers again instead of claiming nobody has walked**: The Top walkers board on /walk read "No walks logged yet. Be the first to put down some distance" for every visitor, while twenty-nine people had in fact logged distance and the full leaderboard at /walk-leaderboard listed all of them. The page was asking the leaderboard endpoint for the ranking and getting a correct answer back, then looking for it under half a dozen field names the endpoint has never used, finding nothing, and drawing its empty state. It now reads the shape the endpoint actually returns, so the top three walkers appear with their handles, avatars, distances, and a link to each profile, and it asks for only the three rows it draws instead of the first fifty. The social section under it now shows placeholder cards while it loads rather than a blank gap. (`/walk`) `[fix]`
+- **The Walk page shows the real top walkers again instead of claiming nobody has walked**: The Top walkers board on /walk read "No walks logged yet. Be the first to put down some distance" for every visitor, while twenty-nine people had in fact logged distance and the full leaderboard at /walk-leaderboard listed all of them. The page was asking the leaderboard endpoint for the ranking and getting a correct answer back, then looking for it under half a dozen field names the endpoint has never used, finding nothing, and drawing its empty state. It now reads the shape the endpoint actually returns, so the top three walkers appear with their handles, avatars, distances, and a link to each profile, and it asks for only the three rows it draws instead of the first fifty. The social section under it now shows placeholder cards while it loads rather than a blank gap. Two keyboard fixes travelled with it: tabbing into one of the nine live demo frames now draws a focus ring, where before you landed inside a demo with nothing on screen saying so, and the touch joystick inside every Walk embed carried a screen-reader label that ARIA does not permit on an unlabelled element, so assistive technology could announce it wrongly. (`/walk`) `[fix]`
- **The Wardrobe's garment forge no longer locks itself after a job expires**: Forging a garment takes about seven minutes, so the Wardrobe (/wardrobe) remembers your job and picks the progress back up when you return. The catch: once the forge had cleared that finished job, the page treated the resulting "no such job" answer as a temporary network blip, so it kept the job saved, kept the prompt box and the Forge it button greyed out, and retried forever. One expired job made the generator permanently unusable on every later visit, with "Reconnecting" as the only explanation. An expired job is now recognised as finished business: the page clears it, unlocks the form, and tells you nothing is pending. A genuine outage is still retried, but it now gives the form back after several failed attempts and keeps your job saved so a reload resumes it. Separately, inspecting a piece in 3D and then typing in the search box no longer throws that 3D view away and reload every thumbnail on the page, filtering by slot with the keyboard keeps your place instead of dropping focus, the search and prompt boxes finally show a visible keyboard focus ring, and when the catalog itself fails to load the page now names the actual cause underneath the apology instead of swallowing it. (`/wardrobe`) `[fix, improvement]`
- **The widgets gallery stopped clipping its controls on phones and now recovers from a failed load**: The widgets gallery (/widgets) is where you pick a pre-built chat, voice, or 3D-avatar embed and copy the one line of HTML that drops it into your own page. On a narrow phone screen, each card's preview frame and its Customize panel were wider than the card itself, so the right edge got cut off: the mint field ran past the panel and the Reset button was pushed off-screen entirely, out of reach. Card layout now shrinks to the screen it is on, and the whole page is clean from 320px up. If the showcase list fails to load, the page now says so in plain language and offers a Try again button that reloads it in place, plus a link to the widget docs, instead of leaving a one-line error with no way forward. If the list comes back empty, the gallery explains what it would normally show and points at the Studio rather than showing a blank space. The widget count in the header now reflects the widgets actually loaded in every language, the page has a real top-level heading, the type filters announce which one is active to screen readers, the Preview and Code tabs are wired up as real tabs, and Escape closes the embed-format menu. (`/widgets`) `[fix, improvement]`
- **Three docs pages stop pointing readers at a dead page, a missing section, and a snippet that does nothing**: The Vanity page told you to grind a long address yourself in the browser at /vanity, but that path has never existed and answers 404; the in-browser grinder lives at /vanity-wallet, and both links on the page now go there. In Troubleshooting, the fix for a Quick Look model that opens and instantly closes linked to a model-optimization section that is not on the AR page, so the link dropped you at the top with nothing to read; it now opens the section that actually covers it. The same page told you to add a responsive attribute to size an inline embed, with a snippet that set the width in CSS. Neither half worked: responsive sizing is already on by default, and the element reads the width attribute rather than the computed style, so the documented snippet never produced the 3:4 ratio it promised. The instructions now show the form that does work, and name the two things that switch it off. (`/docs/troubleshooting`) `[fix, docs]`
diff --git a/public/changelog.json b/public/changelog.json
index e72aeb122..59b1b85c4 100644
--- a/public/changelog.json
+++ b/public/changelog.json
@@ -1,11 +1,22 @@
{
- "generated_at": "2026-08-16T00:24:26.928Z",
+ "generated_at": "2026-08-16T00:58:19.283Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json",
"site": {
"name": "three.ws",
"url": "https://three.ws"
},
"entries": [
+ {
+ "date": "2026-08-16",
+ "type": "update",
+ "title": "Trending: muted text on the board is readable, and the Tip button that only navigated is gone",
+ "summary": "Ten pieces of text on the Trending board sat below the WCAG AA contrast floor: the subtitle, the two unselected tabs, the 7d and all-time buttons, the column headers, agent descriptions and the unit labels next to each number. They are all legible now, and the Oracle link in the footnote is underlined instead of being told apart by colour alone. The wallet chip on each row carried a Tip button and a hover card, but the whole row is a link, so the browser followed the row instead of running either one: pressing Tip took you to the agent's wallet page rather than opening a tip. Both controls are gone from the board and tipping stays where it works, on the agent page the row opens, while the chip keeps showing the wallet address and its live balance. An automated accessibility scan now reports zero violations on all three boards and on their loading, empty and error states.",
+ "link": "/trending",
+ "tags": [
+ "fix",
+ "improvement"
+ ]
+ },
{
"date": "2026-08-15",
"type": "update",
@@ -965,7 +976,7 @@
"date": "2026-08-15",
"type": "update",
"title": "The Walk page shows the real top walkers again instead of claiming nobody has walked",
- "summary": "The Top walkers board on /walk read \"No walks logged yet. Be the first to put down some distance\" for every visitor, while twenty-nine people had in fact logged distance and the full leaderboard at /walk-leaderboard listed all of them. The page was asking the leaderboard endpoint for the ranking and getting a correct answer back, then looking for it under half a dozen field names the endpoint has never used, finding nothing, and drawing its empty state. It now reads the shape the endpoint actually returns, so the top three walkers appear with their handles, avatars, distances, and a link to each profile, and it asks for only the three rows it draws instead of the first fifty. The social section under it now shows placeholder cards while it loads rather than a blank gap.",
+ "summary": "The Top walkers board on /walk read \"No walks logged yet. Be the first to put down some distance\" for every visitor, while twenty-nine people had in fact logged distance and the full leaderboard at /walk-leaderboard listed all of them. The page was asking the leaderboard endpoint for the ranking and getting a correct answer back, then looking for it under half a dozen field names the endpoint has never used, finding nothing, and drawing its empty state. It now reads the shape the endpoint actually returns, so the top three walkers appear with their handles, avatars, distances, and a link to each profile, and it asks for only the three rows it draws instead of the first fifty. The social section under it now shows placeholder cards while it loads rather than a blank gap. Two keyboard fixes travelled with it: tabbing into one of the nine live demo frames now draws a focus ring, where before you landed inside a demo with nothing on screen saying so, and the touch joystick inside every Walk embed carried a screen-reader label that ARIA does not permit on an unlabelled element, so assistive technology could announce it wrongly.",
"link": "/walk",
"tags": [
"fix"
diff --git a/public/changelog.xml b/public/changelog.xml
index ba4e6c84f..17fda8276 100644
--- a/public/changelog.xml
+++ b/public/changelog.xml
@@ -6,6 +6,14 @@
<atom:link href="https://three.ws/changelog.xml" rel="self" type="application/rss+xml"/>
<description>What's new on three.ws: features, improvements, and releases, newest first.</description>
<language>en</language>
+ <item>
+ <title>Trending: muted text on the board is readable, and the Tip button that only navigated is gone</title>
+ <link>https://three.ws/trending</link>
+ <guid isPermaLink="false">2026-08-16:Trending: muted text on the board is readable, and the Tip button that only navigated is gone</guid>
+ <pubDate>Sun, 16 Aug 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>Ten pieces of text on the Trending board sat below the WCAG AA contrast floor: the subtitle, the two unselected tabs, the 7d and all-time buttons, the column headers, agent descriptions and the unit labels next to each number. They are all legible now, and the Oracle link in the footnote is underlined instead of being told apart by colour alone. The wallet chip on each row carried a Tip button and a hover card, but the whole row is a link, so the browser followed the row instead of running either one: pressing Tip took you to the agent's wallet page rather than opening a tip. Both controls are gone from the board and tipping stays where it works, on the agent page the row opens, while the chip keeps showing the wallet address and its live balance. An automated accessibility scan now reports zero violations on all three boards and on their loading, empty and error states.</description>
+ </item>
<item>
<title>3D viewer: shared model links keep their name, and every button on the page does something</title>
<link>https://three.ws/viewer</link>
@@ -716,7 +724,7 @@
<guid isPermaLink="false">2026-08-15:The Walk page shows the real top walkers again instead of claiming nobody has walked</guid>
<pubDate>Sat, 15 Aug 2026 12:00:00 GMT</pubDate>
<category>fix</category>
- <description>The Top walkers board on /walk read &quot;No walks logged yet. Be the first to put down some distance&quot; for every visitor, while twenty-nine people had in fact logged distance and the full leaderboard at /walk-leaderboard listed all of them. The page was asking the leaderboard endpoint for the ranking and getting a correct answer back, then looking for it under half a dozen field names the endpoint has never used, finding nothing, and drawing its empty state. It now reads the shape the endpoint actually returns, so the top three walkers appear with their handles, avatars, distances, and a link to each profile, and it asks for only the three rows it draws instead of the first fifty. The social section under it now shows placeholder cards while it loads rather than a blank gap.</description>
+ <description>The Top walkers board on /walk read &quot;No walks logged yet. Be the first to put down some distance&quot; for every visitor, while twenty-nine people had in fact logged distance and the full leaderboard at /walk-leaderboard listed all of them. The page was asking the leaderboard endpoint for the ranking and getting a correct answer back, then looking for it under half a dozen field names the endpoint has never used, finding nothing, and drawing its empty state. It now reads the shape the endpoint actually returns, so the top three walkers appear with their handles, avatars, distances, and a link to each profile, and it asks for only the three rows it draws instead of the first fifty. The social section under it now shows placeholder cards while it loads rather than a blank gap. Two keyboard fixes travelled with it: tabbing into one of the nine live demo frames now draws a focus ring, where before you landed inside a demo with nothing on screen saying so, and the touch joystick inside every Walk embed carried a screen-reader label that ARIA does not permit on an unlabelled element, so assistive technology could announce it wrongly.</description>
</item>
<item>
<title>The Wardrobe's garment forge no longer locks itself after a job expires</title>
diff --git a/public/features.json b/public/features.json
index 9dcc48040..893594b0d 100644
--- a/public/features.json
+++ b/public/features.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-08-16T00:24:26.714Z",
+ "generated_at": "2026-08-16T00:58:19.274Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json",
"site": {
"name": "three.ws",