There was a Blockstack Browser release just before the holidays. This, under normal circumstances, is great. It was a big release (first iteration of user-selected storage is now supported!). However, this release was pushed out right before the entire Blockstack team went away for the holidays. Again, in and of itself, that’s not a problem. The problem comes if and when there are significant problems with a release and no one is around to address them for 2 weeks. That’s what happened here.
Below are a collection of issues that all appear to have stemmed from the new browser release (or the new year not being handled properly):
Many of the above bugs are showstoppers (meaning regular users would not be able to use apps because of them).
As a side note, this issue was not addressed in the browser release and it seems like it should have been before any new release considering its impact:
I appreciate the Blockstack team’s work immensely, but my big ask would be to hold off on releases when there will be no one around to address problems that might come from the release. My smaller ask would be to work on prioritizing bugs in a manner that better identifies what is critical, what is high, what is medium, etc, etc.