t5de-proxy

36 Commits 1 Branch 3 Tags

3 Commits

Include renames

Author	SHA1	Message	Date
dhkatzandClaude Opus 5.5	171e8173af	Recently added, shop sorting, and outfit cards with T5 products CI / build (push) Successful in 34s Details - The inventory's Recently Added puts T5 products added to the library in the last 30 days first. - The shop's T5 listing follows its sort menu: Best Match ranks by name, Newest by upload date (oldest first ascending); ratings and prices (T5 products have neither) sort by newest. - Outfit cards: outfit_products.php gets the outfit's community products added (not for sale), find_bundle.php is asked about IMVU's products only, and removing one in the card (remove_pids) keeps it from IMVU and forgets it in the outfit. Co-Authored-By: Claude Opus 5.5 <[email protected]>	2026-10-30 02:45:02 -07:00
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	c281fb572c	Get T5 products from the hub's catalogs CI / build (push) Successful in 25s Details The proxy keeps the person's library in a cache folder (hub-products in its data folder), one pack per product, served like any other pack: the hub says which revision to load and which catalogs host it, each file comes from a catalog and is checked against the hub's sha256 (files are kept by hash, so a new revision only downloads what changed), and adult files are fetched with the hub's access token. Products someone wears in a room that aren't here yet are fetched too, and put on them when they arrive. Co-Authored-By: Claude Opus 5.5 <[email protected]>	2026-10-29 18:56:26 -07:00

Author

SHA1

Message

Date

dhkatzandClaude Opus 5.5

171e8173af

Recently added, shop sorting, and outfit cards with T5 products

CI / build (push) Successful in 34s

Details

- The inventory's Recently Added puts T5 products added to the library in the last 30 days first.
- The shop's T5 listing follows its sort menu: Best Match ranks by name, Newest by upload date
  (oldest first ascending); ratings and prices (T5 products have neither) sort by newest.
- Outfit cards: outfit_products.php gets the outfit's community products added (not for sale),
  find_bundle.php is asked about IMVU's products only, and removing one in the card (remove_pids)
  keeps it from IMVU and forgets it in the outfit.

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

2026-10-30 02:45:02 -07:00

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

c281fb572c

Get T5 products from the hub's catalogs

CI / build (push) Successful in 25s

Details

The proxy keeps the person's library in a cache folder (hub-products in its data folder), one pack per
product, served like any other pack: the hub says which revision to load and which catalogs host it, each file
comes from a catalog and is checked against the hub's sha256 (files are kept by hash, so a new revision only
downloads what changed), and adult files are fetched with the hub's access token. Products someone wears in a
room that aren't here yet are fetched too, and put on them when they arrive.

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

2026-10-29 18:56:26 -07:00