I ended up cutting Emacs off from ELPA entirely, settled on a ~700-line init.el, and now use Emacs as a glorified Org-mode agenda keeper. It's been heavenly (especially with a dedicated monitor).

The one thing I'm still working out is syncing with calendars and email.

The problem: Webhook platforms either have tiny free tiers or jump to $490+/mo (Svix, Hookdeck enterprise).

EventDock sits in the middle: $29/mo for 100k events, built on Cloudflare's edge.

Comparison pages if you're evaluating:

- https://eventdock.app/blog/eventdock-vs-svix

- https://eventdock.app/blog/eventdock-vs-hookdeck

Happy to answer questions about the architecture (Durable Objects, edge retry logic, etc).

Comments URL: https://news.ycombinator.com/item?id=47151522

Points: 3

# Comments: 0

I can imagine a camera-based input that would help detect the wagging of a tail, or continued interest in the visuals as an indicator of doubling-down on a given feature.

The dog could actually vibe code a game to their liking, but with the wrong input (a keyboard) it's a missed opportunity.

We just shipped a release aimed at bringing FinOps into PRs/CI (instead of another dashboard).

New in this release:

- Public REST API for cost + carbon summaries (JSON)

- /v1/report endpoint that can return Markdown for PR comments

- GitHub Action to generate the report + optionally post/gate on thresholds

- AWS RI/SP recommendations, plus All Accounts rollups and per-account data quality indicators

Would love feedback:

1) What signals/thresholds would make CI cost checks useful without becoming PR spam?

2) What’s your bar for auth/security + least-privilege for a tool like this?

Comments URL: https://news.ycombinator.com/item?id=46365457

Points: 2

# Comments: 1

This is a small, focused webhook inbox: you get a unique HTTPS endpoint and can inspect incoming requests (headers + payloads) in the browser.

It's built on Cloudflare's edge stack and meant for quick debugging and exploration, not production.

I'm the builder - would love feedback on missing features or bugs.

Comments URL: https://news.ycombinator.com/item?id=46273261

Points: 1

# Comments: 2

HN has been a wonderful source of both news and community - it connected me to my industry in ways that could only have been achieved otherwise by moving to SF or NYC.

In a way, it feels like a great continuation of my Slashdot years.

I get pulled into a fair number of "why did my AWS bill explode?" situations, and this exact pattern (NAT + S3 + "I thought same-region EC2→S3 was free") comes up more often than you’d expect.

The mental model that seems to stick is: S3 transfer pricing and "how you reach S3" pricing are two different things. You can be right that EC2→S3 is free and still pay a lot because all your traffic goes through a NAT Gateway.

The small checklist I give people:

1. If a private subnet talks a lot to S3 or DynamoDB, start by assuming you want a Gateway Endpoint, not the NAT, unless you have a strong security requirement that says otherwise.

2. Put NAT on its own Cost Explorer view / dashboard. If that line moves in a way you didn’t expect, treat it as a bug and go find the job or service that changed.

3. Before you turn on a new sync or batch job that moves a lot of data, sketch (I tend to do this with Mermaid) "from where to where, through what, and who charges me for each leg?" It takes a few minutes and usually catches this kind of trap.

Cost Anomaly Detection doing its job here is also the underrated part of the story. A $1k lesson is painful, but finding it at $20k is much worse.

I have seen past comments here debating many relative basic concepts on medicine. Please don't take medical advice from engineers. Drink water, exercise, eat well. Otherwise seek medical advice from a doctor.

Thanks!

If that fails, you can click on "10 Quit" with the mouse (not ideal, but an immediate solution).

Hard to believe it's been 27 years. I remember when it was still in beta, and how exciting it was to have an open source alternative to Internet Explorer.

Good times!

In the end it'll be the scale of the infrastructure itself that will make the difference.

  127.0.0.1 facebook.com www.facebook.com

Comments URL: https://news.ycombinator.com/item?id=42728773

Points: 29

# Comments: 22