@floating hey, I'd be glad to give a little rundown im first impressions and where I could see areas of improvement in the communication. First and foremost though, your certificate expired today on the site, so that's probably more important :D . Looks like the lets encrypt certbot isn't setup to autorenew the cert maybe. Not too familiar with lets encrypt personally though.
Jordan Muir
@floating
Thanks @afmsavage renewed now, yes auto-renew is a little tricky because it's a wildcard cert -- haven't had time to set it up yet. Thanks for reporting!
Antonio Savage
@afmsavage
ahh, yea stupid wildcard... letsencrypt doesn't allow those for autorenew do they?
I understand that to be honest, having a root domain cert VS a wildcard for free and autorenewing could be used for injustice!!!
Jordan Muir
@floating
I believe it's possible but not out of the box
Antonio Savage
@afmsavage
gotcha, ahh well, looks like its good for 3 months, not too much trouble. Could also setup your certs on the Remme.io certificate manager dapp to remind you when they're up. careful tho they get a little pushy with their advertising and "why you haven't been back!!!" type marketing
Jordan Muir
@floating
I'll give it a look :) thanks
Ultra XBT
@UltraXBT_twitter
Working with Frame on rinkeby but the log-in sidebar disappeared and now won't let me test my Aragon fundraising testnet server. What should I do to log in?
Jordan Muir
@floating
@UltraXBT_twitter Custom networks currently aren't supported but will be included in a future version
RikaSukenik
@RikaSukenik
I'm new to frame and wondering how you handle private keys. Do they ever leave the hardware wallet? If not, how do you gain access to them for signing?
Jordan Muir
@floating
If you're using a hardware wallet Frame will talk to the device directly. When something needs to be signed that data will be sent the device, the device will sign it and send back the signed version to be used by Frame. Frame will never touch the private keys of your hardware device.
RikaSukenik
@RikaSukenik
Cool, thanks!
ligi
@ligi
Hey - I am trying to use fame with peepeth - but I am getting this error in the console:
application-8f7613f90eec18faa40f2b7ddf1584a6b3294f5400eab7b6bf79da8b41bd9ed8.js:124 Uncaught (in promise) TypeError: this.provider.send is not a function at a.send (application-8f7613f90eec18faa40f2b7ddf1584a6b3294f5400eab7b6bf79da8b41bd9ed8.js:124) at n.accounts (application-8f7613f90eec18faa40f2b7ddf1584a6b3294f5400eab7b6bf79da8b41bd9ed8.js:124) at basicWeb3Check (application-8f7613f90eec18faa40f2b7ddf1584a6b3294f5400eab7b6bf79da8b41bd9ed8.js:15) at application-8f7613f90eec18faa40f2b7ddf1584a6b3294f5400eab7b6bf79da8b41bd9ed8.js:15
@ligi Is the peepeth client open source? I should be able to figure out what's going on pretty quickly if I can take a look. Lots of people use Frame every day with many dapps. I only know of one other dapp that was reported to have issues similar to this peepeth issue.
ligi
@ligi
@floating unfortunately peepeth is not open sourcce
Jordan Muir
@floating
The other app that was hitting this issue was also not open source. Would love to get to the bottom of it.
The FOAM issue seems to be different
@ligi One quick solution to it could be resetting all settings and permissions. You can do this by going into the settings (>>>) and mousing over the very bottom.
And click "reset all settings and data"
Jordan Muir
@floating
I just saw your response in the thread. It could have been a bug with a state transition running form source. We only handle/test migrating state schema changes between released versions so it's possible your state was in a bad place from running a previous, transitory version of Frame.
_
ligi
@ligi
ah ok
then feel free to close the issue
thanks for looking into it
just using dev to be able to use a hot-wallet
or is this not needed anymore
regarding peepeth I asked bevan on discord
perhaps he answers
Jordan Muir
@floating
This isn't needed, hot wallets are now supported by in the official releases.
ligi
@ligi
cool
Jordan Muir
@floating
Awesome, yes, I'm happy to help debug with the peepeth team.
ligi
@ligi
peepeth seems to be doing something like this:
window.web3=new Web3(window.web3.currentProvider)
Jordan Muir
@floating
Yeah, that should be ok. Running window.web3.currentProvider.send('eth_accounts').then(console.log) in the console on https://peepeth.com/a/login works fine.
ligi
@ligi
strange - I will try to get bevan here - but he seems to be afk now