Shadowlight

I stopped the tracking of user profile fields (after a tip from Fire Dept), and I added some stability changes and made sure that the id of the channel is viewable for easy access.

Worked on defining schema and planning out the backend, starting work on defining the api methods now.

I added user_change events into the bot, so now it also tracks when people change their usernames and real names (although it doesn’t display it publicly), among other fields like status and profile picture. I also shortened the code massively (like from 1100 lines to 500 lines) and cleaned up the code.

I migrated my Sqlite3 database over to Turso for persistency and added file events like file_changed and file_created. Now that the bot can listen for file events, it turns out that it can’t access any details of most of the files it detects, which sucks, but it is what it is.

After creating the initial website, I reorganized the website to be structured better for more efficiency and implemented Turborepo and bun into the repo (was using npm beforehand). Also combined a previous branch from Youssef which had part of the Rust backend, working on the frontend now.

Adding on to the previous functionality of tracking events and displaying them in channel, instead of storing the data in Airtable (which caused me to hit API rate limits), I changed the database to use sqlite3 instead, eliminating Airtable completely.