False alert. Ostrich still needs fixing.
First let me reiterate on why Ostrich needs a server at all. Connecting to Twitter with OAuth requires something else than Javascript. It needs a backend where the connection dance to OAuth can happen. It’s possible in Javascript, but I would have to supply the extension with secure information in an unsecure manner.
In the last two days, I modified Ostrich to fetch tweets (it’s longest lasting requests, which killed the server) in the background. However, it fell short again. Little did I know, I used a technique that wasn’t scalable. The thinking is fine and should’ve worked, but I used one method somewhere that ruined it for the whole application. I need to replace those few lines with something more scalable. That’s the plan for the next few days.
At the moment, the ones being able to use it for a few minutes is the results of me manually restarting the process that serves the data. I’m that dedicated. But that’s enough, I’m putting back the message saying it’s unavailable.
Thanks for understanding.
