Eli Ozcan

oh god finally im done. published it on crates io and vercel. Suprisingly not much AI slop this year! IG I’ll just wait till it officially starts and 50k people join 💀. Eh fun until it’s not ig. Welp, ima zzz.

I am still working on perfecting the model. I have also finished the flavortown adapter.

Devlog endpoint implemented and i rebuilt the fetcher to use concurrency. Training is working just like before. I should be ready to ship but i would like to make a better UI using catppuccin + next.js so it’d be a bit nicer to use and fit with my other project’s theme. Not publishing currently.

Finally implemented flavortown support after constant pushing for the API to work now. Not published but it works locally, getting ready for my PR about the /devlogs API to be merged so I can get it working with devlogs from flavortown.

I fixed the editing UI for devlogs so the colors match and look nice. I made all state-neutral cards have proper colors in the kitchen.

Didn’t know I had 7 hours stored in here, but hey, free time!

This is a port of an app I made a few years ago to next.js so it is deployable. This is a simple (or complex, depending on how you look at it) citation machine. It is powered by 5 different services in the backend: chegg, mybib, readability, hackclub ai, and my own parser. They all work together to ensure credibility and correctness in citations based on a URL. Wait? AI? Doesn’t that hallucinate????!?!?! No. Not the way I did it. The model is constrained to a specific schema and will only change things if most of the previous sources disagree on eachother (old data from a random API is usually less reliable than data scraped off the page by an LLM). Backend does all the fetching, client privacy through a proxy.

Fixed api key reroll button to be white.

Ok so I finally got back to this project! After HCAI came back online I did some tweaks. Firstly, since nest got abandoned, I switched the DB to use Neon! I could NOT upgrade to AI@6 since the openrouter sdk is behind on it, but I will look into upgrading once they do. I also did everything listed below:

Changelog

feat: model parameters
fix: context token button size -> sm
fix: system prompt size and web search prompt
fix; add: field, slider, spinner
fix: open search citations in a new tab

I themed the API docs. I added a font family override switch to change the font to your system font. I added a proper accent-color to all inputs. Fixed the colors on modals (transparent bgs!). Added footer reference to me (i ned creds). I fixed scrollbars and the spacing on project card stats.

Stock badges now have @base text, improving readability. I also tweaked some colors on the sidebar to make the icons less blurry.

Revised all of the input stuff. All input colors now match the opposite of their background color, specifically @base. Text colors have been normalized with a very odd less loop that makes all text @text unless in an input group, then it is @base. This in turn fixed the search bar in the shop, and all of the comment inputs. I also added the UI for the vote pages and the list of your votes page. I have also added a @surfaceX background to the achievement toast.

I added themed scrollbars. Doesn’t really work on firefox but eh it’s better than nothing.

This devlog actually encompasses over 40 hours of work but I am not sure why it isn’t tracked… hm. Anyways, here’s a rundown:
I began work on a custom frontend for the hackclub ai service after I found out that @mahad had redone most of it to make it viable as a service that people can use.

Step one was figuring out what I even had to do! I’ve had experience with building chat interfaces in the past, and I settled on my personal favorite combo – the Vercel AI SDK + Next.JS. Recently, the AI SDK, in collaboration with shadcn/ui, added a new “AI Elements” component library for building chat interfaces. Perfect, this saved me much work!

Next, I had to design the backend. I rarely do DB stuff, so this was all a bit new to me, but, I decided on using Drizzle ORM + Hackclub Nest’s PostgreSQL instance. I used better-auth and Hackclub’s own OAuth solution to get a user ID I could store in the database. The database also stores your API keys so you can access it anywhere all the time. The DB stores chats too (what a suprise!).

Anyways, that’s about it for the technical side (or what I could recall). The actual application has many features not too dissimilar from a client like ChatGPT or OpenWebUI. It has a sidebar for chats and it uses a model to generate a name for your chats (plus a fun little emoji) on the fly. UI uses shadcn all across the board. Auth and API keys are handled in the bottom left corner. The mobile UI is quite nice IMO. Image gen works pretty well.

NOTE: Currently nonfunctional since hackai is down due to a temporary lack in funding.

I themed /leaderboard, /achievements, and /users/*. I also added a mixin to show the secret achievements available in code. I fixed the post track to keep the images centered.

I fixed some of the blinding color issues from the previous versions. I collapsed the entire thing into one ruleset that affects the entire domain (since the page system didn’t even mean anything as all of the css is bundled in one file anyways). New color system and I darkened the green color by 10% so ye peepers don’t stop functioning. I fixed many issues with the sidebar and addressed the user profile under the sidebar. I also added some tweaks to the sizing of images in devlogs so they shrink to fit instead of being clamped to an aspect ratio.

I repackaged the entire style using the catppuccin library. I also rewrote it in less to support some macros which made it easier to maintain. I added support to switch themes and accent colors using stylus. I changed it so all buttons are now the selected accent color.

Got stylus set up to track my progress in hackatime, then I began work! Started off with my catppuccin css variable base then I went through the source code of flavortown, first changing all hardcoded colors to similar variables as a layer in my userstyle. Then, I patched the entire site with those colors making sure it looked nice in every case. Finally, I published it to userstyles.world. This served as an initial step that allows me to improve over time.