It also, if the new paid for mark is anything similar to it in looks means that Musk has quite probably opened twitter up to a legal minefield that the original blue check was meant to defuse.
Especially as Musk has got rid of most of the people that used to deal with things like fake accounts and impersonators, so the next time someone takes Twitter to court for allowing someone to impersonate them/breach their trademark twitter can't even now say "we were making a best effort to prevent this (entirely foreseeable thing) happening".
I find it funny how many people seem to think the blue check was entirely for the benefit of the person who had it, rather than it being primarily a way for Twitter to remove some of it's legal liabilities and I suspect a number of blue ticks would have been given to people who'd had attempts to impersonate them (as was the original impetus for the first ones).
i've been seeing some interesting comments in various places about how/why musk firing people he didn't seem to think were doing much may not be a great idea, including the fact that a lot of programmers/engineers don't actually produce a lot of written code/hardware changes every day because a lot of their time is spent analysing problems and trying to do preventative work, as if you're doing your job right in those sorts of roles you shouldn't be running around putting out proverbial fires, you should be preventing them from happening in the first place by doing things like observing performance of the hardware/code and trying to understand what is going on before you touch anything (and this doesn't provide a nice easy to see metric for "work done" because most of it doesn't involve writing new or actively physically doing anything, as the main thing you're using is your brain to read/understand/analyse).