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.

build(changelog): publish the selfie-to-avatar fix into the live feed, RSS and page index

nirholas207a86d068b3
diff --git a/CHANGELOG.md b/CHANGELOG.md
index c9ca0e507..e8fd68b86 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-09-11
+
+- **Selfie to avatar is unstuck: a scan that used to wait forever now finishes in seconds**: Uploading a photo on the selfie page could sit on the same message indefinitely and never start the scan, with no error and nothing to retry. One copy of the face-tracking runtime held at our CDN was telling browsers to expect 11 MB and then sending a third of that, so the page waited for bytes that were never coming. That copy is gone, and three changes make the failure impossible to repeat silently: the face-tracking runtime now loads from three.ws first instead of a public CDN, any wait on it gives up after fifteen seconds and builds your avatar from the photo as it is, and a photo is never rejected for having no face in it just because the detector could not load. A new check also walks every large file on the site the way a browser asks for it and fails loudly when the bytes do not add up. Measured after the fix: a selfie became a rigged, animation-ready avatar in about fifteen seconds, and still finished in under a minute with the face-tracking runtime completely unreachable. (`/create/selfie`) `[fix, infra]`
+
## 2026-09-10
- **Sonar Control** (`/sonar`): Control a 3D agent with your hands and no camera. three.ws plays an inaudible carrier tone through your speakers and reads the Doppler shift of your hand off the microphone, so a sweep, a push or a lift moves the avatar on screen.
diff --git a/public/changelog-recent.json b/public/changelog-recent.json
index f847e1d6e..eb1f2781a 100644
--- a/public/changelog-recent.json
+++ b/public/changelog-recent.json
@@ -1,14 +1,25 @@
{
- "generated_at": "2026-09-10T21:11:49.543Z",
+ "generated_at": "2026-09-11T01:21:22.349Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json",
"site": {
"name": "three.ws",
"url": "https://three.ws"
},
- "total": 3670,
+ "total": 3671,
"complete": false,
"full_feed": "/changelog.json",
"entries": [
+ {
+ "date": "2026-09-11",
+ "type": "update",
+ "title": "Selfie to avatar is unstuck: a scan that used to wait forever now finishes in seconds",
+ "summary": "Uploading a photo on the selfie page could sit on the same message indefinitely and never start the scan, with no error and nothing to retry. One copy of the face-tracking runtime held at our CDN was telling browsers to expect 11 MB and then sending a third of that, so the page waited for bytes that were never coming. That copy is gone, and three changes make the failure impossible to repeat silently: the face-tracking runtime now loads from three.ws first instead of a public CDN, any wait on it gives up after fifteen seconds and builds your avatar from the photo as it is, and a photo is never rejected for having no face in it just because the detector could not load. A new check also walks every large file on the site the way a browser asks for it and fails loudly when the bytes do not add up. Measured after the fix: a selfie became a rigged, animation-ready avatar in about fifteen seconds, and still finished in under a minute with the face-tracking runtime completely unreachable.",
+ "link": "/create/selfie",
+ "tags": [
+ "fix",
+ "infra"
+ ]
+ },
{
"date": "2026-09-10",
"type": "launch",
@@ -1608,16 +1619,6 @@
"fix",
"infra"
]
- },
- {
- "date": "2026-09-07",
- "type": "update",
- "title": "Studio Lab reads the same splat formats as the viewer",
- "summary": "The Lab's Gaussian-splat tools ran on a different rendering engine from the Splat Viewer, so the two disagreed about which files they would open: the viewer had just gained .spz and .sog and the Lab had not. Both now share one engine, so anything one of them opens the other opens too, the Lab works out a dropped file's format from its contents instead of its name, and its camera frames the scene it loaded.",
- "link": "/forge-studio",
- "tags": [
- "improvement"
- ]
}
]
}
diff --git a/public/changelog.json b/public/changelog.json
index ec12ce81d..487bd24a8 100644
--- a/public/changelog.json
+++ b/public/changelog.json
@@ -1,11 +1,22 @@
{
- "generated_at": "2026-09-10T21:11:49.517Z",
+ "generated_at": "2026-09-11T01:21:22.327Z",
"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-09-11",
+ "type": "update",
+ "title": "Selfie to avatar is unstuck: a scan that used to wait forever now finishes in seconds",
+ "summary": "Uploading a photo on the selfie page could sit on the same message indefinitely and never start the scan, with no error and nothing to retry. One copy of the face-tracking runtime held at our CDN was telling browsers to expect 11 MB and then sending a third of that, so the page waited for bytes that were never coming. That copy is gone, and three changes make the failure impossible to repeat silently: the face-tracking runtime now loads from three.ws first instead of a public CDN, any wait on it gives up after fifteen seconds and builds your avatar from the photo as it is, and a photo is never rejected for having no face in it just because the detector could not load. A new check also walks every large file on the site the way a browser asks for it and fails loudly when the bytes do not add up. Measured after the fix: a selfie became a rigged, animation-ready avatar in about fifteen seconds, and still finished in under a minute with the face-tracking runtime completely unreachable.",
+ "link": "/create/selfie",
+ "tags": [
+ "fix",
+ "infra"
+ ]
+ },
{
"date": "2026-09-10",
"type": "launch",
diff --git a/public/changelog.xml b/public/changelog.xml
index aade3997e..4bb34997d 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>Selfie to avatar is unstuck: a scan that used to wait forever now finishes in seconds</title>
+ <link>https://three.ws/create/selfie</link>
+ <guid isPermaLink="false">2026-09-11:Selfie to avatar is unstuck: a scan that used to wait forever now finishes in seconds</guid>
+ <pubDate>Fri, 11 Sep 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>Uploading a photo on the selfie page could sit on the same message indefinitely and never start the scan, with no error and nothing to retry. One copy of the face-tracking runtime held at our CDN was telling browsers to expect 11 MB and then sending a third of that, so the page waited for bytes that were never coming. That copy is gone, and three changes make the failure impossible to repeat silently: the face-tracking runtime now loads from three.ws first instead of a public CDN, any wait on it gives up after fifteen seconds and builds your avatar from the photo as it is, and a photo is never rejected for having no face in it just because the detector could not load. A new check also walks every large file on the site the way a browser asks for it and fails loudly when the bytes do not add up. Measured after the fix: a selfie became a rigged, animation-ready avatar in about fifteen seconds, and still finished in under a minute with the face-tracking runtime completely unreachable.</description>
+ </item>
<item>
<title>Sonar Control</title>
<link>https://three.ws/sonar</link>
diff --git a/public/features.json b/public/features.json
index 7938f500d..273bfcf17 100644
--- a/public/features.json
+++ b/public/features.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-09-10T21:11:49.503Z",
+ "generated_at": "2026-09-11T01:21:22.312Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json",
"site": {
"name": "three.ws",