> var height = coneRadius / Math.tan(45 * Math.PI / 180.0)
Doesn't that just divide coneRadius by 1? Is there something that I'm missing here?
208 karma · joined August 8, 2013
hnchat:FdoERjfXiD6SKtSlGuck
> var height = coneRadius / Math.tan(45 * Math.PI / 180.0)
Doesn't that just divide coneRadius by 1? Is there something that I'm missing here?
This title is somewhat confusing - it makes it sound as though educational apps and dev tools somehow weren't allowed to execute code before, which doesn't make any sense.
> "potentially as harmful"
That's not 'defensive language', that's rightly acknowledging that a single study isn't enough to determine one way or the other.
> "have as much potential to cause DNA damage"
What's 'unscientific' or 'defensive' about acknowledging that a substance has a certain probability of causing cell damage? Claiming that something 'always' or 'never' causes cell damage, on the other hand, would be unscientific.
Can you clarify what you mean by that?
IIRC, the SameSite attribute is simply ignored by unsupported browsers. Is there any downside to setting it?
> In contrast, Internet service providers do not appear to offer “telecommunications,” i.e., “the transmission, between or among points specified by the user, of information of the user’s choosing, without change in the form or content of the information as sent and received,” to their users. For one, broadband Internet users do not typically specify the “points” between and among which information is sent online. Instead, routing decisions are based on the architecture of the network, not on consumers’ instructions, and consumers are often unaware of where online content is stored. Domain names must be translated into IP addresses (and there is no one-to-one correspondence between the two). Even IP addresses may not specify where information is transmitted to or from because caching servers store and serve popular information to reduce network loads.
This is absurd. Under this logic, telephones "do not offer 'telecommunications'":
* Telephone users never specify the 'specify the “points” between and among which information is sent'. When I call a particular phone number, I can't choose which cell towers are used, or what internal routing is used to connect my call.
* Users are often unaware of 'where [content] is stored'. When I place a call, I don't know if I'm calling a SIP phone, landline, cell phone, or something else entirely.
* If the existence of DNS means that the ISPs don't provide 'telecommunications', then the existence of phone directory services (e.g. Version 411) should mean that telephone companies also don't provide 'telecommunications'.
* IP addresses are logical address, not physical addresses. Neither phone numbers nor IP dresses specify exactly where information will end up - a call could be handled by a phone company-provided voicemail service, or redirected to another phone entirely.
It gets worse. From the same page:
> For another, Internet service providers routinely change the form or content of the information sent over their networks—for example, by using firewalls to block harmful content or using protocol processing to interweave IPv4 networks with IPv6 networks
Again, all of those items are analagous (no pun intended) to similar parts of telephone networks. Phone companies can block calls by scammers (e.g. http://fortune.com/2017/03/24/how-t-mobile-plans-to-block-ph...), and can change the encoding and encapsulation of the call audio as many times as they want to.
The real question is, what effect would doing nothing have on all of those people? If Symantec continues to mis-issue certificates (as they have done repeatedly: https://wiki.mozilla.org/CA:Symantec_Issues), keeping their EV status intact could be much, much worse for them.
> As the blog post states explicitly, there are a lot of use cases where updating a deployed app is very difficult, almost impossible, or cost prohibitive.
As others have pointed out, this change would actually have no effect on the 'complex dependencies' Symantec identified:
* This has absolutely no effect on embedded devices, which are certainly not running Chrome. * Mobile applications that pin certificates shouldn't be affected, since the very fact that they're pinning certificates means they're not using Chrome (there's no way for an app to tell Chrome to pin a specific certificate).
Are these large organizations somehow incapable of putting out official statements regarding CAs? If they're being 'under-represented', it's their own fault for not speaking up.
TheDAO very explicitly states that you can't do this: "Your use of the Software does not, in and of itself, create a legally binding contract in any jurisdiction and does not establish a lawyer-client relationship. Your communication with a non-lawyer will not be subject to the attorney-client privilege and (depending on your jurisdiction) may not be entitled to protection as confidential communication."
Honestly, though, I have absolutely no idea what would happen in a legal case involving 'smart contracts', as I don't think there's any precedent involving treating computer programs as contracts.
That's probably true in general, but the idea of 'code as contract' is supposed to be one of the defining features of Etherium. If the project wants to move away from that, then it should stop pretending that smart contracts are "applications that run exactly as programmed without any possibility of downtime, censorship, fraud or third party interference."
That's one my my main concerns - the hard fork has set an incredibly dangerous precedent. Etherium has shown that it's willing to jettison the idea of 'code as contract' whenever the code ends up doing something 'bad'. In the case of theDAO, 'bad' meant anything from "people losing a lot of money" to "we found a 'bug' in an experiment that still isn't ready".
The issue is, the person wasn't a 'hacker' in any meaningful sense of the word.
Etherium claims to be "a decentralized platform that runs smart contracts: applications that run exactly as programmed without any possibility of downtime, censorship, fraud or third party interference" (from etherium.org). That is, an Etherium program doesn't implement a written contract, it is the contract.
Despite this lofty goal, the core team saw fit to hard-fork the chain because they didn't like how a particular program was executing. The claim that the 'hacker' had 'stolen' funds from theDAO is ridiculous - you can only steal what doesn't belong to you, and ownership of theDAO's Ether is defined by the program itself!
More broadly, the hard-fork seems to imply that an Etherium contract is really made up of two contracts. One contract is the program itself, which explicitly spells out what is and not allowed. The other contract is an implicit understanding of what the program 'should' do, and exists only in the minds of the creators of the contract. The issue arises when this implicit 'contract' is used to override the real contract - flying in the face of how Etherium claims to work.
A much better solution would have been to try to address the underlying issues in Solidity - perhaps requiring future contracts to explicitly allow recursion? I personally question the decision to use a Turing-complete language to express contracts in the first place.
How many is 'many'? 50%? 25%? Or simply 'more than zero'?
> but I will take natural (or at least human incrementally improved over generations and generations) over artificial (top down diet science-ing) any day.
I assume that you would prefer an 'unnatural' vaccination to the 'natural' disease it prevents. If so, which categories of 'natural' do you prefer?
Modifying the SNI hostname in transit is pointless - the client still knows what hostname they sent. Changing the SNI hostname would only cause the server to send back a different certificate, which would immediately be noticed by the client.
With a CSRF attack, it's the victim's browser performing the request - which the attack doesn't have control over.
> I feel like I'm missing something but relying on the browser to protect your site is leaving yourself wide open.
Sites can just add in the 'SameSite' attribute in addition to whatever CSRF mitigation measure they use.
Does anyone know why this is the case? Is there some kind of issue with shipping it rooted + a root manger (SuperSU, Superuser, etc) as CyanogenMod did?
I can't opt-out of supporting the military with my taxes - how is this any different?
I think that's a typo - unless the light actually has a frequency of 1khz, or I misunderstood the article.
That's interesting - this is the first project I've heard of that does something like that.