lola

inspired by a portfolio from a show and tell a while ago, im deciding to add a admin dashboard and have all blogs stored in a supabase database !
i want to use github auth (so i don’t have to remember a special password). im using a lot of templated code from supabase docs, but i’ve never done auth or anything really with supabase that much before, so there was a lot of trial and error. but i validate myself now! i can login with github and retrieve my email.
while the ‘validation’ is just email == my email, i intend to add more validation with the supabase sql query. there will be a policy that only allows a user authenticated as me to update the database, and that’ll be the real validation. but right now, only the invisible sort of auth is done.

recent sockets thing added, and fixed a stalling bug, then it returned, fixed it again and then it returned. a lot of debugging so unfortunately not much updates

updated so that the website is truly dynamic in that it’s constantly getting projects from a JSON file. before, the json file was just included in the build, and i’d have to rebuild the website everytime i wanted to change a project. that was super inconvienient because i was hosting the project on a pi, where the website has to be built on another os before being sent over to the pi. so now there’s a server action to read in the json5 data when the projects load, which makes it a million times easier to update my projects. additionally, instead of statically exporting the project, its now being served from next, which allows for image optimization (which i didn’t have before). oh, and i also changed the about page to be more boring (as i need it to be functional). might be the last devlog!

a lot improved! it has basic functionality now of what i want it to do. the packets are still coming in raw, so not sorted by packet packet and more like socket but still cool looking!

spent the last few hours writing about my projects. like little blogs! added tons of photos too. its rly cute. i like it a lot.

okay mostly everything done. still a lot of writng to be done, but the about page is done. it took so so so long to position the photos together, and next aggressively caches images (even on a dev server??????) so the website is not updating with the photos i give it until i clear cache and refresh and restart dev server a few times. but the website looks good! i attached screenshots of my website running on safari and arc - for some reason, next caches LESS on safari. so thats my new web server (see the updated cropped photo). but really just need to fill out the json file and things should be good!

this is taking FOREVER. just added images and fixed a handful of other things. made some design choices. but it looks good for what it is

okay just because the flavortown profile says ‘awful’ for my amount of minutes per devlog, i’ll devlog prematurely. things are going ok - added a page for my custom projects, fixed some stuff from before, but things are kind of slow. i picked a really bad design for showing components and im kinda reeling from it… but the way i did it allows for this cool kind of pop up thing im messing with

first commit - took some three.js scripts i made a while ago and threw them on the site as buttons (and i think it looks really good!). needed a lot of help on making them work in the easel, but as of now, working on projects page.

the beginning of redoing ntwatch! originally, ntwatch was made for the athena initative as purely a macos socket overview. in this version, it will show only sockets that have associated packets coming from the en0 (wifi) interface, with statistics about both the sockets and packets. sort of like a combination of nettop and wireshark! so far, i haven’t done any ui - only restructuring a lot of code, getting rid of a lot of stuff, adding a clean bubbletea command flow with tea.cmds, and extremely basic packet to process matching functionality. the socket table is created at the beginning of runtime and at every tick, and there’s a goroutine that listens for packets - when a packet is recieved, another goroutine checks if there’s an associated socket, and if there isn’t, it refrshes the socket table and attempts to match again. obviously there’s a huge bug here, as a lot of packets will never have matching sockets (stale packets), but it’s a good start. yay!