%q is game changer in very unique situations

real

I saw you’re post on self hosting Reddit, seems to have done well!! Congrats!

oh HECK YEAH

welcome to the dark side 😇

I’d guess it’s people asking “what’s Bruno?” when they see it 😅

0 OpenAPI and a few comments 🫡

try out just files next!

make has a ton of useful stuff for detecting build changes, but with go, it’s not *as* big of a concern, so more simplistic justfiles work really well imo

Charge for an API Key.

Devs can scrape, at least an API key you can track usage and charge appropriately 😉

I’ll Venmo u the last $5

Honestly dunno, I haven’t used either enough! 😅 I like the hands-on-code bit of motion canvas, though.

Quite nice! I’ve always been curious about how to make those nice lines between things.. how are you making that happen?

Is it a chart?

ah yes, the big conundrum of using Snappify or code it up in motion canvas 😩

Correlation events, because why not! 🤩

“What caused that massive spike in downloads? Oh, a spike in Bluesky refereed downloads that day”

“Insightful” feels more actionable.. I can do things with insights; can’t do much with power (well…)

I like the contrast of “yet”. But “simple and insightful” also works 😅

I agree. Taking a closer look at the video, a few things are interesting:
- it never finishes loading
- even once loaded, a cache is used. Clicking refresh does a hard pull. I modified my internal user filter as a demo.

Solution here is probably “let it load, then click reload if still persists”

Somewhere, a Sentry (or ehm PostHog error capture) hopefully triggered

PostHog, usually it’s better than this 😅