XKit

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.

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.

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.

This version brings support for In-Dashboard Blogs (“Sidebar Blogs”): I’ve updated a few extensions, including One-Click Postage and Tag/ReplyViewer to work on the sidebar, but you need this version for them to work.

To get it, you can wait for Chrome to update it, or you can update it manually. After upgrading, make sure to update all extensions from XKit Control Panel > Other > Update All. (Or wait for XKit to update itself.)

It’s still pretty experimental, so please let me know if you experience any problems by sending me an ask.

I’m working on Safari/Firefox ports to bring this feature to them, and they should be available in a few days. Thank you for your patience.

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.

No Sidebar is a simple (and experimental) extension that disables the “preview panel” and opens the blog in a new tab instead of on the right side of the screen when you click on an avatar or username.

Since it’s pretty new, please let me know if you experience any problems by sending me an ask. Thank you!

I’m working on bringing One-Click Reblog and more functions to the sidebar view if you enjoy using it.

Outbox

• Fixed sent fan mail not getting saved.

Tweaks

• Fixed “Hide My URL” hiding blog title instead.
• Fixed Slim Sidebar breaking the sidebar on some pages.

Read Posts

• Storage tweaks and fixes.

Originals Only

• Small bug fixes.

XInbox

• Fixed not being able to change Fan Mail background if “Slim Fan Mail when I’m writing one” option is on.

The XKit Guy

• I apologize for the lack of updates once again, it’s been a very busy and hectic month. Even though I can’t reply to most asks nowadays, I still read all of them and try to provide necessary bug fixes. Thank you for your understanding.