customer support

What’s the simplest schema for an Events API? That’s the exact question I’ve been grinding on for #telesink. I wanted the most minimal thing that’s still actually useful. One path: just accept text and parse everything (Telegram style). Super simple... but Telegram is a generic chat client. We’re building a specific tool. So I landed on this: text + emoji + event (the name) + properties (any key-values you want). Flexible enough because of properties, yet stupidly clear and understandable. Thoughts?

optimizing productivity with baby #nnjlife

wake up 9:00

Register API was not working for a few days 🤦‍♂️ deployed a fix #morflaxstudio

More #mygoo tuning and bug fixes

Watch F1 #life

saturday routine #nnjlife

walk on treadmill

update v1 & v2 to-dos #splittu

morning routine #nnjlife

💼 client work: send launch trailer video for review #tauron

Polishing deliverables #stacknaut

morning breakfast #life

really annoying cause I get scrapped by bots in short bursts from countries like Vietnam, India etc, but the only thing that helps is the "Under attack mode" in Cloudflare, but I can't have that turned on all the time cause if will fuck up the google bot and other ai scrapers #devopsprojectshq

the new pipeline working okayish, but still needs some updates, ah coding #devopsprojectshq

building a sprite splitter because I can't even with the sprites anymore

⚙️ Updated #dotfiles and tmux config

optimize Notion data loading in select flows #notepulse

exploring ideas