Skip to content

The Story

Memet Zx edited this page Nov 14, 2026 · 2 revisions

The Story

Why Mools exists

Mools started out of boredom.

I wanted to keep my hands busy with something useful, and I was also on the hunt for free tools that suit my own workflow: the small utilities a developer reaches for again and again, such as formatting JSON, encoding a string, hashing a file, turning CSV into something else. Instead of bookmarking a dozen different sites, I decided to build one place that I control, that works the way I like and that I can keep extending whenever I need something new.

That is the whole idea: a personal toolbox that grew into a public one.

What the name means

Mools stands for Maling-IT Online Tools. The "Maling-IT" part comes from the maling-it GitHub organization that hosts the project. The word Mools is the short, easy to type form, and the little mascot on the logo is its face.

Principles that stayed from day one

  1. Free. No paywall, no accounts.
  2. Private. Tools run in your browser and your input is never uploaded.
  3. Fast to reach. One page per tool, no clutter, and a search that finds it in a keystroke.
  4. Built around real workflows. A tool exists because someone needed it, and requests are welcome through issues.

Stories from the git log

These stories are reconstructed from the project's history: the commit log, the pull requests and what turned up along the way. The full version-by-version account is in the Timeline.

"Initial Commmit"

The very first commit, on 30 January 2024 at 11:29, has a typo in its own title: Initial Commmit, with three m's. It is still there, and nobody fixed it.

Then nothing happened for almost five hours. At 16:19 the history suddenly bursts: by 16:26 the string tools and the converters existed, by 16:34 there was a GitHub Actions workflow, and one commit was honestly titled add some page but not finish yet. The day ended with 26 commits, and 15 of them are called Auto commit for changes in ... followed by a file name. The editor was committing on every save, so the log of that day reads like a diary of which file was being touched next.

Two lockfiles and the first pull request

The first day also left two lockfiles in the repository, bun.lockb and yarn.lock, because the project could not quite decide which package manager it was. The deploy workflow cached yarn, so yarn.lock mattered, and it turned out to be listed in .gitignore.

That was fixed on 31 January 2024 by Crownss, in the first and, for a long time, only pull request (#1, feature/SEO). It added the SEO tags and un-ignored the lockfile, and it was the first time anyone besides the author touched Mools.

Almost three years later the lockfile story ended the other way: the dependency upgrade deleted both old lockfiles and settled on bun.

"Forget it"

Getting the site onto GitHub Pages took more fights than the site itself. The history reads like a short drama: try to fix error on 30 January, Upgrade Node to 18 on the evening of the 31st, and then, at 00:33 on 1 February, a commit titled simply Forget it. Two minutes later came fix conflict on gh-actions.

The deploy workflow has been rewritten since. It now runs on Node 24 with bun, runs the tests before building and has a sibling that publishes releases. Nobody has needed to say "forget it" since.

The mascot

On 1 February 2024 a commit called add Mools Favicon gave the site its face. For more than two years it lived on as the favicon and a small logo in the corner of the site.

In November 2026 it became the logo in the README and on the wiki. Right after that an image optimizer bot opened a pull request nobody had asked for (#3) and shrank the mascot by 52%. Every pixel was checked afterwards and none had changed.

A Telegram tester in a toolbox

On 4 February 2024, Add Telegram Bot Testing page landed. It was the first tool that was not about text: pick a method, type a token, send a message or a photo and get the exact curl command back.

It makes sense in context: the maling-it organization has several Telegram projects of its own, such as telegram-api-manager, backend-tg and media-search-bot. A way to poke a bot from a browser tab was a toolbox tool in the most literal sense.

The odd one out

Among the first converters is one you will rarely find elsewhere: Van Ophuijsen Indonesian. It rewrites modern Indonesian into the spelling used from 1901 to 1947, where j was dj, y was j, u was oe and c was tj. Yang jauh itu cukup becomes Jang djaoeh itoe tjoekoep.

Its first version replaced letters one after another, so it only worked by luck: the order of the rules happened to keep earlier results from being converted again. It was rewritten to convert everything in one pass, and it has a test now.

Sleeping twice

Mools was built in bursts. After 4 February 2024 the log goes silent for almost sixteen months. It wakes up on 1 June 2025 with five commits in one day, including ToolPage, the shared component that every text tool is built on today. Then it sleeps again for another seventeen months.

One early-morning session

The next wake-up was the biggest. Between 03:19 and 04:44 on 15 November 2026 the log fills with about thirty commits. Mools went from roughly a dozen tools to 115, from a Svelte 4 site to Svelte 5 and SvelteKit 3, and through four new versions, from 0.4.0 to 1.1.0.

The first thing that happened that morning was an error. SvelteKit 3 refused to start with the old svelte.config.js, saying the file was no longer used. The config moved into vite.config.js, $lib became #lib, and everything after that was additions.

Bugs found along the way

Reading the old code and then writing tests for it turned up real bugs that had been sitting there:

  • Replace Text could never have worked. Reading the code showed that typing in the "find" box never reached the logic, so the search text stayed empty, and replacing an empty search would have put the replacement between every single letter.
  • Unescaping decoded twice. &amp;lt; turned into < instead of &lt;.
  • The CSV converter broke on quoted commas. Any cell like "Doe, Jane" split in two.

The tests needed debugging as well. While writing the Wordle tests, three of the expected results were wrong before the game code was. Repeated letters (like the two e's in speed) are subtler than they look.

The sidebar that covered the page

Screenshots at different widths showed that between 768 and 991 pixels the sidebar sat on top of the content, and that after tapping a link on a phone the menu stayed open. A look at the page also showed that the style picker was rendered twice with the same element IDs, so clicking a label could switch the wrong option. None of this showed up in a desktop browser; all of it was found by testing at other sizes.

Too popular for GitHub's API

The navbar shows the repository's star count, which it fetched from GitHub's API on every page load. While testing over a hundred pages in a row, GitHub started answering 429 Too Many Requests. The count is now cached for 30 minutes, which is also kinder to anyone who visits many pages.

The badge that said "Unverified"

The first release tags were created without signatures. GitHub's vigilant mode flagged all seven of them as Unverified, in orange, on the tags page. Fixing it meant re-creating every tag with a signature and force-pushing them in a single push, so that no release workflow would fire seven times. They are all green now, and the repository signs tags by default.

People

  • Memet Zx: creator and maintainer.
  • Crownss: contributed the early SEO work (January 2024).
  • Anyone who opens an issue or a pull request. See Contributing.

Where it goes next

Mools still has no deadlines. The plan is the original one: build whatever is missing from my own workflow, and whatever people ask for. What is lined up is written down on the Roadmap, in themes instead of dates. If you miss a tool, ask for it.

Got a story of your own, such as the tool you use most or the bug you hit? Edit this page and add it.

Clone this wiki locally