Now if they could just clean up the widespread "duplicate comments" issue so I won't get Deja Vu every time I read one of their blogs, that would be great.
There should be a law against ”We are rebranding the customer experience, and conveniently throwing away most user-generated content”
Proof from when I blogged about it, but they reworded it as soon as it started getting press: https://www.brentozar.com/go/gdpr
That's what they call me, the Wild Brent Ozar.
You make a static copy of all of the HTML, archive the systems that generated them as VM images, and then put a "this is archived static data" at the top of every page.
You also fire every executive who considers deleting documentation for technical products.
I wish that archive.org had captured more of deis.com/blog, there were 232 fantastic articles there, and while I still have them, it seems like it will have to take a great deal more effort to republish them all, than it would have taken to just leave them all online.
This is on-topic because it was some legal process in Microsoft corporation which decided to delete this, too. Not as popular though, so not restored. Check deis.com today, it just redirects to the (admittedly very nice) Azure Kubernetes cloud services home-page. It would have been great if even someone was given notice and permission to tell web.archive.org it was time to crawl this blog, first, so those articles could be referenced in historical context.
It is a jekyll blog, and there are many authors, which is really what makes the copyright situation hard. I am working on contacting everyone to clarify their intention, as it was within MS rights to shut the site down, and it's within any author's rights to ask that their work not be republished, and to my knowledge nobody collected copyright releases at any point, so there is no person who can simply authorize it for everyone.
All of the few Deis team members that I've contacted so far, though, have been very receptive to having their work re-published and excited to hear about Team Hephy, which was created to continue some of the work that had to be left behind by Deis, so that they could better follow the demand.
I want to do it in a way that is thoughtful and fair. It's also hard to justify reposting everything when I don't have a plan to balance it with an equal amount of good quality, new content as well. Maybe I need to bite the bullet and take my SEO points, it will almost certainly drive more traffic to our site.
Do you have an "in" at Archive.org, or would you re-host them somewhere else? I'm more worried that when I repost them, they are still not going to be easy to find, and if they weren't in the history of deis.com, that sure won't make it any easier.
I realized I was definitely going to miss the content when I found this post that was just what I was looking for, about the options for schedulers and what it means to have a monolithic scheduler, back when they were considering whether to rewrite Deis on Kubernetes (they did, it became known as Workflow). It came from the original Deis blog.
I don't know if it looks out of place on the new blog, or if it will make sense to grow this one post at a time, I think I don't like this blog, it was just thrown together one day when I said "we need a place to put a release announcement." I like the material style better than anything I myself could come up with alone, but honestly that's hardly a shining endorsement. Could be much better.
> I put my commas after closing quotation marks, because that's what programmers do.
Your blog is really nice, I went through and found the webcam thing and just wanted to call that out!
Growing up, JoelOnSoftware and Raymond Chen's blog were two great companions for me while surfing the net. Knowing HN, I am pretty sure a lot of you would have grown up with these blogs :-)
Old MSDN link : https://blogs.msdn.microsoft.com/oldnewthing
Are those archivable through archive.org?