BnaJns

Final devlog probably, at last, after an all nighter, procrasting on this project till the very last hour, I have gotten everything working. Not everything was added but I shall still claim victory and feat. Overall very proud of this tho, golang is good, probably not the best choice for websites like this, tbh performance is good so it probably is worth it, but still.

• Added post delete button if the post viewer is the post owner
• Added a cap of 5 images to extra images section
• Ran task tidy
• I hate docker why would anyone voluntarily use this
• Fixed broken stuff
• Got it deployed on https://ftpaints.bnajns.dev
• I hate docker
• Fixed annoying file write issues, fedora is kinda annoying
• I made the readme a bit tuffer
• It all finally works perfectly. Amazing.
• It did not
• I fixed the commit hash in the footer
• It works now i hope

I hate docker but im only using it because containerization

Very awesomesauce

Changelog

• fix commit hash in docker
• tuff readme
• asdasdsad
• remove unnecessary check from description
• small fix
• docker sucks
• task tidy, add discord link
• Max extra image count of 5
• post deletion boom
• add commit hash into footer

Wow

• Added settings page with option to logout, and to delete all account data + confirmation modal ofc
• Added TOS and Privacy Policy pages (via chatgpt) because roblox oauth2 needs it, via .md files rendered via goldmark
• Cleaned up some bugs, some pages should look a bit cleaner
• Cookies no longer expire after 15 minutes, set to 30 days now
• Added max post/request size of 20MB so the server doesn’t receive a 2TB zip bomb as middleware
• PORT env variable
• Commit hash is now in the footer

Idk if I can add the individual post delete button in time but I shall try

Changelog

• add commit hash into footer
• account management + settings page + few cleanups
• slight cleanups, better security? maybe?
• it’s all good, man

Final stretch 3am lets get this done fr

• Index/homepage/collection view is 99.9% done now? Everything seems to work nicely, I’m proud of the design, sort filter search works ok, so I can probably consider it done now.
• /search endpoint added, you throw in the query params, it spits out what it finds, with pagination ofc
• favicon.ico added
• Upload button added to navbar to link to /upload

Some stuff left to do:

• Allow creator to delete posted liveries
• Commit ID in footer
• Shut gin up about untrusted proxies
• Admin page? If I have the time
• User profiles

peak fr

Changelog

• this is peak
• index page is basically done? i think
• index page init progress
• livery page adjustments and fixes

A lot of work in this one and very awesomesauce progress ts tuff on fonem

• Livery view frontend basically done, features the data from the SQL data obviously, the roblox texture id with a copy button, featured image and additional images, along with a lightbox, and that’s it
• Moved htmlrender to its own package because of dependency loop issues
• You now get properly redirected to the livery page after doing the upload
• Added functions to the db.postgres for getting user data via id and paint data by id

The layout kinda sucks but I don’t have any better design ideas and it does it’s job, so good enough. I guess the next logical thing to work on is the livery collection frontpage with sorts and allat

I also gotta actually add the logo as a favicon.ico cause rn it doesnt exist and no favicon looks ugly in browsers ofc

I still don’t regret golang and gin for this despite it taking way longer than it would’ve with svelte or next.js or whatever. Trust the process

Changelog

• livery page adjustments and fixes
• livery view kinda doneish

Got the SQL and upload working now, epic

• On user upload, does basic validation checks
• If checks pass, upload images to local file storage
• If uploads succeed, run SQL insert query
• If SQL insert succeeds, returns the livery UUID
• Also made a few small bugfixes

Uploaded images are available via /uploads (or /public/uploads), no frontend for viewing the published liveries exists yet, so I have the choice of working on either the individual livery view, or the collection view first, I’ll prolly just do the individual view first.

Changelog

• fixed up stuff
• woo working user uploads

Progress on getting uploads working:

• SQL Schema is pretty much set up correctly now with everything needed
• Frontend is 99% done, just need to finish up backend. Awesomesauce styling
• Backend is like 50% done, validation exists, but doesn’t run the SQL query/function yet since I need to handle file uploads. Now, initially I thought using minio/garage/rustfs would be the best choice. Then now I’m thinking it’s too much overhead and unnecessary, so what I’ll do instead is probably just storing images and uploads manually in a folder instead.
• After that’s done, the backend is pretty much done for the upload part, I can wire up the final frontend piece, and boom working uploads. Though I still need the paint/livery view page as well

Changelog

• i am iceman i am i am iceman
• wahwahwah upload progress
• user data middleware/renderer

Time to speedrun ts since flavortown ends in 2 days and exams are over for me so I actually have time now

Very awesome changes and stuff working woah:

• I setup the base layout/multitemplate so no navbar/footer copy paste
• Set up the user state middleware/html renderer
• Slight work on the HTML/Styling
• Made a cool simple logo in Pinta, since paint.net is not on linux and all the other apps on linux suck

Stuff to do next probably:

• Upload page
• Show uploaded liveries on index page
• Settings/account management

Kaboom

Changelog

• user data middleware/renderer
• layout works
• oauth working, whoami, amazing
• slight fixes

Finished up the OAuth woohoo

• Roblox OAuth2 login with state+PKCE
• Cookie is stored in db using sha256 + secretkey
• /whoami endpoint, literally only shows basic stuff such as pfp, id, username/display name

Pretty much hard stuff is done now, I think, so I can start actually working on the frontend and handling uploads and yadayada, and I’ll also have to figure out the best way to do reusable components, aweeeeeeesome

Changelog

• oauth working, whoami, amazing

Progress update, i kinda fucked up and lost about 35ish minutes of work because I was working on the project on my laptop, I was also trying out GoLand (which sucks, I’m sticking to VSC), anyways I committed the files to git, BUT, i forgot to push, and then alas, I switched from fedora to cachyos because my laptop is a tractor, and then when I tried to git pull on my PC, it said it’s up to date, I check my laptop, the project files aren’t there, so that’s great. Anyways, current progress is working on getting the login to work and be persistent, I had a docker-compose file on the laptop, which I’ll have to recreate, to use postgresql as the database, goose for SQL migrations, and ofc I gotta finish up this unfinished oauth callback and then I’ll see what’s next

Changelog

• slight fixes
• env example, goose for sql migrations, unfinished oauth callback, i shouldve used next instead but the pain will probably be worth it

Aight so I decided to make this project/website because the ro-racing league I’m in supports making custom liveries for some cars, but there’s no “database” or anything similar to keep track of, or share liveries reliably, so why not make something similar to Trading Paints (a iracing livery collection/app) to keep liveries with data such as texture id, tags, which car type, team, etc. I decided to go with golang for this since gin-gonic (basically express.js for Go) makes stuff hella easy, and using templates is nice as well, I could’ve used next.js but that’s lame and boring and next.js consumes 1gb ram something something. Anyways, plan is to use: Gin-gonic, postgres, and get minio setup on my homelab for screenshot uploads and such. Only concern is how I’ll figure out reusable components like the navbar and footer and allat since react would make that easy but ofc I can’t use react here, only pure html+css+js. Anyways, so far I’ve setup some basic stuff, such as a uptime tracker, router setup, readme and license, very minimal stuff. So that’s that, Go is very cool.

Changelog

• basic setup stuff
• init

Added a code playground with examples cause why not, courtesy of go.dev/play servers, very epic

• CodeMirror for the Go code editor/display via their cdn links
• go.dev/play APIs for formatting + running code in a sandbox, really simple to use
• Wrote 3 basic example scripts, a hello world with time, the infinite monkey theorem thingy using gocurrency and channels, and also copied the base64 image displayer example from go.dev/play, just added the support to my html and changed the logo to be the goship logo ofc
• Backend is basically a really simple proxy, formats raw code text into x-www-form-urlencoded and into the expected struct, sends it to the API which handles the formatting and building, sends back the json response to the client.
• //go:build ignore lines in the public/scripts/ scripts so it doesnt break the actual website build, and then the client JS strips it out so it doesnt stop the script from running in the playground.
• Also added ratelimits to format/run to prevent abuse/spam
• Edit: Also emailed the Golang public mailing list as per the service requirements, https://groups.google.com/g/golang-dev

i didnt know you could add emojis this is cool

Changelog

• add ratelimits to format/run
• remove build ignore lines from code examples
• add build ignore directive to script files
• good enough examples
• code sandbox is basically done but nah

Pretty much done atp adding guides was easier than i expected it to be

• Added three very awesome guides, the Go setup guide, the hackatime setup (which just basically links to the hackatime website quick start), and a hello world tutorial.
• Added a /guides handler, using yuin/goldmark to render the markdown in the template. On /guides?file.md request, checks if file exists, if not respond 404, and ofc other cases like no query param or whatever, if file does exist, it reads the markdown, renders it using goldmark, throws into template, boom.
• Basic guides/index.html template with simple styling
• Made the readme awesome, aka changed it from 3 lines to like 50 lines

Go is awesome

Changelog

• add guides + cooler readme
• guides handler + md render
• fix broken responsive ai gne

AI generated ideas working after wayy too much time, woo

• Added an /generatemeaidea endpoint with POST and GET available, GET returns allowed slot tiles/categories, and POST generates and AI idea via ai.hackclub.com with the generated slot ideas, also double checking to make sure the categories are in the allowed list, and also with a 10 req/hour ratelimit.
• Frontend is simple, you have a slot machine, “spin” button, you click it, it randomly chooses 3 categories, sends the request to the endpoint, gets response back, puts that on display. If ratelimited, or error, it throws a message saying ratelimited/error happened.
• I tried to make a pullable lever, and make a the slots have a spin animation, but I gave up after a few minutes as I couldn’t be really bothered

Very awesomesauce

Changelog

• ratelimit fix
• woo working ai ideas
• sadasdasdasdasdasdas

Prrrrrrrrrroooooooophecy

• Added /prophecy which lets you generate a prophecy tile GIF, not perfect but whatever
• Added a darkworld border option + spoiler image option to /textbox
• I forgor to add updatecount for member count as a loop so i fixed that
  Pretty awesome

devlogging this only now cause I never planned to submit this to flavortown
Alright so ~11 hours, that’s a lot of time, what did I achieve in that timeline? Imma break it down to the best of my memory:

1. Initial stuff, setting everything up, go mod init yadayada. Why go with Go (no pun intended)? Because it’s a very cool and easy to learn language, I barely have experience btw, yet writing stuff is simple, also has a powerful standard library, and it’s basically if Python was a good language. And if I was making a golang YSWS, and didn’t write the site in golang, that’d be a missed opportunity. And why the name “Go Ship!”? Google the card game “Go Fish”. Also, was originally going to use a makefile, but on windows it was a pain, so I discovered taskfile instead, which is also written in Go, and it’s way more awesomesauce than makefile imo.

2. Started building the HTML/CSS and stuff, I’m way too used to react and tailwind so this was a bit slow for me, I could’ve used the tailwind play CDN , but, the IDE wouldn’t autosuggest the classes and stuff then, so I just decided to stick to good old plain HTML+CSS+JS, and it wasn’t that bad. And then I also worked on the RSVP functionality. Fillout? LAME. Using hack club identity? Awesomesauce. Sqlite, Identity, boom, you got a good clean minimal RSVP database, and I can also expand it to support logins as well in the future, technically it already does that with cookies, but it probably needs to be more secure and advanced. No SQLi or anything in there, yet, but still. Basically how the auth/rsvp works is the RSVP button links to hack club auth, user authenticates, gets sent back to callback link, Go grabs the params from the callback request, sends tokens and stuff to HCA, HCA sends response back with more tokens, Go verifies the legitimacy with public keys and JWT to make sure the response is legit, if everything matches, fetch user data from userinfo endpoint with the given user token, save info to the DB and create a session, give the cookie to the user (so they can see they’ve already RSVPed on their browser), 5 big booms.

3. Was basically finished at this point, according to commits, added a few waves to the HTML, also wrote a test cause tests are cool when the orange dot turns to green dot instead of red dot in github, messing around with github actions to setup stuff properly from builds to tests, added a .env.example along with a port option (cause 3000 was already taken on my homelab), added responsiveness to mobile, opengraph for cool embeds on slack/discord, github commit id to the footer because it’s cool, not very useful but cool. Finished stuff up with a potential prizes carousel, and a /stats endpoint which just shows the RSVP count and the binary uptime, the /stats is not used anywhere, yet, but still.

4. Getting up hosted on goship.dino.icu was a bit complicated, since I could’ve just hosted it on goship.bnajns.dev, used CF tunnels called it a day but I wanted to make sure it was on dino.icu, which doesn’t really work with cross-account tunnels afaik, so what I did instead was spin up a free azure VM, install FRP on that and my homelab, did configuring, and used that as a proxy instead, and it works fine.

And that’s pretty much it, I also had the idea to use ai.hackclub.com to make a project idea generator since I saw that idea being used in a few other places, so I’ll add that soon, and also guides, I’ll need to write those as well.

Added a few things all around

• Got rid of dotenv, Bun loads .env automatically anyways
• Fixed CI, I was stupid and forgot to add bluesky to sources.yaml.example
• More prometheus stats for analyzing stuff
• Refactored randomwiki by adding a randomwikiUrl function to the wiki lib, and standardized it to use the exact same embed as the other wiki commands
• Updated commands.md (shoutout claude)
• I was gonna replace the compliments in compliments.ts with an external api, but cancelled that idea and instead replaced some ofthe current compliments which weren’t really even that good, with better fitting up-to-date cringy compliments.
• Redesigned the coinflip emoji icons to be a consistent shape instead of one being a square and the other being a rectangle
• Decided to keep express for now cause I cba to switch over to Bun and tbf it’s probably unnecessary it’s not like express takes 500mb

Stuff still left to do:

• Fix the twitter source by using Nitter instead, and that’s it I think

5 big booms, boom, boom, boom, boom, BOOM
Added /deltawiki and /undertalewiki using deltarune.wiki and undertale.wiki mediawiki apis and the Bun HTMLRewriter constructor. Fortunately, these both run on mediawiki, with the same stuff, so it only needed one file for both commands to work properly and parse stuff. Pretty basic stuff, gets the title, link, thumbnail, description, and some fields if they exist, throws those in a embed, and boom. Also wrote a test for it, both undertale/deltarune.wikis are tested, cause testing is awesomecsauce, and ofc it passes.
Also upgraded all dependencies, again, to latest major version this time.

Stuff to do:

• Remove dotenv, in favor of Bun.env, cause dotenv is not necessary cause Bun exists, and also I don’t like the advertising on startup.
• Remove express in favor of Bun’s HTTP server, the less dependencies, the better.
• Maybe get rid of ffmpeg-static and instruct users to just install ffmpeg systemwide?
• Turn more commands into a embed rather than raw text cause embeds are beautiful and cooler
• Add prometheus statistics for website visits
• That’s all I got in mind right now

There’s this really annoying bug that I might’ve spent too long diagnosing. Basically, if the bot is in a VC with another person, and someone disconnects the bot via the discord menu, the bot leaves fine. BUT, if the bot is alone in the VC, and someone disconnects the bot, the bot does not leave, it instantly rejoins, BUT, /radio stop still works fine. What kind of dark magic is this? I don’t know. But I pretty much fixed it by never letting the bot be alone in the VC, by instead doing event-driven checks, rather than when the current song ended, so whenever someone joins/leaves VC, it checks the VC member count, if the bot is alone, adios. Also added tsradio support, because it gives me a reason to use my other projects, and also, so that I don’t have to upload mp3’s to different services, let alone git, which would be bad for the git size. Summarizing, vc bug, fixed bug with member count checks on join/leave, added tsradio support, while keeping file support, that’s it. Also fixed a disconnect race condition where the message would be sent multiple times. Awesomesauce.

Finished adding prom-client, and cooked up a grafana dashboard which is tuff. I did not not know that my bot is in a whopping 71 server so thats kinda crazy. Was this necessary? No. Is it very cool? Totally. Next up I could probably add sharding, even though the bot doesn’t need it yet, still 2429 servers away, but still, futureproofing fr. There was also this annoying bug, which was my fault, but I blame it on the IDE, which was me using import path from “path/win32”, not “node:path”, so when I deployed it on my Fedora server, you can guess what happened, the /ralsei bluesky handler kept failing. I thought it was a Bun fault, it was indeed not. For the next stuff I have in mind, I could probably add a /wiki command to fetch info from deltarune.wiki, and then display it in a short way in an embed, cause rn there’s only /random-wiki, but I’ll take a look around on what other unnecessary but very badass features I can add. Actually, I was just testing the radio, for some reason when the bot gets manually disconnected, it refuses to leave, which is rude, so I gotta fix that, no idea why that’s happening

Small changes before I work on something big

• Replaced the hero/banner with a new and cooler one
• Moved statuses.json into statutes.ts, added git hash status
• Fixed /random-wiki hopefully
• Planning to add Prometheus for command/latency/etc analytics tracking via Grafana so that my dashboard doesn’t look empty

The sky is blue

• Added a BlueSky handler/source to yaml
• Migrated existing twitter test to a Bun test with proper expects, and wrote a very cool test for Bsky as well
• The twitter (aka X) test fails 100% of the time because X is evil and they charge a lot of money for the API and playwright doesnt seem to be working
• TODO: switch from playwright using x.com to nitter.net i think that might work
• Uses @atproto/api because I cba to handle with curl and auth errors
• Got rid of the YAML package and just used Bun.YAML.Parse instead

Out of nowhere, I remembered I made this project a while ago, and apparently according to logs random people are actually using it, so this deserves a good refactor and cleanup.
What I did so far was switching from npm/node to Bun, cause Bun is very awesome and faster and better overall. Also setup dependabot monthly alerts so that the dependencies dont gather dust, and after that, which was kind of a pain was refactoring motivational-quote.ts which took me way too long. I started by changing the drawn image from stretching to the square constraints, rather to just fit and the remainders get clipped, and then I changed out the font for deltarune.ttf, which was the pain point. I spent a good few minutes debugging this until a github issue at https://github.com/Automattic/node-canvas/issues/2285 figured out the issue was not having the font installed on the system, which is kinda stupid, why use the .ttf if it needs the font installed. Anyways that’s all for now, next up I’m probably gonna refactor the entire /ralsei command to use better sources, deprecate reddit as a source, maybe add bluesky or whatever, and etc. I’m also probably gonna remake the banner cause the current one just uses art I found on twitter, and it could be better.

Blowing the dust off this project and starting to refactor stuff, i was gonna start with refactoring from sqlite3 to better-sqlite3 but honestly im prolly just gonna move to drizzle probably even though I’ve never tried it, prisma would be safer but it’s too bulky I hate their ads and whatever they sell, but anyways for now I just started with migrating from npm i to bun i, and i gotta start figuring out the rest of the stuff. I wonder why last.fm is called last.fm and not last.am, anyways I gotta refactor a bunch of stuff in the bot, especially move from sqlite to drizzle or something, because of the 500 dependabot alerts caused by the npm sqlite package, cause it’s unmaintained, for a whole 3 years now. Some other things I gotta do is refactor to typescript because javascript yellow looks ugly and typescript blue is very cool, and other than that I don’t have any bright ideas other than adding automatic slack status updates to show what you’re listening to, while slick stats already has last.fm support, it doesn’t have customizability afaik and I want slack.fm to be fully customizable to your needs. I should probably make a new logo as well because I hate the current logo it looks ugly and uhhhhhhh maybe cleanup readme of unnecessary clutter nobody needs to see env variables in the readme when they’re in .env.examples anyways. Switching from npm to bun because bun is also cool and easier to use and mmmmmm it’s awesomesauce i hated it and then i loved it. Also the bot is finally back, online, since I got a azure server using the student pack, because nest is still dead, and I don’t expect it to come back up anytime soon unfortunately, and the data that was on Nest, gone adios never will be seeing it again, most likely. That’s all shoutout to Rick Ross Teflon Don