The reason this is like this (and same for the kissing/biting page, and some other event pages) is because this page gets displayed when you click the little Dance button next to HAs in the Masq forums. We have some complicated code on the kissing page, as you saw, that allows it selectively choose to show the site layout depending on where you clicked from.

This is not super complicated, but can easily have mistakes. It's unlikely I will work on it this Masquerade due to the circumstances and time/effort involved.

Possible? Yes. Would it solve the problem and be worth the man hours, work, and server strain? Not remotely. You may be surprised, but there are a lot of users with naked HAs that have been active in the last month, and the clothing would not be foolproof unless we also checked for backgrounds, foregrounds, ground items, other items that cover the whole body, makeup (because someone could wear 3 face items and be still mostly naked) etc. So it's about as good as it will get right now :/

The frozen users thing is a glitch that will be fixed. The inactive users thing is a non-issue as they wouldn't be posting in the forums anyway.

Yeah, I think it's a non-issue with other holidays because there's no penalty for throwing flowers at an inactive user, or kissing them or stuff. With Masquerade, you can lose out on trinkets since you never get the trinkets if your dance is never accepted. But with other holidays you get the currency right away, so I don't think there is a problem.

I'm sorry to hear you have trouble loading it! This is due to a known issue with the way HAs are generated. At the very least I can say the problem has not and is not being ignored. It's just that the solution is taking us some work.

A few months ago Keith attempted to implement a caching solution which actually did speed things up a LOT, but it had one problem: HAs would get cached based on the server you happened to be on, so what would happen is, people would change their HAs and but their HA wouldn't stick. Like you'd refresh the page and it would sometimes show you the new one, sometimes show you the old cached one. So we had to revert it.

We are working on solving the problems we ran into, because we do think caching is a solution, we just ran into some issues with it that need to be smoothed out before we can attempt putting it into action again.

Unfortunately in the meantime there's not much that either of us can suggest to the other. I hope it helps at least to know the problem's diagnosed and being worked on.