If you’ve been active on tumblr lately, you may notice that they’ve started running a new type of ad in the right-hand sidebar unit. Specifically, there’s been an uptick in ads that auto-play loud audio, some of which are even un-mutable.
We’ve addressed this in Anti-Capitalism version 1.3.0, which adds a new option:
(small mea culpa: the naming here is slightly confusing. this will *always* remove the sidebar ad, even if it doesn’t happen to be one that plays audio, because we don’t have the ability to distinguish between them. the other difference is that it does it in a way that also takes care of the audio-visual component instead of just hiding the ad, like some adblockers have been doing)
let us know what you think! I’m probably going to be going to bed soon, but you can always reach us in our ask box, our support blog, or our live support chat. In general the dev team has less time to reply to asks nowadays because of both real-life obligations and the sheer quantity of asks we receive, so you’ll generally have a better time with the support chat, if you can catch one of us online. If nobody is online, you always can leave a message for us to read later. thanks for understanding!
(one last plug—If you’re interested in helping us run New XKit, for example by answering asks or helping other users with questions + problems, come stop by and introduce yourself! we don’t bite, we promise!)
Some of you on loading Tumblr today may have received a popup that looks like this:
This popup is in fact lying. Some of Old XKit’s services finally expired and stopped running today, and while we operate our own codebase, there are some references to the old one in a few places that triggered a notification when they went down.
New XKit still works. In fact, if you reload the page, the notification should no longer display and New XKit should still function normally.
If you are still using Old XKit, now is a great time to download New XKit!
This is likely to be buggy and imperfect, and is definitely not totally optimized, but it is at least a start at fixing the atrocity that is the new reblog structure.
Your posts will look something like this:
Instructions:
It took me a bit to get it to work, but the FAQ helped me
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.)
Hey guys, lets all go donate a dollar or 5, yeah? I know if we all did it would make a hug difference!
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.)
So this is why xkit isn’t working right today. *shakes fist at chrome*
(also YR TAGS MADAM: “xkit tumblr it’s bigger on the inside nothing hurts every happy fandom cliche ever kittens puking rainbows naked mermaids with cupcake tits my God it’s full of stars”)
Posted on
tumblr staff: hey guys we’ve just added this new feature to the site, isn’t it great?
xkit guy: here’s the extension to get rid of this one
the xkit guy is like a friend who volunteers his house to host the party, decorates the whole thing himself, makes sure to buy everyone’s favorite albums so the party mix is as bangin as possible, pays for the keg and an open bar, stays sober so he can take care of you when…
