6 Years Building Video Players. 9B Requests. Starting Over
Posted by bolp 4 days ago
Comments
Comment by Dachande663 2 hours ago
- No 2FA support, at all. Support says it's not on their roadmap. Not acceptable in 2026.
- Editing subtitles requires a series of API calls, meaning I had to make a mini editor for our staff to change a word.
- Same with editing anything really. Playback restrictions, glossaries etc. There's no UI for doing it in-app. I understand that the majority of traffic is via the API, but having nothing in-app feels like an omission rather than a choice.
- Every video has multiple keys; uploads, assets, playbacks. And it's a pain moving from one to another.
Overall we use them, but I wouldn't choose to use them again.
Comment by dceddia 1 hour ago
Comment by dixie_land 2 hours ago
The main incentive to have these custom controls I see is anti adblocking
Comment by VladVladikoff 38 minutes ago
Comment by TheAceOfHearts 1 hour ago
Note how the author in detailing their 6-year journey only focuses on their customers without any care for the actual end-users that have to engage with these tools in their final form.
Comment by bflesch 1 hour ago
Current situation around ad-blocking is just symptom of the problem. Users try to extract value from the website they are presented with and websites try to hook users into their platform without chance to leave.
The good thing it is only software
Comment by vee-kay 59 minutes ago
Guess whether their reader base has increased or decreased from their heydays.
Most newspapers or magazines have reduced or stopped their print editions.
Subscription model works only for niche audience, willing to pay for the premium content and premium experience. Rest of the audience will not pay a penny - they are okay to use the site if it is free but with ads, and many users will use some adblocker, but if site refuses to show content if it detects adblocker, they will simply go elsewhere rather than paying for a subscription.