XKit

Extensions that started glitching after today’s update should now be fixed. To get them, you can wait for XKit to update itself, or you can perform an Update All from XKit Control Panel > Other > Update All.

Please note that these updates are for Chrome and Safari users only. I’m working on uploading the updated files to the Firefox server, and they should be available shortly.

Thank you for your patience and support.

I thought Step 1 was done, but apparently Tumblr staff changed the CSS/HTML code once again today, breaking every extension that got fixed yesterday.

I’m working on an update and will make it available as soon as possible, though it might take a little longer this time. Sorry about this.

If you’ve reset your XKit or just installed it, there was a problem with the tutorial where the XKit button, which you need to click to get started, would be unclickable due to the recent design refresh.

It is fixed now, so if you are stuck there, please click here to reset XKit and refresh the dashboard to get started. My apologies for this.

I got the new layout and updated the extensions to work with the new layout, and just wanted to tell you how XKit is going to be updated, in three phases:

1. Fix the extensions on desktop ( ← You are here. )
2. Fix XKit Mobile if anything needs fixing.
3. Write extensions to revert the changes.

To get the updated extensions, you can wait for XKit to update itself, or you can perform an “Update All” from XKit Control Panel > Other > Update All.

Since these changes break the extensions on the old layout, please don’t perform an Update All yet if you are still on the old design.

I’ll be writing extensions to un-stickify the header and restore the margins on the posts as soon as possible.

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.

A recent Tumblr change broke XKit Mobile’s photo loading support, limiting displaying of images to just photosets. 

Apparently, for some reason, Tumblr has completely removed the photo width and height data from the HTML, which is required by XKit to calculate the space for the image (both the actual space the photo takes on your dashboard, and for resizing image for memory usage optimisation.)

I’m still trying to find a workaround, but in the meanwhile I’ve updated XKit Mobile configuration to use a predefined value, which has the side effect of making pictures appear in wrong dimensions.

I will try to find a “configuration file” update, which would be available as soon as possible, but if I can’t, I might have to send a new version of the app to the App Store, which might take 7-8 days.

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

Well, this version didn’t last long.

Apparently a bug in version 7.5.1 for Safari caused XKit to not set proper “header” data while posting data to Tumblr servers, causing some functions like One-Click Postage to not work. This version fixes this problem. 

To upgrade, please visit the XKit website and re-download XKit.

You do not need to uninstall XKit if you are on XKit 7.5.1 (you need to remove it first if you are on 7.4 or below, though.)

My apologies for this.

It took a while, but XKit is now once again available for Safari users.

This version is a near-complete rewrite of the old version, so if you currently have XKit on Safari, please uninstall it before installing this version.

I’ve tested it on Safari 8 and as far as I know there aren’t any Safari-related bugs left, but as always it is provided without any support.

I couldn’t test it on Safari 8 since Apple only allows one version per computer, so I’m not sure if it runs on Safari 7. Please let me know if it runs on Safari 7 or not. (And if it does not, you can re-download the old version here)

To download it, please click here.

What is complete:

The following extensions have been updated (again, with huge thanks to WyohKnott) to work with Tumblr API v2, so they now work correctly on Chrome: 

Notifications+, Read More Now, Post Limit Checker, Blog Tracker, Post Archiver, Profiler, XStats, User Menus+, Tag Replacer, TagViewer, View on Dash.

These updates depend on a change made to XKit Patches, a “hidden” extension, so please use XKit Control Panel > Other > Update All to update the extensions.

What is left to do:

XCloud needs some rewriting to make it compatible with the latest changes, since even though it now supports logging in and downloading your saved data, it still does not support creating a new account or uploading your settings. Audio Downloader also needs a rewrite, but it will be available as soon as possible.

I’m also working on Safari port, and since now XKit has two separate servers, I will be updating the Firefox port to use the server Chrome uses too, to unify the code.

A personal message, again:

I would like to once again point out that, on my personal blog, I’ve never made any racist, xenophobic/homophobic/transphobic comments. There was one post I’ve made, which was written shortly after seeing posts like “kill Tumblr staff” in relation to their April Fools prank, and for which, you can find my reply and apology here. (Also includes my response to allegations of racism, transphobia, etc.)

I know this might be futile attempt, especially to those who make stuff up like I’ve made fun of someone’s pronouns, made rape jokes or other behaviour that I would never do to paint me as an evil man hiding behind a “good guy” mask, but I guess it is worth a try since silence (even though this is my 4th post about this) is usually interpreted as accepting the allegations.

And I use “make stuff up”, since there is absolutely nothing on my personal blog that can be even misunderstood as transphobia/homophobia or jokes about rape. Those are completely groundless.

And as always, thank you for reading, and thank you for your support and patience.

XCloud Support

You can now login to XCloud and restore (download) your settings. I’m currently working on synchronising (uploading) your settings and creating a new account, and hopefully it will be up and running in a few days.

API Support

With help from WyohKnott (whom I can not thank enough) XKit can now connect to Tumblr API v2 without a CORS error, which means that extensions that use it, such as Retags now works again.

For it to work, you will need XKit 7.5.1, which is now available on the WebStore. You can wait for Chrome to update it or you can follow the instructions here.

WyohKnott also rewrote some extensions that use API v1 (which XKit can no longer use) so they would use API v2. I will be making available as soon as possible. Please note that some extensions, such as TagViewer currently use API v1, so they might not work for now.

Once again, thank you so much for your support and patience. 

(PS: If you have tried to install XKit recently but got a “Package is invalid” error, it’s my fault: this is why XKit jumped from 7.4.9 to 7.5.1. It should work now, sorry about that.) 

First of all, thank you so much for your patience and support. My inbox is full of nice messages, and a few friends linked me some nice posts about me, which gave me moral boost during this whole ordeal.

Secondly, XKit now (kind of) works on Chrome. It did took a while, since whenever XKit can’t update itself, it starts trying to connect to the servers over and over again, which kind of resembles a DDoS attack. I had to move the servers once again, and switch providers, but it seems like the servers are stable now. So, in a nutshell:

The Good

XKit now installs and works normally on Chrome, and it should also stop complaining about not being able to reach the servers. Extensions that do not require API connections, such as One-Click Reblog/Reply, Blacklist, XInbox, QuickTags, AccessKit and more should also work normally.

The Bad

Extensions that require API connections, such as Reply/TagViewer, Timestamps and Read More Now as well as XCloud does not currently work.

And The Ugly

This whole ordeal has burnt me out completely, and I have a huge project with a very short deadline starting on monday, so it might take a while for me to fix the aforementioned extensions and services. But I will try my very best to fix them as soon as possible.

Once again, I can’t thank you enough for your support and for your patience. Hopefully, XKit will work as it used to in a few weeks.

I’ve been working on this for about 5 hours now, but seems like I’m back to square one again, but this time, since it affects release version of Chrome, things are even worse.

To reiterate, Chrome now forces all connections to be made using HTTPS. To overcome this, I’ve done two things: (1) move all files to a server that supports HTTPS (2) wrote a small “bridge” that connects to a non-HTTPS page and serves it using HTTPS, so XKit can still use Tumblr API (which is required for many extensions, like Timestamps, TagViewer, ReplyViewer and more)

The problem is, Tumblr API does not work with HTTPS. API v1 does not support HTTPS connections, and API v2 does not send a CORS header that allows XKit to use it, hence the need for a “bridge”. But the problem with the bridge is that now my servers need to handle millions of connections per second, which is impossible, hence the server crash.

I’ve pushed XKit 7.4.9, which disables the bridge that is bringing down the server, but it will be a while until everyone gets upgraded to that version so the server can start running properly again.

After that, though, XKit will need a huge rewrite, and I’m not sure if it can have the features it has right now, at least on Chrome. I’m still trying to come up with a workaround for this problem, so if you have any ideas or suggestions, please let me know.

For now, there is absolutely nothing I can do except recommend either uninstalling XKit or switching to Firefox and using it there.

I’m terribly, terribly sorry about this. I will keep you updated.

Thank you for reading, and for your patience and support.

(Short Version: A recent Chrome change now requires me to do either impossible things or drop the majority of XKit features in order to actually work. I’ve tried doing the impossible thing today and failed miserably, crashing the servers, and I’m still searching for a workaround.)

As the latest Chrome version now forces every connection to be over HTTPS on HTTPS pages, it broke XKit this morning. XKit 7.4.8 connects to the new XKit servers with HTTPS support, fixing this problem.

You can wait for Chrome to update XKit automatically, or you can manually update it yourself using the instructions here.

Note that even after installing 7.4.8, some extensions will not work properly until they are updated to support this change, which might take a few days. As far as I know now, only XCloud and Retags are affected by this, but there might be more. You can still make them work by clicking on the shield icon until they are updated. (Except for XCloud, which will require a re-write.) My apologies for this delay.

Thank you for your patience and support.