A surprising amount of product work is deciding what not to build. The temptation is to keep expanding: monitoring, performance, logs, and everything else. Sometimes it’s better to let a product do one thing well.

A surprising amount of product work is deciding what not to build. The temptation is to keep expanding: monitoring, performance, logs, and everything else. Sometimes it’s better to let a product do one thing well.

Most redesigns add things. I removed them. Turns out, deleting CSS is also design.

Rate my landing page:

Most redesigns add things. I removed them. Turns out, deleting CSS is also design.

Rate my landing page:

lobste•rs just switched to SQLite I’m genuinely happy about it. It’s a wonderful site... (and a Telebugs customer) SQLite keeps winning 🎉

lobste•rs just switched to SQLite I’m genuinely happy about it. It’s a wonderful site... (and a Telebugs customer) SQLite keeps winning 🎉

Say hi to my new profile pic

Say hi to my new profile pic

I woke up to no internet, no electricity, and not even a mobile signal. There was only one thing left to do: varnish my bench. youtu.be/si-VwD3Px7o

I woke up to no internet, no electricity, and not even a mobile signal. There was only one thing left to do: varnish my bench. youtu.be/si-VwD3Px7o

Three days after launch, the flag battle is already getting serious: 🇩🇪 Germany is leading with 203,063 clicks 🇧🇷 Brazil is chasing with 106,122 clicks 🇺🇸 USA is far behind with only 19,249 clicks Is Germany really going to win this easily?

Telebugs runs on SQLite. Not as a toy setup. Not as the thing I plan to replace once Telebugs gets "serious." SQLite is part of the design. I like that. Actually, I love that. telebugs.com/blog/telebug...

Three days after launch, the flag battle is already getting serious: 🇩🇪 Germany is leading with 203,063 clicks 🇧🇷 Brazil is chasing with 106,122 clicks 🇺🇸 USA is far behind with only 19,249 clicks Is Germany really going to win this easily?

Telebugs runs on SQLite. Not as a toy setup. Not as the thing I plan to replace once Telebugs gets "serious." SQLite is part of the design. I like that. Actually, I love that. telebugs.com/blog/telebug...

I shut down Coffee World Rush. The project had been receiving almost no traffic for the past few months, so it was time to say goodbye.

I built a small web game called Flag Click. The idea is almost embarrassingly simple: you click your country flag, your flag climbs up the pole, and you try to overtake everyone else. That’s the whole game. kyrylo.org/projects/202...

I built a small web game called Flag Click. The idea is almost embarrassingly simple: you click your country flag, your flag climbs up the pole, and you try to overtake everyone else. That’s the whole game. kyrylo.org/projects/202...

I made a stupid little game where countries fight by clicking their flags. Every click lifts your country. Top country gets the crown. Play here: flagclick.com

I made a stupid little game where countries fight by clicking their flags. Every click lifts your country. Top country gets the crown. Play here: flagclick.com

God made some programmers senior and some junior. Sam Altman made them all equal.

Very cool project

God made some programmers senior and some junior. Sam Altman made them all equal.

I completely remade Telesink. The idea is simple: 1. Send events to the Telesink API. 2. Collect them in a sink. 3. Filter them into custom views so you only see what matters.

I completely remade Telesink. The idea is simple: 1. Send events to the Telesink API. 2. Collect them in a sink. 3. Filter them into custom views so you only see what matters.

End of my mini era. P.S. They still owe me about $50.

Telebugs 1.18.0 is out. This one is about what happens when your app starts screaming.

Telebugs 1.18.0 is out. This one is about what happens when your app starts screaming.

It has always bothered me that there was no straightforward way to know what Telebugs is doing in the background (and it's doing a lot). There was no way to see what was purged and when, when VACUUM ran, or what maintenance tasks had completed. So I fixed it with the new Maintenance Activity feed.

It has always bothered me that there was no straightforward way to know what Telebugs is doing in the background (and it's doing a lot). There was no way to see what was purged and when, when VACUUM ran, or what maintenance tasks had completed. So I fixed it with the new Maintenance Activity feed.

Telesink work continues! I'm going through a series of changes: 1. The product is now clearly positioned for developers. 2. It's heavily inspired by IRC (the logo hints at that). 3. I'm embracing Codex as the hands of the project (I'm the brain). So I'm vibe coding it under my supervision.

New Telebugs guardrail: Queue Protection. If your apps send errors faster than Telebugs can process them, intake pauses before the queue grows too large. Rate limit handles the front door. Queue protection handles the backlog. An error storm should not become an infrastructure incident.

Telesink work continues! I'm going through a series of changes: 1. The product is now clearly positioned for developers. 2. It's heavily inspired by IRC (the logo hints at that). 3. I'm embracing Codex as the hands of the project (I'm the brain). So I'm vibe coding it under my supervision.

New Telebugs guardrail: Queue Protection. If your apps send errors faster than Telebugs can process them, intake pauses before the queue grows too large. Rate limit handles the front door. Queue protection handles the backlog. An error storm should not become an infrastructure incident.

One of the best ways to crack a problem is to step away from your computer.

One of the best ways to crack a problem is to step away from your computer.

The more your app breaks, the more work your error tracker suddenly has to do. I’m adding first-class rate limits to Telebugs. Set how many incoming errors your instance should accept per minute. When the limit is reached, Telebugs returns 429 before the queue, SQLite, or disk get overwhelmed.

Up until now, Telebugs would keep accepting new errors even when the server was running low on disk. With SQLite, full disk is not a fun place to be. You need to free space, clean up old data, and only then safely compact the database.

Up until now, Telebugs would keep accepting new errors even when the server was running low on disk. With SQLite, full disk is not a fun place to be. You need to free space, clean up old data, and only then safely compact the database.

I always knew SQLite was good. But the real surprise was how far a boring, single-container architecture can go. I reran Telebugs benchmarks on a small Hetzner VPS: 2 vCPU, 4 GB RAM, local disk.

HTML is still King. You can now control popovers and modals without *any* JavaScript using the Invoker Commands API. Works great with <dialog> too (show-modal / close). developer.mozilla.org/en-US/docs/W...

I had measured Telebugs throughput before with Locust, but I wanted a cleaner benchmark I could explain and rerun. So I built a k6-based load test around real Sentry envelopes and queue drain time. On a 2 vCPU / 4 GB Hetzner VPS: ~50 fully processed reports/sec ~4.3M reports/day

I always knew SQLite was good. But the real surprise was how far a boring, single-container architecture can go. I reran Telebugs benchmarks on a small Hetzner VPS: 2 vCPU, 4 GB RAM, local disk.

HTML is still King. You can now control popovers and modals without *any* JavaScript using the Invoker Commands API. Works great with <dialog> too (show-modal / close). developer.mozilla.org/en-US/docs/W...

It's kind of ridiculous how expensive basic error tracking has become. Take a 100,000 errors/month plan billed annually. That's barely anything for a production app, and more than half of those events are usually just JavaScript noise. Go over the quota, and the bill keeps climbing.

Telebugs 1.17 is live with MCP support. You can now connect AI coding tools to your self-hosted Telebugs instance and let them inspect real production errors, and take actions. Telebugs knows what broke. Your coding tool knows the code. MCP connects the two. telebugs.com/blog/telebug...

It's kind of ridiculous how expensive basic error tracking has become. Take a 100,000 errors/month plan billed annually. That's barely anything for a production app, and more than half of those events are usually just JavaScript noise. Go over the quota, and the bill keeps climbing.

Telebugs 1.17 is live with MCP support. You can now connect AI coding tools to your self-hosted Telebugs instance and let them inspect real production errors, and take actions. Telebugs knows what broke. Your coding tool knows the code. MCP connects the two. telebugs.com/blog/telebug...

A customer from 🇨🇭 Zurich asked for a tiny Sentry thing they missed: “mute until this happens N more times” It stuck with me. Some errors don’t need silence forever, or a timer. They need: “tell me if this is actually coming back” Coming soon to @telebugs.com