mitch

Your last point is a fair one, but it's also still important to mention because that specific strain of "it's all political, who cares" is what creates tolerance for a lack of transparency and public accountability.

If anyone wants to take this problem seriously, it is also important to understand that even if what is released as an executive summary is deeply flawed, there are real civil servants there still trying to do the best they can with as little as possible. The data is all still published. We, as consumers of journalism, really should be pressuring editors to actually fix the way they uncritically gobble up and report anything that the DoL puts out.

Or, really, reporting on it ourselves and trying to learn and maintain a common set of journalistic ethics.

my personal experience agrees. I think this is what is powering Qanon as well — a deep, wrestling anxiety over the thought that they might have enabled really terrible things happening around them.

Like, for God's sake, this entire thing started with John Podesta supposedly emailing someone about a "cheese pizza," which is a term that is probably, unfortunately, deeply familiar to anyone who had precocious levels of Internet access in the early 2000s.

Basically, it is not a code word that a 70 year old man would use in 2014, in public email, on the campaign trail. In fact, he was ordering, literally, a fucking pizza for his staff.

Yeesh, even beyond the obvious, sticking around after that probably puts a real target on your back for a few years later. I would do the same thing.

Seriously, folks. I was born here, grew up here, and never left. Do not come into the country. Basically, we will all let you know when the coast is clear. 🤷 Until then, please, do not risk it, even if you think you are from a friendly country.

I'm so frustrated. It's happening exactly like everyone said it would. I wanted to think everyone was smarter than this, but this is the Executive equivalent of yelling, "IT'S COMING RIGHT FOR US" right before you kill illegal game.

To be honest, this is just kind of how jobs reports have tended to work since Bush. It is kind of a consequence of both how reporting has failed to really contextualize how jobs reports tend to release in the US, as well as some (arguable) juking of the stats that make it easier to show positive growth in one area and then use the correctance to show the worse numbers.

Basically the Bureau of Labor and Statistics releases a monthly report, and at the beginning of the year it is based more on statistical modeling ("hockey stick growth! I got $5 today to mow the lawn, and $10 the next day to do it. If this rate keeps up, by next year I'll be pulling in a couple billion."), then they issue corrections as the actual data rolls in and either confirms or denies their modeling.

24 hour news (cable and online) got into the habit of basically reporting on the monthly reports like they are gospel, when realistically they are only reliable around November or December. I think the Fed encourages it too because it's quietly one of the levers they can use to inspire foreign investment.

But, it is difficult to adequately describe how seriously the nerds at the BLS take their jobs. They gather and report real-ass data that you can go look at pretty much back to the 60s. This rhythm must be their compromise with the partisan pressures of the executive.

I worked with one of the inventors of IPv6 for a bit of time, and I think knowing Carl really gave me an insight into who IPv6 was invented for, and that's the big, big, big networks — peering groups that connect large swaths of the Internet with other nations' municipal or public infrastructure.

These groups are pushing petabytes of data every hour, and as a result, I think it makes their strategists think VERY big picture. From what I've seen, IPv6 addresses very real logistical problems you only see with IPv4 when you're already dealing with it on a galactic scale. So, I personally have no doubt that IPv6 is necessary and that the theory is sound.

However, this fuckin' half-in/half-out state has become the engine of a manifold of security issues, primarily bc nobody but nerds or industry specialists knows that much about it yet. That has led to rushed, busy, or just plain lazy devs and engineers to either keep IPv6 sockets listening, unguarded, or to just block them outright and redirect traffic to IPv4 anyway.

Imo there's not much to be done besides go forward with IPv6. It's there, it's tested, it's basically ready for primetime in terms of NIC chip support... I just wish it weren't so obtuse to learn. :/

Yeah.

fun fact, the years 1999, 2000, and 2001 were actually all the same year.

oldest baby: "I was totally born in the wrong generation."

my first world problem is that my commute is too short to finish a full podcast 😩😭

that was my experience when I lived in Minneapolis. when there was zero traffic and in the summer, you could get from any place in town to any other place in between 15-20 minutes. snarled traffic was rare because there were so many additional terrestrial roads to take the burnt.

Contrast that with living in Philly, and we have a highway (676) that is so jammed all the time that the exits are measured on signage in fractions.

the funny thing is, every city is always just one more lane away from solving their traffic problems.