2 Commits

Include renames

Author	SHA1	Message	Date
dhkatzandClaude Opus 5.5	2df46da3ad	Invitations into hosted rooms: the dialog's details, and joining as a public room ... The invitation carries the room as the dialog shows it (name, owner, image, occupancy, description) and the inviter's picture, age and gender from IMVU's public profile. Accepting names the room (room_instance_id), so the client joins it as a public room with the invite rather than opening a private chat, and getParticipants before joining asks the hub, so the client sees its inviter there. Co-Authored-By: Claude Opus 5.5 <[email protected]>	2026-10-30 06:44:33 -07:00
dhkatzandClaude Opus 5.5	210bc064e9	Hosted rooms phase 2: boots, invitations, favorites, ratings, live occupancy ... The client's own room actions work in hosted rooms, through the hub (t5de-hub's docs/hosted-rooms.md, Phase 2): a "*boot" line goes to the room, then to the hub as room.boot; refused joins are declined as the client's own are (booted ones as booted). Invitations: chat.attemptInvite polls the hub's answer, and the invitee's client gets chatInvite on its user queue, accepting with the invite. Favorites (favorite_rooms.php, add/removeFavoriteRoom, the favorites list), ratings (room_rating.php), the room card's moderators, image and score, and room_occupancy queues fed from room.watch. Web API parameters are read from JSON bodies too (imvu.http.securePost), and hosted rows added to an empty IMVU list keep their flags numeric ("0" counted as set). Co-Authored-By: Claude Opus 5.5 <[email protected]>	2026-10-30 06:30:42 -07:00