@dorpie this is an issue that gets reported every now and then, and we (both the community and us) shared similar images to poke silly fun at the situation. They are not intended to make fun of the person reporting them nor have ever been, in any of the previous iterations of this issue being reported or this one in particular.
Unfortunately, the status for the fix of this bug remains at the moment unchanged. It is not considered a high priority fix for now, but our team is aware and it might get re-prioritized in future sprints.
We’ll proceed to close the thread since the report has been acknowledged and relayed to the team, and any further conversation seems to be seeking an unnecessary heated debate.