Anonymous asked:
Yes, we increased the version number in our extension to reflect several major improvements (like fixing all the CORS bugs).
Anonymous asked:
Yes, we increased the version number in our extension to reflect several major improvements (like fixing all the CORS bugs).
Anonymous asked:
It should be under “New XKit”. You can also follow the link in our announcement post.
This will fix all the various disabling problems, and is overall easier. Please spread the word—we’re getting a lot of asks about the .crx method.
This should solve the connection errors you guys are having.
nyrneria-stark asked:
We’ve just submitted to the Chrome Store. Once it’s sent through, you’ll be able to download from there and the problem will be fixed. The submit process supposedly takes up to an hour. We’ll post an announcement when everything goes through
culturalrebel asked:
This should be fixable by simply trying again. If you are supremely unlucky, you can wait until we upload it to the Mozilla appstore, which we’ll do concurrently with the Chrome Store (hopefully late tonight, but no promises).
Anonymous asked:
A couple other people have shared your concern. This is a fairly common practice in the world of opensource software, and services like github (where we and the original XKit Guy host our source code) allow you to edit other people’s software easily by “forking” it into your own directory. If you look at the github page, you’ll see that there are 72 forks of XKit, meaning 72 people have created their own offshoot version. XKit Guy uploaded his sourcecode to github with the intent of letting people do this.
Additionally, XKit is GPL-licensed, which grants users/other developers the right to share, copy, and modify the software. XKit Guy would have released his software under a more restrictive license if he were uncomfortable with this.
I hope this assuages your concerns!
thestarstruckdragonboy013 asked:
Right now there are two people working on this. If you know javascript, you’re welcome to contribute code yourself over on github. If you don’t know how to use github, there should be tutorials floating around the internet.
hello! i am using the latest version of chrome and have uninstalled old xkit (losing my archived posts, i should have seen that coming though). however, when i drag the file and install the new extension on chrome, every time i open a new tumblr page i get this:

and the extension will not successfully install. any ideas as to what could be going wrong?
sorry i got it workin, had to disable stylish for it to install (after which i could re-enable it), and i don’t know if someone has already told you this but the quick queue system is not working for me :c thank you so much for doing this!!!
I’m posting this in case anyone else was having the same issue. I’ll add the quick queue system to our to-do list.
Anonymous asked:
This is good to know. We’ll start working getting this on the Chrome Store ASAP. Thanks to everyone who reported in!