Algo-Redirect Extension for Chrome and Firefox

Redirects URLs from algoexplorer.io and algoscan.app to allo.info.

Security, privacy and permissions

This extension can only interact with algoexplorer.io and algoscan.app. It cannot read your data or interact with any other domains in any way.

It requires permissions to inject code and redirect for the aforementioned domains.

No user data is collected by this extension.

No-monetization pledge

The limited permissions required by the extension make it a reasonably safe choice already, but monetization through data collection, ads or selling the extension are always options available to extension developers.

My pledge to the community:

This extension is provided as a public good utility. It will never be monetized by any means, including but not limited to:

No user data collection
No ads
I will not sell it

Installing

Chrome based browsers

You can install this on Google Chrome and compatible browsers using the Chrome Web Store.

Rating the extension will help discoverability.

Alternatively you can find the compiled extension here.

Mozilla Firefox

You can install this on Mozilla Firefox using the Firefox Browser Addons listing.

Alternatively you can find the compiled extension here.

Supported networks

Algorand Mainnet. Testnet & betanet may be supported in the future.

Supported redirects

Transaction
Transaction Group
Address
Asset
Application
Block

Algoexplorer redirect test links

https://algoexplorer.io/tx/FHUBCP5JDDWPNU2YQFXXX3CCSLEPBM3S2XBSBPCQC3NCVFGO37ZA

https://algoexplorer.io/tx/group/3PZVL8pHLjKdRVAmnNfuTP9sKTjP371u33cffp1CSsE%3D

https://algoexplorer.io/address/JPEGRZ6G4IBZCOC7UV6QZWJ6TENNKRIPENUJTLG5K7PKIKMVTJHUGERARE

https://algoexplorer.io/asset/796425061

https://algoexplorer.io/application/1177117711

https://algoexplorer.io/block/32000000

Algoscan redirect test links

https://algoscan.app/tx/FHUBCP5JDDWPNU2YQFXXX3CCSLEPBM3S2XBSBPCQC3NCVFGO37ZA

https://algoscan.app/tx/group/3PZVL8pHLjKdRVAmnNfuTP9sKTjP371u33cffp1CSsE=

https://algoscan.app/address/JPEGRZ6G4IBZCOC7UV6QZWJ6TENNKRIPENUJTLG5K7PKIKMVTJHUGERARE

https://algoscan.app/asset/796425061

https://algoscan.app/app/1177117711

https://algoscan.app/block/32000000

Implementation Details

Chrome

For algoscan, this uses declarativeNetRequest. Defined in rules_algoscan.json.

The same method is programmed for AlgoExplorer (rules_algoexplorer.json), however the service worker deployed to algoexplorer.io interferes with this redirection method, so a secondary redirection method is injected into algoexplorer.io pages (algoexplorer.js).

Firefox

The Firefox implementation uses the webRequest/webRequestBlocking methods to redirect. I have included the injected scripts for AlgoExplorer. I am not sure they are actually needed, as the service worker interference that I observed in Chrome was not present in Firefox, but I left it in as a fallback.

Why not a single codebase

Cross-browser compatibility in manifest v3 extensions is severely lacking. The following issues prevented reusing the same source code for both extensions:

Firefox considers the host_permission optional
- Leading to a need for a background script to check and request the permissions on installation
The background scripts / service-worker method preferred by Google Chrome is not supported by Firefox
Chrome will deprecate v2 manifest extensions at some point
(v2 and v3) Chrome disallows webRequestBlocking permission unless the extension is whitelisted

Overall it was easier to create a separate v2 manifest version for Firefox.

d13co/algo-redirect