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.