Chrome blocking chaturbate embeds for requiring too many resources!
 

If user uses lastest chrome browser and watch
chaturbates embed (Embeds are seen as ads on chrome.) they will
get this error :

This ad requires too many resources on your device.
That's why Chrome has removed it.


The embeds are no longer loaded!

End of story.

Lol indeed, it goes on for a few seconds then I get an 'ad removed' message

Hope there's a work around.

Wow. That fucks things up a bit.

I have a roboscript embed "Full video mode" and I don't experience that same issue.

But i have experienced this issue with old iframe banner from Cb and Camsoda.

Weird time ahead :Oh crap

Probably it has something to do with the chat.There are constantly posted smileys and pictures (consumes bandwich).
The video stream itself is not a problem.


@Brian mike
Wich parameter can i use with API - Users Online v1
to get full video embed codes?

https://chaturbate.com/affiliates/ap...at=xml&wm=XXXX

V1 seems to be now legacy .

A newer version of this API is available
API - Users Online v2

Did you try v2 ?


To get that " Full video mode" in Roboscript Setting:
Dashboard > RBS CAM MU > configure sites > Choose Which Live Chat > select " interactive mode " and save.

I have on Robo following:
Desktop Image or Live Chat - Live Chat / With Chat;
Mobile Image or Live Chat - Image to Live Chat.

On latest Chrome desktop version working fine, but on mobile, when i click on image to show live chat - i have blank screen.
In console Chrome shows:
Here is CB iframe response headers:

Both v1 and v2 embed data are same.They offer the iframe chat window+viodeostream.
I coded my script to grab just the embed code without editing it
(i don´t manipulate the iframe code like : add &embed_video_only=1 to the iframe url. )



Tested now with &embed_video_only=1 (Full video mode without the chat)

Looks like chrome mobile blocks all ads (Video ads, gifs,banner,embeds)
after it reaches 4mb of data.

No more chaturbate embeded cams.Full video or not.It doesn´t matter since thise embeds are
ads (for google and adblocker).

CB could move promotools like embeds, etcpp to another domain.
It could help.Who knows.

Sorry for your issue can't help on this custom coding stuff. ( I wish I could code my own stuff too ).

Pretty sure someone will jump in to give you a hand.

Good luck :thumbsup

When i use "Full video mode" in Robo - iframe gets blocked on mobile randomly.

Is there a way to disable autoplay so a person has to click on the cam to start the stream? I found out if a chrome user interacts with the iframe (ie clicks on it) it doesn't get blocked.

Not really...
It´s a 4MB restriction for ads.CB embeds are considered as ads.

If CB moves those embed urls / promotools to a different domain (or offers those on another domains)
and you renew your embeds from your DB it should be fine .

Best solution would be :
Promotools could be grabbed from the domain like whitelabel.your-own-site.com
You would embed
<iframe src='whitelabel.your-own-site.com
and not
<iframe src='https://chaturbate.com/in/?tour=12345

Well, tested everything.

So no matter what setting you use - with chat or interactive - blocks come on desktop and mobile randomly. After page refresh all working again.
So reason of this should be some chat messages.
We can use Video Only Mode, but i do not think that way we get registrations.

You can do that by yourself. Just send traffic to whitelabel on Robo. And embeds will be as you want.

Embeds still will come from <iframe src='https://chaturbate.com/in/?tour=
and they are considered as ads (advertisement) for google chrome and adblockers.

Or do i miss something here?

If you interact with the ad it doesnt get blocked.

https://developers.google.com/web/up...-interventions

An ad is considered heavy if the user has not interacted with it (for example, has not tapped or clicked it)

For me embeds come from whitelabel.com if i set to whitelabel.

hmmm.can you show me a sample of your api to get those embeds?

https://www.roboscripts.net/
https://gfy.com/announcements/120700...cam-sites.html

okay.i don´t use roboscripts.

Just want to know how i can use my own whitelabel api.
At moment my projects generates a good amount of traffic just using the v1 embed api.

I use videos on some sites and get plenty of regs, another option would be put a play button over still image from room when users click on play button chaturbate room opens on Chaturbate or whitelabel, that also speeds up your site as well.

So i left for half an hour 10 models desktop and 10 mobile opened on site which is using chaturbate.com iframe, not whitelabel.
No one was blocked.

My CB WL doesn't work in Chrome, it returns an error: "NET::ERR_CERT_COMMON_NAME_INVALID"

Hi. Have the same problem. Have you already found a way, to avoid this? Or adressed it to chaturbate?

If i understand it correct, then a simple "play" button on beginning of the stream could be the solution for it. Right?
Good would be also when the stream could be fetched from an own down, so that not everyone is fetching the stream from the same chaturbate domain, that google cant easily mark it as an advertisement. Right?

Greets

Found a way to detect it (when Chrome closes the iframe thinking it's an ad)

Should come up with a solution and an update next week...

Did anyone find a solution to this ?

It's not just Chaturbate; it happens with other cams too.

:2 cents:

I think there may be a way around it using a white labels so the domains aren't flagged, still testing atm

any issues with xrateduniversity.com ?

Welcome to big tech.

Our "tools" are not ours any more. Virtually every application/app/program is now a marketing venue for the publishers of that tool - and that plays out by censoring any content they choose.

Did you manage to figure this out? Or anyone else?

Read this article on how to bypass it -> https://www.roboscripts.net/set-up-a...es-sub-domain/

For those coming to this thread and seeking a solution, I found that on mobile I have to use a direct embed from Chaturbate, but on PC I can use a whitelabel embed.

Unfortunately still a pain in the ass to get around but at least it works