• It requires stern discipline to maintain this service.

  • I tried being smart by using Puppeteer to automate this service. My Puppeteer script checks what's new (by checking websites, RSS feeds, and more), BUT I still need to review the "fetched resources". In other words: the curation drains time and energy.
  • I need to look into ways to automate the curation step.

• It's tough to know what the reader's specific OTT interest is. Some readers might be interested in relevant browser updates, others might be interest in changes to technical specifications. I try to make this service as holistic as possible, but I still feel like I'm leaving some things out.

  • Let me know if you know what it is!

• I don't feel like I have the time (/willingness) to promote this specific service. I need to improve the surrounding framework to "bring it to the next level".

Moving forward, I will stop doing "The OTT Changelog" (on a weekly basis). Instead, I'll A) look into doing it on a monthly basis (and with less "sources"|), or B) try to further automate my script. I haven't decided.

I have merged the existing articles into https://ottball.com/ott-changelog/.

• This was not an easy decision. I  learnt a lot, but I feel I need to be smarter about my time.
• Instead, I'll write more original content. (Past examples include https://ottball.com/lazy-loading-video/ and https://ottball.com/hbo-max-dissected/.)
• ❤️ If you enjoyed this service in the past, feel free to support me through my https://ko-fi.com/ottball. (I am saving for a new batch of cookies from my local Chip City! 🍪)