We apologize for the instability of composr.app and appreciate your patience. We are working on the statistics addon and trying to find an optimal way to store and render data. Unfortunately, we have yet to find a solution that can handle the traffic (and therefore, tens of millions of statistical records) of composr.app. We're working hard on one.
For reference, code was already very smart about this, but just buggy.
It reads everything up to the line end, and then does an OR query based on all possibilities against all possible non-word cut points (i.e. any possible parse for a username). It picks the longest username matched.
It reads everything up to the line end, and then does an OR query based on all possibilities against all possible non-word cut points (i.e. any possible parse for a username). It picks the longest username matched.