THE EDITOR

Anton H.

Editor of pnclPULSE.

What I cover

On pnclPULSE I cover the drop-alert stream: how a threshold and a window define a drop, what each alert carries, how to keep a server-sent events connection open and how to reconnect it without losing your place.

I write for developers who run alerting bots and market monitors and already know what a price move should trigger in their own system. My pages stay on the stream and leave capacity planning, plan comparisons and calculators to the sister sites.

How I work

Every price, quota, rate limit, endpoint and field name on my pages comes from the vendor's published documentation and carries the date it was checked. When the vendor's own pages disagree, the page says so rather than picking a number.

I do not publish measurements I have not run. Latency, freshness and uptime figures appear only with the method and the date behind them.

Dated notes on the blog are drafted with software assistance under my direction and pass an automated editorial check before publication. The byline is mine and so are the corrections. The editorial policy sets out the rules in full.

Corrections

If a page states a price, a limit or a field that no longer matches the documentation, the page is corrected and its updated date changes. Nothing is corrected silently.

Recent notes are on the blog; the pages they build on are listed in the footer.