Hi! Let’s use this thread to discuss further development of the events streaming backend (Muxy), events website (https://sun.tidalcycles.org/) and archiving related stuff.
For those who are unaware, based on some brainstorming with @iSaladino and a discussion on the Discord chat about the way we were handling these streaming events (a single, shared stream key) we started developing a streaming backend system for this last TidalCycles-related Solstice Marathon stream. It aims to facilitate streaming keys for streamers of a shared online event stream. Currently the main issue that solves it that it allows each user to have her/his/their own unique stream key, and they can only use it during a time slot they booked. It’s developed in Python using Django and Django REST Framework, and the source code is already available here.
Related to this, @sfradkin has been working for some time on archiving the stream recordings of past events, and is now automatizing parts of the process, and it would be nice to make sure this system works towards easing this process. There’s already an issue for fixing a few things to help him with this.
One of the things we discussed on the chat was to integrate the Solstice website (developed by @mashaal - looks like he isn’t here?) with Muxy. Right now the website and Muxy have their own databases (the website uses Firebase Realtime DB, Muxy an SQLITE db, soon to be replaced I think…) and we had to sync them up for the last event due to lack of time, but ideally we would be using a single database as a truth source. Muxy exposes a REST API so I guess the easiest way to do this is to make the website use this API for sign ups/slot creation, edition and removal. I know @mrreason and @mashaal wanted to contribute here, maybe someone else wants too?
Do you think it’s best to discuss, suggest and organize here and then use a chat (like the new TOPLAP Discord server or chat.toplap.org) for more pair programming/discussion stuff?