office is wired for ethernet š¤
i'm keith, a very sleepy boy.
previously @keith, but i got lonely running my own solo instance.
office is wired for ethernet š¤
i'm using a tiny react + server components framework for this, because i wanted to see how they work.
it was pretty pleasant. probably not something i'd use for anything bigger but š¤·āāļø fun for a weekend project
and i'm making some actual progress! i'm reusing a bunch of css iāve Frankensteined together over the years (shoutout to open-props and those gt maru fonts i splurged onāzero regrets). still lots of tweaking ahead, but the basics are working. wild how much you can pull off with bun, sqlite, and a couple react bits. the code is a mess, but hey, itās just for me and my pals
spending my long weekend turning our legendary trip spreadsheet into an actual web app for my friends. this thing started back in 2016 when we tried to organize a trip and somehow it became the blueprint for every adventure since. usually a spreadsheet is all you need, but this time... i might be crossing over to the dark side (aka building a whole app).
@stefan SUCH A PAIN! Being on the admin side was even worse, we couldn't do something simple like query all of of the assets we were hosting, or ones in active projects, or ones that'd been accessed in x days, nothing!
And we set up a job to run through and get those assets into a DB, but it required waking up every glitch project into the container, which obviously had some level of breakage š
This all made sense when Glitch was just a prototype. But Glitch never really stopped being a prototypeāwe just kept moving forward at breakneck speed, shipping features and workarounds instead of circling back to clean up the core. By the time I joined, it was nearly impossible to untangle something as fundamental as ā`.glitch-assets.json`.
Itās a wild ride seeing how quick hacks and ājust ship itā energy can become permanent infrastructure that the future Keith's have to live with.
Weād upload files via drag & drop, stash them in an S3 bucket, and only track them in a hidden ā`.glitch-assets.json` fileānever in the database. If you remixed a project, weād blindly duplicate all the assets, assign new UUIDs, and update the JSON. No easy way to scan assets, no real way to reason about things after five years of uploads. And if you deleted that asset file? Congrats, you just orphaned everything in S3.
jumped in a thread on bsky and one of my favorite (and most chaotic) quirks of Glitch is how much of it was still a prototype, even years after launch.
one week to moving back into the house, the back yard is so overgrown and i cannot wait to be out there gardening again
@r3dcrosse omg really?!? hahah it used to be a porn studio before it was offices, so that tracks
itās been almost ten years since i worked here lol
okay now that the party is over you can all see the beautiful website i made for my birthday https://bday-25.keith.is/
gemini season, pride, and my birthday. june 1st is a powerful day āŗļø
hi friends i hope you are thriving today
@keith Thanks for Glitch, been a huge inspiration!
Iāve just published a first alpha version of a kind of āHTML/CSS/JS for Peopleā with accompanying VSCode for Web extension. Runs all in the browser, incl. deploy to GitHub Pages!
@zachleat this one now / for good š
Wrote about the end of Glitch - the platform, the union, the dreams, and the technical debt that killed it all. Tried to keep it honest but not too spicy. Been gone a year now but felt like the community deserved some context š
https://blog.keith.is/blog/the-end-of-glitch-even-though-they-say-it-isnt/