vroom vroom, Devlog 9: WE’RE BACK TO RACING!!

so since i’ve only been able to work in short bursts of time over the past few days, progress had been very slow and not very devlog worthy, until today!

i’ve been working on getting the most important OpenF1-dependent items to work offline, so in case of request blocks, they can still work just fine. this includes mainly the season calendar and the demo.

the calendar now gets cached in storage for offline access. it is also able to update its contents by fetching from OpenF1 when possible, which helps make it proof to unexpected race calendar changes.

for the demo, i created a .MJS file to create a .JSON file that saves the data from silverstone 2025 used in the demo. this allows the demo to always run offline and separate from openf1, instead of fetching data every time its used. this also allows the demo to run waaay faster than before, and makes it always available, even when openf1 blocks access to historical data when a live session is active.

as a bonus, i also fixed the timing tower to actually differentiate between a race and practices/qualis, so for the latter it orders positions by best lap and show gaps to pole instead of race intervals, which are used for just the race itself.

next up, i need to prepare the electron scaffolding for the app, as in order to fetch live data from F1 directly i need it to run as a desktop app. F1’s server doesnt send CORS headers, so browsers refuse to read it, but CORS is a browser rule, and electron’s main process is just node, so this allows a desktop app to connect where a webpage cant. and i need this to actually get the live session feed working, cuz as i said before…

you mean i cant see LIVE data in the f1 LIVE experience app?! what kind of scam is this?!?!