Makisuo

For the last 5 months, I’ve been working on Hazel, and I’m super excited to finally share a first open beta version: hazel.sh, try it out now! Fully open source as always of course github.com/HazelChat/hazel I started building Hazel because I’ve been super unhappy with work chat apps for quite some time. Slack feels lacking in a lot of areas, customization support feels limited, Discord is amazing but sadly feels way too unprofessional, and I don’t even want to talk about Teams… I knew it would be a fool’s task to try to build something to replace these tools, but I wanted to try anyway and quickly got obsessed. I kept grinding on it more and more, slowly chipping away at one thing after another, and I can finally say I’m happy enough to use Hazel over any of the other solutions for my day‑to‑day communication, it's far from perfect but in a state I would love to get some feedback to make this truly the best communication platform. I built Hazel from the ground up with @EffectTS_ , @ElectricSQL , and @tanstack db to not only make it really, really fun to develop, but also great to use and maintain. For now, some core features include: - Public / Private / DM channels - Threads & replies - Reactions & file uploads -A media explorer - A smart notification system …and much, much more. Hazel is far from done, but I hope I can inspire some of you to join me on this journey to do the impossible and build the Slack of the modern era.

@yoeven @nooriefyi What scale are you running on? I have a worker doing 2k req/s without any issues

We did the reverse. cf workers are horrible to scale. logging is bad, observability is just unusable, random 529 errors. branching on repos are just a pain with multi developer branches. support is trash. we do use cloudflare r2, which works great. I would pay a premium to vercel saving me devops cost or even just run my own vps at this point on railway or fly.

Our Vercel bill was $25k per month. We just switched to Cloudflare and our spend is $2k per month. This is your sign to switch to Cloudflare

Maple's overview dashboard now shows some extra service health data. Making it easier to see overall system health in one place

Maple gives you a lot of different options to visualize and explore a trace for any use case. Debugging an error? Use the waterfall. Debugging perfomance issues? Use the timeline. Exploring the executing order or debugging retries? Use the flow view

@rauchg maple.dev 70% Opus 4.5 and 4.6. 30% codex models

Show me the thing you’ve built with AI you’re most proud of. Reply with a working product URL and what model / agent you primarily used.

@BriansAngles YES

Experimenting with something new, not sure if I love it or hate it. wdyt?

@_mjmeyer @imax153 👀

@makisuo @imax153 you should have @makisuo on office hours 👆

Something really cool coming to Maple soon. Automagically record Browser Sessions and auto link them to backend traces

@RajShak96083714 Thanks man, means a lot 🫶

@makisuo Hey man ur shipping crazy 🫡. Really appreciate it , it also inspires me a lot .

@_mjmeyer @EffectTS_ 🫶

if you haven checked out @makisuo amazing work here 👇, you should! it’s built with @EffectTS_ too 😉

Maple had over 100 sign ups yesterday, still can't believe it

Now when clicking on Service details in maple there is a new dependency section giving an overview over all 3rd party services

Hugops

@EffectTS_ bunx skills add github.com/makisuo/skills --skill effect-review-v4

I finally updated my @EffectTS_ Review Skill for V4, have been using it for a week now and it's been working great, give it a shot 👀

@_mjmeyer this is the way

@makisuo this is why the best of us are pooors

Telling myself I already did marketing by posting on twitter and going back to building instead.

@danieljvdm @harrysolovay Ah yeah cool makes sense, maintaining my own bindings for most stuff across projects right now might contribute a bit love your taking the initiative to finally turn something into a library lol

yeah correct, requests are scoped so resources get automatically get cleaned up that are request-scoped, and if you have forked fibers that you want to outlive the request you (currently) need to be explicit with `waitUntil`. The OTEL stuff is tricky, I had a working implementation that was quite hacky to keep the worker alive to flush that data. I might bring it back but I just wanted to start simpler for now...

The talented @danieljvdm made cool-looking Effect + Cloudflare library––check it out: github.com/danieljvdm/eff…

@SandroMaglione @EffectTS_ There is a first party XState x Effect integration coming soon right?

New article drop (after a while, first post-AI) A better way to sync XState machines with @EffectTS_ Reactivity module This is a big one, I use this pattern everywhere now 👇

Maple's service map automatically shows Databases your services are calling, with integrations for providers like Planetscale, Tinybird and Clickhouse coming soon to show more details about the specific Database