The Daily Parker

Politics, Weather, Photography, and the Dog

Andrew Sullivan ends The Daily Dish

After 15 years and hundreds of thousands of posts, Sullivan posted the last Dish entry this afternoon:

I hope that this fifteen-year catalog of insights and errors, new truths and old lies, prejudices and loves, jokes and intimacy, prescience and forgetfulness, will not be taken for anything more than it was, or ever could be. I hope we can all simply look back at the journey, and the laughs we had, and the pain we lived through together and the love that sustained us as a team and as a community, as we struggled together to figure out the truth about the world.

And yes, this was a labor above all of love. Love for ideas and debate, love for America, love for my colleagues, and love, in the end, for you.

I sit here not knowing what to write next. And yet, in the end, it is quite simple.

Know hope.

Earlier today he promised to leave the content up permanently.

The Dish has been my favorite blog for probably 10 years. I'm going to miss Sullivan and his team, and their 50-or-so posts a day. I may have more free time, but the Internet won't be the same.

Good luck, Andrew.

Updates

There have been interesting developments in two stories I've mentioned recently:

Otherwise, it's just work work work. But fun work.

Sullivan hanging it up

Andrew Sullivan, one of my favorite bloggers, announced this afternoon he's moving on from blogging:

Why? Two reasons. The first is one I hope anyone can understand: although it has been the most rewarding experience in my writing career, I’ve now been blogging daily for fifteen years straight (well kinda straight). That’s long enough to do any single job. In some ways, it’s as simple as that. There comes a time when you have to move on to new things, shake your world up, or recognize before you crash that burn-out does happen.

The second is that I am saturated in digital life and I want to return to the actual world again. I’m a human being before I am a writer; and a writer before I am a blogger, and although it’s been a joy and a privilege to have helped pioneer a genuinely new form of writing, I yearn for other, older forms. I want to read again, slowly, carefully. I want to absorb a difficult book and walk around in my own thoughts with it for a while. I want to have an idea and let it slowly take shape, rather than be instantly blogged. I want to write long essays that can answer more deeply and subtly the many questions that the Dish years have presented to me. I want to write a book.

It's not clear yet what will happen to the Daily Dish, or to his staffers. I hope that he'll keep the enterprise running.

Daily Parker readers have no such luck: I'm sticking with it for now.

Was Jack Conte's blog post a marketing stunt?

Pomplamoose front-man and Patreon CEO Jack Conte published a blog post last week discussing the economics of touring musicians. I commented here, both as a fan of Conte's and as a supporter of Pomplamoose (including through Patreon).

Within a few days, music critic Bob Lefsetz accused Conte of fabricating his figures, and also of concealing his role with Patreon. Master click-bater Mark Teo piled on, Conte responded, and it's now a standard Internet catfight.

I don't see the ethical problem here. I do see that musicians and other artists who make it, unless they vault over the middle, hard-working part of their career right into multi-millions, often get accused of selling out.

More later, when I'm not about to board a flight...

Daily Parker statistics, first 9 years

The modern Daily Parker started in November 2005. Since then I've posted 4,376 entries, averaging 1.32 per day—though, for the past 48 straight months, I've averaged more than 1.32 per day, with pretty high consistency:

The green line is the 12-month moving average, which I have (alas) brought down most of this year. The red line is the raw mean, which, because of mathematics, has gone up every month since December 2010.

Is there a point to all this? Nope. Not at all. It's just a testament to a habit of writing.

Home for the holidays?

Only a little, it turns out. I'm in the second of three weeks without travel, but I'm back on the road for the first two weeks in December. I even have to miss a concert, which is a bad thing, but it's because I'll be doing a technical diligence in freakin' Paris, which est pas mal. I'm also going to see about taking a quick side-trip to London, which, given the agenda for the diligence and flight schedules back to the U.S., might not make a difference as far as my work schedule goes.

I've also noticed that I keep missing posts on Saturdays. Not sure why; possibly because I've had a lot going on during the week, and Saturdays have been a little more vegetative than expected.

One hundred tech tips for non-techies

Microsoft's Scott Hanselman provides a list:

"Knowing computers" today is more than just knowing Office, or knowing how to attach a file. Today's connected world is way more complex than any of us realize. If you're a techie, you're very likely forgetting how far you've come!

The #1 thing you can do when working with a non-techie is to be empathetic. Put yourself in their shoes. Give them the tools and the base of knowledge they need.

  • Backup everything. Is your entire company on your 10 year old computer’s desktop? Look for Backup options like CrashPlan, DropBox, OneDrive, etc. Literally ANYTHING is better than leaving documents on your computer’s desktop.
  • Learn to use search to find your files. Press the Windows key and just start typing on Windows, or use Spotlight (Command-Spacebar) on Mac.
  • Don’t CC more than 10 of your friends or neighbors. At that point, consider another way to talk to them. Some of your friends may not want their email given to the world. Perhaps this is a time to use BCC (Blind Carbon Copy) so you don't expose everyone's email address to each other?

Techies should read this post to understand what their non-techie friends don't understand. Everyone else should just read it.

Cheating

For more than four years, I have not failed to post an above-average number of entries each day. Since its official launch in November 2005, I've averaged about 1.28 entries per day. As of the last entry, the 39th for September, the average was 1.25. This makes it 1.33.

It's a simple target, really: 40 or 41 per month, depending on the number of days in the month. Since one of the stated purposes of the blog is to encourage daily public writing, meeting this target is almost a requirement.

Someday, probably early in 2015, the average daily rate will exceed 1.32, and I'll have to write 41 or 42 per month to keep the long-term trend positive. And someday I'll slip. But not this month. Oh, no. This month, I'm posting 40.

See you in October.

Lost weekend?

Nah, I've just been super-busy the past few days. Regular posting should resume shortly—depending on how this week in Cleveland goes.

What's going on with the Microsoft Azure blog?

For the last couple of days, I've had trouble getting to Microsoft's Azure blog. From my office in downtown Chicago, clicking the link gives me an error message:

The resource you are looking for has been removed, had its name changed, or is temporarily unavailable.

However, going to the same URL from a virtual machine on Azure takes me to the blog. So what's going on here? It took a little detective work, but I think Microsoft has a configuration error one of a set of geographically-distributed Azure web sites, they don't know about it, and there's no way to tell them.

The first step in diagnosing a problem like this is to see if it's local. Is there something about the network I'm on that prevents me from seeing the website? This is unlikely for a few big reasons: first, when a local network blocks or fails to connect to an outside site, usually nothing at all happens. This is how the Great Firewall of China works, because someone trying to get to a "forbidden" address may get there slowly, normally, or not at all—and it just looks like a glitch. Second, though, the root Azure site is completely accessible. Only the Blog directory has an error message. Finally, the error message is coming from the foreign system. Chrome confirms this; there's a HTTP 200 (OK) response with the content I see.

All right, so the Azure Blog is down. But that doesn't make a lot of sense. Thousands of people read the Azure blog every day; if it were down, surely Microsoft would have noticed, right?

So for my next test, I spun up an Azure Virtual Machine (VM) and tried to connect from there. Bing! No problem. There's the blog.

Now we're onto something. So let's take a look at where my local computer thinks it's going, and where the VM thinks it's going. Here's the nslookup result for my local machine, both from my company's DNS server and from Google's 8.8.8.8 server:

Now here's what the VM sees:

Well, now, that is interesting.

From my local computer, sitting in downtown Chicago, both Google and my company's DNS servers point "azure.microsoft.com" to an Azure web site sitting in the North Central U.S. data center, right here in Chicago. But for the VM, which itself is running in the East U.S. data center in southern Virginia, both Microsoft's and Google's DNS servers point the same domain to an Azure web site also within the East U.S. data center.

It looks like both Microsoft and Google are using geographic load-balancing and some clever routing to return DNS addresses based on where the DNS request comes from. I'd bet if I spun up an Azure VM in the U.S. West data center, both would send me to the Azure blog running out there.

This is what massive load balancing looks like from the outside, by the way. If you've put your systems together correctly, users will go to the nearest servers for your content, and they'll never realize it.

Unfortunately, the North Central U.S. instance of the Microsoft Azure blog is down, has been down for several days, and won't come up again until someone at Microsoft realizes it's down. Also, Microsoft makes it practically impossible to notify them that something is broken. So those of us in Chicago will just have to read about Azure on our Azure VMs until someone in Redmond fixes their broken server. I hope they read my blog.