In advance, I haven't tried other browsers. But on XPsp3 with Chrome, tried both with a clearing of cache and cookies and without -

If I post in my legion comm and I use the number symbol, for example, cheering that our legion is #26 in the leaderboard, the message doesn't register, the comm pop-up goes blank, and the app goes back to the news page as if I had just connected to Galaxy Legion.

I've narrowed it down to this one symbol by copying and pasting the same message, and changing # to "number" - it then posts fine. I've also tried with varying size messages.

# works fine for me. Win7 and chrome. Just adding some info so the problem can be narrowed down...

Now that I think of it... It could be that the # sign is included somewhere in GL's programing, and that is conflicting with your message. (possibly acting like a cmd line)

Update - I posted "Whohoo - we're legion #25!"

Andi t posted as "Whohoo - We're legion"

So the bug is doing something different today than the last couple weeks.

things like that or "<" ">" some other symbols are excluded for security reasons (could inject code). Although, I use math enough that not doing greater than symbol etc is a minor irritation-- you just learn to type out the word instead.