Chrome: XKit 7 keeps on re-installing

I’ve been exchanging asks with 4 people today over XKit re-installing itself over and over again: you click download, it downloads, it says “Thanks for installing me!”, you click okay, and boom. It starts installation again.

And I think I’ve nailed down the problem: it’s a corrupt Chrome preferences file. Luckily, the fix is an easy one, although it is a bad one if you want to keep your Chrome settings. It involves creating a new user on Chrome.

So if on your computer, XKit keeps re-installing:

1. Click on the top-right Chrome button (three-lines)
2. Click on “Settings”
3. Scroll down and click on “Add New User..”
4. Now install XKit. It should be working properly.

Send me an ask if you are still having problems!

“Maybe they unfollow you because you can’t read”, Part II

Thank you. I really mean that, thank you. I’ve been getting a lot of asks thanking me for XKit, and donations. I really appreciate this, and I know that you know the post I’ve made yesterday was not made for any of you.

Let me clarify that I love every XKit user. That post (and it’s addendum) was made to people who don’t donate, don’t make any suggestions, don’t file any bug reports, and then when something goes wrong, writes a 4 page rant on how rotten I am, calling me childish names, and how much they want to “punch me in the face” and stuff. I don’t usually make posts like this, and if you look into the archive of this blog, you’ll see that I’ve been posting here for over 2 years, and that you can count the “editorial” posts with one hand.

That post was directed to people who think it’s their right to demand (let me repeat, demand) things from me or threaten me because they’ve downloaded XKit. I just don’t like this “I’ve downloaded your extension, I demand respect and answers and functions added, now! You should be thanking me, I’ve downloaded it!” mentality.

To clarify: “Hey, you should add a feature that automatically adds tags” is something I have no problem with, and enjoy getting as an ask. “I’ve downloaded this shit but it doesn’t have unfollower checker, are you gonna add that soon or I’m gonna uninstall this crap and switch to another extension”, is not.

For a better example, take a look at the Missing E tag: the creator of Missing E moved to another country, got a divorce and looking for a job (and posted about this on the Missing E blog), but people under the tag are cursing at him and his product for not being updated. Apparently, for some people, he has to update his product immediately, even after all this. Yesterday’s post was directed at those people.

My respect and love for everyone who writes bug reports, suggests functionality, donates and promotes XKit is stronger than ever.

XIM 2.7 Rev A

XIM 2.7 is now available on XKit servers, so you can get it by clicking on the Update button on your control panel.

This version brings notifications sounds for when you get a new message, or when a user becomes online/offline, made by pageofmelody (who has really neat 8-bit music on his blog btw!).

If you are one of those people who don’t like beeping computers, you can turn off notification sounds from the control panel.

XIM + Avast / AVG / BitDefender

Seems like some versions of Avast / AVG / BitDefender likes to block WebSockets, while some versions of them allow usage of port 843. Unfortunately, XIM uses port 8081, which might cause problems. 

So if you have any of the software listed above installed and have problems signing into XIM (get the “Server down” message), you might want to temporarily disable them, or if possible, add port 8081 to their whitelist in order to use XIM.

I apologize for this, but it’s beyond my control.

Fix for not seeing blog buttons (or, XKit 7.0.3 for Firefox)

[ This is for Firefox users only. This bug does not affect Chrome users, and Chrome users get automatic framework updates from Web Store. ]

Thanks to XKit + Firefox users, I’ve spotted a bug that causes the Like/Reblog/Follow/Dashboard buttons on a user’s blog to disappear when XKit 7 is active. It’s a bug related to XKit Bridge, and has been fixed now.

If you’ve downloaded XKit more than ~20 minutes ago, please follow the instructions below:

• Go to the XKit download page
• Install XKit again and restart browser

You do not need to delete XKit 7, 7.0.3 will replace the one you have (7.0.2) now. Sorry about that.