About_CORS_Proxy

About "CORS Proxy Settings"

There is no backend for our website, which means:

1. We don't provide any information to you. All tweets are directly fetched from archive.org
2. Your browser will act as a web scraper

However, because archive.org don't attach CORS header, the browser will refuse to fetch from archive.org.

To solve that problem, we provide three options to you.

Note: It's very important to properly configure these settings.

Modify the Settings

Clicking the "menu" button on the right up corner:

Then adjusting the CORS proxy options in the popup menu:

Cloudflare mode

This mode uses the cors proxy set up by the author. It's usable for the most of the time, but cloudflare limiting the total number of requests to 1000 requests/min. So be careful to not reaching the limit, or you'll get tons of 429 errors.

None mode

If you're using the desktop browser, this mode is best for you. This mode will not use any CORS proxy. We recommended to bypass the CORS policy by browser plugins.

For example, if you're a chrome user, installing the Access Control-Allow-Origin - Unblock plugin. Then:

1. Setting the Mode to None

2. Click to enable this plugin

Custom mode

You can provide you own CORS proxy. Setting Mode to Custom, and fill the Proxy URL form with your proxy url.

For example, if you want to use corsproxy.io, you should:

1. Setting the Mode to Custom
2. Filling the Proxy URL with https://corsproxy.io/?