[MV3 Beta Bug] Redirect infinite loop with Brave when hitting "purple IPFS button" about ipfs-companion

[whizzzkid]

@BigLep on step 6 you just see a white screen? Is the browser still redirecting? The purple button is shipped by brave, it has its own quirks. Since the purple button redirects to dweb.link instead of staying on what the current url is, companion is seeing this url for the first time. Once the URL is known and rule is added it should work from there. Maybe I can add a manual rule if it's brave.

[lidel]

@BigLep just for the record, what are your settings on brave://settings/ipfs, mainly resolution method? Gateway?

[BigLep]

Here's more info:

brave://settings/ipfs

Here's a screen recording:

Screen.Recording.2023-09-20.at.09.55.08.mov

[whizzzkid]

@BigLep this is a very weird edge case, looks like since you have the Method to resolve IPFS resources set to Gateway, this interferes with companion behaviour. Because brave does not find the Gateway it believes public resolution is required to dweb.link, which gets observed by companion and back to localhost. it's a timing issue I believe, where dweb.link just takes long enough to not be redirected by companion's rule. Because if you directly try to go to https://dweb.link/ipns/explore.ipld.io/ it just resolves fine. It's if the double redirection, first from brave then from companion, which makes it hard. I'm looking into if I can reliably resolve the urls and then reload.