It turns out to be a fingerprinting method setting off the shields in brave.
Steemworld and steemconnect have to have that turned off to work, too.
Should that be a concern?
You are viewing a single comment's thread from:
It turns out to be a fingerprinting method setting off the shields in brave.
Steemworld and steemconnect have to have that turned off to work, too.
Should that be a concern?
I turned off shields in Brave and I still couldn't do anything with keychain on steemworld (or even steemconnect for that matter).
As for a concern, not likely, probably just some JS code or something that was blocked.
Shield mostly blocks cookies and javascript stuff. It isn't 100% accurate but is useful 98% of the time.
I like it, so far.
Steemchiller said it was blocking html5.
I just turned off the fingerprint shields and it has worked since, even collecting rewards.
I had to do that to get steemconnect to work, too.
They said they were doing something special with security.
That was questionable, but I had to use them.
I don't have the coder knowledge to know what to argue anyway.
I worry that we will have the first big hack come about because folks trusted the wrong site to input their keys.
A long game there could be years before the day of reckoning.
I haven't gotten to use keychain, yet, no desktop access to sync up this tablet.
Imagine the damage were that to emerge as a long con.
Brave tells me that I have over 600 'https everywhere' upgrades, does https make what I am sending/receiving unreadable to the isp?