I asked AI to draw a mascot for @telesink.com. This character is called Pulse. But no, I won't use it 😅

I just launched the first public @telesink.com demo! Watch real-time events: ✈️ live aircraft 💵 Binance transactions 🐙 GitHub activity 👨‍💻 Hacker News posts & jobs ☀️ weather in major cities See what’s happening, as it happens 👇 demo.telesink.com

Inspired by messaging apps, I added a “seen” bar to @telesink.com. Here’s how it works: ✅ When you’re not viewing a sink, it continues receiving events ✅ Telesink remembers the first unseen event ✅ When you open a sink, it shows exactly where you left off

Columns in each @telesink.com feed now include day delimiters. Previously, the continuous stream of events made it hard to track activity. These delimiters give each column clear structure.

Just added a smart visual cue to @telesink.com. When you're not viewing a sink, it now gets bolded in the list to show new events have arrived.

Just added column reordering to @telesink.com Now you can drag your columns around to put the most important events exactly where you want them. Prioritize what matters most!

Some call it OCD. I call it attention to detail. In @telesink.com, I made scrollbars thinner and added subtle accent colors to the sidebar, footer, and column headers. The goal: let the main content stand out. Feels like a small change, but it noticeably improves the UI.

Scroll a @telesink.com column and jump back to the top instantly. Since it’s real-time, you’ll see how many new events arrived while you were browsing older ones.

🎉 The @telesink.com JavaScript SDK is here: telesink.com/blog/telesin...

⚡️ See your events instantly at @telesink.com Demo in the video: sink setup + first event in <30 seconds. Production apps: SDK in minutes. Know what your product is doing. Right now.

Out with the old, and in with the new (@telesink.com logo)

Just shipped column filtering in @telesink.com, and holy shit, the dashboard finally feels like a real product 🔥 I’m already dogfooding it on my own projects. Here’s the quick demo I recorded: - Button clicks tracked with JS - Completed games coming in from Ruby

[email protected] is built in Ruby on Rails, so the first official SDK had to be Ruby. It’s now here: telesink.com/blog/telesin...

🎉 I just published the first version of telesink-javascript - a lightweight Browser+Node SDK for @TelesinkHQ. Already using it in a few of my projects. It’s simple to integrate and designed to stay minimal. Code’s on GitHub 👇 github.com/telesink/tel...

🎉 I just published the first version of telesink-ruby, the Ruby SDK for @telesink.com I’ll be dogfooding it across all my projects to validate behavior in real-world use. Once it’s solid, I’ll roll out the rest of the SDKs. The code's on GitHub 👇 github.com/telesink/tel...

🛡️ Pro tip for building reliable Events APIs: Network delays, retries & hiccups make duplicate events inevitable. (Double charges, repeated notifications, messed-up state - all bad.)

Cloudflare’s email obfuscation caught me off guard when I deployed @telesink.com to production. I track @telebugs.com downloads and display the real customer email in my private dashboard to see who downloaded and when. But every event came back as [email protected].

What’s the simplest schema for an Events API? That’s the exact question I’ve been grinding on for @telesink.com. 1/

I decided to avoid modals and toasts entirely in @telesink.com. Everything is rendered inline with Turbo Frames. The goal is ultimate simplicity and speed. In the video below: signing up and sending the first event.

Quick glimpse of @telesink.com that I'm actively building. ✅ Every event your app sends lands in a sink ✅ Dashboard columns: slice, organize & group events (in the future) ✅ Click any event for full details

Events in @telesink.com will be grouped into sinks and displayed as columns. You’ll be able to add as many columns as you like. Each column will filter a sink based on your own criteria. P.S. This is the goal. I'm still very early in development.

CSS clamp() is straight-up MAGIC. I’m having an absolute BLAST building this buttery-smooth fluid layout for @telesink.com Going full unconventional with the experience, but honestly, clamp() was made for dense, information-rich UIs like this. Feels like cheating (in the best way).

For @telesink.com, I went with a fluid, text-first design. Entire UI built on text. The design is its absence. Your feeds elegantly fill the whitespace, making every view uniquely yours.

I'm building @telesink.com - an open-source real-time event dashboard. It replaces the scattered notifications from Slack, Discord, Telegram, and Teams with a multi-column layout so you can actually see what's happening in your product right now (different streams side by side).

Laying the first brick for @telesink.com 🧱

Telesink requirements I’m optimizing for: ✅ Real-time updates without refreshing the page ✅ Fast iteration so I can ship quickly as a solo developer ✅ No over-engineering, especially with zero users today ✅ Open source and self-hostable from day one (free forever). telesink.com/blog/tech-ch...