Less Broken Than You Think

[Less Broken Than You Think]

Anonymous asked:

Thank you so much for updating xkit! One of the main things I've noticed about the state of the extension as it stands is the greyed out font for many of the profile viewed extensions (similar to, dashboard stats etc.). Are you guys working on fixes for those?

We just fixed this for Post Archiver, Tag Replacer, XInbox, and XStats. You might have to manually hit “update” in the extensions browser to see the changes. Please tell us if we missed anything!

[Less Broken Than You Think]

Anonymous asked:

Hi. Thank you so much for doing this. You are amazing. Are there any plans for you to do something with Safari?

Unfortunately, the Safari Developer Program costs $100 a year, and we’re broke, so we’re not planning on updating the Safari extension. Sorry about that.

[Less Broken Than You Think]

Anonymous asked:

I forgot to mention in my submission about the missing icon that I am using the latest firefox 39.

That’s very strange. Can you type “about:config” into your address bar (click through the scary notification), search for “xkit7.xkit”, and send us a screenshot of the results?

[Less Broken Than You Think]

I disabled the old xkit and installed the new one, but the xkit icon doesn’t show up in the header bar. Did I install it incorrectly?

Are you using an old version of Firefox? This error happens when you try to install XKit on an old version of Firefox. If this is the case, you should update to Firefox 39. If not, can you send us what browser and version you’re using?

[Less Broken Than You Think]

donjuan-auxenfers asked:

The joy I feel in knowing that someone has taken up the duty of maintaining xkit is immense. Best of luck to you all. Right, with that said, the header options is a little buggy, the search bar moves into awkward positions and the show blogs in the header isn't working. Again, much thanks.

Thanks for the report. If you manually update header options in the extension manager, things should work now.

[Less Broken Than You Think]

Anonymous asked:

First I want to say thank you so much for doing this. And may I ask if you'll be fixing the firefox version?

We have both Firefox and Chrome versions available on github. You have to update to the newest Firefox (39) for XKit to function. Is there anything specific you are having problems with?

[Less Broken Than You Think]

v0.1.0 Release Notes

This marks a mostly-stable proper beta. Download it on the Releases page.

Interesting changes from the last release:

• Fixes audio_plus’s volume control
• Reduces memory usage (in theory)
• Fixes blacklist’s button display
• Switches help text over to this blog
• Fixes issues with Firefox’s XHR’s error handling

[Less Broken Than You Think]

[beardednegro]

How is it that there’s not ONE developer on Tumblr that’d be willing/able to take over xkit-extension from the Xkit guy?

Or maybe a few if one can work on the Firefox version, one for Safari, etc.

[new-xkit-extension]

Hey.

[Less Broken Than You Think]

Anonymous asked:

Is there any way you could put this on the chrome store? Chrome only allows extensions from their store, and disables anything else

Chrome is actually lying to you when it gives that notification. If you open the extensions page and drag the .crx file into it, Chrome should install the extension, even though it will try to tell you otherwise. Step-by-step instructions and more information can be found here, if you need it.

We’ll get it on both Firefox’s and Chrome’s addon stores once we fix a bunch more stuff (old XKit really wasn’t that stable), but until then this should work. If you try the above and it’s still not working, shoot us another ask.

[Less Broken Than You Think]

XKIT: IT’S HAPPENING

We have a mostly stable new XKit release for Firefox and Chrome! Available here. Uninstall your old XKit (if you haven’t already) before trying our new version.

Firefox users: Make sure you have the newest version of Firefox. Click the .xpi file. Firefox will ask you to confirm the installation. Get it here.

Chrome users: Download the .crx file, then drag the file into Chrome. Get it here.

We haven’t been able to test every aspect of every extension yet, so if you find a bug, please send it in to this blog or leave an issue on github, along with which browser you are using.