Categories
Just Shelley

DoS Attacks on Servers

Linode, the company that provides the server I use for my sites has been under constant DoS (Denial-of-Service) attacks for days. Right at this moment, I can access my site and the Linode manager, but the London servers are supposedly all down. Tomorrow, the Dallas servers may get hit, again.

We haven’t heard why there’s such a persistent attack against Linode. The company maintains status updates, but isn’t providing any details.

I’m not leaving Linode. That would be like giving assholes a win. However, access to my sites may be erratic for a bit.

In other news…we didn’t get flooded because of the Missouri rains, though we did lose access to our plumbing capability for a few days. Our back yard was a wet and soggy mess, and our personal river and waterfall, River des Powers, was flowing freely. We were very lucky compared to many surrounding areas, where homes were flooded and freeways and roads shut down. House Member’s co-workers had commutes that hit 3 hours, one-way, last night.

Right now plumbing works, ground is dry, floods are receding, and I can write to my site again. Not a bad way to end 2015.

Happy New Year!

Categories
Just Shelley

New Incarnation

I always make major site changes during the Christmas holiday. Traffic to my sites is at its lowest, and it just seems a good end-of-year task.

I wasn’t quite expecting that the Linode server where my site lives would crash right in the middle of the upgrade, but life isn’t exciting without the little challenges.

I decided to switch from Drupal to WordPress about the time when I decided I no longer had time to pursue PHP and CMS software tweaking, since my tech interests are focused on JavaScript, Node, Internet-of-Things (IoT), mobile, and DIY (microcomputers and microcontrollers). WordPress requires less time when all you want is a site where you can publish your writings.

Categories
Burningbird

Drupal to WordPress…and Donald Trump

I’m migrating this site from Drupal to WordPress. WordPress makes more sense for my needs. And it’s not as complicated to make a static archive of a Drupal site as it used to be.

There, I said it. I’m moving from Drupal to WordPress. It used to be when we made these pronouncements in the past, there’d be great debate about the political implications of choosing one CMS over another. Now, saying we’re moving from one CMS to another is right up there with, “I’m switching from mint flavored toothpaste to bubblegum.”

Drupal fans won’t be offended, and WordPress folk won’t rejoice. It just is. A bit of tedious work, most likely some broken links no one will notice, and what is is, and continues, because we find stories now via Twitter, Facebook, and the like. Or Google, and Google doesn’t care as long as you’re using HTML5 and proper mobile technologies so it doesn’t drop you from search engine results. (“Please, Mr. Google. Please don’t drop me from mobile search results!”)

I’m moving from Drupal to WordPress. No excitement. Well, not unless I mention “Donald Trump”.

Maybe that’s the key.

I’m moving my site from Donald Trump to Bernie Sanders.

Now, I’ve done it. I just offended the Drupal people.

Categories
JavaScript Writing

My latest, and last, book for O’Reilly

I said a few years back that when Node.js released version 1.0, I’d issue an update for my book, Learning Node. Little did I know that waiting for Node.js 1.0 was like waiting for Godot, but in JavaScript.

I did try to do an update on the first edition of Learning Node earlier this year, but the changes were just too significant. So many of the modules I covered are no longer supported, Express 4.0 happened, and then there’s that Node.js/io.js thing, and skipping version 1, altogether. The first edition of Learning Node just can’t be updated, in place. The only solution was a new edition. It’s also a good time to do a new edition: there’s more stability in the development of Node.js, and less personal ownership.

I just hit the half-way mark in Learning Node, the second edition. It should be out for early release in January or so. The finished book should be in the market some time around April/May. We took a different direction with this book: smaller, learner, and staying closer to the core of Node.js. I’m very happy with the direction it’s taking. It’s the Learning Node book I probably should have written, way back in Node.js’s infancy.

Of my books, I finished JavaScript Cookbook, second edition earlier in the year, and I’m happy with it. I like the design of the book, and feel it’s nicely comprehensive. A new author has taken over for the Learning JavaScript series, beginning with Learning JavaScript, third edition. I’ve been chatting with O’Reilly about releasing Practical RDF to the public domain. With the second edition of Learning Node on its way to completion, I feel it’s a good time to ease my way out of writing books for O’Reilly, and finally take the plunge to self-publication.

My first book for O’Reilly was Developing ASP Components, published in 2001. It actually hit the Amazon top 100 bestselling books list for a brief moment. In 15 years, we’ve managed to publish 16 books, and I’m proud of all the work we’ve done together. O’Reilly has been a good publisher, and a good company to work with. They’ve always been supportive of my efforts. I’ve enjoyed working with the people, including, and especially, my long-time editor, and friend, Simon St. Laurent.