HNHacker News
TopNewBestAskShowJobs

tjgq

177 karma · joined September 25, 2012

submissionscomments
tjgq··on Rob Pike: Reflections on Window Systems (2008) [video]
Not really "at length", but he goes a bit into why he thinks computation should be decentralized here: http://rob.pike.usesthis.com/
tjgq··on What the Tortoise Said to Achilles (1895)
Not everyone thinks the same way. There are certainly lay persons out there who do not find proofs by contradiction jarring when they come across them for the first time. I remember I was one of them.

But the impression I get from my (possibly biased) sample is that most non-trained people intuitively see proof by contradiction (or any form of nonconstructive proof, really) as a way of "cheating", because it asserts something does or does not exist without actually producing a (counter)example. YMMV, of course.

tjgq··on What the Tortoise Said to Achilles (1895)
> I have to disagree. A trained mathematician understands why a proof is or it not valid, based on a combination of axioms and a logical sequence predicated on axioms, but with no gaps or overlooked assumptions.

First off, to dispel any misunderstanding, I was talking about the process of becoming a mathematician, which you necessarily go through before you can call yourself one.

But even for full-fledged mathematicians, what I'm saying is true to an extent. For instance, although ZFC set theory is usually accepted as the basis for all mathematics, most mathematicians (precisely: those who do not study formal logics or other areas of metamathematics) do not state their results in terms of set theory, but instead write informal proofs that appeal to other established results in their field of study.

That is absolutely not the same as saying that their thinking is fuzzy or sloppy. The fact that I personally do not state (or, even, understand) all the details behind an established theorem X has no bearing on the validity of my proof for a theorem Y that hinges on X being true.

> The Incompleteness Theorems show the degree to which mathematicians expect to know why something is true, and if they cannot, why not.

This is a separate matter. Whether in theory it is possible for you to ascertain whether X is true or not, and whether you fully understand (down to first principles) why X is true before you use it as a stepping stone for other results are different issues.

tjgq··on What the Tortoise Said to Achilles (1895)
To expand a bit further: this is an example of the "rabbit-hole" nature of mathematics. All but the most trivial theorems depend on previous results, and in most cases you cannot realistically follow all the dependencies until you get to the first principles, also known as axioms (and even then, there's the question of which axioms you are willing to accept!)

In order to be able to understand and appreciate mathematical proofs, you have to develop the ability to accept the truthness of a result - and to realize the consequences of it being true - even though you do not yet understand why it is true. You have to learn to accept the ensuing confusion as a natural state of mind (read [0] if this idea intrigues you).

[0] http://j2kun.svbtle.com/mathematicians-are-chronically-lost-...

tjgq··on Hacking with DNS
Thanks for the background! I didn't know about the original dnscat - that's why I mentioned iodine in case someone was interested in trying this out as a tunneling method.

And thanks also for your thoroughly enjoyable talk.

tjgq··on What the Tortoise Said to Achilles (1895)
> 2. If it's not prime, it has divisors. This proof claims it must include divisors that are prime but are not among those we started with. <-- THIS IS THE BIT I DON'T GET

This step of the proof invokes the Fundamental Theorem of Arithmetic [0]: the statement that every natural number can be expressed as a unique product of primes (uniqueness isn't the important bit here, just the fact that such a factorization exists).

So you need to accept the Fundamental Theorem of Arithmetic as true before you can fully understand this proof.

[0] http://en.wikipedia.org/wiki/Fundamental_theorem_of_arithmet...

tjgq··on What the Tortoise Said to Achilles (1895)
The overall structure of the proof is not by contradiction, but one of the steps is. The Wikipedia article calls this out, right after the sentence you quoted.
tjgq··on Hacking with DNS
Slide 56 onwards (2-way communication over DNS) is basically what Iodine [0] does to defeat firewalls. Quite a cool hack.

[0] http://code.kryo.se/iodine/

tjgq··on What the Tortoise Said to Achilles (1895)
In my humble opinion, proofs by contradiction are not the best examples of mathematical reasoning to be presented to the uninitiated. It has been my experience that people untrained in mathematics find it difficult to (intuitively) accept them as valid.
tjgq··on Constants
What happens when you write

  var x []string = strs ?
If you make a copy of the slice's underlying array and point x to the copy, then you are hiding a potentially expensive allocation behind an apparently innocuous initialization (something that Go tries very hard not to do).

If, instead, you make x point to the same underlying array as strs, then you would have to have immutable slices, which is something that currently does not exist in Go.

I'm not saying neither of the two options is acceptable, but they surely raise issues that go against the grain of the language.

tjgq··on The Internet hit 512K BGP routes today, causing widespread issues
> I was trying to say something like this; I don't think it's true that you don't ever store full addresses in a router (You don't always store the address, sometimes just a prefix), but when you are describing a destination for a block, you would need a full address to finger that gateway, wouldn't you?

Oh, I see your point now. You mean the IPv6 addresses assigned to the nodes that the router forwards the packets through (i.e., the egress nodes), not the destination addresses for those packets.

> Unless the gateway is always at the front of the address block, which I'm sure "they never taught us" in small network design school, at least I believe I've seen routes where the gateway was inside the netblock range or at the end rather than beginning, but again... big networks maybe.

Sure, the gateway address almost never belongs to the address block you are forwarding to. You could be forwarding to a very distant network which isn't directly connected to, nor belongs to the same address block, as your gateway.

I can't tell for sure how routers implement this, but it's safe to say that the total number of egress nodes for a router is much, much smaller than the total number of routes (prefixes). So the obvious optimization is to store the egress node addresses in a lookup table, and only store an index into that table for each route. That way, the fact that you are now forwarding through IPv6- instead of IPv4-addressed gateways does not increase the routing table size (though it does increase the size of the much smaller lookup table).

> What I was trying to say was that when you have the freedom to write bigger ranges by an exponent factor of four like you have if you're the governing bodies of the internet with IPv6 vs IPv4, the expressive part of your network number can be made shorter, at least until your new network begins to approach the size of your old network.

I think you probably meant "at least until the used fraction of your new address space begins to approach the used fraction of your old address space".

> You don't avoid this problem at all, even if you are not storing 128 bits of address there are probably never scenarios where two internets of the same size last longer on the same hardware because IPv6.

I'm not sure I understand the last sentence. The sense in which the IPv6 network will "last longer" in the same hardware is that, for the foreseeable future, you will be able to satisfy most new allocations by choosing an address block that is adjacent to an already existing allocation for the requesting entity. Because the two blocks can then be aggregated into a single prefix, the routing table stays the same size.

tjgq··on Something is amiss with the Interwebs: BGP is a flapping
Apart from the fact that "geographically close" does not always coincide with "network-wise close", that's essentially the principle behind route aggregation as used by routers today.

However, applying it successfully to IPv4 is severy compromised because, due to rampant address space fragmentation during the last years, increasingly longer prefixes (i.e., smaller address blocks) have had to be assigned. IPv6's much larger address space makes it unlikely that the routing table will ever become that fragmented in the foreseeable future.

tjgq··on The Internet hit 512K BGP routes today, causing widespread issues
IPv6 addresses are larger, but routers only store prefixes, not full addresses. And yes, one of the design goals of IPv6 is to reduce address fragmentation, allowing the global routing table to contain fewer and shorter prefixes.

That's only achievable in the long term, though - the currently assigned IPv4 prefixes will have to coexist with the IPv6 ones for a long time.

tjgq··on A world without statistics
> "universal constants" are really just statistically measured values.

Except for the speed of light, interestingly.

tjgq··on A detailed exposé on how the market is rigged from a data-centric approach
I'm curious: can you name an optimization problem you would get that intuition from?
tjgq··on Introducing Pseudo IPv4
First off, good luck trying to implement any kind of decentralized network service when almost nobody has a globally routable address.

Second, if ISPs are willing to keep records of IP-address-to-customer mappings, it's not much of a stretch to add TCP/UDP ports to those records as well.

tjgq··on Why Using .* in Regular Expressions Is Almost Never What You Actually Want
Also read Russ Cox's writeup on implementing regular expressions [0]. Backtracking can be done efficiently; it's just that most regular expression engines have suboptimal implementations for it.

[0] http://swtch.com/~rsc/regexp/regexp1.html

tjgq··on Google updates indexing to execute JavaScript
Google has a system [0] whereby their crawler appends a special parameter to the query string to signal that you should serve a static, "indexable" version.

What I get from this announcement is that their crawler is becoming good enough at executing dynamic pages that having to serve a separate static version may soon become unnecessary.

[0] https://developers.google.com/webmasters/ajax-crawling/docs/...

tjgq··on Level3 is without peer, now what to do?
> There is no such service. Not only does it not exist, it cannot exist. No ISP can provide that. Any independent network on the Internet can start dropping your packets tomorrow for any reason. Including a lazy admin filtering out your entire country. Or due to a copyright agreement. Happens all the time.

The point of net neutrality is that, while ISPs should not be held liable for what other entities in the network do, they shouldn't engage in those practices themselves. In logical terms, that's a perfectly reasonable goal.

tjgq··on The Conflict at the Heart of Open Source
> The kind of software that everyone uses, but that is not a differentiator ("the secret sauce") that makes something stand out.

Doesn't OpenSSL fit this definition perfectly?

tjgq··on Let’s Keep the Internet Dumb
> The author advocates for treating telecom infrastructure like public utilities, but then says that competition is the answer. These are not compatible ideas!

They are compatible if you decouple the infrastructure owner from the service providers, as it happens in other industries.

tjgq··on The Heartbleed Bug
In most systems, this will only work within the same process. Contemporary Unix kernels always allocate zeroed pages to processes, so it's impossible for a process to recover data from another unless there's a kernel bug.
tjgq··on -2000 lines of code
I suppose (s)he means that, if you squash commits, you lose the intermediate states containing code that was later deleted. It's not necessarily bad - squashing is a useful tool to clean up your changes before you merge them in.
tjgq··on -2000 lines of code
Also reminiscent of this quote from Dijkstra [0]:

  My point today is that, if we wish to count lines of code,
  we should not regard them as "lines produced" but as
  "lines spent": the current conventional wisdom is so
  foolish as to book that count on the wrong side of the
  ledger.
[0] http://www.cs.utexas.edu/users/EWD/transcriptions/EWD10xx/EW...
tjgq··on Editing binaries: easier than it sounds
Ah, the memories. I had to thrice reinstall DOS on my childhood computer because of that. I later learned that editing binary files in a text editor wasn't a very bright idea...
tjgq··on Openssl: uses only 32 bytes (256 bit) for key generation
You should read the article to answer your own question in depth. The short version is: on Linux, both /dev/random and /dev/urandom are fed from the same CSPRNG. A CSPRNG only needs to be seeded with a few bits of entropy to generate a whole stream of unpredictable numbers. After the CSPRNG is seeded (at system boot) it no longer matters that you run out of entropy.

Disclaimer: I am not a cryptographer.

tjgq··on Any Android app can read your WhatsApp database
I think the widespread practice of Android applications storing potentially large data in /sdcard dates to a time when /data was extremely small on most phones, and would fill up quite rapidly if you had a large number of applications installed. I don't think that's the case any longer, at least certainly not for an SMS app.
tjgq··on 2014: The year the Americans broke the internet
By that same logic, all websites are European (Swiss? French? German?) because HTTP was invented by Tim Berners-Lee while at CERN.
tjgq··on Whatever happened to the IPv4 address crisis?
It's worth noting that during the transition period the core routers will actually need more memory and processing power, since they'll have to route both IPv6 and IPv4 prefixes for most destinations.
tjgq··on Quentin Tarantino is suing Gawker for posting a link to the script of his film
I think (and the article also suggests) that it is especially hard to explain to people who come from a CS background. We often get too caught up in our own way of seeing the world that does not, for better or worse, correspond to how most people see it.
← PreviousPage 2 of 4Next →