2,429 karma · joined December 1, 2014
/embed/$videoidHaving written that first comment: I was merely wondering aloud – without doing a tour du Google myself – whether such genetic intervention would be possible at all.
I cannot see many problems with sterilizing pest animals, as long as we don't define pests so strictly as to include any nuisance. For example, in cities in The Netherlands, feral pigeons are sterilized when population numbers increase too much. The article about the lanternfly also clearly specifies that small populations of lanternflies do not pose a problem. Any intervention would not need to "eradicate" lanternflies from the earth.
Perhaps you are referring to the suggestion of 'improving' the to strategy to produce non-viable offspring.
What is your own opinion on these matters?
[1] https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4001467/
[2] https://www.popsci.com/mosquitoes-designed-self-destruct
Their low-tech process steps: https://github.com/libresilicon/process/raw/master/process_s...
Lightning talk during the 34c3: https://media.ccc.de/v/34c3-9256-lightning_talks_day_2#t=178...
For an idea of how you could build transistors in your (admittedly pretty large) basement: https://www.youtube.com/watch?v=TrmqZ0hgAXk
HN thread with article about a home-made litographically-fabricated IC: https://news.ycombinator.com/item?id=16955549
As for the actuators: "One of the implementations used pneumatic actuators integrated into an elastomer substrate, whereas the other used coiled shape memory alloy (SMA) actuators integrated onto a fabric substrate."
[1] https://9to5mac.com/2018/05/25/apple-will-reportedly-open-up...
If only they'd bring back a usable server browser, or (god forbid) release the server software for community game servers.
[1] https://www.polygon.com/2018/5/23/17386912/battlefield-5-loo...
[2] https://www.pcgamer.com/battlefield-5-will-have-no-premium-p...
The Netherlands partly has this system, where cannabis sale is 'tolerated' for shops with permits, and where advertisements are forbidden. The system is far from ideal, but I think better than complete (de)criminalization. Additionally, the discussion about drugs is very open thanks to a number of publicly funded organizations. They do not hesitate to also note the positive sides of certain drugs, which all the more encourages a conversation about the responsible use of drugs.
Portugal has gone even further in decriminalizing other (more addictive) substances [1] with fairly good results.
[1] https://www.theguardian.com/news/2017/dec/05/portugals-radic...
Would anyone know how they plan to represent Idemix (or U-Prove) keys and proofs, for example for Hyperledger Indy / Sovrin? There doesn't seem to be anything in the w3id.org JSON-LD schemes, and while wading through the mountains of code of Hyperledger Indy I haven't been able to find any interface to DID documents.
That canary has now died. It did so along with a statement [1][2] that signing a canary every 6 months with an airgapped computer is too impractical, which isn't very plausible as this is a perfectly schedulable event which will take at most an hour for every person involved, twice a year. I suppose they sign their (APT, RPM) releases in the same way (please ask them; seems answerable). Additionally, they were three days late with their statement about moving away from the canary, which is otherwise irresponsibly late for an event that can completely erode trust in them as a security company.
The irony is that their conclusion in [1] that the "canary’s effectiveness as a tool has been questioned, the usage of it at other companies is not consistent, and verifying it and keeping track of it is complicated for users" is spot on; the confusion that can be created about whether the canary is dead or merely deprecated, that after it has died once it cannot be reinstated, and that the only recourse for users is to move away from the service, makes it a pretty useless signal to act upon.
[1] https://spideroak.com/articles/transparency-report/
[2] https://twitter.com/SpiderOak/status/1025488889564327936
[1] https://addons.mozilla.org/en-US/firefox/addon/old-reddit-re...
[2] https://chrome.google.com/webstore/detail/old-reddit-redirec...
It still made me think of it, because in that thread there is a domain expert which lays out careful reasoning for the decision to place constant-time arithmetic inside big/int. Among some other discussion, the main hangup is about the placement of the code, and not any core maintainer is signalling go-ahead with any direction. The issuer author could of course continue to work out the existing strawman proposal, but that risks to be abandoned if the core maintainers turn out to change their mind.
Meanwhile, on March 19 2018 a core maintainer asks if "anybody want to fill out this proposal to see what changes would be required in math/big?", despite that the issue itself has an extensive PR with test suite which reveal most of the necessary changes. (either that or it refers to the Aug 17 2017 comment, but that seems to be exactly bford's proposal with a different public API)
This response is a long one, of which the ending deserves special note:
> I hope this story serves as a warning to others: if you’re interested in making substantial contributions to the Go project, no amount of independent due diligence can compensate for a design that doesn’t originate from the core team.
> Maybe some of you are reading this and thinking to yourself, “well, no duh, Peter, that should be obvious.” Maybe so. My mistake.
It personally made me think of this issue / PR in the Go issue tracker, https://github.com/golang/go/issues/20654, about support for constant time arithmetic with bigints. Currently, operations on bigints in Go may leak secret data via timing channels, because calculations with different values take predictably different time. The maintainers have chosen to specially modify only the P256 curve (but not P224, P384, or P521) to work in constant-time.
The author of the issue has written an extensive (somewhat strawman) PR that includes the constant-time code inside the current implementation of the bigint. That's a choice – for seemingly good reasons laid out in the issue, and of which the author admits that it also could be a separate package – but the rest of the conversation is halted in indecision about how the core team should proceed, without referring back to any of the arguments and reasons the original author has put forth.
I can agree with the first part of your argument, but you're going overboard here by declaring any form of regulation to be totalitarian in nature. Considerations on the interests of companies versus the interests of society as a whole can be made (and are made) in well-functioning democracies. It's continually difficult to strike a balance, and overzealous mistakes may be made or the process might be corrupted. Still, you can't wholly dismiss governmental regulation as the modern world simply functions on it.
What do you mean with the ability of the museums to choose a license for the paintings, and what is the "sub-A4" license you refer to?
[1] https://en.wikipedia.org/wiki/Bridgeman_Art_Library_v._Corel....
One which seems to be heavily influenced by a European and Canadian conference / competition for African entrepreneurs. While there are some photos of 'plastic bricks', the products predominantly seem to be conference demos, especially the mobile app [2].
[1] https://www.facebook.com/gjengemakersltd/
[2] https://play.google.com/store/apps/details?id=com.noriega.g_...
It allows extensions in the form of Lua scripts. There is an extension [2] that opens up a TCP socket which can be used to modify the environment in any language across the network. There is an accompanying Python library [3] that is quite accessible (I had to use the 2to3 tool to seamlessly convert it to Python 3 because of some dependency problem).
I've been trying to get it to work in WebAssembly (some notes here [4]) and maybe connect Blockly / Scratch to it, but unfortunately the WebAssembly shared memory model is postponed due to the Spectre and Meltdown debacle [5].
[2] https://github.com/sprintingkiwi/pycraft_mod
[3] https://github.com/sprintingkiwi/pycraft_lib
[4] https://news.ycombinator.com/item?id=14855176
[5] https://github.com/WebAssembly/meetings/blob/master/2018/CG-...
While the black and white paint does seem to negate a lot of natural contrast human faces have – and on which the recognition of faces is currently based – there seems a lot of information left to recognize specific faces, especially when considering stereovision or even possible pulsed laser reflection / LIDAR based solutions (think long-range iPhone X sensor).
Even if the recognition of an individual within a database of millions yields too many false positives, the set can be further refined by considering other subject metadata, say geolocation or social connections.
While considering this, it's still important to not succumb to privacy nihilism. Not everything is lost, but it's hard to practice that when 'beating' facial recognition tech means "looking like a fucking juggalo" [1].
(oh, and the on-board system still boots even after additional high-pressure cleaning: https://www.youtube.com/watch?v=P5_J5h2UFiY)
Is that correct? (I'm not familiar with the US broadband market)
[1] https://github.com/ipfs/js-ipfs
[2] https://github.com/ipfs-shipyard/ipfs-companion
[3] https://github.com/ipfs-shipyard/ipfs-companion/blob/master/...