People should absolutely try to break my code as hard as possible and document successes doubts etc...
In terms of trying to game the POE method of /r/GetFairShare with alt accounts there are plenty of people cheating the system already and people should just go look for them and figure out ways to fairly deal with that problem.
They are kind of obvious if you pay attention. I don't know why more people haven't called them out.
Security wise all the crypto at http://fairshare.website is done by http://bitcore.io
Also I'm taking the approach that nothing is secret except your passphrase and temporary reddit session data. Both of which get stored in ram and forgotten as soon as you close tab or refresh the page.
The fairshare.website never even sees any other private data at all.
I have plans for this already, this is why there are flairs on the posts at /r/GetFairShare
Probably gonna use this: https://github.com/green-arrow/ember-cli-c3
Examples: http://c3js.org
If someone can put together some jsfiddles of configs/data for those libs that would speed things up.
Otherwise I'll figure it out eventually.
>Namely, you want something like the OSL, making the IP and derivatives free to use unless they are being used for commercial purposes, in which case a limited license must be purchased using CUBI coin.
This part reminds me of the P2P Production License, which aims to bootstrap the development of a material commons. It also seems like the OP suggests something similar to what the license above seeks to do for the commons could be done with money in order to help get a decentralized UBI off the ground.
Keybase.io attempts to link humans to accounts by allowing you to "get a public key, safely, starting just with someone's social media username(s)."
> For now I want to stick with keys generated from passphrases
With Keybase, I'm using a key generated with a passphrase. If you're interested in trying Keybase, PM me your email address. Or encrypt it right here with my public key!