Earlier quoted context omitted.
It's also trivially easy to fix. 1 min delete and deploy.
I'm guessing it's not trivial to fix without breaking other things? The weakness seems to be that anyone can turn UUIDs into details like email. But I assume this functionality is necessary for other flows so they can't just turn off all UUID->email/profile look ups. And similarly hiding author UUIDs on posts also isn't trivial. Conceptually, I agree it should be easy, but I suspect they're stuck with legacy code and…
if (metadata.is_public)
Simple fix.