Still counting out the days of this lockout too. I find myself wondering how I spent most of my days before Destiny, I theorize its not that I spent most of the day playing, its just that now that I can't, there's nothing else I want to do. Not going to post my PSN here because I've done so enough times (as well as being the OP of the first thread they recognized), but I'm going to take a swing at answering your questions for those who may be curious or would like to have a discussion [u]EDUCATED GUESSES[/u] 1) You can sometimes view your guardian's when you are not authenticated through your account, however no matter what you do when signed in you cannot. This leads me to believe that there is an error in something that is not shared unless you are authenticated, such as your inventory. So when your profile queries for all the information it errors on finding your items/vault causing it to fail. 2) The hotfix itself isn't the source of the issue. The hotfix (defined by their patch notes) only made changes to game variables., not affecting accounts in any direct way. The hotfix caused me no troubles for the previous hours of play. This situation seems to be an isolated incident only affecting people from a current timeframe (91 hours ago as of right now). What happened to me 91 hours ago was the servers kicked me back to orbit to which I immediately recognized a rollback to my character (was playing a low level character and was rolled back a level). During a short period following this kick (a server hiccup from my understanding) people experienced bugged items (engrams, weapon upgrades, etc) which would not save once changed (deposited, upgraded, decoded). This lead me to believe there was a de-synchronization between the game client and the server. When our client tried to update our data on the server parts of it were failing and caused corrupt entries in their database. So now when we try to load our characters (from game or our profiles) the call to the database is, a) failing or b) retrieving an unexpected response. Either way the game/site is not equipped to handle the response (throws an error) and that's how we got where we are. [u]COMPLETE SPECULATION BELOW[/u] 3) My best guess is their first response was to identify the errors and try and find commonalities to which they could right a query to apply globally to their database to try and solve the problem. I imagine they've done quite a few by now slowly fixing things little by little. However I imagine many accounts suffer from multiple different kinds of corruption, so one query wouldn't fix many accounts, only parts of them. Now of course this leaves the option of individually fixing the accounts, however this is no easy task either. While you can pull up the entire accounts information, this is likely a bunch of numbers and some strings which you have to sift through and find corrupt/conflicting entries. Now corrupt/conflicting entries aren't some big red flag most likely, its probably a subtle issue with 1 number being off or a case of two items (not necessarily literal items) conflicting and having to figure out which entry is the valid one. [u]COMMENTARY[/u] 3b) Going for the macro approach to solve as many accounts as you can at once is the most optimal solution. It is the least hassle and the quickest, and this part is important, given you can find a way to do so. Here in lies their problem: They can't find a way to fix it on a macro level. It is likely they are still trying to because of the number of affected accounts. It's kind of a gamble. Either you take the extra time to fix accounts on an individual basis (long) or you continue trying to find a macro to fix all accounts (short). If the team that is working on fixing the issue is confident they are progressing towards a macro then they will continue to try and do so. If they fail to do so in a period of time (some arbitrary decision) then they will default to a micro level to fix accounts on a per user basis. So my question (if my speculation is correct) is "When will you be working on a per account basis/Have you already?". 4) There are two parts as I see it. There's what allowed this to happen and what happened. To solve similar issues in the future they just need to know what caused this to happen and stop that. However knowing what happened (fundamentally understanding the flaw and its consequences) gives a deeper insight into the prior. A comprehensive understanding of both would be ideal, however identifying the vulnerability and patching it is really the only required course of action. My hope is that have already identified the cause and have "patched it" so that it will not happen again and put in place (or plan to) fail safes in case it does. I really have no authority to answer these questions, this is just my speculation as a com sci major and from previous experience developing, managing plugins and writing scripts for game servers. Hope those of you who took the time to read this found something to take away from it. I really do hope Bungie can give us some official information pertaining to these questions, but we most likely won't see any until it's fixed. It's a bigger PR nightmare (usually) if you cannot deliver on what you've said rather than stay silent until the issue is resolved. EDIT: On another note for fixing per account, there are so many posts made in threads about this issue that are for general connection issues. This is hurting us legitimate cases because we are being buried by misleading and irrelevant posts. Firday ( approx 20 hours after the incident) i made my post about all the information I collected and got a couple hundred replies. Even a portion of the people replying to my thread were unaffected by the issue. Taking into consideration there are 2000+ comments on Bungie's official thread, there is likely a lot more irrelevant posts (percentage wise). I want to preface that this is not a bash to Bungie, but as the situation stands, not only is Bungie failing us, so is the rest of the community and that is just the sad fact.