Well that title, I’m guessing, can sum up what happened this morning / yesterday, depending on where you live. A lot of semi-independent things happened last night, which caused chaos here.
Before I start, I must apologize: I’m sorry, this happening right after me asking people to switch to XKit 7 because it’s “less buggy” must have made most of you really mad. Also, sorry that it took so long to fix it, I was sleeping.
Most XKit users are from America, while I’m on the other side of the world.
1. Me: A line of code.
When committing XKit to GitHub, I’ve forgotten about a line of code I had locally that was used to stress-test Paperboy, the little script I have running on XKit servers that brings you the update news. After making a few changes to XKit, I accidentally pushed that code to XKit servers, making every single XKit 7 installed hammer the server, checking for news every time you refresh the page, not every ~2 hours as it should.
2. Me: Recommending XKit 7
I’ve recommended everyone to migrate to XKit 7 last night, which caused a lot of people to upgrade, which caused a spike on server usage.
3. Tumblr: Dashboard Changes
Tumblr, on some accounts, changed the place of reblog buttons on dashboard (I’ve yet to get them, so I’m working on it. It broke One-Click Postage and Wrap Tags, and possibly, Blacklist.) This caused Tumblr Savior and Missing E to stop working, so people started suggesting to others that they use XKit instead, causing people to install XKit, hammering the server even more. I’m guessing some XKit users started resetting XKit because they thought it was a bug, causing XKit hammering it even more.
4. Yahoo: Lack of communication
No, this is not because they’ve bought Tumblr. I just happen to use their Web Hosting service. When the spike happened, Yahoo Webhosting servers thought it was a Denial-of-Service (DoS) attack, and shut down (sub)domains that XKit connects to in order to function. I wasn’t alerted via phone or at least e-mail, so I just kept on sleeping. I’ve talked to them this morning and they’ve told me that it will probably go away after ~24 hours, though people I’ve talked to didn’t know what was going on exactly. If you go to www.studioxenix.com, you might get a “Yahoo 999 Error” instead of the page. Or not, depending on your location, or since the spike is gone.
Summary
In summary, more than half of the blame is on me. Even though it’s a series of events which caused this, it’s that my single line that caused this.
In the end, the little XKit 7 made a horrible first impression on nearly all of you.
I’m deeply sorry and I thank you for your patience and understanding.
Also, If you haven’t updated XKit since yesterday (and running XKit 7.0.3 on Chrome or 7.0.4 on Firefox), please see this post to avoid server problems. Thank you.