Summary
1. Webhooks alone can’t guarantee delivery; a pull‑or‑reconciliation fallback is essential
"Webhooks aren't at-least-once, nor at-most-once, nor are they guaranteed in‑order. Some people build systems to make them more reliable, but if you really care about the data you need to think of a webhook delivery as best‑effort, a bit like UDP." – qlkzy
2. A common, Stripe‑style event‑polling API is needed to avoid vendor lock‑in
"Stripe events API is one of the examples of how to do things properly. And SCROLL is just trying to create a common spec so that everyone offers a stripe‑like event polling api." – weli
3. Cursor semantics and state‑sync issues must be handled explicitly
"How does the provider know what event the cursor you provided refers to?" – weli
These three themes capture the dominant concerns: unreliability of pure webhook pushes, the push for a standardized polling spec, and the practical complexities of cursor management and state reconciliation.