packetized

Less than 60% of Californians have air conditioners at home, as opposed to 80% of Americans. So, you seem to be missing a comparison to the 47 other states whose AC ownership percentage is strikingly higher.

I have nothing to contribute except that, as a person that generally works with computer systems and writes a bit of software, I can totally imagine someone undertaking this kind of project, and cannot believe that it started with a Ferrari chassis/Pininfarina coach nearly sixty years ago. Jawdroppingly amazed.

B E S U R E T O D R I N K Y O U R O V A L T I N E

just as unsurprisingly, bishop fox points the blame at the BGP protocol instead of at the netops at omantel.

from rfc4277 import bcp as clue

Looks like it was still crossing Market headed south on Van Ness when the light changed from green to yellow and then red. Too much following distance?

https://youtu.be/1Tp6Ubf6mE4?t=1m20s

In my mind, some sort of graphical user interface that would allow you to query data and have the log system return results that are easily parsed. At the very least, have some sort of API that allows you to do this. The /query endpoint exists, but doesn't seem to return anything that's really fundamentally useful from a large-scale perspective.

While super-interesting (and something that I wish I had time to really evaluate against Elasticsearch/Solr), I feel like it's missing one of the most useful things about Loggly/ES/Solr - the ability to quickly visualize log trends. And despite the statement that it's a "distributed and coördination-free log management system for big ol' clusters", I'm confused why you would want a "big ol' cluster" without visualization or field searches more complex (and less computationally expensive) than regexes. Am I missing something?

e: To be fair, I'm not attempting at all to defend Elasticsearch/Solr, just slightly confused about the actual use cases in prod.

Well, he's riding an Origine Axxome 350 fitted with Ultegra, based on the photos - so 105 isn't that far off. Heh.

Well, the difference here is that Google seems to be looking at Golang as the future for their internal tooling currently implemented in Python 2.x, instead of Python 3.x. I'm curious to know how much additional work might be necessary for this to support 3.x, but it doesn't sound like that's part of their use case.

Ah, very good point.

I'd be interested to know how much potential advertising data is collected via these microphones.

Previous discussion: https://news.ycombinator.com/item?id=10562207

The depot is the former Otto building, I believe - seen plenty of Otto tractor cabs pulling off of the Bay Bridge, left on to Harrison, then straight down and into their garage/depot there.

Odd, works on my end in an incog window.

Unrelated: huge fan of your lpeg_patterns & mmdblua work, among others. Many, many thanks - made my life much easier.

Oh, I don't blame the IEEE wholly - but I think that they probably changed tack after realizing that a number of manufacturers were simply not paying the fees to actually be assigned a block of OUIs. I view it as kind of a cudgel to be used against vendors, and end-users (read: netops/sysops) are caught in the middle.

Relevance: The recent discussions[0,1] on the sinking Millennium Tower (and possibly Salesforce East/350 Mission, based on the ESA isometric plots in [1]). The map[2] clearly shows that the corner of Mission & Fremont was once just offshore.

Additionally, as someone who's been lucky enough to live nearby, it's just absolutely cool to be able to 'walk' through history like this in an area that is largely derided as being sterile and faceless.

[0]: https://news.ycombinator.com/item?id=12206158

[1]: https://news.ycombinator.com/item?id=13036377

[2]: http://www.sfgenealogy.com/sf/history/hpshpb_2014.jpg

I'm not sure that you read on the internet. The statistics cited in the article support his points in a fairly well-constructed way. Can you give an example of some specific works of his that you find fault with?

Until fairly recently (in IEEE/OUI terms, ~2012), the distribution has been entirely sequential. FTA:

"I believe IEEE changed their strategy to attempt to purposefully higher the chance of collisions with MAC squatters, to encourage people to register and pay the fee"

Why?

Also of note: you can actually see the buckling of the sidewalk and curbing immediately adjacent to the Millennium Tower. I'll see if I can get a photo to share today. There's certainly quite a bit of heavy construction equipment traveling on Fremont/Mission, but I can't see how it would cause buckling sidewalks.

Interesting that the lead photo[0] also shows Salesforce East (formerly Salesforce Plaza, 350 Mission) also sinking at a similar rate. I'm wondering what all of this will end up meaning for Salesforce Tower (the large hole in the ground to the left of the Millennium Tower), since it's close to topping out and will be one of the two tallest buildings west of the Mississippi River.

[0]: http://www.esa.int/spaceinimages/Images/2016/11/Millennium_T...

Similar to https://github.com/gdestuynder/audisp-json and https://github.com/mozilla/audit-go

I love how none of these charts use 0 as a base for the y-axis. Lies, damned lies, statistics...

If you're upset about the expected operation of a service based on open-source software (github.com/letsencrypt/boulder), then I'd strongly recommend reading the code before use. Additionally:

"I also expect that our Enigma Bridge Cloud HSM service (check our PKI product with hardware key security) can securely control storage and use of the account key to prevent thefts of the keys and their subsequent misuse."

Using this as a way to promote your product and not reading the code first is a serious failure of tradecraft on your part.

Apologies, I stand corrected.

Why is disallowing spoofing not desirable in the first place? What legitimate uses to spoofing can you enumerate? Because I see none in your comment.

Flatly incorrect. The latest and largest attacks are generally UDP reflection attacks, with a smattering of TCP SYN flood & pure L7 attacks thrown in.

I agree with you wholeheartedly on the documentation, but having a full-featured HTTP ReST API from the beginning has been a powerful driver for ES, imho. Depending on your use case, this may or may not matter. Currently, I use/admin both - ES for logs, Solr for actual full-text document search.

Huge fan. Use this nearly daily in my terminal opening screen; nice and quick to tell you where are, net-wise.

Erm, this does not actually seem to work on Centos7, running systemd-219-19.el7_2.13. Even tried it as root inside of a sandbox - nothing.

Incorrect.