HNHacker News
TopNewBestAskShowJobs

Aaron1011

208 karma · joined August 8, 2013

[ my public key: https://keybase.io/aaron1011; my proof: https://keybase.io/aaron1011/sigs/YvPVLODThi-mvDtXbYE2AvypMiaEtx0Uv8DXq0NC758 ]

hnchat:FdoERjfXiD6SKtSlGuck

submissionscomments
Aaron1011··on Interactive Voronoi Diagram Generator with WebGL
From the source:

> 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?

Aaron1011··on Curl doesn’t spew binary anymore
It's perfectly plausible that the user is piping it to a tool which can parse whatever binary format the file is using. Outputting it to the terminal, however, will just result in a mixture of unprintable characters and ANSI escape sequences.
Aaron1011··on Stardust: GPU-Based Visualization Library
What's wrong with d3?
Aaron1011··on Apple’s Guidelines Now Allow Executable Code in Educational Apps and Dev Tools
> Apple’s Guidelines Now Allow Executable Code in Educational Apps and Dev Tools

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.

Aaron1011··on E-cigarettes ‘Potentially as Harmful as Tobacco Cigarettes’
I can't read the full study, as it's behind a paywall - so take this with a grain of salt:

> "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.

Aaron1011··on Five years of IPv6: whither the next five?
> IPv6 will be a huge mess, if I only think about sending emails via IPv6, how should that even work properly?

Can you clarify what you mean by that?

Aaron1011··on UH Researchers Report New, More Efficient Catalyst for Water Splitting
> The catalyst, composed of ferrous metaphosphate grown on a conductive nickel foam platform, is far more efficient than previous catalysts, as well as less expensive to produce.
Aaron1011··on HTTP security headers
> Unfortunately, as of writing, SameSite cookies are available only in Chrome and Opera, so you may want to ignore them for now.

IIRC, the SameSite attribute is simply ignored by unsupported browsers. Is there any downside to setting it?

Aaron1011··on Google and Paint.NET need to stop misleading users (2013)
Exactly the same type of ads are still present at https://www.getpaint.net/
Aaron1011··on A Trick That Hides Censored Websites Inside Cat Videos
Here's the website for Slitheen (the project described in the article): https://crysp.uwaterloo.ca/software/slitheen/
Aaron1011··on “Restoring Internet Freedom” Notice of Proposed Rulemaking [pdf]
Go ahead! Glad to have been of help :)
Aaron1011··on “Restoring Internet Freedom” Notice of Proposed Rulemaking [pdf]
From Page 10:

> 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.

Aaron1011··on Symantec CA Response to Google Proposal and Community Feedback
> The point of the first part of their post is not "we're too big", it's "a move like this would disrupt the lives of an awful lot of people."

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).

Aaron1011··on Symantec CA Response to Google Proposal and Community Feedback
> This cohort is an important constituency that we believe has been under-represented to date in the public commentary that has been posted to the Google and Mozilla boards since large organizations rarely authorize employees to engage in such public discussions, particularly in an area related to security.

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.

Aaron1011··on Status – A Mobile Ethereum OS
Thanks! I had mistakenly thought that Solidity was still the only way to write Etherium programs (other than directly using the bytecode).
Aaron1011··on Status – A Mobile Ethereum OS
> he could have revealed his identity and sued the developers

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.

Aaron1011··on Status – A Mobile Ethereum OS
> you have to look at the full precedent though which is that forks can be used to keep a chain nimble and if you do disagree with where the majority goes you can still use the unaffected chain with others who feel the same

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."

Aaron1011··on Status – A Mobile Ethereum OS
> I doubt anything like it will happen again as even those who were in favor now understand the damaging effects it can have.

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".

Aaron1011··on Status – A Mobile Ethereum OS
> Letting the hacker walk away with millions at that point would have been silly.

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.

Aaron1011··on Show HN: 'Hack' the user cursor
I found that setting the 'cursor' css property to 'none' (in the style for '*') fixed it for me.
Aaron1011··on What is this colored fiber in my chicken?
> Many medicines also cause more harm than they provide help

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?

Aaron1011··on The House just voted to wipe out the FCC’s landmark Internet privacy protections
> not to mention tamper with

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.

Aaron1011··on CIA malware and hacking tools
http://money.cnn.com/2017/03/07/technology/wikileaks-cia-hac...

http://www.msnbc.com/andrea-mitchell-reports/watch/former-ci...

"Completely avoiding"?

Aaron1011··on Cross-Site Request Forgery is dead
> Wouldn't an attacker just use an older browser that doesn't support 'SameSite' to launch a CSRF attack?

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.

Aaron1011··on Update and Build Prep
"We will NOT be shipping root baked into the ROM."

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?

Aaron1011··on Affordable Care
> Preserve their moral objection to killing. It's too valuable to society for us to trample on it.

I can't opt-out of supporting the military with my taxes - how is this any different?

Aaron1011··on First ‘water-wave’ laser created
> The possibility of creating a laser through the interaction of light with water waves has not been examined, Carmon said, mainly due to the huge difference between the low frequency of water waves on the surface of a liquid (approximately 1,000 oscillations per second) and the high frequency of light wave oscillations (1014 oscillations per second).

I think that's a typo - unless the light actually has a frequency of 1khz, or I misunderstood the article.

Aaron1011··on Self-Healing Transistors for Chip-Scale Starships
I didn't get a clear sense of what exactly 'chip-scale' would mean from reading the article - presumably on the order of centimeters?
Aaron1011··on Building a Botnet on ServiceWorkers
IIRC, service workers allow you to intercept all requests made by the page, for the purposes of implementing offline caching.
Aaron1011··on Last.Backend becomes open-source
> Last.Backend provides some benefits for active contributors, via 20% discount for our cloud resources.

That's interesting - this is the first project I've heard of that does something like that.

← PreviousPage 2 of 3Next →