Kouio RSS Reader (@kouioapp) profile picture

The RSS reader you've always wanted

Sydney, Australia
Joined June 2013
Photo by Kouio RSS Reader (@kouioapp)Photo by Kouio RSS Reader (@kouioapp)Photo by Kouio RSS Reader (@kouioapp)
Next on the blog, "Really Real-Time This Time" - a look at even more real-time features we've added! kouio.com/blog/really-real-t…
Today on the blog - Enhanced Security via our new CDN for third-party content: kouio.com/blog/enhanced-secu…
Next up on the blog, we take a look at our new recommendations engine: kouio.com/blog/our-recommend…
First up, let's look at creating your own public profiles on Kouio: kouio.com/blog/kouio-goes-pu…
1
1
We've released a lot of features over the last year without any fanfare - this week we're going to look back and write about each of these!
1
1
Upgrade took a little longer than expected, but all went smoothly and everything's back to normal.
In about 12 hours from now we'll be upgrading our server - the site will be unavailable for up to 10 minutes.
Unread counts for feeds stopped updating a few hours ago due to a service failure - that's now resolved and counts are back to normal.
Our dns service is experiencing issues, more info here: dnsimplestatus.com/ Meanwhile you can access kouio via http://t.co/qlncC3DD3m
Here's a fun graph showing the new engine's behaviour - lots of feeds remain dead, while lots come back to life:
One thing to note from this is that you may now notice a bunch of dead feeds come back to life!
1
We now continue checking feeds we'd mark as dead at a very infrequent rate, currently once a day. [cont]
1
We've just released a new version of our feed engine - we no longer mark feeds as dead after many failed retrieval attempts. [cont]
1
We've just rolled out some extra sharing preferences, such as the ability to share via Linkedin company pages: cl.ly/XfCG #rss
2
1
This week we had our 4000th user sign up! Here's to the next 4000 :-)
Our elasticsearch instance has always been secured, so all our services have promptly been restored by our provider - apologies again!
Our hosting provider had to shut down a large number of sites running vulnerable elasticsearch instances and we got caught in the crossfire.
1