slederer

We independently scanned 500+ Lovable-deployed apps as part of a larger study of 1,764 vibe-coded apps. The RLS problem is systemic — not a one-off. X% of Lovable apps we tested had wide-open Supabase tables where the anon key could read/write everything. The $6.6B question isn't whether the product is useful, it's whether the security liability of millions of deployed apps becomes a material risk. We published the full breakdown: securityscanner.dev/reports/2026-q2

Great example, MCP servers like that will be needed for every B2B as well as B2C service to give structured access to LLMs and agents. It’s what API’s have been for the past 20 years, but for AI users of those services

Very interesting, where do you see value:

a.) in Kubernetes setups that operate the same software stack, with the ongoing updates and regular releases.

b.) in Kubernetes setups that frequently install new software/diverse software

well, DRM has its necessarily out there. not everything on the internet can be free

Super useful and detailed! I'm keen to see what apple comes up with, and if the same approach for encoding can be followed

While we have CMAF and CENC as standards, politics of companies like Apple just decide to change the cipher mode on DRM for HLS Fairplay and suddenly it's a problem for the whole industry.

Just took 6 years for this bug being addressed :-)

Oh, totally agree, just because we can stream and display the content in HDR, it doesn't mean that the production was really worth it. However, content quality in HDR just increases every day, there is so much competition for great content right now that we will just see more great things. Even normal user generated content can now be created with the iphone and dolby vision, which is really crazy and cool. I think we are just at the beginning, maybe HDR will be the standard in a few years from now

Awesome, initial AV1 support!

Thanks!

For us it was really important to find people that help us along the way, and that definitely includes all our investors, as well as Ycombinator. We're engineers and we definitely learned so much about building a product and a go to market strategy during our time at YCombinator. Having a technology alone is often not enough.

We also raised money form some silicon valley veterans and angels, and I use them as a resource for advice and expertise. One of the was the first CTO of Cisco for example, and I always learn so much in talking with him. Pretty cool to see how one can apply things from those companies also today.

But most importantly, it's the team. you need a great to come to this point, otherwise you struggle quite early. I'm really proud to work with our folks, they really do all the work.

Thx folks, it has been a awesome ride so far. That's only possibly due to the great Bitmovin team. (I'm one of the cofounders)

haha, yes :-)

also check out the quality comparison in the blog post, outperforming today's VP9, HEVC and H.264 video codecs

It would be great to hear your feedback, thoughts, questions to our new API layer. It's like Stripe or Twilio for video streaming use cases.

We are also on Product Hunt today, if you want to check it out there: https://www.producthunt.com/tech ... there is also a 20 GB free plan for people from product hunt ;-)

Best, Stefan

Thx for posting :-)

If you have any question, feel free to ask!

bitmovin (YC S15) is hiring engineers, solution architects, account executives, marketing people and a director sales. Check out the details at https://bitmovin.com/jobs/

Austria and San Francisco, as we have office locations there. I'm splitting my time every month between the two locations.

This stream is just a test stream we did for fun. It's using a Giroptic 360° cam + the bitmovin live encoder + Google Cloud Storage + the bitmovin 360° HTML5 player.

Maybe a more general question: in what programming language and framework you are using or you want to have API clients?

the great thing is that also apple moves now to broadly accepted open standards, which are also compatible to the HTML5 Media Source Extensions, HbbTV, ATSC3.0, etc.

There are a couple of cool P2P companies out there like http://www.streamroot.io/ or https://www.peer5.com/

?

We did tests here and got down to 8 seconds end to end delay, including transcoding. but also HTTP2.0 push will be super interesting here.

That's possible in HTML5 using the MSE, no problem at all.

well done! I like the list of open source tools

No, mplayer doesn't support the needed DRM systems afaik.

don't know if we talk about the same. DRM (Digital Right Management) is just the overall term, there are different systems out there (Widevine Modular, Playready, Fairplay, Primetime, etc.), which are used e.g. by Netflix. So, why do you think DRM is a problem for legitimate users?

there are of the shelf players supporting the EME (see above), thus you can just use one of them. It makes actually sense to seperate the player from the decoding (MSE), as the browser manufacturers might not be able to provide a good implementation of streaming formats. We saw this already with poor implementations of streaming formats/players on TV-sets, so it's good to have specialized and good working player vendors/projects.

hopefully not :-)

the difference between Flash-like plugins and the EME is that the EME is directly build into the browser, with a narrow and focussed use case. This limits als the vulnerability, in contrast to a lot more powerful plugin-systems like Flash or Silverlight or Java.

the EME is widely used by services like Netflix, Hulu, etc., and it's now the first time that DRM is not a pain for developers. So I think the EME helps to simplify a huge problem (=DRM), and make it manageable for the people to use it.