Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
colmmacc
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
42 ms
·
391.
▲
by
colmmacc
12y ago
Publishing an incomplete copy of your zone seems like a bad idea, an ANY dig at the zone apex is going to retrieve less than 30% of the records (on average) for real-world zones. Negative responses in DNS are cacheable - so you can easily p
392.
▲
by
colmmacc
12y ago
You can use two or more DNS providers, but if you do try not to list more than two name servers from any one provider when you delegate. You should also take care to do the same in your own zones "NS" record set. Some providers do
393.
▲
by
colmmacc
12y ago
Google Public DNS allows anyone to flush its caches ( https://developers.google.com/speed/public-dns/cache ). I've gone ahead and flushed "images.craigslist.org" which may help.
394.
▲
by
colmmacc
12y ago
> Would you help me understand why this isn't closer to the security of a random 6 character password? There are about 80 characters you can type, so a 6 character secret has 262,144,000,000 permutations (80^6) which is about 38 bit
395.
▲
by
colmmacc
12y ago
A significant factor is that privacy addresses won't be released if there are active connections using that address. So if the machine is running something with long lived connections; big downloads, push notifications, IM clients, ssh
396.
▲
by
colmmacc
12y ago
This paper is needlessly hard to read (4 pages in before there's even an explanation!) so first a refresher: A traditional bloom filter sets k bits to 1, using k hash functions to determine which bits. So for input 'i', we mi
397.
▲
by
colmmacc
12y ago
axfrdns is a confusing mis-nomer; the daemon handles all TCP DNS queries too. TinyDNS will truncate any UDP response that doesn't fit in 500 bytes (it also doesn't implement EDNS0), leaving it to be handled by axfrdns. That's
398.
▲
by
colmmacc
12y ago
djbdns is a great read and exemplary code, but I wouldn't use it in production without significant modification; it's far too easy to DOS. TinyDNS and dnscache can each be sped up by about a factor of two by replacing a few of a h
399.
▲
by
colmmacc
12y ago
The handle is very similar to an Irish Hurley; http://upload.wikimedia.org/wikipedia/commons/d/d4/Hurling_B... , which has been around a few hundred years. ( https://www.youtube.com/watch
400.
▲
by
colmmacc
12y ago
'X' always seemed fitting for another, more poetic, reason: The kiss of death (X also represents a kiss). I wonder if it was in the designers mind.
401.
▲
by
colmmacc
12y ago
Unfortunately the TTL settings on top-level zones are less than friendly if your goal is to withstand a DNS provider outage by changing the registration. The TTLs on NS records in the ".com" zone are two days long. So when you log
402.
▲
by
colmmacc
12y ago
whois protection is included; http://aws.amazon.com/about-aws/whats-new/2014/07/31/amazon-... "When you purchase new domains via Route 53, the service will automatically configure a Hosted Zone
403.
▲
by
colmmacc
12y ago
> Even if we assume Twitter and Healthcare.gov serve the same number of users, the engineering and scalability challenges of Twitter far outweigh those of Healthcare.gov. I may have a bias because of my background, but I absolutely don&#
404.
▲
by
colmmacc
12y ago
Another reason I find the comparison to twitter interesting is that both Healthcare.gov and Twitter have no intrinsic value; their innovation and value is that they facilitate and mediate in ways that couldn't have gone before. The rea
405.
▲
by
colmmacc
12y ago
Maybe this is facile, maybe it is illustrative, but I find it interesting to compare HealthCare.gov and Twitter. Twitter has raised over a billion in funding so far, has been going 8 years and has over 3,000 employees. Healthcare.gov is at
406.
▲
by
colmmacc
12y ago
From the article: > a better conceptual model is to treat logs as time-ordered streams At scale it's probably better still to re-think logs as weakly-ordered lossy streams. One form of weak-ordering is the inevitable jitter that co
407.
▲
by
colmmacc
12y ago
I can talk about Ireland, as I've been an election observer there. The way we do it is that ballot boxes are locked and sealed with tamper-evident seals after a polling station has closed. Elections observers; including representatives
408.
▲
by
colmmacc
12y ago
The Dutch group "We don't trust voting computers" [1] hacked up a machine to play chess [2]. It could easily beat a novice. [1] http://wijvertrouwenstemcomputersniet.nl/English [2] https://www.flic
409.
▲
by
colmmacc
12y ago
I don't mean any offense - but your position is not self-consistent. "Showing us the code" does not invalidate "could change it every day to match their whims". For example the entire source code to Linux is public,
410.
▲
by
colmmacc
12y ago
Let's say that the software is published, and the code is audited and it looks ok - it seems to implement all of the intricacies of the transfer system and so on correctly. Then what? What if the operator forgets to use the latest vers
411.
▲
by
colmmacc
12y ago
In that case a simpler fix would be to allow any independent party (within reason) to supply and use their own software and render their own tally. If the parties are mutually distrusting, and their tallies still agree, that can be enough t
412.
▲
by
colmmacc
12y ago
Visibility of the source code is a side-show in electronic voting systems. Even if the source code is published, there is no way to be sure that that is the code that is running on the hardware, or to be certain that the hardware itself has
413.
▲
by
colmmacc
12y ago
It would not be unreasonable for a runtime or VM (like a JVM for example) to use a native library for TLS (performance reasons). It would also not be unreasonable for a VM to use clone() directly, maybe it's part of how it implements i
414.
▲
by
colmmacc
12y ago
http://yarchive.net/comp/linux/getpid_caching.html Reading that thread it seems like direct calls to clone(2) can bypass at least glibc's pid cache (which would likely also break LibreSSL's approach). An
415.
▲
by
colmmacc
12y ago
http://www.cacert.org/ is a similar-ish effort that's been ongoing for quite a long time.
416.
▲
by
colmmacc
12y ago
Anyone with an IPv4 address can use one of several 6to4 gateways to get a whole /48. This gives them access to 2^80 addresses they can originate traffic from.
417.
▲
(Amazon Route 53) A Case Study in Global Fault Isolation
(awsarchitectureblog.com)
1 points
by
colmmacc
12y ago
|
0 comments
418.
▲
by
colmmacc
12y ago
Your browser as the static site generator; http://composedit.net/ - for when even running the static site generator itself is too much effort!
419.
▲
by
colmmacc
12y ago
Route 53 developer here. That's on our roadmap, but in the mean time there is this; https://code.google.com/p/route53d/
420.
▲
by
colmmacc
13y ago
Author here! Well that's embarrassing, you're right about the 7 million number. I've updated the post to correct it. We'll be following up in a later blog post on the numbers we use for Route 53.
More ›