Working as Intended
I've got the new site working, but I'm not abandoning WordPress quite yet.
Posts in
26 posts
I've got the new site working, but I'm not abandoning WordPress quite yet.
A bit of World of Warcraft, some development and project lamentation, and the usual Star Citizen editorial.
I suck at design, so should I let a framework design for me? If so, which framework should I use?
Grab Bag for Week Ending May 10, 2025
A short (mental) film about what happens when I lose sight of my original intent.
I think I've found my preferred back-end platform for auth, data, and file storage. So far, everything has been smooth and easy, with the exception of registration validation.
"Do what you love and you'll never work a day in your life...because you'll end up hating it and will never want to do it again, ever."
I stumbled across a front-end content display platform called Astro, which might serve as another brick in my long-term goal of writing a custom blog platform.
Here it comes again: More thoughts on webrings since external forces keep putting the subject in front of me...now with potential options for making it happen.
I forgot that I'd need to be able to easily create HTML-able rich text for a blogging platform, so after some research I settled on Lexical.
Talking to the duck about the possibility of choosing Supabase or Appwrite for this custom blog project that I am totally only considering at this point. Totally.
Feeling dissatisfied; might hand-develop a custom blog platform later.
I'm porting my Node application to Deno and while I'm finding it pretty easy going and occasionally beneficial, I'm still not 100% sold on some of their design decisions.
Arbitrary updates on games, software, and projects here at Chez Scopique.
My development project is on hold (surprise!) so I'm considering 3D modeling again (more surprise!) but I still have a lot to learn...but nowhere to learn it from (saddest surprise).
I've coded myself into a corner on account of trying to bring too many new-to-me systems on-line all at the same time.
I had a panic attack about styled components versus plain CSS, but after writing about it, I'm not sure it was warranted.
Here's an example of using the web socket server to handle messages and store the results in Redis. Since I wrote this, modifications have been considered, but that's a post for another day.
Before we move to the next part of the WS + API Server series, I wanted to talk a bit about Redis and Redis-OM.
Now we're getting somewhere: dynamically handling messages from the client.
WS + API: Web Socket Handler
Thinking about web rings, and what we'd need to do in order to bring back a smaller, more intimate World Wide Web.
Before we continue with code, I wanted to stop off and talk at a very high level about HTTP and WS, and what each protocol means to me from a purpose standpoint.
Ever server needs a starting point, although this one doesn't do much on its own.
WS + API: Getting Started
I've got nothing else to talk about right now, so how about a series of posts about this web socket and API endpoint server I'm rewriting for the nth time?