t5de/t5de-proxy
2
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 3 Wiki Activity
36 Commits 1 Branch 3 Tags
v0.2.0
Commit Graph
4 Commits
Author SHA1 Message Date
dhkatzandClaude Opus 5.5 8ae45fc07a Choose the hub: Settings' choice, else the install's channel's; state kept per hub
CI / build (push) Successful in 18s
Details 
The client's Settings > T5DE chooses the hub from the next start on (POST /hub/server, kept in server.json);
without a choice, -channel (which the client passes) decides: staging for nightly and dev, T5DE's hub for
releases. $T5DE_HUB still wins. Each hub's sign-in, product IDs and products are kept in their own folder
(T5DE's hub in the data folder as before, others in hubs/<host>), so a hub never gets another's token and
product IDs from two hubs never clash; a sign-in saved for another hub is ignored. Signing in always goes to
this run's hub.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
 2026-11-02 09:09:34 -08:00
dhkatzandClaude Opus 5.5 455dae1013 Answer the client's T5 badge lookups
CI / build (push) Successful in 29s
Details 
POST http://t5de-proxy.local/badges {imvuIds} -> {badges}: which IMVU accounts show the T5 badge,
asked of the hub (POST /api/v1/badges, in batches of 200) and remembered for 10 minutes.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
 2026-10-30 02:52:55 -07:00
dhkatzandClaude Opus 5.5 400831bf3c Sign in again to the hub last signed in to
CI / build (push) Successful in 30s
Details 
Co-Authored-By: Claude Opus 5.5 <[email protected]>
 2026-10-29 19:25:47 -07:00
dhkatzandClaude Opus 5.5 5eca0b57a6 Sign in and out of the hub from the client: the proxy answers t5de-proxy.local
CI / build (push) Successful in 28s
Details 
A manager runs the hub connection, so signing in or out takes effect while the client runs; the client's T5DE
settings page asks it for the status and to sign in (showing the code and opening the hub's page) or out.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
 2026-10-29 19:18:14 -07:00