戦争の犬

[ i know i haven’t been online for quite some time, and that’s going to continue ]

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.