namecast

9 ms·

31.
by namecast 11y ago
Assuming your house is rentable and there's a liquid market for rentals in your neck of the woods - and that's an untenable assumption. "Property can be rented for profit" and "Your specific property can be rented p
32.
by namecast 11y ago
Neato. Just one minor nitpick: I see two points where vim is invoked but no way to tell what edits were made to the files (though it's easy enough to guess from the filenames). Switch those two out with appropriate sed or echo commands
33.
by namecast 11y ago
FWIW, if you have to look to the Soviets to find favorable counterexamples, that's not a good sign, is it?
34.
by namecast 11y ago
Found the Red Sox fan... ;)
35.
by namecast 11y ago
No, only that the article is being misleading in it's breathless clickbaitiness. The quote is absolutely in line with the article; actually including the quote in the article would have rendered the headline 'Bitcoin dev thinks
36.
by namecast 11y ago
Mike's resolution was apparently to join up with a consortium of banks back in November: http://bravenewcoin.com/news/30-top-banks-and-mike-hearn-hav... Read the article, he was clearly laying the groundwork for t
37.
by namecast 11y ago
Worth reminding people: On August 15th, 2015, Mike Hearn announced Bitcoin XT, and his attempt to fork the blockchain: https://medium.com/faith-and-future/why-is-bitcoin-forking-d... On January 14th, 2016, 5 months lat
38.
by namecast 11y ago
I get why that would jump out immediately and you'd stop reading from there on, but straight after that block of code, from the article: "Now I'm certain that a lot of readers will have something to say about the style or the
39.
by namecast 11y ago
From your profile: https://keybase.io/breakingbits/sigs/DIO92uX_zdSeZEwYeQ74qj1... throws an error. Just FYI.
40.
by namecast 11y ago
Neat idea! Some technical details from clicking through to the github repo for their fork of BIRD, detailing the config and protocol changes you'd need to make for interoperability: Change in BGP Configuration: In each BGP protocol sec
41.
by namecast 11y ago
Etcd (at least up to 2.1, which I'm running now in prod) doesn't bother with niceties like service discovery and failure detection; it's strictly focused on serving as a distributed k/v store. I think that's the big
42.
There is no 'now': Problems with simultaneity in distributed systems(queue.acm.org)
25 points by namecast 11y ago|3 comments
43.
by namecast 11y ago
At that point, you'll need to have multiple regions in play, and some sort of mechanism to direct traffic to regions when one becomes unreachable (for most people on AWS, this will be Route53). Devil's advocate, though: if you&#x2
44.
by namecast 11y ago
> If you back test over the past 20 years then I'm not sure it helps much as the market of 20 years ago didn't really have any of the major market drives of today's markets +1, and I'll add a link that argues that dat
45.
by namecast 11y ago
The paragraph before the one you just quoted: "We Zimbabweans are left shaking our heads, wondering why Americans care more about African animals than about African people." And the paragraph directly after: "And please, don’
46.
by namecast 11y ago
alias c='noglob perl -e '\''shift; $x = eval qq(@ARGV); print $x; printf " 0x%x 0%o %b\n", $x, $x, $x'\'' _' ' "' Quick and easy perl calculator, with octal, decimal
47.
by namecast 11y ago
Or complicit. The message posted sounds like a plea to return the recently departed CEO to power, or am I misreading it?
48.
by namecast 11y ago
+1 for being awesome - but the OP mentioned 'across the Pacific' - if he's got to transfer 10TB to, say, Sydney or Beijing, I'd bet your upstream won't be the limiting factor, it'll be the congested peering por
49.
by namecast 11y ago
I just remembered, GBLX was bought by L3 a few years back - I'm guessing someone has a "tighten up route maps for GBLX ASN" ticket open in their backlog at the Level 3 NOC. The people managing peering for AS 3356 and AS 3549
50.
by namecast 11y ago
Yeah... no. Sorry, but please read what I wrote again. "An extremely small number of people under the proper set of circumstances may potentially benefit from income contingent plans, and then be forgiven after 25 years", is simpl
51.
by namecast 11y ago
Again, worth noting: there is no risk to the taxpayers for the balance of your loan. You cannot discharge student loans through bankruptcy, and the government can garnish your wages, tax refunds, and social security to repay them.
52.
by namecast 11y ago
Worth noting: you cannot default on student loans. The government can and will garnish your wages, tax refunds and social security for them, and you can't discharge them through bankruptcy.
53.
by namecast 11y ago
Do you really believe that it didn't turn into billions over the years? Seriously, add up the billions upon billions we've spent as an industry (in terms of $/KwH delivered to all the datacenters across the world) over the pa
54.
by namecast 11y ago
I actually wouldn't be surprised if it were. "Hey $ATT_EXECUTIVE - see what happened to [Qwest's CEO] Joe Nacchio? Good. Now go splice me some fiber or you'll be joining him."
55.
by namecast 11y ago
Seconded. "Money can't buy happiness, but it can sure chase away the blues". (And the debt collectors and irate landlords, I would add).
56.
by namecast 11y ago
Something I just realized - why is this being handled by the SEC and not the CFTC? Don't prediction markets fall under the CFTC's jurisdiction, e.g. Intrade? I guess given the nature of the prediction market they could have flippe
57.
by namecast 11y ago
Well stated. Cisco's docs go into great detail on this - they've spent a lot of time thinking about how to address the issues in plain ol' BGP with SoBGP (Secure Origin BGP), and they concluded that determining a BGP speaker
58.
by namecast 11y ago
Hmm. How about mixing and matching, like by having a DNS record with a special TXT record syntax, e.g. 'IN TXT "gt=yoursha256hash"'. That way you could find your destination via DNS and verify the hash in the TXT record
59.
by namecast 11y ago
None of my comments are TCP specific, but as I said - at 3 PoPs, you won't see routing weirdness; announcing the same prefix from 70 PoPs will cause the likelihood of route instability to increase. For the case of UDP, hopefully no one
60.
by namecast 11y ago
Depends on who's doing the accepting ;) I actually meant a /48, mea culpa! I'll leave this here: https://labs.ripe.net/Members/dbayer/visibility-of-prefix-le... It's from 2010-ish but still sad

More ›