XKit Mobile

XKit Mobile should now login properly. There is no need to update the app from App Store, though you might need to restart the app.

Tweaks

I’ve added 4 new tweaks to the extension under “Post / Post Editor Tweaks”, which allows you to revert the post title font/text size change, swap the editor buttons back, and more.

One-Click Reply

One-Click Reply should now work, except for the tagging (see below)

Getting the updates

You can wait for XKit to update itself, or you can go to XKit Control Panel > Other> Update All to get today’s updates.

QuickTags / Auto-Tagging

The new post editing popup behaves very differently from the old one, and will take a while to reverse engineer (it is very hard to follow obfuscated code after 2 AM) so for now, functions that add/remove/modify tags on the New Post / Edit Post / Reblog Post popups does not work. 

As soon as I figure out what is going on, QuickTags, Auto Tagger and the tagging section of One-Click Reply will return. My apologises for the delay. 

Thank you for your patience and support.

(PS: If you had the chance to mess around with the code and know how to modify tags, please let me know. Thank you.)

There is apparently a new update from Tumblr. An update that brings a brand new text editor, among other small tweaks. Unfortunately, none of my test accounts received the update yet, so I don’t know much about it.

From the message I’ve been getting, I know that it breaks the QuickTags functionality, One-Click Reply extension and and some other Post Editor tweaks. 

I’ve also been receiving messages about XKit Mobile quickly logging users off right after logging in.

Unfortunately, since I don’t have the update yet, there is absolutely nothing I can do about this for now.

As soon as I receive the update, I’ll do my best fix the extensions that were affected by this change and the XKit Mobile app as soon as possible.

Thank you for your patience and support.

XKit version 7.4.5 is now available. This version adds Firefox 35 compatibility and should fix the “too much recursion” error.

To upgrade, all you need to do is just re-download XKit from the download page. Your settings will be preserved.

A recent Tumblr change broke the XKit button on the header. It’s now fixed, and button should appear after XKit updates itself.

This is where I would recommend a Update All from the XKit Control Panel, but since it’s inaccessible right now, unfortunately the only solution is to wait for XKit to update itself.

This might take somewhere between a few minutes to an hour, depending on the last time your XKit checked for updates.

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.

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.

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.

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.)

I’m sorry about the lack of updates: It’s been 2 weeks without an update, so I thought it would be good to tell you what I’m working on.

Safari support: I’ve recently upgraded my laptop to run OS X 10.10 for the latest version of Safari, and I am working on bringing back Safari support. It does require a huge rewrite though, so it will take a while. (No estimates yet, I’m sorry.)

Chrome (Beta) support: As you know, XKit does not work on the beta versions of Chrome because it does not like non-HTTPS connections being made on HTTPS pages (ie: Tumblr) Since my web hosting service does not (properly) support HTTPS, I’m currently trying to move all the files to a VPS. After that, XKit will work properly on Chrome betas (and future versions.)

XKit Mobile: For the last few weeks I’ve been working on XKit Mobile. The next version will have iPhone 6/iOS 8 support, and it has lots of bug fixes and user interface and speed improvements. I’ve also discovered and fixed several bugs that would cause it to crash. Since iPhone 6 and iOS 8 is pretty new and everyone is currently submitting new versions of their apps, the app approval process is very slow, but it will be released as soon as possible.

As always, thank you for your patience and support.

Well, things did not go well today, so it was not a very happy saturday for me.

To recap things in case you’ve missed:

1. I moved things to HTTPS to make sure XKit works on Chrome betas (and future versions of it).
2. Since there are things that XKit accesses that have no HTTPS counterpart, I’ve decided to use a “proxy” that converts HTTP pages to HTTPS. My web hosting provider, not expecting half a million users making 15-30 requests per minute, experienced problems. XKit servers were down for an hour or two.
3. I’ve moved all the files to another web hosting service, and disabled the proxy service. 
4. Apparently their servers/limitations were worse. The same happened, but quicker.
5. I’ve reverted all the changes with XKit 7.4.7 for Chrome.

That means once again XKit does not work on Chrome betas, but at least it now works once again on stable release versions of Chrome.

For now, I have no idea how I’m going to correctly fix this (I have to before this version of Chrome leaves beta state) unless I start renting some very-feature-packed-and-expensive dedicated servers. But I’ll keep you updated.

Please follow the instructions here to make XKit work again.

I’m terribly sorry for this.
Thank you so much for your patience and support.

A while ago I wrote about XKit not working on Chrome Betas, and it would require a huge re-write. XKit 7.4.4 is now available to fix this.

I found a way to make it work by changing how some requests are made to XKit servers, and by using a “proxy” to load HTTP pages (a page on XKit servers that downloads the HTTP pages and serves it using HTTPS).

As a result, not only XKit is now working on Chrome betas, it will no longer display the “broken lock” icon on pages after it is loaded.

Please follow the instructions here (or wait for Chrome to update XKit itself) to get XKit version 7.4.4. (recommended even if you are not using Chrome beta.)

After updating, you might need to update all extensions by going to XKit Control Panel > Other > Update All.

If an extension is not working properly even after updating, please let me know by sending an ask and I’ll fix it as soon as possible. Thank you!

Unfortunately, Chrome decided to block non-HTTPS requests on HTTPS pages on the latest beta version.

This affects XKit in two ways: one is that all XKit servers must support HTTPS now, something that my current web hosting service does not support properly (they do, but it’s so half-baked it doesn’t even work properly) and now I can’t access version 1 of Tumblr API because it doesn’t support HTTPS, meaning I have to re-write a huge portion of XKit (including Timestamps, Blog Tracker, View on Dash, and more).

I had to buy another web hosting service, from a difference provider, to fix the first problem. I’ve requested a SSL certificate, required for HTTPS, and it’s “pending” right now, so I’m not sure when it will be activated. I’ll be transferring all the data to these new servers soon.

For the second problem, I don’t know what to do yet. All I know is that since it’s a huge rewrite, it will take some time.

In the meanwhile, you have two options: use the “stable” version of Chrome, or click on the gray shield on the right side of the address bar to temporarily allow XKit to work whenever it appears.

I’m sorry about this. I’ll keep you updated.

I’ve released a bunch of small updates to No Sidebar to make it open every user link in a new tab instead of sidebar, but the last update (before this one) was a bit too zealous and would open nearly everything in a new tab.

Updating the extension manually (or waiting for it to update itself) should not only fix that problem, but also greatly improve the extension. Sorry about that.

I’ve just pushed updates to XKit Control Panel, Themes+ and Panorama extensions to make them compatible with the latest update.

This is where I would recommend you to go to the control panel to manually update them so you wouldn’t have to wait, but as you know, there isn’t a control panel to go to, yet.

But XKit should automatically update itself, although it might take an hour or two for that to happen. If you have your settings backed up on XCloud, you can go to the XKit reset page to force it to reinstall itself, but as that would delete your settings, it is not recommended.

If you have a problem that started after today’s change, but is not related to the XKit Control Panel, Themes+ or Panorama, please let me know.

Once again, I’m terribly sorry about this, especially about the delay.