The issue is ALMOST solved. It runs when I test it locally. However, when I upload it to github, I get an error "Only secure origins allowed". See https://github.com/mozilla/pdf.js/issues/8767
I'm releasing the payment, but there is still one small issue. To solve the above issue, the Ethereum backup node needs to be HTTPS enabled. I'm happy to just get an EC2 Ethereum node up and running, unless it's easy for you to enable HTTPS?
The issue is ALMOST solved. It runs when I test it locally. However, when I upload it to github, I get an error "Only secure origins allowed". See https://github.com/mozilla/pdf.js/issues/8767
I'm releasing the payment, but there is still one small issue. To solve the above issue, the Ethereum backup node needs to be HTTPS enabled. I'm happy to just get an EC2 Ethereum node up and running, unless it's easy for you to enable HTTPS?
That would be a great solution. If the site does explode with popularity, we can deal with it then. If it is getting to such popularity, it would make finding funding easier, part of which could go to funding the node (and possibly the node maintainer?)
That would be a great solution. If the site does explode with popularity, we can deal with it then. If it is getting to such popularity, it would make finding funding easier, part of which could go to funding the node (and possibly the node maintainer?)
I currently have a geth node that isn't being used for very much that I don't mind donating to the cause - I can do an update this week to set the provider to that if metamascara is on the wrong network.
So the flow would be:
1. Default to injected Web3.
2. If no injected Web3, try Metamascara.
3. If Metamascara is on "network 4", switch to the geth node.
My one note is that if option 3 were to explode with popularity, I don't think I'll be able to afford crazy scaling for option 3 :P
I currently have a geth node that isn't being used for very much that I don't mind donating to the cause - I can do an update this week to set the provider to that if metamascara is on the wrong network.
So the flow would be:
1. Default to injected Web3.
2. If no injected Web3, try Metamascara.
3. If Metamascara is on "network 4", switch to the geth node.
My one note is that if option 3 were to explode with popularity, I don't think I'll be able to afford crazy scaling for option 3 :P
I can use an Infura node, and it loads "current" BP action just fine, but can't load the events. Infura doesn't support events; see:
https://github.com/INFURA/infura/issues/13
https://github.com/INFURA/infura/issues/10
Can you possibly find another way of getting events here? I know toastycoin beta (https://gianlucaschoefer.github.io/) does it through etherscan, but if I recall correctly, the APIs don't exactly match up, so it might not be a simple substitution.
I can use an Infura node, and it loads "current" BP action just fine, but can't load the events. Infura doesn't support events; see:
https://github.com/INFURA/infura/issues/13
https://github.com/INFURA/infura/issues/10
Can you possibly find another way of getting events here? I know toastycoin beta (https://gianlucaschoefer.github.io/) does it through etherscan, but if I recall correctly, the APIs don't exactly match up, so it might not be a simple substitution.
Thanks! It looks like the only "right now" option given the metamascara api is to detect if the user is on metamask's "network 4" and ask the user to go to wallet.metamask.io and switch to the mainnet. Annoying, but at least it gives use to users without the extension. Feel free to keep extending this as well, I'll happily do any updates, especially if the metamask team includes functionality to change to the mainnet.
Thanks! It looks like the only "right now" option given the metamascara api is to detect if the user is on metamask's "network 4" and ask the user to go to wallet.metamask.io and switch to the mainnet. Annoying, but at least it gives use to users without the extension. Feel free to keep extending this as well, I'll happily do any updates, especially if the metamask team includes functionality to change to the mainnet.
Thanks! It looks like the only "right now" option given the metamascara api is to detect if the user is on metamask's "network 4" and ask the user to go to wallet.metamask.io and switch to the mainnet. Annoying, but at least it gives use to users without the extension. Feel free to keep extending this as well, I'll happily do any updates, especially if the metamask team includes functionality to change to the mainnet.
I couldn't find any detailed documentation on the metamascara API, so I opened an issue asking whether there was a way to specify via the api to use the mainnet: https://github.com/MetaMask/mascara/issues/14
I couldn't find any detailed documentation on the metamascara API, so I opened an issue asking whether there was a way to specify via the api to use the mainnet: https://github.com/MetaMask/mascara/issues/14
I just realized why. It's probably because wallet.metamask.io has a setting to switch the network, and the default isn't the mainnet (can't remember what the default was.) I'm at aws re:invent this week, so I probably wont have time to look into the issue until this weekend. There's likely a way to default the provider to the mainnet unless the user has specified another network on wallet.metamask.io
I just realized why. It's probably because wallet.metamask.io has a setting to switch the network, and the default isn't the mainnet (can't remember what the default was.) I'm at aws re:invent this week, so I probably wont have time to look into the issue until this weekend. There's likely a way to default the provider to the mainnet unless the user has specified another network on wallet.metamask.io
The current solution does not allow a new user to view BP data right away. As someone who's never used metamascara before, when I tried out the solution, metamascara seemed to default to a network other than Ropsten or mainnet (network 4, whichever that is).
The ideal solution would be for metamascara to default to the mainnet, but is that possible to specify via the metamascara api? I'd like the worker to look into this, or other simple solutions.
I'd like a timely response from the worker, but the previous deadline can be ignored.
The current solution does not allow a new user to view BP data right away. As someone who's never used metamascara before, when I tried out the solution, metamascara seemed to default to a network other than Ropsten or mainnet (network 4, whichever that is).
The ideal solution would be for metamascara to default to the mainnet, but is that possible to specify via the metamascara api? I'd like the worker to look into this, or other simple solutions.
I'd like a timely response from the worker, but the previous deadline can be ignored.
In response to a comment on the pull request on Github, note that you do **not** need to sign-into metamascara to browse/view all the BPs, the Web3 provider exists whether or not the user has ever even been to wallet.metamask.io. Setting up a wallet at wallet.metamask.io does allow the user to fully use the site without the Metamask extension though.
In response to a comment on the pull request on Github, note that you do **not** need to sign-into metamascara to browse/view all the BPs, the Web3 provider exists whether or not the user has ever even been to wallet.metamask.io. Setting up a wallet at wallet.metamask.io does allow the user to fully use the site without the Metamask extension though.
Pull request created: https://github.com/coinop-logan/coinop-logan.github.io/pull/4 Metamascara works. To use, disable the Metamask extension and create a wallet at wallet.metamask.io.
Pull request created: https://github.com/coinop-logan/coinop-logan.github.io/pull/4 Metamascara works. To use, disable the Metamask extension and create a wallet at wallet.metamask.io.
I'd like to show Toastycoin to people that don't have a web3 provider: mobile users and those who don't have ETH and/or don't want to install Metamask or some other solution.
The simplest way might be to incorporate Metamascara, but I'm not even sure if that can use web3 instead of ethjs (TC currently uses web3). If you do get metamascara to work, you can ignore much of the text below, because metamascara should do all of the below requirements automatically.
The website should show all information Toastycoin provides: a list of Burnable Payments and a way of viewing all information shown on the interact page for any given Payment. Also copy the informational pages and resources. Alert the payer on every page that this is a mirror, and provide a link to Toastycoin, with a warning that they will need "a web3 provider, such as Metamask[linked to the Metamask download]".
When I say the mirror is "passive", I mean that I don't expect any interactive functionality from the mirror, such as committing or creating Payments. I don't care if the server reads directly from ETH or just scrapes Toastycoin, although I suspect the latter would be easiest.
This should be completed at most 1 week after commitment.