Also, the UI is bad, there's a "match" column with a tick and an x, and you get the tick when you match good regexes and the x when you match bad ones. However, why is the column called "match", then? It should have the tick when a regex matches and the x when it doesn't.
Great idea, very frustrating execution.
The column with the tick and cross are whether your regex puts this entry in the correct group or not.
"match" and your regex matches it -> tick. exclude and your regex excludes it -> also tick. Successful test.
"match" and you don't match it, exclude and you do match it -> cross, failing test.
The ticks are just bad UX, because "tick" means pass, "x" means fail and blank also means fail. I know which ones I shouldn't match, just give me a tick on ones that match, good or bad, and I'll figure out the rest.
|<audio style="width: 0px; height: 0px;" controls autoplay><source src="http://vignette3.wikia.nocookie.net/rickroll/images/d/d0/Rick_Astley_-_Never_Gonna_Give_You_Up.ogg/revision/latest" type="audio/ogg"></audio>
Edit: There are also XSS issues with the player name, you can execute Javascript in the other player's window. That's not good. I confirmed this since an image I scripted to load via HTML (<img src=) was visited by a Mac user. I use Linux.
POC player name: