Kako

iterate
iterate
ever
iterating
my chimera

so much effort
...

Am I really going to end up moving away from RISC-V and over to Raspberry Pi after all this effort? I'm starting to consider it.

Guess I'm learning Rust.

Today I learned that git commits give away your system's timezone setting.

That seems a little unnecessary. It's also rather obnoxious to override as well when using git through a third-party application. Hrm...

Managing to get responsive web design working on a website feels like such a flex.

Hell yes. I own kako.dev now. Maybe I'll make kakoaethes.dev my secondary domain now...

I'm just going to try doing something leaner this time around. Just a simple static site probably. I don't think I should need a database for this honestly.

Mmmm... goodbye Wordpress. It was a good run.

Not finished but good enough. I just want to use some art that isn't that (adorable) meme picture.

New profile picture, new me I suppose.

You do so wish, it would seem.

Haha. Drawing my cat is fun... soon I'll actually have a decent avatar of my own instead of borrowed art.

Starting to realize that I've already done enough work that I need to start forming write-ups and figuring out how I'm going to disseminate this information.

The point will be (at some point) to log everything I've done and why, without using any templated bologna anywhere.

The ultimate crash course in system dev from firmware level all the way up.

Awaking from deep slumber yet again.

The website project is on pause while I do some bare-metal freestanding C development on QEMU's virtual "virt" RISC-V board.

No standard library. No basic system functionality. Just me, a device tree, and a hart ID, a UART, and a C compiler. More or less.

My favorite use of technology still has to be those that change how we socialize and how that affects society. It just kind of sucks it's so unappreciated and/or outright used for abusive purposes nowadays.

I had no interest in blockchain technology back when it was being hyped. As well, my interest in AI isn't non-existent but it is pretty limited in terms of pragmatic applications I'm interested in.

Honestly it makes me feel old.

The JSON I made that describes the route tree for my site's API is getting unwieldy . . .

Ugh. I have to figure out how I'm going to get an audience and money at some point for my project...

Upset at realizing that someone else already owns the domain "🐈‍⬛.dev".

And, well, nerdy communities in general at some point.

So many irons to put in the fire in the future.

I should be more serious about engaging with the webdev community.

Just Golang, HTML, CSS, JS, some custom OS / web server / database configs. The only stuff that's third party are the OS (Debian), web server (Nginx), and database (MongoDB). Fairly similar to ye olden days.

The idea that I have an actual, functioning site with login functionality and other dynamic functionality (even if it is very rough around the edges) is wild to me considering I'm using essentially no frameworks. Holy hell.

Just Golang, HTML, CSS, JS, some custom OS / web server / database configs. The only stuff that's third party are the OS (Debian), web server (Nginx), and database (MongoDB). Fairly similar to ye olden days.

The idea that I have an actual, functioning site with login functionality and other dynamic functionality (even if it is very rough around the edges) is wild to me considering I'm using essentially no frameworks. Holy hell.

It's the stupid SCRAM. Currently using a table for user auth data, one for login challenges, and one for authenticated sessions.

Question was whether to pull data from the first and second for the login process as one transactions or two. I think it's fine if it fails midway the more I think of it.

Trying to design my site in a secure way is maddening.

Currently agonizing over whether two separate atomic transactions should be combined into a single one.

I'm pretty sure I've hit the upper bound for the amount of technical debt I can handle alone. I don't see a less painful way forward without refactoring my code to be less hideous.

Starting to think I'll just use session identifiers, represent permissions via bit-fields, and keep session data in memory as much as possible on the server side instead of using JWT. Should be efficient (I think).