529 karma · joined July 17, 2017
Questions exist around post-and-pre-processing code in folks' Python stacks, with e.g. NumPy and opencv. There's some NumPy to JS transpilers out there, but those aren't feature complete or fully integrated.
Companies like Google now have employees issues with Yubikeys [1].
[1] https://www.yubico.com/resources/reference-customers/google/
They don't have the resources to store files on the cloud, even encrypted, and don't appear to have taken WhatsApp's approach of backing up unencrypted media and messages on user's third-party cloud services like Google Drive and iCloud.
You can mitigate this by having disappearing chats (current longest self-destruct time is 4 weeks), or by going to Settings->Data and Storage->Review Storage and deleting the largest files.
This isn't a great UX design, as users are not informed there is a problem, or how to solve it.
It feels like Linux debugging is stuck in a viscous cycle, since few people are putting the capital into a decent debugger UI, and thus few people are using debugging UIs (and thus using printf debugging, or gdb CLI). Folk might not realise how much better it could be.
Same colleague had some vocal criticism of `gdb` as a debugging tool, and the state of Linux-based debugging tools as a whole, with claims that "Borland's were much better, and Visual Studio (not VS Code) being one of the few development environments with a quality debugger".
I'm not sure how fair that assessment is, I've found `gdb` to be a helpful tool, though I've never used Visual Studio.
I don't follow your logic, could you elaborate? One could say that about other things subject to carbon tax. Like all goods and services, the price is set by how much people are will to pay for it.
"the price people are willing to pay for short-haul flights could just increase, and therefore the airline profits are unaffected." "the price people are willing to pay for aluminium could just increase, and therefore the smelters are unaffected."
They don't really make sense. Carbon taxing would change miner behaviour, because greener energy would be more attractive (by virtue of being cheaper, especially with carbon taxing and reduced fossil fuel subsidies).
The trial was never meant to ascertain if Wright is who he claims to be, since both parties asserted for the purposes of the trial that this was true.
Thus, no cryptographic signatures were required to prove identity.
There are further policies planned in a similar vein.
The number of scenarios where the new variant is engineered are vastly reduced, since it's less likely that this variant is a lab leak.
Other scenarios can still be within the realm of plausibility, but there are fewer of them.
Ofc, it's not good to scale, but that doesn't matter --- it does the job well at small scales.
[1] https://superset.apache.org/docs/databases/google-sheets
It is mostly written in C++ and Python, integrates external libraries like LLVM, OpenCL, CUDA, etc.
Indeed, Amazon have used the Pinkerton detective agency [1] against their employees to root out union activity. For those unfamiliar, the Pinkertons have existed in the US since the 1850s, with a history fraught with violence and questionable ethics, famously the Homestead strike of 1892 [2].
[1] https://www.businessinsider.com/amazon-pinkerton-spies-worke...
[1] https://gist.github.com/wassname/78eeaaad299dc4cddd04e372f20...
Otherwise, given their involvement in the PRISM program [1] I don't see how we can take that canary seriously.
[1] https://en.wikipedia.org/wiki/PRISM_(surveillance_program)
I suppose much like with BitTorrent, the criminal needs will be both good and bad; allows routing around unjust laws (of which there are many), as well as routing around just laws (of which there are many).
It seems that this is their first month in posting --- I spent a minute looking for older scan, before checking the wayback machine.
A good lesson in buyer beware - many NFTs are being made (and sold) by people who don't know what they're doing.
Another quote from Moxie RE IPFS [2]: > another strange phenomenon is that NFTs which host metadata on IPFS often don't use ipfs:// urls, but rather an explicit https IPFS gateway, which isn't fundamentally that different from some random webserver in terms of what clients are capable of enforcing.
[1] https://ipfs.io/
[2] https://twitter.com/moxie/status/1448162369553637376?s=20
That deals with DNS (though how much has it been used?), but what about the layers of the stack?
[1] https://disasterarea.home.blog/2019/07/12/apple-headquarters...
[2] https://twitter.com/richgel999/status/1436934781955190788
We don't have a good frame of reference for how machines might behave with their failures, which means that accidents could be worse than they would be otherwise.
There's a drop-down menu underneath the last-message received timestamp in the list of chats.
The design is open, and you can make your own with commodity parts. People are starting to sell PCBs, and complete devices.
It has its own open software stack, and I hope will have a variety of vendors in the coming years.
Ofc the e-ink patent issues remain, but this goes some of the way to solve things at the e-reader level.
Compared to France, which is so green due to high levels of nuclear, Germany has banned the building, and is compelling the decommissioning of all nuclear plants, with the last ones expected to be shut down in the next couple of years [2].
[1] https://www.electricitymap.org/?lang=en [2] https://www.cleanenergywire.org/factsheets/history-behind-ge...