I’ve been receiving a lot of asks about a new dashboard update. Apparently, last night was just the beginning.

Unfortunately, none of my accounts have access to the update so far, since Tumblr does not roll out updates to all accounts at the same time. I am not sure when I’ll get it, but I’ll be working on an update as soon as that happens.

In the meanwhile, XKit and XKit Mobile might not work properly. I am not sure how big the damage is, so all I can say it that it might take a few hours to a few days to get all the functions of XKit working correctly again.

My apologizes for this, and again, thank you for your patience.

This morning, I had to switch XKit servers to HTTPS because the latest beta versions of Chrome was blocking HTTP requests on HTTPS pages (ie: Tumblr)

And now, it appears that the HTTPS servers are down. I’m trying to move the files to a new server and I’ll be releasing a new version of XKit for Chrome (Firefox users are not affected by this) as soon as it’s possible.

I’m terribly sorry about this. In the meanwhile, please do not reset XKit, as it won’t be able to re-install itself after a reset.

XInbox, Outbox, Timestamps and XKit Patches extensions are now updated to work properly with today’s (invisible) Tumblr changes.

To get the updates, you can wait for XKit to update itself or go to XKit Control Panel > Other > Update All panel. After the update, publishing asks, reblogging posts and timestamps should once again start working.

I’m currently investigating if any other extension is affected by today’s Tumblr update. If, after updating XKit, an extension still does not work, please send me an ask and I will update it as soon as possible.

Thank you for your understanding and patience.

If your XKit went missing after enabling the new “SSL Security” setting from Tumblr, it’s because XKit disables itself automatically on pages served using SSL protocol.

The reason for it is pretty simple: before today’s update, the only Tumblr pages served using SSL was the login and settings pages, and both of those pages contain your e-mail and password, so it was a no-brainer to disable XKit on those pages to protect your privacy.

I’m working on a workaround that will let XKit work on SSL, but still protect your privacy, and an update will be made available as soon as possible. In the meanwhile, if you want to use XKit, unfortunately, you have to turn off that setting. I apologize about this.

PS: SSL does not exactly provide any additional security unless you use a public network such as the Wi-Fi at your local Starbucks or your workplace’s internet connection to use Tumblr. It will not protect you from viruses, it prevents people from snooping on the data your computer sends and receives on public places.

Right now, all XKit servers are down for an unknown reason: xkit.info is not working, and you might have trouble updating/installing XKit, using some of it’s features or even visiting this blog (since some of the theme files are hosted on the same servers).

What is going on is beyond me, since even my web hosting provider’s “service status” website is down. Seems like they are having an outage.

If XKit complains about not being able to update itself and asks for you to reset it, please do not reset it. It will stop asking you once the servers are back up again.

This is beyond me and there is absolutely nothing I can do about it, but please accept my apologizes. Thank you for your patience.

UPDATE: The issue seems to be fixed now.

Once again, if you are using Safari 6.1.1 or 7.0.1, due to changes Apple made, you need to update to XKit 7.3.2 available here.

Just re-download XKit from the link above and restart your browser. Your preferences will be preserved. Please send me an ask only after if you’ve updated to 7.3.2 and the XKit is still not showing up. Thank you!

I’m aware that there is an incompatibility between Safari 7.0.1 and XKit, but I’m afraid I can’t provide any official new release to fix it today.

Update: As I’ve received more than a few messages about the “temporary” update fixing the problem both on 7.0.1 and older versions of Safari, it’s now available as an official download on the XKit website.

If you are having problem with XKit disappearing on Safari, please just re-download XKit from xkit.info/download and restart your browser. Your settings will be preserved.

The XKit servers are completely down. So here is what I believe happened, posting because of my transparency policy:

1. I went to sleep.
2. Because of a spike in the network activity, not sure if legit or a (successful) DoS attack, Yahoo, which provides my webhosting, shut some of the subdomains down to protect the servers (which I believe is completely fair.)
3. XKit, unable to update itself when the time for automatic updates came, started hammering the server again and again hoping it would reach it, caused other subdomains to get shutdown also, and is still doing that.

The last time this happened, I just created a bunch of new subdomains and redirected XKit to use them, but unfortunately, they are now preventing me (or having some technical difficulties) from doing the same, so I don’t know exactly what to do, and still am searching options.

In the meanwhile, if you are getting the popup, just ignore that little bugger and do not reset XKit.

If you did reset XKit, I’m terribly sorry to say this but the only way to access Tumblr on a computer with XKit installed is to temporary disable it. Instructions are available on the FAQ.

Again, I am terribly, terribly sorry about this, and working hard to fix it as soon as possible. Thank you for your patience.

I just woke up, and yes, the XKit servers are down.

I have no idea what is going on, but I’m trying to find the cause and fix it.

In the meanwhile, please do not reset XKit.

I’m terribly sorry about this, and I thank you for your patience.

A recent Tumblr change added an extra layer of security, which broke XInbox. Luckily, I was preparing for this (starting with One-Click Postage, a couple of days ago), so XInbox is now updated to work with the changes.

If you can’t publish asks, go to XKit Control Panel > Other > Update All or wait for XKit to update itself, which might take someplace between 10 minutes to 1.5 hours, so Update All method is recommended.

I’m terribly sorry about this, but there was a problem in 7.3.0 which totally broke XKit on some Safari versions. XKit 7.3.1 is now out and should fix this.

Again, to install, just go to the XKit download page, install it and restart your browser. If the problem continues after updating, please send me an ask. Thank you!

A few people reported and I’ve confirmed that scrolling down on the dashboard, tagged pages, inbox and other pages does not load new posts right now.

This is not related to XKit since I’ve just tried it on a computer that never had XKit installed before, and the problem is present there too.

I don’t know what is going on (all I know is there is an error on the browser console from a script called dashboard.js, which is by Tumblr), and again, it is not related to XKit and there is absolutely nothing I can do about this.

In the meanwhile, you can turn off endless scrolling from Tumblr Settings > Dashboard page.

When you install an extension, it remains on your computer even though it’s been removed from the extension gallery a long time ago, for various reasons. As you know, I hate removing features: that one extension I remove might be the reason you installed XKit, so I can understand if people get mad at the decision.

But I also want people to have a stable XKit they can trust. As I’ve written before, I would rather have 4-5 extensions than 50 extensions that barely work. So after today’s update, XKit will perform a “Spring Cleaning”, removing the extension that no longer work for one reason or another.

The following extensions, if you have them installed, will be removed from your XKit:

1. XIM
2. Filter-By-Type
3. Unreverse

The reason(s) can be found on the notification when you receive it, or this page I’ve created to shed some light on the removals. I’m really, realy sorry about this, and I hope you can understand the decision I’ve had to make. Thank you.

While trying to add a new feature to the backend, I accidentally pushed the wrong update, which broke some of the extensions on the computers that received the update. The update was up for less than 2 minutes, so I don’t think a lot of people received it.

But if you are receiving error messages such as “cannot call method of undefined”, you have two options:

• You can disable XKit, wait for an hour or two and re-enable it. After that, XKit will try to update itself again, and fix the borked update.
• Or, especially if you’ve backed up your data using XCloud, reset XKit by going to www.tumblr.com/xkit_reset. This will, however, delete your preferences and settings such as blacklist and blocked posts.

I’m terribly, terribly sorry about this, it is all my fault since I’ve skipped some of the safety measurements I have to prevent something like this from happening. Thank you for your understanding.