DIMMiN

Created at: May 31, 2026, noon Updated at: May 30, 2026, 1:52 p.m.

2026-05-28-Thursday

Found out the IRC connection disconnected for both the
Used the get chatters endpoint to manually generate the starting wall of joins (i'll have to correct the user attendance sessions soon to reflect that)

Created at: May 31, 2026, noon Updated at: May 23, 2026, 10:14 a.m.

Completed migration from SQLlite to PostgreSQL
Updated the Django Admin page to reflect the newly available models
Catalixia updated the Twitch Dev Console to reflect the twitchio OAuth configuration

Created at: May 31, 2026, noon Updated at: May 22, 2026, 9:34 p.m.

Created at: May 31, 2026, noon Updated at: May 20, 2026, 2:40 a.m.

Figured out why the Virtual Machines had such a slow transfer speed to the NAS (rsync issue, network connection is fine)
Created a Docker Container to help host PostgreSQL 16 on the NAS
Established a connection between the Catalixiahbot Django App and the PostgreSQL server on the NAS

Created at: May 31, 2026, noon Updated at: May 28, 2026, 10:27 a.m.

Applied a quick fix to the leaderboard using the fix_user_sessions script
Gained access to the new twitch token, allowing the first successful call to the get chatters endpoint of the Twitch Stream REST API
Updated Catalixiahbot's trackerbot to include the new oauth flow, began setting up the upgraded functionality to include new features like tracking followers, channel points redemptions, stream online / offline status, etc.
Found the fetch_chatters endpoint which I can use to monitor user watchtime in an updated version of Catalixiahbot
Began investigating slow transfer speeds between AM and my NAS, main culprit is probably Port Trunking

Created at: May 18, 2026, noon Updated at: May 18, 2026, 1:31 a.m.

Finished up the daily watchtime calculation
Updated the fix_user_sessions Django Management Command so that args for individual users or resetting all sessions actually work
Sent the steps required to get the refresh token to test out the twitchio REST API

Created at: May 16, 2026, 12:20 p.m. Updated at: May 16, 2026, 12:18 p.m.

Found that the backup server was deployed after the graceful shutdowns started (so it wasn't much help for fixing existing active user sessions).
Manually updated the active users in the Production database
Validated the updated active user daily watchtime component
Created the start of the session based component of the daily watchtime query (clipping user sessions to the start and end of the subathon duration)

Created at: May 16, 2026, 12:20 p.m. Updated at: May 16, 2026, 1 a.m.

Found the bug in daily watchtime calculation - there are users who are marked as still active who actually left during the server shutdown. Since I did not get the wall of joins the last time I rebooted the server (now that I have two connections to the source I won't get the wall of joins) I'll need some other way
Otherwise validated the daily watchtime calculation for active users (works, but we have too many active users)
Found a way to get the list of active users in chat (up to 1k users) with the get chatters api call

Created at: May 16, 2026, 12:20 p.m. Updated at: May 14, 2026, 9:08 a.m.

Created a backup Docker Container that runs Catalixiahbot without development, meant to run forever just to collect Event data, trackable on port 1336
Updated is_graceful_shutdown to display in the admin page
Updated the attendance validation step to mark graceful shutdowns as invalid, essentially solving the server shutdown issue with watchtime / user attendance errors
Fixed formatting of watchtime calculation to output a human readable string in addition to the total seconds
Started re-calculating daily watchtime from active sessions

Created at: May 16, 2026, 12:20 p.m. Updated at: May 13, 2026, 9:26 p.m.

Found the main bug in the watchtime calculation - session history needed to be recalculated for every user that had sessions based on invalid attendances. When the individual session was removed and sessions were re-calculated, it resulted in valid (but not necessarily directly sequential) attendances being paired together.
Pushed updates to Production