6 Commits

Include renames

Author	SHA1	Message	Date
dhkatzandClaude Opus 5.5	171e8173af	Recently added, shop sorting, and outfit cards with T5 products ... - 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	2280ad6314	Show T5 products in the client's shop; keep float IDs and unknown paths off IMVU ... The shop's T5 filter (maturity_rating "t5") is answered from the hub's products, fetched so they can be shown and tried on; buying T5 products adds them to the hub library, and product.php details for community products are answered here. The client sends some product IDs as floats ("2000000008.0"): product.php passed the worn community product to IMVU that way. Every ID is now read either way, and products.Guard refuses any request to IMVU that still names a local ID given out. T5DE_PROXY_DUMP logs request and response bodies. Co-Authored-By: Claude Opus 5.5 <[email protected]>	2026-10-30 01:15:16 -07:00
dhkatzandClaude Opus 5.5	6506c641f0	Keep community products out of saved outfits ... Saving an outfit (POST /api/outfits.php) sent its community products to IMVU. They're now taken out (any ID in the community range, known or not), the request re-signed, and the products remembered under the outfit's ID, then added back when the client loads its saved outfits (marked AP if one is adult). Co-Authored-By: Claude Opus 5.5 <[email protected]>	2026-10-29 19:30:59 -07:00
dhkatzandClaude Opus 5.5	ca7a86ce89	T5 products in the client's inventory ... 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 ... 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