It was a fun weekend project. All done!

I wish an LLM could build this dressing table for me. Stepping out of virtual reality into real life (where you still need hands to get things done). Wish me luck 🙏

Honestly, I’m starting to wonder what the point of Google even is these days. Whenever I search, I almost never click any links. I just read the AI Overview and I’m done. The Dead Internet Theory doesn’t feel that far off anymore.

I wish an LLM could build this dressing table for me. Stepping out of virtual reality into real life (where you still need hands to get things done). Wish me luck 🙏

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 👇👇👇

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.

I just fixed Google Sign-In on @weuserails.com Some of you tried reaching out but your messages went to spam. sorry about that. Total flop on my side. The fix was embarrassingly simple: I forgot to initialize the Google Sign-In env vars. Yeah... it’s been broken for a month 🤦‍♂️

Honestly, I’m starting to wonder what the point of Google even is these days. Whenever I search, I almost never click any links. I just read the AI Overview and I’m done. The Dead Internet Theory doesn’t feel that far off anymore.

Turns out the issue was a misconfiguration. In production @telebugs.com runs jobs via Procfile. Demo instances instead rely on SOLID_QUEUE_IN_PUMA=true. Since demos also run in the production env, those two setups conflicted. Fix: use a separate environment so Procfile.demo (etc.) can run cleanly.

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 👇👇👇

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.

I just fixed Google Sign-In on @weuserails.com Some of you tried reaching out but your messages went to spam. sorry about that. Total flop on my side. The fix was embarrassingly simple: I forgot to initialize the Google Sign-In env vars. Yeah... it’s been broken for a month 🤦‍♂️

Turns out the issue was a misconfiguration. In production @telebugs.com runs jobs via Procfile. Demo instances instead rely on SOLID_QUEUE_IN_PUMA=true. Since demos also run in the production env, those two setups conflicted. Fix: use a separate environment so Procfile.demo (etc.) can run cleanly.

Filtering sensitive information in @telebugs.com. The upcoming update will automatically scrub passwords, tokens, API keys, credit cards, and other secrets from error reports (server-side, before they ever hit your database).

Today’s oatmeal included: - chia seeds (imported by me) - flax seeds (imported by me) - roasted peanuts - bananas - fresh coconut meat - cooked in coconut milk I’ll probably tweak it further as I discover new ingredients.

I gotta say, having access to AI in the 🇵🇭 Philippines is a game-changer. It used to be really hard to discover things online because there wasn't a central information hub. Now I can just ask AI whatever I want and it does the heavy lifting. It's helping me make decisions way faster.

I'm really close to shipping a new @telebugs.com 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 😍

Filtering sensitive information in @telebugs.com. The upcoming update will automatically scrub passwords, tokens, API keys, credit cards, and other secrets from error reports (server-side, before they ever hit your database).

I'm a huge fan of oatmeal, but in the 🇵🇭 Philippines, people rarely eat it. Luckily, 🇦🇺 Australian oatmeal is widely available. In 🇺🇦 Ukraine, I used to eat oatmeal with: - chia seeds - flax seeds - honey - cashews, hazelnuts, almonds, pumpkin seeds - cinnamon

I gotta say, having access to AI in the 🇵🇭 Philippines is a game-changer. It used to be really hard to discover things online because there wasn't a central information hub. Now I can just ask AI whatever I want and it does the heavy lifting. It's helping me make decisions way faster.

I'm really close to shipping a new @telebugs.com 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 😍

Durian is probably my favorite fruit of all time.

Durian is probably my favorite fruit of all time.

Exciting update for @telebugs.com users! A community member has built an unofficial MCP server (telebugs-mcp) that lets AI agents query and retrieve error reports from your Telebugs instance. Super useful for AI-powered debugging. Give it a try! 👇 github.com/jilio/telebu...

Sundays are for fishing. Took a boat out and went fishing. Only caught 3 small fish, but the whole experience made it worth it. Along the way we ate raw: - shrimp - sea urchin - jellyfish with plenty of rice and vinegar, of course. Ato ni bai 🇵🇭

Exciting update for @telebugs.com users! A community member has built an unofficial MCP server (telebugs-mcp) that lets AI agents query and retrieve error reports from your Telebugs instance. Super useful for AI-powered debugging. Give it a try! 👇 github.com/jilio/telebu...

Sundays are for fishing. Took a boat out and went fishing. Only caught 3 small fish, but the whole experience made it worth it. Along the way we ate raw: - shrimp - sea urchin - jellyfish with plenty of rice and vinegar, of course. Ato ni bai 🇵🇭

🚨 PSA for all @telebugs.com users If you installed Telebugs using the default installer, manually truncate your Docker logs. Due to an oversight, the log file is never truncated. A future Telebugs release will cap the log size.

Improved timestamp handling in @telebugs.com. Projects each have their own timezone, but cross-project views use UTC timestamps. This was confusing: project views showed local time, while others showed UTC. Now we display relative time everywhere, and on hover the tooltip shows both (local+UTC).

Finally got my new setup. I have everything I need to ship in 2026: ✅ Second monitor ✅ Mouse ✅ Tea P.S. This is Telebugs I’m building.

Ever rewatched a video 3 times just to decide if it’s real or AI? You’re not being careful - you’re being played.

Overnight, I received 3 emails asking me to activate accounts on completely different services. They seem to be coming from Zendesk. Does anyone know what’s going on?

🚨 PSA for all @telebugs.com users If you installed Telebugs using the default installer, manually truncate your Docker logs. Due to an oversight, the log file is never truncated. A future Telebugs release will cap the log size.

Improved timestamp handling in @telebugs.com. Projects each have their own timezone, but cross-project views use UTC timestamps. This was confusing: project views showed local time, while others showed UTC. Now we display relative time everywhere, and on hover the tooltip shows both (local+UTC).

Finally got my new setup. I have everything I need to ship in 2026: ✅ Second monitor ✅ Mouse ✅ Tea P.S. This is Telebugs I’m building.

Ever rewatched a video 3 times just to decide if it’s real or AI? You’re not being careful - you’re being played.

Overnight, I received 3 emails asking me to activate accounts on completely different services. They seem to be coming from Zendesk. Does anyone know what’s going on?

A few weeks ago, a @telebugs.com user shared a really insightful request that hit home for anyone running critical applications.

Every shitpost starts as this goofy, larval thing. Low-effort, absurd, maybe even intentionally dumb. It is just crawling around looking for attention. Most get eaten by the algorithm or ignored in the scroll.

A few weeks ago, a @telebugs.com user shared a really insightful request that hit home for anyone running critical applications.

I’ve been to 🇵🇱 Warsaw last month and it’s been incredible. If I were to describe it, I would say it’s “Ukraine that could”.

Every shitpost starts as this goofy, larval thing. Low-effort, absurd, maybe even intentionally dumb. It is just crawling around looking for attention. Most get eaten by the algorithm or ignored in the scroll.

I'm a Ruby dev with 15 years behind the belt and I hate syntactic sugar. What draws me to Ruby is its runtime capabilities similar to Smalltalk. The underused part of Ruby is its metaprogramming. The one that humans struggle with but AI could leverage.

I’d like to share a few thoughts on AI. AI. AI AI AI. AI? AI. AI AI? AI AI. AI AI AI AI AI AI AI, — AI AI AI, — AI AI, AI, AI AI AI. AI! Thank you.

Today I added support for sentry-cli v3. In @telebugs.com, it’s used to upload source maps. I still have ~10 support requests pending, and I’m sorry to everyone who’s been waiting. Bad timing: I took a few weeks off, and a lot of tickets came in at once. Normally, I address issues the same day.

I’ve been to 🇵🇱 Warsaw last month and it’s been incredible. If I were to describe it, I would say it’s “Ukraine that could”.

I'm a Ruby dev with 15 years behind the belt and I hate syntactic sugar. What draws me to Ruby is its runtime capabilities similar to Smalltalk. The underused part of Ruby is its metaprogramming. The one that humans struggle with but AI could leverage.

I’d like to share a few thoughts on AI. AI. AI AI AI. AI? AI. AI AI? AI AI. AI AI AI AI AI AI AI, — AI AI AI, — AI AI, AI, AI AI AI. AI! Thank you.

Telebugs demo server got absolutely hammered by crawlers of every flavor. Running on a modest VPS, it just couldn't keep up. Had to throw up a Cloudflare rule to block the bots so real users could actually browse. Anything else worth adding to the block list?

Coming soon to @telebugs.com: 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.