If you were to buy @telebugs.com, what’s the one thing it should have?

Taking a short pause from @telebugs.com for a few weeks - working on a new project! I’ll still be on standby for bug fixes, though.

@telebugs.com 1.8.0: New dashboards, wide view, error ownership, and more: telebugs.com/blog/telebug...

Telebugs 1.8.0 released.

One last change before I ship @telebugs.com: project cards no longer show reoccurred and unique error counts. They turned into a resource hog on large projects, and I want Telebugs to stay snappy (~150 ms response time). On the index view, what really matters is comparing error volumes.

🚨 @telebugs.com 1.8.0 drops tomorrow! This is the most packed release since day one. It took *a lot* of sweat 💧

[email protected] relies on Solid Queue for job processing. It’s a great library, but I made a big mistake. As an early adopter (jumped on it the day it launched), I got burned by a misconfiguration: Telebugs never cleaned up finished jobs.

I’ve decided to postpone the @telebugs.com release until next week. This week I uncovered some important issues with data truncation that need to be fixed before shipping. I’ll share more details as I make progress.

One last tweak in @telebugs.com before wrapping up: copying now updates both the icon *and* the button text, so there’s no doubt it worked.

Exactly why I built @telebugs.com. Error tracking has the same problem.

I’m working on the final major feature of @telebugs.com 1.8.0: wide view. With the new Error and Report dashboards, it makes sense to let the dashboard breathe. Still, not everyone may prefer it, so wide view will be configurable per user. Work in progress!

First Telebugs guest post by @seuross, author of gems used by thousands 👏 Lapsoss is a vendor-neutral error tracker adapter: send errors to Telebugs, AppSignal, BugSnag, or any provider. Rails 7+, zero boilerplate, fully compatible with @telebugs.com. telebugs.com/blog/introdu...

Don’t want to sound like a broken record, but I’m keeping it real with you. @telebugs.com is dropping this week, and this is your last chance to lock it in at $299. If you care about keeping your apps stable, that’s basically nothing. The checkout page is already updated to reflect the price hike.

Trying out a new feature in Rails 8.1.0.beta1 for @telebugs.com! Markdown rendering landed a few weeks ago, and it's perfect timing to power Telebugs' first AI feature. Soon you’ll be able to view any error report as Markdown and feed it to your LLM (copy-paste for now).

The next @telebugs.com release brings brand-new dashboards: - All Errors - All Reports Each dashboard comes with handy filters: - Filter by project - Date range (with a nice HTML date picker!) Results are paginated with cursors, giving O(1) page fetches even with millions of records.

I’m experimenting with another @telebugs.com dashboard: Report Overview. The upcoming release will include two dashboards: - Projects Overview — the one we’ve always had. - Error Overview — the new one (screenshot).

Gotta give mad props to @seuros for shaking up the Rails error tracking game. He’s building Lapsoss - a vendor-agnostic library for error tracking. Think ActiveJob, but for errors. Switching from Sentry to Honeybadger? With Lapsoss, just change the adapter, the API stays the same.

This is one of those cases where the code is trivial, but the feel of the feature takes all the thought. I wasn’t happy with how the current Error Ownership UI in @telebugs.com felt, so I spent last night (and part of this morning) thinking it through more carefully.

Error ownership in @telebugs.com in action (still in development):

In @telebugs.com, you won’t "assign" errors - you'll own them. The word "assign" in the software world carries a lot of managerial baggage. Telebugs is free of that. It's a developer-first product and developers mess up. And when you mess up, you own your mess. bsky.app/profile/kyry...

🏗️ I'm kicking off the Error Ownership feature in @telebugs.com. Right now, if you’re on a team, you have no idea who’s working on an error. You end up talking it out, then just... remembering. That’s wasted brainpower.

Telebugs in one sentence:

✅ Done with the All Errors view in @telebugs.com This dashboard lets you track recent errors across all your projects in one place. With it, you can even turn off notifications entirely and just use this view to keep an eye on what’s breaking.

This new view in @telebugs.com gives you a helicopter view of errors across all your projects. Still a work in progress: - performance isn’t production-ready - more filters are coming - and probably a few things I haven’t thought of yet

This is how you’ll switch between all projects and all errors in the upcoming @telebugs.com Does it need cute icons? Nope. Toggle animations? Nope. Understandable? Yep. Boring? Proudly yes. Don’t overcomplicate it. Don't overthink it.

Good morning, wherever you are! 🌍 It’s the start of the week, which means I’m planning the next @telebugs.com release. This one is all about better support for multi-project and multi-user teams.

This morning, a @telebugs.com user reported sparklines not loading for Apps. I uncovered a bigger issue: new installs missed v1.7.0’s perf upgrades (yikes!). A few hours later, Telebugs v1.7.1 is out with fixes. That’s how we roll! bsky.app/profile/tele...

Telebugs 1.7.1 released.

Telebugs 1.7.0 released.

🎙️ I'm happy to announce that @telebugs.com 1.7.0 is here! This release *massively* improves performance on low-end hardware (noodle arms VPSs, you can relax now!) - with over 10x faster speeds.

Almost shipped @telebugs.com 1.7.0 today: ✅ blog post ✅ changelog ✅ doc updates Then a critical bug showed up 🤦‍♂️ New plan: sleep, fix, launch Friday.

We've been using Telebugs for Lobsters the last few months, it's great. Usable, flexible error reporting with painless self-hosting. No fluff, no regrets.

🚨 @telebugs.com 1.7.0 releases tomorrow! This update makes performance way smoother, especially on noodle-arm VPSs that used to struggle with big error loads. It’s also the last version at $299. After that, price goes up to $499. If you’ve been on the fence, now’s the time.

The upcoming @telebugs.com 1.7.0 release will make the dashboard at least 10–20x faster (from 🐌 to 🏎️). On budget hardware, the difference is night and day!

Performance tuning in @telebugs.com is done with Benchmark.realtime. It’s a super simple way to measure how fast your Ruby code runs: 𝙱𝚎𝚗𝚌𝚑𝚖𝚊𝚛𝚔.𝚛𝚎𝚊𝚕𝚝𝚒𝚖𝚎 𝚍𝚘 # 𝚈𝚘𝚞𝚛 𝚌𝚘𝚍𝚎 𝚎𝚗𝚍 It comes with Ruby’s stdlib, so no extra setup needed.

What if I released Minibugs - a 100% free, open-source, ultra-lean error tracker by @telebugs.com? Features: ✅ Self-hostable in minutes ✅ Compatible with Sentry SDKs ✅ Projects, error grouping, and search ❌ Notifications ❌ Teams ❌ Anything else Built for solo devs who want privacy + basics.

If you use SQLite in your web app, run `PRAGMA optimize;` periodically. Why? It collects table/index stats for smarter queries (ANALYZE). It's essentially a speed boost for free. Shipping in @telebugs.com 1.7.0! P.S. First run might take a few minutes, but subsequent runs are almost instant.

Service Messages in @telebugs.com let me (the developer) run heavy computational tasks on your machine, in the background. To make it clear to users, I treat each one as a mini task of its own. That’s why some careful design is required.

Writing self-hosted software is a different beast. In a SaaS, you choose where and how to host and run your software. In self-hosted, it’s the user who decides (within the limits your app allows).

The charts in @telebugs.com use a technique that would probably fail you in a coding interview: pulling records from the database and aggregating them in memory inside the Ruby process.

Telebugs 1.6.0 is fresh out of the oven, and I’m already cooking up @telebugs.com 1.7.0 (no shortage of ideas here). Details will come later, but here’s a little clue: think performance. For now, it’s time to explore before I can proudly yap about it!

Telebugs 1.6.0 released.

I’m *so* excited to introduce @telebugs.com 1.6.0! The project index view just got an upgrade: organizing projects is easier than ever, thanks to the new Apps feature. Read more 👇 telebugs.com/blog/telebug...

In @telebugs.com, every piece of UI lives inside a card. Each card has a little (i) icon in the top-right corner. It’s your shortcut to the docs. Before, some cards didn’t have an icon at all, or the link just pointed to the general /docs/ page because the detailed pages didn’t exist yet.

I don’t build @telebugs.com by peeking over a competitor’s shoulder. I don’t care about copying. Telebugs is a breath of fresh air - full of fresh ideas, but not “experimental for the sake of it”. Every time I solve a problem, I ask: what’s the most straightforward approach?

Dirty implementation of the table view for projects in @telebugs.com. Yay or nay? I’m leaning toward “nay”. I don’t want to introduce bloat for something less useful than the cards. The only real advantage is the ability to compare stats, but that doesn’t seem particularly necessary.

Project (un)pinning and filtering coming soon in @telebugs.com

The projects view in @telebugs.com is designed to give you a helicopter view of your projects’ status over the last 24 hours. I have a series of improvements in mind to make it shine.

These have gotta be the sexiest tables I’ve ever designed (in other words, @telebugs.com releases/artifacts are done):

A @TelebugsHQ user reported that the releases view is crashing for them. Currently, it loads all projects’ releases along with all attached artifacts. I honestly didn’t realize a single release could have thousands of artifacts.