Taking a look at this today, thanks for the reports everyone.

I've got a couple of questions for you:

• If you log out on subeta.net and log back in (not on new.subeta.net), does the wardrobe start loading?
• While you're having difficulty with the wardrobe loading, do other areas of the site (forums in particular) continue working for you?

I pushed out authentication 'improvements' last week and it looks like it changed the balance from issues on subeta.net to issues on new.subeta.net :(

I've been sharing info as people mention it, including screenshots of the 'loading avatar data' freeze and Keith's been putting together a plan he's working on to at least get an update today.

Unfortunately it's proving hard to pin down; a single factor like wardrobe size or ad blockers would be a great guess if it happened consistently, like it always failed to load. But being able to get a successful response when refreshing after a few times is proving difficult on finding the resolution. That different browsers work sometimes is also complicating. We know it's frustrating and it is being worked on! I'm hoping to have more for people later.

Whoops, that was the data I was searching for but I pinged the wrong person. Thank you for providing it!

Doubleposting for great justice here, but:

Can people please try this link

And tell me what you get? Or better yet, screenshot it?

Jumping in very quickly to outline our new process, and that it's going great (well, except that this bug still isn't' resolved 😭)

When a new bug is found and investigated (either by other staff, galaxia, or y'all) we create an issue in our task management system. Then through that, collects details from the thread (and asks the questions I'm asking) and condenses the information back into the issue.

That way, it's all in one place, we have it tagged to the user who is experiencing it, and I can work on the problem without worrying about missing a particular piece of information.

This is working great, and means that we're communicating way, way, faster even if it doesn't' feel like it from your end.

And with that I'll leave y'all back in the very capable hands of !

We're getting closer! It's an authentication issue, so we're moving through the API endpoints that are continuing to have issues. This is good 🤞

If anyone has any other pages that are causing issues (or telling you that you aren't logged in, especially!) please drop the link to that page here so that I can take a look!