t5de-proxy

15 Commits 1 Branch 3 Tags

3 Commits

Include renames

Author	SHA1	Message	Date
dhkatzandClaude Opus 5.5	ca7a86ce89	T5 products in the client's inventory CI / build (push) Successful in 25s Details The inventory's product list (test.showInventory) gets the community products the person has: local packs, and hub products in their library. Hiding one is answered by the proxy (and removes a hub product from the library). When the library changes, the client is told to load its inventory again, with the server event IMVU sends after a purchase. A product whose revision or info changes gets a new local ID, since the client keeps product info for good; names lose characters the client's pages could take as HTML. Co-Authored-By: Claude Opus 5.5 <[email protected]>	2026-10-29 18:59:52 -07:00
dhkatzandClaude Opus 5.5	93fa2f5d90	Room channel: other T5DE users' community products on their avatars CI / build (push) Successful in 28s Details The proxy follows the client's IMQ chat subscriptions and tells the hub which chats it's in (and the room, from chat.getOrMakeChat). For the other T5DE users the hub says are in a chat, it gives the client the community products it has packs for, as use and remove lines from them, and adds them to the whole outfits they send. It also takes community products out of the outfit the client posts to IMVU's chat participant endpoint, which had been sending them to IMVU. Co-Authored-By: Claude Opus 5.5 <[email protected]>	2026-10-29 18:14:44 -07:00
dhkatzandClaude Opus 5.5	887e8a2364	Serve community products from local packs The proxy serves products from local packs (t5de-api's format) under local IDs from 2,000,000,000: product info and permission answers (with the parent's derivation chain from IMVU), the product's CFL, and the shop's bundle lookup. Community products are taken out of outfit saves and outfit chat commands before IMVU sees them, remembered per account with the outfit they belong to, and added back when the client loads that outfit. Changed requests are re-signed with the session key from the login response. Co-Authored-By: Claude Opus 5.5 <[email protected]>	2026-10-29 03:17:14 -07:00

Author

SHA1

Message

Date

dhkatzandClaude Opus 5.5

ca7a86ce89

T5 products in the client's inventory

CI / build (push) Successful in 25s

Details

The inventory's product list (test.showInventory) gets the community products the person has: local packs, and
hub products in their library. Hiding one is answered by the proxy (and removes a hub product from the library).
When the library changes, the client is told to load its inventory again, with the server event IMVU sends
after a purchase. A product whose revision or info changes gets a new local ID, since the client keeps product
info for good; names lose characters the client's pages could take as HTML.

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

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

dhkatzandClaude Opus 5.5

93fa2f5d90

Room channel: other T5DE users' community products on their avatars

CI / build (push) Successful in 28s

Details

The proxy follows the client's IMQ chat subscriptions and tells the hub which chats it's in (and the room, from
chat.getOrMakeChat). For the other T5DE users the hub says are in a chat, it gives the client the community
products it has packs for, as *use and *remove lines from them, and adds them to the whole outfits they send.
It also takes community products out of the outfit the client posts to IMVU's chat participant endpoint, which
had been sending them to IMVU.

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

2026-10-29 18:14:44 -07:00

dhkatzandClaude Opus 5.5

887e8a2364

Serve community products from local packs

The proxy serves products from local packs (t5de-api's format) under local IDs from 2,000,000,000: product
info and permission answers (with the parent's derivation chain from IMVU), the product's CFL, and the shop's
bundle lookup. Community products are taken out of outfit saves and outfit chat commands before IMVU sees
them, remembered per account with the outfit they belong to, and added back when the client loads that
outfit. Changed requests are re-signed with the session key from the login response.

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

2026-10-29 03:17:14 -07:00