Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Is a single point of failure with the URL prefixes not a terrible idea?


From the homepage [1]

> We've been running smoothly since Sept 2022, now measuring over 15 million podcast downloads every month across more than 1600 shows

Knock wood, but OP3 podcast redirecting has never had an single outage since it launched in Sept 2022.

Turns out Cloudflare Workers do a great job at simple http redirecting via their hundreds of edge locations, even during extended outages of the other parts of their stack.

[1] https://op3.dev


Indeed, you have to be really careful and monitor your prefix provider very closely. But it's the best (only?) way to get podcast analytics. Other technologies such as RAD would have been much more resilient, but no one wanted them. :-/


At some point I wanted to embed a monitoring feature within Castopod that would disable op3 in case it fails to respond… but it would add some much plumbing that the monitoring mecanism itself would probably fail long before Op3…


If you look at any major podcast, they likely already have 2 or 3 of these. They're rarely a problem. OP3 in particular is Cloudflare workers IIRC so it's about as reliable as Cloudflare.


Apple will stop following 302 redirections after… 25 of them!




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: