I’m going all-in on #telesink again (the open-source real-time event tracking dashboard of my dreams). Kicked it off about a month ago, but poor planning + some bad luck meant I barely touched it since. Starting today, I’m in full Telesink mode (while staying on standby for Telebugs support tickets).

#telebugs 1.14.0 is live! Big usability wins: ✅ Extended filters: last 3/7/28/91 days ✅ Automatic sensitive data scrubbing (passwords, tokens, credit cards) ✅ Sparklines next to every error group ✅ “Notify on every occurrence” rule ✅ Dual timezone timestamps ✅ Auto-refresh checkbox 👇👇👇 Full details + screenshots: telebugs.com/blog/telebugs-1-…

This release wasn’t planned. But during a two-week break from my laptop, I got swarmed with more support requests than ever before. That made priorities very clear. I had planned to start something new, but instead I chose to show up, stay consistent, and focus on what people were relying on. The new #telebugs is out! telebugs.com

I'm really close to shipping a new #telebugs version. There are just a few more bugs to iron out before it is ready. The upcoming version will get a lot of bug fixes, more polish and beautiful sparklines per group 😍 You can view these sparklines live in the demo: demo.telebugs.com

Sneak Peek: “Notify on Every Occurrence” - Coming Soon to Telebugs A few weeks ago, a #telebugs user shared a really insightful request that hit home for anyone running critical applications. They manage systems where every error (even rare ones) needs immediate attention. Marking an error as “resolved” is helpful for organization, but it shouldn’t prevent alerts if the issue happens again. Their words summed it up perfectly: “We have apps doing critical stuff. If someone forgets to un-resolve an error, we miss the next occurrence. We need a way to get notified on every instance, resolved or not.” It was exactly the kind of feedback that makes building Telebugs so rewarding. This isn’t a one-size-fits-all tool. Real teams have nuanced workflows, and this use case (low-volume, high-signal projects) deserved a dedicated solution. Good news: I’ve implemented it. Coming in the next release: “Notify on every occurrence” This new rule will alert you on every single instance of an error, regardless of the resolved state. Ideal for: - Mission-critical apps - Compliance-driven environments - Teams that treat every exception as urgent - Projects where “resolved” is more of a temporary note - It’s deliberately powerful (and noisy), so it’ll be opt-in and best used selectively on projects where volume is low. This will land in the next version update - stay tuned for the release notes. A huge thank you to the user who raised this (and to everyone who shares ideas). Listening to you is how #telebugs keeps getting better for real-world use. Excited to ship this soon. If you have feedback or other workflow needs, reply or DM (I read it all).

Coming soon to #telebugs: sparklines for every error. Each error has its own occurrence pattern. You can already see that on the error page, but until now, there was no quick way to compare errors side by side and spot what needs attention first. Now, sparklines make frequency trends instantly visible across all error groups. This change is now live in the demo: demo.telebugs.com

Coming soon to #telebugs: Sparklines beyond the last 24 hours. Some users don’t check the dashboard daily and want to compare error volume over a few days (Friday sign-off → Monday return). Now you can filter project sparklines by timeframe. This change is now live in the demo: demo.telebugs.com

Laying the first brick for #telesink 🧱 github.com/telesink/telesink

Now that the new #telebugs version is out, I can focus on #telesink. The goal is to build an MVP that’s good enough to launch. It doesn’t need to be pretty or complete, but it must do one thing well: display real-time events in a feed. I’m still deciding on the tech stack. Rails is a no-brainer, but the database is trickier. As much as I’d like to use SQLite, my gut says PostgreSQL is the safer choice. The reason is SaaS support. SQLite won’t scale well here, and ActiveRecord Tenanted being abandoned rules it out for me. If this were a self-hosted-first app like Telebugs, SQLite would be perfect. But it isn’t.

#telebugs 1.13.0 is here with 3 major features: 1️⃣ Microsoft Teams notifications 2️⃣ One-click opening of backtrace frames in your favorite local editor 3️⃣ Direct links to view or edit code right on your repository host. Bonus point: lots of bug fixes 🐞🔨 Read more: telebugs.com/blog/telebugs-1-…

New #telebugs is out! Lots of bug fixes and polish 💅 Blog post coming tomorrow (I'm too tired now)

Preparing the changelog for #telebugs 👀

New in the upcoming #telebugs release: Edit files directly on GitHub via the web version of VS Code. How it works: 1️⃣ Set up GitHub as your project's repository 2️⃣ Click "Edit on GitHub" next to "View on GitHub" 3️⃣ YOLO your fix! Shipping soon.

New in the upcoming #telebugs release: Open files directly from the backtrace How it works: 1️⃣ Set your preferred text editor in Account Settings 2️⃣ Browse the backtrace of any error 3️⃣ Click “Open in editor” to open the file at that exact frame locally Supports all major text editors. Shipping soon.

New in the upcoming #telebugs release: Link errors directly to your source code. How it works: 1️⃣ Set your repository and deployment branch when creating a project 2️⃣ When an error arrives, Telebugs builds a direct link to the exact code No repository access required. Supports GitHub, GitLab, and Bitbucket. Shipping soon.

Publish "The real-time event tracker I want" #telesink telesink.com/blog/the-real-ti…

Closing the year on a high with an awesome #telebugs testimonial. Thank you for the kind words 🙇‍♂️

🎁 Open source #telebugs docs github.com/telebugs/docs.tele…

I fucking shipped justfuckinguse.com

It's out! 🩸💧😭 Blog post coming today! #telebugs