Embed does not work on .be domains

[BarryCarlyon]

Brief description

Embeds don't appear to work on .be domains

How to reproduce

https://cytu.be/twitch-test.html

this example clip embed appears to be correctly configured. But throws a

Twitch embed error message:[FailedAttributeCheck] mandatory requirements were not metDocs: https://dev.twitch.tv/docs/embed/video-and-clips/

Expected behavior

The embed works

Screenshots

Additional context or questions

Original report

https://discuss.dev.twitch.tv/t/embed-api-parent-parameter-not-working-for-specific-domain/26671/

[jbulava]

I cannot test .be domains at the moment, but it looks like there might actually be issues with the embed code. Can we try correcting those first before assume the domain?

The embed URL on https://cytu.be/twitch-test.html has & instead of & before the parent, so this value is not being found. That should fix the misconfiguration. The clip trying to be embedded also does not exist. Let us know and provide an example if the URL fix and using an existing Clip does not work.

[calzoneman]

The embed URL on https://cytu.be/twitch-test.html has & instead of & before the parent, so this value is not being found.

The & in the page source is an XML escape -- technically putting &parent in the page source would be incorrect HTML. However, I have updated it just to be sure, and the result is the same.

The clip trying to be embedded also does not exist.

Updated to one that does exist. Same error.

[calzoneman]

Btw the exact same page source (with the domain changed) works: https://beta.synchtube.me/twitch-test.html

So it does seem to be related to the specific domain name being used.

[jbulava]

Got it, can confirm that the only difference appears to be the .be domain. Inquiring with the embed team.

[calzoneman]

Thanks!

[calzoneman]

Any update on this?

…

On Wed, Jun 24, 2020, 13:04 Jon Bulava ***@***.***> wrote: Got it, can confirm that the only difference appears to be the .be domain. Inquiring with the embed team. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#150 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAC6FCA7HNETGGUHT2WOXB3RYJL6JANCNFSM4OGQZVLQ> .

[calzoneman]

It's now been about 2 weeks and my website embeds are still broken despite folks on this thread indicating my embed parameters are correct, is there a path forward to getting this resolved? @jbulava

[calzoneman]

Hi,

It has now been about 3 weeks. I know we are all busy, but is there any estimate on when this can be fixed? I really don't want to have to migrate everything to new domain name just to make the Twitch API work...

@jbulava

[Edudls]

Hi @jbulava
Is there any update on this? It's been almost 2 months and this is still an open issue.

[jbulava]

Apologies for the long delay to respond to this issue. I wanted to make sure that I understood all of the details talking with other teams and that we had the right information to share. This is not applicable for all .be domains as was mentioned when opening the ticket, but does include cytu.be.

Twitch retains the right to restrict the domains on which its embeddable experiences may be used. Twitch embeds may not be used on websites that have a primary purpose to share or host content that would violate Twitch’s Terms of Service or Community Guidelines. The website above was determined to have such a primary purpose, and we have therefore restricted our embeddable experiences from appearing there.

[calzoneman]

Hi Jon,

Really appreciate you getting back to me. I'd like to follow up on a couple questions if you don't mind:

1. Could you please direct me to the right location to privately discuss with Twitch the specific problem which led to this block and how to remediate it? I assume Twitch would prefer not to discuss that on a public issue tracker, but I would like to follow up on it -- the site in question hosts user-generated content and I never received any specific complaints from Twitch so I'd love to hear about those and resolve them so that those users who are complying with Twitch's terms of service can continue to use it.
2. Is it possible to change the error message that is displayed in this scenario? If I knew from the beginning that my embed was blocked due to a ToS issue, it would have saved a lot of back and forth churn on the developer forum and here.

[jbulava]

Apologies for an extremely long delay to your followup questions. At the time, we did not have a process in place for appeals or remediation. You can now do this by filing a support ticket. Select the "General" category and "Community Guidelines Questions/Appeals" sub-category when submitting. Your request will be routed to someone who can speak to you directly regarding embeds policy.

The confusion around the error message is understandable and has also been brought up for discussion.