Cloudflare

Hey <@456226577798135808> what wasn't quite right about the docs you linked? I ran through it with a fresh API token and it worked for me

it worked with `Authentication: Bearer <key>` and without the "required" x-auth-key and x-auth-email headers

https://developers.cloudflare.com/stream/viewing-videos/securing-your-stream/#step-1-call-the-streamkey-endpoint-once-to-obtain-a-key

this one worked for me and returned a pem and a jwk

Ah! I see, gotcha. Appreciate the clarification

Keep an eye out for docs improvements in the near future 🙂

why is `exp` (https://developers.cloudflare.com/stream/viewing-videos/securing-your-stream/#supported-restrictions) clamped to 24 hours? what if I want to grant access for a month

Aye, our usual recommendation is to reissue signed URLs regularly, as necessary. There are various issues with longer lived tokens from an access control perspective.

What use case are you thinking where a user would have access for >24h?

a user fills out a form and then gets emailed a link valid for 30 days to view a video

I don't want to track users or store account information

I just want to send them a link that'll work for a month

if I needed to revoke access, of course this would not work, but I will not ever need to do that.

(Chatting with team, might be a little bit before I have a response)

appreciate it. if you’re interested in “industry context,” Apple requires JWTs to expire within 1 year

perhaps that could be an appropriate length of time, if your team agrees with the use case

it would need to be easy to revoke keys though

just curious if you heard any feedback on this

We're still chatting about it; changing the upper limit isn't a major priority at the moment versus other planned work.

However, while that is the documented limit, it is the case that's more of a policy limit(mainly oriented around preventing issues with churning through signing keys) rather than enforced in code; consider trying a JWT with a longer expiration 😉

I guess I just have to identify the user another way and re-sign?

I'm getting 503 errors when trying to use WHIP/WHEP endpoints. Is it just me? I was in the process of validating E2E encryption of video frames (using the Insertable Stream API). I'm not sure if I upset the server 😬

Can you DM me a live input ID you're using?

Hey <@846615693796835329> we've reverted a bad change that was impacting those endpoints; please do let us know if you run into any further issues

This issue snuck past our usual observability and alerting, we'll be fixing things up in that area to prevent future issues like this

✨  **Two changes to help you build your live video platform or app** ✨ 

**Unlimited live inputs**
https://developers.cloudflare.com/stream/changelog/#create-an-unlimited-number-of-live-inputs

**More accurate bandwidth estimates for live video playback**
https://developers.cloudflare.com/stream/changelog/#more-accurate-bandwidth-estimates-for-live-video-playback

*Lots more to come!*

when will we be able to add a custom domain?

If I disable cloudflare caching, will ToS still appear?

https://developers.cloudflare.com/stream/stream-live/custom-domains/ This is all you can do as of now

At the moment, it may, but if it does, contact support, and they will fix it

If an admin contacts, I can forward the domain.

Do you have a support ticket filed? I can send it up if you do.

I understand that cloudflare does not want a live broadcast, but the workers are already paying their wages.

It was supposed to do that, because previously, the developer platform was not allowed to be used to proxy video. While that is the case now, you may sometimes be flagged, which is why I was asking if you filed a support ticket. If you do so, you should be able to get that restriction removed

If cf-cache shows DYNAMIC why is it getting banned? This is ridiculous.

Millions of users have to open a support ticket for this?

Well, there’s nothing in the terms saying you can serve video with just Workers - and for obvious reasons, DYNAMIC is still using bandwidth and being proxied.

so if we use cloudflare we can't live stream.

With <#893253103695065128> or a storage product, yes - you can stream.

Just proxying any random origin with Workers doesn’t have a 2.8 exemption.