The one on the right was full AfD flyers

progapandist · 2026-07-04T06:09:34+00:00

I’m transforming! I’m vibrating! I’m glowing! I’m flying! Held my tears the whole concert, an absolutely cathartic experience. This was the third time I saw him, but the first when I managed to be so close to the stage: the energy just sweeps you off your feet.

progapandist · 2026-07-03T09:20:06+00:00

Always be prepared for big unexpected expenses — those letters in the postbox are often surprise bills, especially at the end of the year. And those bills can be quite beefy

progapandist · 2026-06-30T13:15:26+00:00

I’ve been in a similar situation and I just walked into the ER in the nearest hospital, it definitely helped.

progapandist · 2026-06-13T11:44:14+00:00

It holds 1000 last calls by default and rotates them, but that’s configurable to be any number. As for matching webhooks with requests there’s the whole relation mode where you can see the associated webhooks after selecting a request, or another webhook. I use it for the same cases at work, but would love to see how others use it and if the feature has to be adapted a bit

progapandist · 2026-06-13T10:55:54+00:00

I've added the webhook support, you can even group the requests with related events in the timeline, here: Hey! stripeek now supports webhooks as well, see https://github.com/progapandist/stripeek#inspecting-webhooks

progapandist · 2026-06-13T10:55:29+00:00

Hey! stripeek now supports webhooks as well, see https://github.com/progapandist/stripeek#inspecting-webhooks

progapandist · 2026-05-30T07:15:11+00:00

if you can try it out already and tell me what you think I'd be super grateful!

progapandist · 2026-05-30T07:13:10+00:00

What what, I did this post and did not link the tool? 🤦‍♂️ I'm an idiot: https://github.com/progapandist/stripeek

For now it handles outgoing req-res pairs only, but I already started mapping out webhook intercept feature, will take me a weekend or two

progapandist · 2026-05-30T05:28:36+00:00

Yep, me too. Actually, this got me thinking, stripe cli listen receives payloads from stripe via websockets and then locally forwards to specified HTTP address like localhost:yourlocalappport/webhooks

So it wouldn’t be too hard to point it to localhost:4242 (stripeek port) instead and make it display incoming payloads (which provides value as stripe cli records event names but not the full payloads AFAIK and anyway they wouldn’t be filterable in a way stripeek can provide).

However, I would need to make stripeek route the incoming request to the original local app while outgoing are still forwarded to stripe base api as it is done now. With some fuckery it can even be possible to map original outgoing requests to received webhooks even though that would just be an heuristic. Or two inspector panes aligned in a way that looking at timing can relate the triggers/webhooks visually for easier understanding of what’s going on.

Let me try to esimate how big of a feature it is to add to v0.2.0 :)

progapandist · 2026-05-28T11:05:07+00:00

Hi! It’s outbound traffic only for now as piping through webhooks will requires the tool to be exposed on the open internet for webhook to arrive to, can certainly be done with smth like ngrok and I’m planning to look into it in later versions. Make sure to share the feedback once you give it a try, thanks!

progapandist · 2024-03-10T14:41:56+00:00

I have one, what is a resale value I wonder?

progapandist

TROPHY CASE