XKit

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.

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.

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, seems like I’m having one of those unlucky months (1, 2) This morning I’ve started receiving messages about XKit Mobile crashing upon startup, which is related to the “Net Neutrality” theme of the dashboard (spinning wheels instead of photos). Since this effect is only visible to United States users (although I’ve received messages about it being visible to UK and Australian users - and I’m not in any of these countries) the most I could do was post a tip I’ve received from a user.  

Turns out, even though this fixes the problem on some accounts, on some accounts, the problem is still there. I’ve used a USA based VPN service (a proxy service) to test the application and it indeed crash on 2 of my 3 test accounts.

I wrote a fix and submitted it to Apple. As you know, on desktop versions, I can/do push updates instantly, but on App Store, I have to wait for review process, which can take several days. I’ve requested an expedited review, which reduces that time to less than 24 hours, and am waiting for their approval.

The best case scenario is that they’ll review and publish it, and it will be fixed in a few hours. Worst case scenario is that they will not accept the expedited review request, and it will be fixed once Tumblr stops the themed dashboard, which should be less than 24 hours. 

Once again, I’m terribly, terribly sorry about this. You have every right to be mad, since this is an oversight on my behalf (the original code was missing a check that could prevent this from happening) but my hands are completely tied and for now there is nothing I can do but apologize and ask for your patience and support.

Thank you so much,
The Xkit Guy.

To illustrate the importance net neutrality, Tumblr decided to replace all images on dashboard with a load “spinning wheel”. This, however completely throws XKit Mobile off, causing it to crash upon login. Since this effect is only visible to United States users, I only have screenshots of it and can’t do anything to fix it remotely.

Fortunately, the fix is easy:

Login using a computer (or Safari on your phone, you’ll have to switch to “Desktop View”) and tap on the “Make it stop” button on the top of the page. This will remove the spinning wheels on your account, and XKit Mobile will start working again.

I’m terribly sorry about this.

(PS: Net neutrality is a really good thing.)

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.

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.

I’ve been getting reports of the XKit button missing on both Firefox and Chrome. Some people report only the button missing but the features working, some people report it not working at all.

Unfortunately, I’m very far away from home / a computer so it might take 3-4 (or more) hours until I can check what is going on and provide a fix.

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

UPDATE: From the replies/asks I’ve received, I can confirm that this is because of a Tumblr change. Once again, it will take a few hours for me to fix this and I’m terribly sorry about that. Thank you so much for your patience.

I would like to apologize for the lack of updates again.

I’ve been working on version 1.0.3 of XKit Mobile, which should bring a much better experience for it’s users, with Hold-To-Reblog, Shorten Posts, revamped user interface (which should be less glitchy and feel less, well, rigid) and much faster GIF and page loading (up to 4-5x faster for GIF loading, and up to 25% faster for page loading) and lots and lots of small improvements and bug fixes. (iPad version is coming in 1.0.4, as it’s proving to be a little more difficult than I’ve predicted, my apologizes for that.)

After it’s released, I’ll be focusing once again on the desktop version, fixing the known bugs and bringing back Safari support. I am also experimenting with new features.

I also apologize for delays on answering your asks. The things is, in the last 3-4 months, the amount of asks I receive jumped from 15-20/day to more than 100/day (especially after Tumblr changes something), which is the reason why I can’t respond to asks like I’ve used to. I’m considering getting a few close friends to help me with the asks.

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

A recent Tumblr change removed the underlines from links completely, making it impossible to determine what is linkage or not.

Although I would write an extension that reverts this, this seems like a bug to me, so I’ll be waiting a few hours to see if it gets fixed first. If it does not, a new extension will be available shortly. Thank you for your patience.

Update: They are back.

I just wanted to make a personal post to thank you for your support this week. I really can’t thank you enough. I will be honest, I wasn’t expecting such a warm reception on XKit Mobile.

As I’ve said, it being the very first version, there was a possibility that it would have bugs, and sure enough, with your bug reports, I’ve fixed around 13-15 reported bugs, and version 1.0.2 is on it’s way. It should also dramatically improve the image loading speed. Apart from bug fixes and speed improvements, it also has several small user interface improvements and features such as Smart Safe Dash, which only blocks images from known NSFW/Adult blogs.

I’ve submitted it to App Store, and I’m estimating that it will be available for download in 6-7 days (regular application review time).

I also apologize deeply for the bugs, and my slow reply time to your asks.

Thank you so much for your support and patience.

Missing Features and Known Bugs: I’ve added a list of missing features and known bugs to the transparency page. I know I should’ve done this a couple of hours ago, and I apologize deeply for that. I do realize that “it’s missing a few features I really wanted to add” was not very descriptive. 

iPad Version: XKit runs on “scaled mode” on iPads, but I’ll be adding full-screen iPad support as soon as possible. And yes, it will be a “Universal” app, and not a separate purchase.

Android Version: As I’ve said, it’s on my to-do list, but I can’t give you any estimates or make any promises. I’m sorry about that.

Asks: Thank you so much for your asks. Unfortunately, I’m completely burned out today so I can’t be replying to all of them for now. But if you found a bug on XKit Mobile, please send the XKit Mobile blog an ask and I will reply as soon as I can.

Again, the app is still in it’s infancy, and this is very, very first release. I will be doing my best to make sure it performs perfectly, and I apologize in advance if you hit any of it’s rough edges. Thank you for your patience and support.

Before you ask: yes, I am also planning an Android version. But it requires me to learn yet another programming language and re-write it from ground up, I can’t say anything about when it will be available, I’m sorry.

XKit 7.4.4 is now available for Firefox 29 and up. It brings compatibility with Firefox 31 and above, so if you are on version 30, please upgrade before Firefox 31 is released.

If you are on Firefox 28 or below, unfortunately, this version breaks XKit on your browser. In a nutshell, Firefox 31 brings changes that used to break XKit, so I had to rewrite parts of XKit to make it compatible with it, which in turn broke it on Firefox 29 and 30, prompting me to make more changes, which in turn, due to the way they changed things, made it incompatible with version 28 and below.

If you are on Firefox 28, you can still download XKit 7.4.3 from this link.

If you are on Firefox 29 or above, just re-download XKit and it will upgrade itself, preserving your settings.

I’ve received a lot of asks (most of them I couldn’t reply to yet, I apologize for that) asking me if I would reconsider adding Safari support back to XKit with the release of Safari 8 and OS X Yosemite.

The short answer is: “probably”. I know about the improved HTML5 support and other improvements, so it should be easier to write code for, but I will probably end up re-writing the whole Safari version of XKit (even if it’s not required) and I can’t upgrade to OS X Yosemite for now, so I can’t say anything yet.

I know a lot of people love Safari, but as you probably already know, I had to drop support about a month ago for various reasons. As I’ve said in that post, I know it’s absurd to ask people to switch browsers just to use XKit, so if everything goes well, Safari support might be back in a few months.

Today’s post is kinda long and personal, even though I try my best to refrain from personal posts, I thought it was a good idea to write this.

Since it’s very long, it’s read mored. My apologizes if you are on mobile.

Keep reading

There is an ongoing problem where you can’t insert photos to asks while answering them, but since the problem continues even after disabling XKit, I can confirm that it is a Tumblr bug, not an XKit one.

I’m sorry about this, but there is nothing I can do except let you know.

Yesterday, I’ve introduced XKit Packs, which allows developers to distribute XKit extensions without my permission/inspection. And I’ll be honest, I had about 4 hours of sleep last night.

Although I’ve implemented some server-side checking for scripts, which forbids developers from using IFRAMES, redirect pages or open popups, as you know, no system is bullet-proof.

So, I’ve started thinking: what if someone, somehow, bypasses this security system? Or what if they write a perfectly fine extension, get everyone to install it, then send an update that does bad stuff? Or what if they manage to break the “kill switch” used to delete malicious extensions? Or what if a developer with good intentions write a very buggy extension that causes a lot of problems for users?

Yes, bad software is everywhere, and any extension/application you install can do some very nasty stuff. But I just don’t want to provide the bad people yet another method of distribution. I want people to be able to click that Install button without worrying about what it might do.

So, less than 12 hours after it’s release, I am temporarily disabling creating/editing XKit Packs: if you’ve already published a Pack, people will be able to install it, but you won’t be able to edit it for now. Although it defeats the purpose of Packs, I will be implementing an approval system, so whenever you create/edit a Pack, it will need my inspection and approval to make it publicly available. Still, since it will be automated, when finished, it should be much faster and easier than the traditional way of submitting an extension to the Extension Gallery.

I’m terribly sorry and I apologize for this, especially to the extension developers. I hope you understand. When the approval system is done, I’ll be announcing it on the XKit Developer Blog.

Search Likes

• Now searches the tags of the posts too.

Outbox

• Added “Shared Outbox Storage” option, if you want to use the same inbox under different accounts or having problems with sent asks disappearing.

Read More Now

• Added smaller Inline Button option.

For the full list of today’s updates, including bug fixes, please click here.

No Recommended is an experimental new extension that removes “Recommended Posts” from your dashboard, and is now available on the Extension Gallery.

Please note that this only removes Recommended Posts. To remove Recommended Blogs on the sidebar, you can use the Tweaks extension.

And since I couldn’t test it personally, if you hit any bugs or see recommended posts after installing it, please let me know by sending me an ask. Thank you!