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.
JavaScript 3d-generationai-agentsanimationavatardigital-humangenerative-aiglbgltfimage-to-3dllmmcpmcp-servermodel-context-protocolsolanatext-to-3dthreejsweb-componentswebglwebxrx402
docs(changelog): regenerate the published feeds for the smart home entry
nirholasce0d96eac0ec
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex 8c3b0955c..4ec43b015 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -34,6 +34,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr- **Sign Language Avatars is usable the moment the page opens**: The signing avatar on /sign-language is a multi-megabyte model, and until it finished downloading the page had nothing to say: an empty box, an empty status line, and buttons that had not been wired yet, so an early click on Sign it did nothing at all. The stage now shows a breathing silhouette while the avatar loads, every control is wired before the download starts, and anything you type, click or open with a ?say= link in the meantime is queued and signed the moment the avatar lands. If the model fails to download, the stage says so and offers Retry the avatar plus a link to the sign API below, which runs on the server and works without the 3D preview; the vocabulary chips and the Sign it button now explain why they cannot sign instead of doing nothing. An avatar with no signing skeleton says so in the same words. (`/sign-language`) `[improvement, fix]`- **Sign Mirror tells you why the camera did not start where you are actually looking**: On /sign-mirror, pressing "Turn the camera on" and being refused, or being on a device with no camera, put the explanation on the far side of the page: it appeared in the status strip over the 3D avatar, in the other column, while the box directly above the button you had just pressed carried on giving the same idle tip as before. The button snapped back to "Turn the camera on" with nothing visibly changed beside it, so a refused camera read as a button that simply did not work. Every camera and hand-tracker failure now lands in that box beside the button, in both the side-by-side and the stacked phone layout, and the box turns amber and solid-edged so a problem no longer looks like a coaching tip. The sentences themselves are unchanged and still say what to do next, naming the browser permission prompt, a camera busy in another app, a missing camera, or a hand tracker that could not be downloaded. Picking another letter clears the warning and returns the box to its normal hint. (`/sign-mirror`) `[fix, improvement]`- **Signal Marketplace: publisher avatars appear, prices read like money, and a feed page no longer goes blank for signed-out readers**: A full audit of /signals, the directory of paid trading feeds ranked by proven edge. Four real defects came out of it. Every publisher without a profile picture showed an empty grey square: the generated fallback avatar is an image, and the card was assigning it to a CSS background, which browsers ignore, so it never painted. A publisher whose profile picture had gone missing showed the browser's broken-image icon; both now render as an image that quietly falls back to the generated avatar. Prices were printed as raw numbers, so a feed charging 12.345678 USDC advertised exactly that; amounts are now grouped and rounded the way money reads, while a genuine sub-cent price keeps its digits instead of rounding to zero. Subscriber counts skipped the same shortening every other number on the card uses and printed as 1234567. Worst of all, opening any live feed's own page while signed out crashed the render and left a blank panel where the sign-in prompt belongs, which is exactly the reader that panel exists to convert. Each card's screen-reader description now carries every number a sighted reader sees (rank, edge, hit rate, average ROI, signal counts, subscribers and price) instead of just the headline score, and the loading skeleton's shimmer now sweeps across the card rather than starting halfway off it. (`/signals`) `[fix, improvement]`+- **Smart Home reads and works without a mouse, and now speaks past English**: Three fixes to the connected house, all of them things a person hits rather than reads about. The room you have selected states what is on in it at full contrast: on the highlighted row that line sat below the readable minimum, which is exactly the row you are looking at. Answering the safety question that stands between you and an unlocked door now hands the keyboard back to the control you pressed, whether you answer with Yes, with Cancel or with Escape; the list rebuilds itself while the question is up, so the keyboard used to land back at the top of the page and you had to tab the whole house again. And the connect flow, the manage view and the floorplan editor now read from the same translation catalog the rest of the site does, so they are ready for the 86 languages three.ws ships in. Your own words are never translated: the name you gave your house, your rooms, your devices and anything your Home Assistant says come back exactly as you wrote them, in every language. (`/docs/smart-home`) `[improvement, fix]`- **Smart Home: the connection pool now sizes itself to the server it is running on**: The number of houses one server holds open at once was set by hand, in a different place from the memory that has to hold them, and the two drifted apart three times. Left alone, that ends with a server running out of memory and taking the whole API down with it, which every part of three.ws would feel, not just Smart Home. The pool now reads the memory its own container actually has and refuses to hold more houses than fit, saying so in the health endpoint when it does. When there is less room it connects fewer houses per server and keeps working, instead of risking an outage for everybody. (`/docs/smart-home`) `[infra, fix]`- **The "have you tried" card no longer hangs off the side of the screen on a phone**: The small suggestion card that appears in the bottom corner of the site was drawn 34 pixels wider than the space it asked for, because its padding and border were being added on top of its width instead of counted inside it. On a phone that pushed the card 22 pixels past the left edge of the screen, so its kicker, title and description were all cut off mid-word and the button inside it ran wider than the card itself. This only happened on the pages that do not load the main site stylesheet, which includes the whole markets family: the screener, coin pages, categories, the heatmap and about thirty others. The card now sits fully on screen with an even gutter on both sides at every width, and its button fits inside it. (`/screener`) `[fix]`- **The 3D Playground recovers when a model will not load, and now works from the keyboard**: Dropping a .glb into /playground had exactly one failure mode: a dimmed screen and a spinner that never stopped. If the file was corrupt, the download stalled, or the 3D viewer script itself was blocked, nothing on the page said so and there was no way back. That spinner is now a shimmer inside the viewer frame instead of a curtain over the whole page, so the controls stay usable while a model streams, and a failure lands in a designed error card that names what went wrong and offers Retry or a file picker. A load that never finishes gives up after 25 seconds rather than hanging forever. The lighting presets no longer strand the scene on the previous preset’s exposure. The page also gained the structure it was missing: a real heading that says what it is for, headings on every control group, an accessible name on each switch, slider and field, a focus ring on everything you can tab to, and an upload button the keyboard can actually reach (it was hidden with display:none, which drops it out of the tab order entirely). On a phone the top navigation scrolls instead of vanishing. Animation names read out of an uploaded file are rendered as text, never as markup. (`/playground`) `[fix, improvement]`diff --git a/public/changelog-recent.json b/public/changelog-recent.jsonindex 7fed5092c..229758b49 100644--- a/public/changelog-recent.json+++ b/public/changelog-recent.json@@ -1,11 +1,11 @@{- "generated_at": "2026-09-09T15:24:45.853Z",+ "generated_at": "2026-09-09T15:27:22.929Z","generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json","site": {"name": "three.ws","url": "https://three.ws"},- "total": 3643,+ "total": 3644,"complete": false,"full_feed": "/changelog.json","entries": [@@ -309,6 +309,17 @@"improvement"]},+ {+ "date": "2026-09-09",+ "type": "update",+ "title": "Smart Home reads and works without a mouse, and now speaks past English",+ "summary": "Three fixes to the connected house, all of them things a person hits rather than reads about. The room you have selected states what is on in it at full contrast: on the highlighted row that line sat below the readable minimum, which is exactly the row you are looking at. Answering the safety question that stands between you and an unlocked door now hands the keyboard back to the control you pressed, whether you answer with Yes, with Cancel or with Escape; the list rebuilds itself while the question is up, so the keyboard used to land back at the top of the page and you had to tab the whole house again. And the connect flow, the manage view and the floorplan editor now read from the same translation catalog the rest of the site does, so they are ready for the 86 languages three.ws ships in. Your own words are never translated: the name you gave your house, your rooms, your devices and anything your Home Assistant says come back exactly as you wrote them, in every language.",+ "link": "/docs/smart-home",+ "tags": [+ "improvement",+ "fix"+ ]+ },{"date": "2026-09-09","type": "update",@@ -1600,17 +1611,6 @@"tags": ["launch"]- },- {- "date": "2026-09-04",- "type": "update",- "title": "A knock now holds the money until you actually get a reply",- "summary": "Paying to reach someone used to send your money the instant the payment cleared, which meant an owner could take every knock and answer none, and you had no way to get it back. A new Solana program makes the payment conditional: it sits in a vault that only the knock itself controls, and exactly three things can happen to it. The owner answers inside the reply window and gets paid, the owner declines and you are refunded in full with no fee taken, or the window closes and anyone at all can trigger your refund. There is no admin key that can move a knock that is parked, the fee is capped at 10% in the program itself, and the fee you agreed to when you knocked cannot be raised on money that is already in escrow. Your message never touches the chain: only a fingerprint of it is stored, so either side can later prove what was sent without publishing it. Ten invariants covering every one of those promises run against the real compiled program on every test run.",- "link": null,- "tags": [- "feature",- "security"- ]}]}diff --git a/public/changelog.json b/public/changelog.jsonindex 54e07856b..c78cb995a 100644--- a/public/changelog.json+++ b/public/changelog.json@@ -1,5 +1,5 @@{- "generated_at": "2026-09-09T15:24:45.795Z",+ "generated_at": "2026-09-09T15:27:22.887Z","generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json","site": {"name": "three.ws",@@ -306,6 +306,17 @@"improvement"]},+ {+ "date": "2026-09-09",+ "type": "update",+ "title": "Smart Home reads and works without a mouse, and now speaks past English",+ "summary": "Three fixes to the connected house, all of them things a person hits rather than reads about. The room you have selected states what is on in it at full contrast: on the highlighted row that line sat below the readable minimum, which is exactly the row you are looking at. Answering the safety question that stands between you and an unlocked door now hands the keyboard back to the control you pressed, whether you answer with Yes, with Cancel or with Escape; the list rebuilds itself while the question is up, so the keyboard used to land back at the top of the page and you had to tab the whole house again. And the connect flow, the manage view and the floorplan editor now read from the same translation catalog the rest of the site does, so they are ready for the 86 languages three.ws ships in. Your own words are never translated: the name you gave your house, your rooms, your devices and anything your Home Assistant says come back exactly as you wrote them, in every language.",+ "link": "/docs/smart-home",+ "tags": [+ "improvement",+ "fix"+ ]+ },{"date": "2026-09-09","type": "update",diff --git a/public/changelog.xml b/public/changelog.xmlindex 9d3b47c97..73f065602 100644--- a/public/changelog.xml+++ b/public/changelog.xml@@ -230,6 +230,14 @@<category>fix</category><description>A full audit of /signals, the directory of paid trading feeds ranked by proven edge. Four real defects came out of it. Every publisher without a profile picture showed an empty grey square: the generated fallback avatar is an image, and the card was assigning it to a CSS background, which browsers ignore, so it never painted. A publisher whose profile picture had gone missing showed the browser's broken-image icon; both now render as an image that quietly falls back to the generated avatar. Prices were printed as raw numbers, so a feed charging 12.345678 USDC advertised exactly that; amounts are now grouped and rounded the way money reads, while a genuine sub-cent price keeps its digits instead of rounding to zero. Subscriber counts skipped the same shortening every other number on the card uses and printed as 1234567. Worst of all, opening any live feed's own page while signed out crashed the render and left a blank panel where the sign-in prompt belongs, which is exactly the reader that panel exists to convert. Each card's screen-reader description now carries every number a sighted reader sees (rank, edge, hit rate, average ROI, signal counts, subscribers and price) instead of just the headline score, and the loading skeleton's shimmer now sweeps across the card rather than starting halfway off it.</description></item>+ <item>+ <title>Smart Home reads and works without a mouse, and now speaks past English</title>+ <link>https://three.ws/docs/smart-home</link>+ <guid isPermaLink="false">2026-09-09:Smart Home reads and works without a mouse, and now speaks past English</guid>+ <pubDate>Wed, 09 Sep 2026 12:00:00 GMT</pubDate>+ <category>improvement</category>+ <description>Three fixes to the connected house, all of them things a person hits rather than reads about. The room you have selected states what is on in it at full contrast: on the highlighted row that line sat below the readable minimum, which is exactly the row you are looking at. Answering the safety question that stands between you and an unlocked door now hands the keyboard back to the control you pressed, whether you answer with Yes, with Cancel or with Escape; the list rebuilds itself while the question is up, so the keyboard used to land back at the top of the page and you had to tab the whole house again. And the connect flow, the manage view and the floorplan editor now read from the same translation catalog the rest of the site does, so they are ready for the 86 languages three.ws ships in. Your own words are never translated: the name you gave your house, your rooms, your devices and anything your Home Assistant says come back exactly as you wrote them, in every language.</description>+ </item><item><title>Smart Home: the connection pool now sizes itself to the server it is running on</title><link>https://three.ws/docs/smart-home</link>diff --git a/public/features.json b/public/features.jsonindex 8dd135d1d..3159d14b9 100644--- a/public/features.json+++ b/public/features.json@@ -1,5 +1,5 @@{- "generated_at": "2026-09-09T15:24:45.754Z",+ "generated_at": "2026-09-09T15:27:22.859Z","generated_by": "scripts/build-page-index.mjs from data/pages.json","site": {"name": "three.ws",