Quoted By:
IDVTuber Tracker
I don't think that I have posted it here, but here you go.
>Disclaimer
I'm not a CS/IT professional, and this project is 100% vibe-coded, so don't ask me about the technicalities on the low-level architecture, because big chance that I don't know. I only provide the algorithmic instruction to Claude and let it build it. I only need to deploy, trial, and debug this.
>What is this
It's VStats look-a-like, but made to track listed VTubers form my personal list. Currently I'm only tracking active Livium talents, Whicker Butler, and PANDAVVA.
>Why those three? Why not agency A or B, or indie VTuber C?
Basically I find that they are interesting to track, and I prioritize the local corpo blindspot that haven't been covered by VStats (AKA, EOS, Re:Memo, and MAHA5 are already tracked by them). For indies, I still don't have an idea on who to track.
>Consideration on scalability
The deployed system now can track up to 20 channels, but the API cost is over by a factor of at least two (according to the tests I've done several days ago), compared to what Google provides to individual in default. I'm currently submitting a quota increase request for a comfortable headroom, but I'm still unsure whether Google can approve it or not.
>What do I need to do next?
Fix the frontend, simplify it so that only the lowest level of the webpage hierarchy that are dynamically generated.
Rebuild the source code to accommodate a scale up in the event of more chuubas that need to be tracked.
For future proofing plans, search for a storage to store historical data, and way to connect it to the main dashboard. Also, this means that the webpage UI will have to be updated to accommodate historical queries.
