You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think it would make sense to have an on/off switch for metamask in the metamask menu, here is why:
Currently, if one has metamask enabled in chrome and connected to the mainnet, and navigates to something like app.augur.net, then the webapp will fail to work properly because it is supposed to run on another net (some testnet), through its own interface (without using a separate local node like metamask, parity, etc.). So in order to use the webapp properly one has to disable metamask completely via the chrome extensions menu. This is sort of inconvenient and a simple on/off switch in the metamask menu would be very useful. In the future I suspect that this problem could arise pretty frequently if dapps become prevalent.
The text was updated successfully, but these errors were encountered:
I think our current plan is to let people specify network + account when logging in to a new site, and maybe we shouldn't inject web3 until that point either.
I think it would make sense to have an on/off switch for metamask in the metamask menu, here is why:
Currently, if one has metamask enabled in chrome and connected to the mainnet, and navigates to something like app.augur.net, then the webapp will fail to work properly because it is supposed to run on another net (some testnet), through its own interface (without using a separate local node like metamask, parity, etc.). So in order to use the webapp properly one has to disable metamask completely via the chrome extensions menu. This is sort of inconvenient and a simple on/off switch in the metamask menu would be very useful. In the future I suspect that this problem could arise pretty frequently if dapps become prevalent.
The text was updated successfully, but these errors were encountered: