player VS revenut-web

vidstack is very light on technical details but starts with a concise intro and a screenshot, as well as relevant links: https://github.com/vidstack/player

payload is well-structured in general: https://github.com/payloadcms/payload

nanostores starts out with an intro and telling code examples, followed by lots of technical details: https://github.com/nanostores/nanostores

Hey everyone!

The motivation for this started with some initial exploration of how native captions are inconcistent and extremely limited with respect to positioning + styling across browsers. In addtion, existing captions work was glued inside player libs and all open-source parsers were ancient (e.g., mozilla/vtt)!

I wanted to modernize it all with newer web APIs such as `fetch` and `ReadableStream` and extend support out to multiple captions formats. I also noticed that a lot of popular players on the web in recent years started adding caption customization options. Turns out accessible captions can be legally enforced!

Do note that accessible captions not only includes sync/timing, but also an adequate set of controls to customize the style of the captions, ensuring they're readable for everyone. You can see an example of this on YouTube when you go to the captions and click customize.

It just seemed silly that probably every single company is internally building this type of lib which is insanely hard to get right. I built this to serve our accessiblity goals at Vidstack[1] where we're working on enabling you to build production-ready player quickly.

It took me about two weeks to build this and honestly there's still a lot of areas that need work but it's a great start. I hope you find it useful. You'll find a lot more helpful information in the repo.

I'll also leave you with this YouTube video where Dan Sparacio beautifully explains the complexities of building accessible media captions on the web at Paramount [2]. This is one of my favourite Demuxed talks. In there case, acessible enough to meet FCC guidelines _Highly_ recommend checking it out to learn more!

[1]: https://github.com/vidstack/player

One side effect my SaaS[1] experienced with card testing is that Stripe's reporting still includes this fraudulent activity as successful which throws off my numbers. For those who can relate, I documented it on GitHub[2] and even developed a mobile app (PWA) that corrects the issue with Stripe's mobile app reporting.

[1] https://last10k.com

[2] https://github.com/hbcondo/revenut-web

Same here, I was using Draw.io but just did a sequence diagram showing a Stripe integration in Mermaid.js on a GitHub readme:

https://github.com/hbcondo/revenut-web#-workflow

But that diagram just renders as code for the same readme via GitHub Pages:

https://revenut.com

I specifically selected Expo / React Native + Typescript for its Authentication library[1] that allowed me to easily integrate Stripe's web login[2]. Expo apps can also be exported as PWAs using Workbox[3] so you could have your app distributed by yourself and have a native version in the app stores

[1] https://docs.expo.dev/develop/authentication/

[2] https://github.com/hbcondo/revenut-web#-authentication

[3] https://developer.chrome.com/docs/workbox/