Théo champion tzvc

Use Case: Media Repurposing for Retail Engagement

Explanation and Benefit: Transform long-form media like documentaries and tutorials into captivating short clips for TikTok and Instagram Reels, enhancing social media presence and engagement.

Practical Case: "I am the Digital Marketing Manager at Leroy Merlin, and I want to leverage our extensive library of DIY tutorials and mini-documentaries to engage with a broader audience on social media. By using Klap, I can easily convert these long videos into engaging short clips perfect for TikTok and Reels, instantly boosting our online visibility and customer engagement."

Use Case: Capitalizing on Short-Form Video Shopping Trends

Explanation and Benefit: Lower the barriers to creating high-quality, engaging short videos for showcasing products and tutorials, tapping into the Gen Z market and viral shopping trends like "TikTok made me buy it."

Practical Case: "I am a Product Marketing Specialist at Decathlon, aiming to capitalize on the v

The first error you encountered was indeed caused by a mismatch in binaries version between Chrome and the WebDriver.

But you've already figured this out, so onto the issue you are facing now:

org.openqa.selenium.NoSuchSessionException: no such session

This error implies that the ChromeDriver was unable to communicate with the existing Browsing Context i.e. Chrome Browser session.

Custom profiles on selenium-webdriver are sometimes fiddly. Try setting the preferences directly.

Here's the updated code for your example:

import {Builder, WebDriver} from 'selenium-webdriver';
import {Options} from "selenium-webdriver/firefox";

const customUA = "Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36";
const options = new Options().setPreference('general.useragent.override', customUA);

As @Grubshka mentionned, it's always a good practice to make your request look like it's coming from a web browser by setting "common" headers. More infos here.

In your case though, it looks like the website you are targeting is rate-limiting based on IP address, and that 25 requests coming from the same IP in 10 minutes is exceeding their limit.

The easiest way to get around this would be to use a [residential proxy](https://brightdata.com/blog/proxy-101/what-is-a-proxy-server?kw=&cpn=14745430544&cam=aw_all_products-all_geos-search_dsa_blog-kw_en-desktop_blog-proxy-101__612826834975&utm_term=&utm_campaign=all_products-all_geos-search_dsa_blog-kw_en-desktop&utm_source=adwords&utm_medium=ppc&utm_content=blog-proxy-101&hsa_acc=1393175403&hsa_cam=14745430544&hsa_grp=136943772153&hsa_ad=612826834975&hsa_src=g&hsa_tgt=dsa-1649388331144&hsa_kw=&hsa_mt=&hsa_net=adwords&hsa_ver=3&cq_src=google_ads&cq_cmp=14745430544&cq_term=&cq_plac=&cq_net=g&cq_plt=gp&

There are a few potential reasons for this error.

One is that the web server is not configured to allow outgoing connections on the port that the web scraper is trying to use (8443).

Another possibility is that the web scraper is trying to connect to a website that is blocking connections from the web server's IP address as part of an anti-scraping protection.

In that case you can try routing your requests through [a proxy server.](https://brightdata.com/blog/proxy-101/what-is-a-proxy-server?kw=&cpn=14745430544&cam=aw_all_products-all_geos-search_dsa_blog-kw_en-desktop_blog-proxy-101__612826834975&utm_term=&utm_campaign=all_products-all_geos-search_dsa_blog-kw_en-desktop&utm_source=adwords&utm_medium=ppc&utm_content=blog-proxy-101&hsa_acc=1393175403&hsa_cam=14745430544&hsa_grp=136943772153&hsa_ad=612826834975&hsa_src=g&hsa_tgt=dsa-1649388331144&hsa_kw=&hsa_mt=&hsa_net=adwords&hsa_ver=3&cq_src=google_ads&cq_cmp=14745430544&cq_term=&cq_plac=&cq_net=g&cq_plt=gp&gclid=Cj0KCQjwkt6aBhDKARIsAAyeLJ3_I8YAAH72WUyacs

If you're getting blocked every 4 requests, it's likely that your IP address is being flagged. One way to work around this is to use a proxy server that will automatically rotate your IP address with each request. This way, you're less likely to get flagged and blocked.

There are a few different ways to do this, but one example is to use residential proxies. These are IP addresses that are associated with real physical locations (homes, businesses, etc.), so they're less likely to be flagged as suspicious.

Some allow scoping to a particular geo region and use "sticky" IPs (use the same IP for a set amount of time)

There are a number of different providers that offer this service, so you'll need to do some research to find one that meets your needs. Once you have a proxy server set up, you can use it in your code just like you would any other proxy.

Here's how it would work in your case:

	async function get(type) {
	const rottentomatoesResponse = await fetch(`https://www.rottentomatoes.com/api/private/v2.0/browse?sortBy=popularity&type=${type}`)
	const json = await rottentomatoesResponse.json()
	const titles = json.results.map(element => {
	return {
	url: element.url,
	title: element.title.split(':')[0]
	}
	});

	window.onload = function load() {
	window.close('','_parent','');
	};