Gabs

This devlog was all about making the dev experience smoother and more flexible. I’ve added live reloading so you don’t have to keep hitting refresh, and the build process now handles nested folders properly.

The Highlights:

• Live Reload via SSE: I injected a small script into served HTML pages that listens to a /reload endpoint. Now, when you save a file, the browser refreshes itself automatically.
• Recursive Builds: Steno isn’t limited to flat folders anymore. I updated the build logic to use glob patterns and Deno.mkdir({ recursive: true }). This means nested content like content/blog/post.md will actually show up in the right place in your dist folder.
• Cleanup: Tidied up deno.json by removing the example theme from the workspace and cleared out some unused imports in fileUtils.

What’s Next?

The core mechanics are there, but the code needs a little polish. This includes testing, DRYing up the code, and maybe more checking here and there

This is the devlog about this project, here some details:

Experiment window: 7 days
Test environment: Discord server Snug Nook (snugnook.org)

This was a 7-day experiment to see if a single main.ts process could feel like a persistent person instead of a command bot. The goal was technical: stable behavior, memory over time, and believable pacing in chat.

Core setup:

Adrian runs on a simple stack:

• Deno runtime
• discord.js-selfbot-v13 for Discord events and presence
• Local MLX endpoint (http://127.0.0.1:8080/v1/chat/completions) for generation
• SQLite for user memory (users, user_facts)

Everything is wired together inside main.ts.

How it behaved:

The flow is straightforward:

• Listen to incoming messages and filter obvious noise.
• Score whether a message is worth replying to (ping, DM, question, reply context, etc.).
• Buffer user input for ~5 seconds so split messages can be merged.
• Generate a response with persona constraints.
• Clean and validate output before sending.

On top of replies, Adrian also:

• Updates mood/presence every 10 minutes from recent context.
• Posts occasional autonomous “icebreaker” thoughts.
• Reacts to hype/meme messages and sometimes joins reaction bandwagons.

Memory and state:

Two memory layers were used:

• Persistent (SQLite): trust score, vibe summary, extracted user facts.
• In-memory: short rolling context, pending reply buffers, recent ping history.

This gave decent continuity across chats while keeping runtime logic lightweight.

Guardrails that helped:

A few practical safeguards carried most of the stability:

• Coherence checks to reject weird/noisy outputs.
• Strict formatting prompts for mood, vibe, and fact extraction.
• Fallbacks when generation failed or came back too long.
• Sleep/wake scheduling so behavior had natural downtime.

Limits we hit:

The design worked, but it has clear limits:

• Persona consistency is mostly prompt-based.
• One global isProcessing lock can bottleneck multiple concurrent conversations.
• Some conversational state is process-local and resets on restart.
• If the local LLM server is down, behavior degrades hard.

Final takeaway (7 days in Snug Nook):

In Snug Nook (snugnook.org), this looked less like a classic chatbot and more like a small autonomous loop: ingest events, reason with local inference, store lightweight memory, and keep running. It stayed technically coherent for the full 7-day window, with most failures handled by simple guardrails rather than heavy infrastructure.

ps: I’ve attached some of the funniest moments of his while talking with fellow discord members

Hey! Welcome to my website! I’ve decided to redesign my website to something more professional, something that looks close to a writing feeling, therefore, this was the result! (before we continue, you can see the current website on https://gxbs.dev). Now I think it looks amazing, let me break it down:

1. Homepage, with nice animations, and TYPOGRAPHY!! maaan I love this font, its called PP Editorial New. Very good.
2. Projects page, took the data from the last website
3. Commissions page, again designed with care and a builder
4. Studio, a little portal for my commission clients where they see live updates & more
5. Blog, ditto.

Anyway, I hope you guys like it too, and please comment feedback, i’d love to make it better!!

Redesigned and build the website!

So initially my friend Mirko had a simple 11ty theme which you can still see on https://bromb.in. He had the idea to redesign it and to make it better. So I decided to make that theme for him! It’s build with astro, and it contains most of the important pages including all the stuff related with blogs. In rest, it’s placeholder text since it’s a theme, he will put all the text in.

Complete redesign over the application to fit in with the new design for most of the tool in the Vanilla OS project. This includes:

• A new collections view
• New articles list view
• And a almost complete redesign of the article page. Now with a sidebar where not only the navigation itself is, but also the reading time + share/print button and lastly the navigation clicks.

The header and footer also changed with now the search bar not taking the full available space of the header.

Lastly the authors pfps became black and white so it isn’t a distraction.

The pr can be found here: https://github.com/Vanilla-OS/chronos-frontend/pull/210