Decided to make a slideshow presentation filling in the months since my last videos. 00:00 INTRO 00:29 WHERE DID YOU GO 03:35 BIBLE 09:15 WHAT ABOUT FINANCE STUFF 12:34 NFTs 24:53 MUSIC 28:19 MUSIC CONT. 31:14 ELECTRONICS 37:06 DE-GOOGLE 46:50 DECENTRALIZE 49:53 AND LIFE Slideshow created with: https://www.libreoffice.org/discover/impress/ Audio, compressed, normalized and silence removed with: https://www.audacityteam.org/ Video created with: https://ffmpeg.org/

8:27 we take a look at one of those little white creatures from the Mystery Pets video: https://odysee.com/@MindsForge:9/new-pets:5 We did get some good images, unfortunately the water flea didn't make it through the coverslip application, surface tension is no joke that those scales! https://en.wikipedia.org/wiki/Daphnia the anthro anime girl version: https://www.deviantart.com/jun075/art/Arthrogirls-Daphnia-pulex-895384883

Haven't done a microscope stream in a while and the algae dish has really grown into something of beauty Not much under the scope this time, and finished the stream with a reading of Junji Ito's manga story "MOLD" @ 2:00:40

I've been putting this off for a few days. It feels like a big job, I need to basically remove a lot of old "ways of going about things", nodes, and start querying the orderbook database instead of relying on websocket messages themselves. I feel like having our own local "game loop" sort of clock will be more conducive to our style of trading (market making), so instead of being reactive to every single market change, we can look at the up to date book every at sub-second intervals to recalibrate our orders and model. Right now, since I built the system as an IV chart with dreams of trading, one of the major flows takes non-authenticated book top messages from the FTX US Derivatives websocket and calculates an IV surface, updating an SQLite db with a theoretical IV for each contract (along with it's actual bid and ask IVs) From there it sends messages to the front end which are rendered as charts. You can see how this will end up rooting up old code and throwing it out in favor of a more local "polling" type system that checks the in memory SQLite db state and generates the IV surface. From there we can send messages like we were, but it should be much less hard on the CPU since websocket messages could arrive in bursts causing the system to calculate 10s of IV surfaces and render them per second... This new way would allow us to take control of the amount of CPU to use and have better control of our timing and certainty of the exchange book state (I hope). It should also make programming and testing various algorithms easier. I don't know if it's the right move or not, but it seems to be.