Meet Kukuruku Hub v2.0

We are happy to announce a new, redesigned version of Kukuruku Hub! First of all, we would like to say «Thank you!» to the whole team, who worked really hard to get this project off the ground. We have redesigned most of the web site and hope the UI/UX is more smooth and sleek now. Please let us know what you think and how we can improve. Really! Your opinion is super important.

Premature Optimization is Evil

There were no signs of trouble until we noticed a mix of 200 and 500 HTTP statuses in Kukuruku’s web server logs. We were a bit confused when we started to look into it. The weird thing was that the server responded with either 200 (OK) or 500 (Internal Server Error) statuses even to requests were going to the same URL. What would you blame first? In most cases caching is the first places that you might have to take a look into — some results may have been cached and cause issues for a set of users.

The heartbeat is on

Dear %username%, We are live and ready to win the internet! If you are new to Kukuruku, then stay tuned as we add updates and improve the world of Ku. In case you are an old kukuruker, then we say «Welcome to the very first post. You found it! But, shhhh, don’t tell anyone».