t5de-hub

26 Commits 2 Branches 2 Tags

3 Commits

Include renames

Author	SHA1	Message	Date
dhkatzandClaude Opus 5.5	f65f36c1ea	Decorations over IMVU rooms: the hub's side CI / test (push) Successful in 1m13s Details T5 products placed in ordinary IMVU rooms, kept per room instance (room_decoration, migration 0006). GET /api/v1/decorations/:instance (and ?instances= for up to 20) gives what the viewer may see, with a hash; PUT is for the room owner's T5DE person only, checks the products exist, and tells every realtime session with a chat in that room ({"type": "decor"}). Hosted rooms' IDs are refused. Co-Authored-By: Claude Opus 5.5 <[email protected]>	2026-10-30 03:58:42 -07:00
dhkatzandClaude Opus 5.5	6668b55117	Products: carry the IMVU parent's image and categories CI / test (push) Successful in 49s Details Revisions with an IMVU parent store its public info (image, category path, gender) from IMVU's product API, looked up after registering and in a periodic pass. Product views gain parent, image and categories; GET /products takes category and limit. The website shows the image on cards and product pages. Co-Authored-By: Claude Opus 5.5 <[email protected]>	2026-10-30 01:03:02 -07:00
dhkatzandClaude Opus 5.5	b4f6fce9df	Product registry: catalogs, revisions, product info and libraries CI / test (push) Successful in 43s Details The hub registers catalogs (hidden until a moderator approves them), hands out upload tokens, and records the revisions catalogs register after validating uploads: numbered, never changed, signed by the hub (its own Ed25519 key, published at /.well-known/t5de-keys.json). Creators edit product info (descriptions cleaned by an allowlist) and can retract revisions. People get products into their library, optionally staying on a revision; the proxy asks which revision to load and where. Contract in docs/products.md. Co-Authored-By: Claude Opus 5.5 <[email protected]>	2026-10-29 18:53:52 -07:00

Author

SHA1

Message

Date

dhkatzandClaude Opus 5.5

f65f36c1ea

Decorations over IMVU rooms: the hub's side

CI / test (push) Successful in 1m13s

Details

T5 products placed in ordinary IMVU rooms, kept per room instance
(room_decoration, migration 0006). GET /api/v1/decorations/:instance (and
?instances= for up to 20) gives what the viewer may see, with a hash;
PUT is for the room owner's T5DE person only, checks the products exist,
and tells every realtime session with a chat in that room ({"type":
"decor"}). Hosted rooms' IDs are refused.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

2026-10-30 03:58:42 -07:00

dhkatzandClaude Opus 5.5

6668b55117

Products: carry the IMVU parent's image and categories

CI / test (push) Successful in 49s

Details

Revisions with an IMVU parent store its public info (image, category path, gender)
from IMVU's product API, looked up after registering and in a periodic pass.
Product views gain parent, image and categories; GET /products takes category and
limit. The website shows the image on cards and product pages.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

2026-10-30 01:03:02 -07:00

dhkatzandClaude Opus 5.5

b4f6fce9df

Product registry: catalogs, revisions, product info and libraries

CI / test (push) Successful in 43s

Details

The hub registers catalogs (hidden until a moderator approves them), hands out upload tokens, and records the
revisions catalogs register after validating uploads: numbered, never changed, signed by the hub (its own
Ed25519 key, published at /.well-known/t5de-keys.json). Creators edit product info (descriptions cleaned by an
allowlist) and can retract revisions. People get products into their library, optionally staying on a
revision; the proxy asks which revision to load and where. Contract in docs/products.md.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

2026-10-29 18:53:52 -07:00