Unfortunately, since then a new problem has popped up, which is intermittently slowing Soup down yet again and even lead to several hours of downtime yesterday.
We're doing what we can to get to the bottom of this. Since signs point to the cause being in the notification system, we need to experimentally disable notifications for the next day or so as part of our debugging efforts. Sorry about that!
I know how much it sucks when Soup is slow or unreachable, when support requests remain unanswered and obvious feature improvements aren't implemented.
Unfortunately, our resources are very limited right now. @
lfittl decided to leave the company earlier this year, and despite everyone's intentions of a smooth and swift transition to another full-time technical team member, it has been plagued by delays.
That you all are willing to tolerate these circumstances and continue to be active in the community and entrust us with your data is humbling and motivating, and just strengthens my unwavering commitment to the site and its future. Here's what's currently being done:
– I'm expecting to be able to introduce you to some new team members shortly.
– Plans are being made to future-proof the database architecture of Soup. This is just the start of a process that will take months, but will ultimately give us lots of breathing room from scaling issues.
– I'm busy working on the
general future direction of Soup. I'm
seriously excited about the way the plans, mockups and prototypes are developing and can't wait to share them and get some feedback from all of you. Right now, the only aspect I can give away is an increased focus on mobile devices, but that's just one part of it. Stay tuned!
– We're actively talking to investors to put these plans on a more stable financial foundation, while still keeping a plan B in mind for when that doesn't work out.
To stay in the loop on the progress of these plans, consider adding
kitchen as a friend, if you haven't already. Thanks so much for your continued support!
