The current state of Nindo
You might have noticed that after December last year Nindo went silent. That is for a reason. The core functionality of Nindo, the RSS features, is built wrong.
What does that mean? That means every post on every RSS feed loaded into Nindo is cached twice. In memory. That means that after adding 8 or more feeds Nindo basically crashes. That is easily fixed by just slamming a lot of RAM at the Nindo instance, but is that really a solution. So I’m trying to rework the inner workings of Nindo while keeping it compatible with the current web interface and also working on other projects and trying to get good grades at school. Which is a bit too much. So I just stopped.
That doesn’t mean that I won’t work on Nindo anymore. It just means development will be a lot slower, if not none, for the coming months. I hope my three readers will understand and I hope Nindo will become somewhat stable in the coming year.