3,597 karma · joined September 18, 2014
[ my public key: https://keybase.io/grahame; my proof: https://keybase.io/grahame/sigs/6dBCi0Tz9tPB9Ol-1vfm3GzBKcerqzjiH57YFG_hpOs ]
I could imagine transferring some lumens to a friend for my share of dinner, but only if my friend is actually going to want lumens. Even if they're a keybase user, they're hardly going to be excited if I transfer them tokens that they are then, themselves, going to find difficult to exchange for goods or services.
If Keybase had to cancel this because all of the people signing up were after the lumens to speculate, maybe they should work on making the currency actually usable and liquid. I'm not interested in speculating; if I could use this to buy something down the supermarket, I'd be very interested.
A really neat example of a design choice which makes a lot of sense for the problem domain in question, but it's also just so awesome that someone could actually see this solution: I can't imagine I would have!
It makes me sad to think that exploration and settlement of the solar system would take with it this kind of thinking, which is dangerously close to rendering the Earth uninhabitable.
The Earth (and Mars...) are, in some sense, closed systems, in that exploitation of resources has a hard limit beyond which we're looking at biosphere collapse, or just plain resource exhaustion.
Maybe we could use space exploration to come up with a different way, and then roll that back into how we live here on Earth.
==> Homebrew has enabled anonymous aggregate formulae and cask analytics.
Read the analytics documentation (and how to opt-out) here:
https://docs.brew.sh/Analytics
Opt-out analytics capture? A bit of a shame it's not opt-in.The fix is to run:
brew analytics offThis seems incredibly rich. If you have a bunch of this kit, and you don't immediately shut it down to apply firmware updates, then HPE wash their hands of the consequences.
This shouldn't have happened. We need international law with some teeth, and better norms for behaviour on the international stage. I absolutely agree that we shouldn't concede to 'of course'.
My bugbear was hitting the siri button by mistake, I swapped that for a 'do not disturb' button which is harmless when pressed.
In Python it's a mess. Some packages specify their deps in setup.py; some in a requirements file, which may or may not be read in by their setup.py. It's not rare to have to have multiple 'pip install' commands to get a working environment, especially when installing fairly boutique extensions to frameworks like Django.
There just isn't a holistic, opinionated approach to specifying dependencies, especially at a project level. Which leaves unexpected upgrades of dependencies (occasionally leading to regressions) as a reality for Python devs.
Pedestrian crossings aren't provided on most roads outside of shopping and business areas - you simply have to cross at a safe point and try to be visible.
I really don't know about the US but I can't imagine it's that different: surely people need to be able to cross the road without being run down as an unclassified object.
Which is fine, and good, except when algorithms keyed only to engagement cause the noisiest, most provocative and potentially divisive content to be amplified.
We have, for a very long time, had laws concerning appropriate behaviour in a town square, or any other 'public' setting: don't incite riots, don't behave violently towards others, be respectful if someone doesn't want to talk and walks away. I support the efforts we're now seeing to bring those norms into online spaces.
Of course, now I'm used to Firefox, and my routine is centred on it - so now when I fire up Chrome, I have the same experience in reverse.
I don't think Firefox advocates should under-play the amount of time and disruption the shift to Firefox involves: but I do think it's worth doing. While there are a few things I miss, Firefox meets all my needs and more.
> We quickly learned, however, that the LLVM linker plugin crashes with a segmentation fault when trying to perform another round of ThinLTO on a module that had already gone through the process.
It sounds like they worked around this, rather than fixing the segfault and putting some error handling in place? Might make it easier for the next bunch of people working in this part of clang.
It's not an issue I really see, but it seems to me that CI infrastructure (Travis, ...) really should have caching proxies in place.