I'm glad I'm not the only one thinking that. If a delay is happening, it's good that they notified us of it, but the other part of the issue is then updating the schedule. The slight delay notification mentioned it was a big but not insurmountable problem, but even knowing general software development procedures that isn't really good as a way to estimate how long the delay is. Now that it has been a week since that previous notification I imagine the scale of the problem could at least be figured out to a degree by which either:
A. A ballpark estimate can be reached as to how long the delay will continue for.
B. It can be determined that the problem is larger than expected and thus such an estimate is impossible at this time.
I won't deny that part of my impatience is coming from having started preparations to get other backer beta friends together and thus my excitement has built up and is now starting to burn. I know how rough unexpected problems can be in a software development process, especially when putting together all of the separate pieces.
What would really help us here is some sort of information. People will jump to conclusions without any updates, so all that's necessary is some sort of hint at the progress on the problem. We're all here to support the team, I don't think anyone will be annoyed if it turns out the problem was bigger than expected and the beta needs a significant delay. We just need something so no one starts getting worried.