(no title)
bkm
|
3 years ago
Not a cryptophobe, but his rule seems reasonable: 'use it, but you won't get support if you use it for things I don't like'. Certainly better than the 'you may only use this product if you support/disavow $x' emerging trend in 'OSS' README's.
jobigoud|3 years ago
np_tedious|3 years ago
Why would any issue be "about" crypto? Or traditional finance. Or social media. Or recipe websites. Or gardening
I'm not understanding why the content of the website / application would be an important detail of a github issue at all.
closewith|3 years ago
shrimpx|3 years ago
samthecoy|3 years ago
st_goliath|3 years ago
Bruce Perens wrote about this in late 2019[1][2], specifically focusing on the "hippocratic license", proponents of which IIRC at the time attempted to spark a debate if the Open Source definition needs to be changed, to allow discrimination like this.
[1] https://perens.com/2019/10/12/invasion-of-the-ethical-licens...
[2] https://perens.com/2019/09/23/sorry-ms-ehmke-the-hippocratic...
rvz|3 years ago
> I’m aware of efforts to build proof-of-stake models. I’ll care once the total energy consumption of all cryptocurrencies drops to a non-bullshit level.
> I will summarily close issues related to Bitcoin or cryptocurrency in any way.
Have we seen any creator of a deep learning library, take a similar position if not stopping any support for anyone using it for mass surveillance or burning up the planet by using their deep learning library to train it on tons of GPUs in the cloud until the data centres catch fire? I don't think so.
It's business as usual for them as the author is getting upset over PoW systems to taint all of them under the same brush despite many alternatives that are more energy efficient than others.
JD557|3 years ago
1: https://anticapitalist.software/
2: https://github.com/raisely/NoHarm