I suggest we add a special header to any network request to ivelt.com so that ivelt should be able to identify requests originating from the extension for many different use cases.
Possible use cases includes:
- Temporarily filter/block such requests on server overload.
- Filter such requests from statistics and view counts.
I suggest we add a special header to any network request to ivelt.com so that ivelt should be able to identify requests originating from the extension for many different use cases.
Possible use cases includes: