Smalls

I think I might finally be making this live this week? 👀👀👀

Damn. I'm really digging the design I've done for the code blocks. 👀

What's funny about AI bros complaining about Codeberg's recent anti-LLM policy change is that they can just... You know... Self host it themselves.

Actually dipped my toes into creating Rust proc macros finally. Made one for quickly making an API client so I don't have to do a lot of boilerplate code.

@Undead_Zeratul@ocw.social @Metal_Link@ocw.social ALL HAIL

Rewatched Avengers Endgame and all I could think of was "Man... Wouldn't it be cool if it were 2019 again?".

Took a lot longer to do, but that's done. Only a few things I have left to do. Mostly some minor fixes and optimizations.

I'm so fucking close. This week I've been putting together the API and CLI for blog publishing. Biggest pain was designing the OAuth authentication and validation. Not so much the implementation, but more on the library API.

Case in point: https://kotaku.com/playstation-store-movies-digital-studio-canal-terminator-2000711013

GTA6 not having a legit physical release is just disappointing. Digital is convenient, but you're also at the mercy of the platform.

Uhhhh, excuse me?

Does take a bit of work to get 1:1 parity since it doesn't expose a socket for the docker CLI to use. I only need that because there are tools out there that exclusively look for that. socketainer helps with that: https://github.com/socktainer/socktainer

BuildKit seems to be broken at the moment with socktainer due to an issue with bind mounts, but you can easily get past it by setting up one through the container CLI and configuring a builder instance using the remote driver. SetupCreate a default builder with the Apple Container CLI: container builder start Create a remote builder with the Docker CLI: docker builder create --driver "remote" --use --name "apple-buildkit" docker-container://buildkit Make it the default for docker build Add this environment variable to your shell profile (.bashrc, .zshrc, etc.): export BUILDX_BUILDER="apple-buildkit"

Guess it's time to rewrite the Markdown AST converter again. For the third time. lol

The other thing I ran into was the assets system. Neat system, but heavily limited. I utilize the Bootstrap Icons library and the pre-bundled CSS file expects the woff and woff2 font files in the fonts/ directory relative to the bootstrap-icons.min.css file. The assets system breaks that. Also the exposed path for assets is hardcoded to /_topcoat/assets. Not a huge fan of that. Should be configurable, IMHO. Much like the components issue I ran into, there is no other obvious way to serve files. I ended up creating an "API route" with a custom output type to handle that. That custom output type is what gets the contents of the file to set the response body to and sets the Content-Type response header based on what type of file it is. Been working out great so far, but I need to make sure path traversal isn't possible.

Welp... I did it. You'll never guess where I had the most issues: Dynamically generated Markdown components. Basically components can get finicky when they can potentially be recursively called within themselves. Creates a type dependency cycle. It's very hard to debug the compiler for it and took a lot of looking at the source code and how the view!{} macro expands when compiled. It's also a little painful to create components when you're in that situation. Going the route I did wasn't all that obvious. topcoat is very heavily geared towards you staying within the documented macros.

Ouch.

The good news is that I'm no longer using regex for parsing heading attributes from Markdown.

That is currently only usable at runtime. I want to also have the opposite of it so I can write the page components in Markdown and have those components' code generated at compile time.

Started out with that because I'm planning on making the reverse of this: https://git.smalls.online/smallsonline/md-topcoat

If you want to know how much AI usage there was during all of this: Very minimal and all local. Mostly confined to just git commit messages and doc strings.

Oh sweet! Valve has finally made it so that the resolution override settings for games on SteamOS (and adjacent) are generated based on the display's aspect ratio. Let me ch- Oh...

VSCode moving to a weekly release cycle was extremely obnoxious. Call it update fatigue. https://www.reddit.com/r/vscode/comments/1ul6f7c/keeps_updating_every_single_day_now/

They're not doing real work Define "real work". Genuinely. Dev work Ah. Typical. https://www.youtube.com/watch?v=wnfxSxP8pGs

I just like emo/core-adjacent music. https://reddit.com/r/Metalcore/comments/1uzjgto/new_loathe_should_be_called_postmetalcore/

Loudest pop I've heard in a long time. Been a long time since I've had lightning strike that close to where I live too.

Rip a fart for a breakdown callout ☺️ https://www.youtube.com/watch?v=XtTnRpvR8Pg

Just finished rewatching the Watchmen TV show. Last watched it about five-ish years ago. If you haven't watched it, watch it.

@GossiTheDog@cyberplace.social https://www.youtube.com/watch?v=7SSnrtNrbkA

@Undead_Zeratul@ocw.social I feel like the last time I've had lightning strike that close was back in 2019 when it hit one of the copper lines very close to our building. Fried both my router and modem and tripped the fire alarm system for the whole building.

@oz@uate.social Yuuuup. Switched to it around March. Still have to keep VSCode around for some work things that require a few of Microsoft's proprietary extensions that don't work outside of it, but I use VSCodium for everything else now.