Make an iced cocoa (20g of pure cocoa, so as much caffeine as a cup of tea) by myself for the first time in my life; spent a ridiculous amount of time trying to figure out how to get Go to store my user password hashed; ran into an issue using the 'air' live reloader where it wasn't working after I redid the project structure, and it didn't have useful error messages or documentation to help me figure out what setting I needed to set to get it to work again; got past the air issue, it turns out I had to specify the directories to watch and without any leading "./"; created a user via the Vuetify app and confirmed that the password is hashed on the backend; created a Stack Overflow Q&A explaining how I fixed the issue for future newbies; committed my code. Set a goal for tomorrow: implement the authenticationHandler.

Managed to work for about 1h and continue coding the login #exerciseapp

today was my first day actually doing Go development instead of just tutorials: took a magnesium tablet b/c I felt anxious last night, I think from the caffeine in the cocoa I had been drinking; copied my frontend code from my flask/vuetify template repo to my go/vuetify template repo; confirmed I can serve the frontend code locally; installed Go; drank an iced cocoa; successfully started my 'Hello World' main.go backend file as a web app server; asked ChatGPT for help converting my "POST /users/" request to use Go; created a Go module; installed Postman macOS; took a 15min break after an hour; got my frontend app "talking to" my Go backend (successfully returned "Hello World" and had it on-screen in my frontend app); added Go middleware to log every request to the console so I can see what is happening; renamed my (default) branch from 'master' to 'main'; got live reloading for my Go backend (it automatically reloads the backend when I make changes to the code); confirmed my "POST /users/" returns 201 when I use the frontend registration form; came up with a task for tomorrow: get "POST /api/session" working; set up PyCharm to be able to explore my SQLite db from within the DB toolbar; confirmed that my user registration created a new user record in the db

Go: Bought "Let's Go Further" b/c it has a section on authentication for API backends; read that section; notice he has the code in his project set up differently than mine; rearrange my project directory structure to match the book's recommendation; spent some time looking at how he does authentication in the book; decided that I should maybe instead try to follow the Huma guide to doing OAuth 2.0: huma.rocks/how-to/oauth2-jwt/

figured out some Okta login issues that I struggled with last week #revsys

Opened up my IDE just before the deadline for the day to log a TODO; got my frontend storing the auth token returned by the backend;

Go: Switched my existing 'hello world' route/handler to use huma as a way of familiarizing myself with huma; checked out the huma-auto-generated /docs endpoint; spent ~90 minutes debugging an issue w/ how I defined a handler b/c the error message was not at all helpful; got POST /api/users (new user registration endpoint) working with the new setup (chi/huma).

Morning work on #booklet - hopefully finishing auth system

Some progress on authentication #didit

Finished the frontend code for login (functionally works, UI needs some adjustments) www.loom.com/share/b747870fc3… #simpleotp

Make progress on the X integration, got login working. Decided to go with an approach using headless Chrome and scraping to make getting detected as a bot harder #watchdog !private

Been silent on simpleotp.com for a bit because I was stuck on a testing issue, but finally figured out a way to way to test webauthn by patching the credential data! #simpleotp

Continued trying to get the authentication system working. #govuetifytemplate

late night hacking on a scraper project and mostly getting the UI updated

Researched, read up on PHP API authentication - normal user auth for login/signup is simple enough but protecting api endpoints and access control is the key step to moving fwd for my approach #indiejourney #decodingcoding

Got my auth-required Go endpoint working and returning the user's ID w00t

caught up on some client work to finish an auth project #revsys

Finished writing most of the backend, got to finish some middleware (upload, download) functionality and make the landing etc.

Struggled to incorporate the Line "echo bot" code into my existing Huma Go backend framework code, so I just YOLO'd it and copied the example code into my `main.go` for the purpose of seeing if I can get it working...ran into an error when pushing to Dokku, it seems to be because I didn't set the Line-related env variables before pushing...set those vars on my Dokku server...clicked the Line 'Verify' button for the callback URL and got a 404, so I now need to look into what happened...I think the issue is that the echo bot code assumes I'll use the DefaultServeMux, but I'm actually using a chi Mux. The key line difference is `log.Fatal(http.ListenAndServe(":"+port, r))`, where the example has `nil` instead of `r`...YOLO'd it again by just disabling the router I had gotten working, just to see if the webhook will work, and got a Success when I clicked the Verify button...next up is to either clean up this mess I've made in my code or keep pushing forwards and try to get the ChatGPT part working.

Struggling with signature verification issues for webauthn tests and spent all day trying to figure it out. Think I must be signing the wrong data or similar. Trying to get this done correctly so I can launch passkey support #simpleotp