> If it is 23:00 then no time display should ever display 11:00 without a PM because it’s then lying because 11:00 with no AM/PM unambiguously denotes 11:00AM.

In one specific linguistic context. In others, 11:00 for 23:00 is perfectly fine and expected. Yes, it is ambiguous; no, it is not “lying”.

> In one specific linguistic context.

No, in all of them, including the 12 hour time default places. That’s what the “AM” or “PM” is for; if it isn’t there then it indicates it is 24 hour time regardless of the number displayed.

I am not sure why you are taking this so personally or why you insist. It is an English notation and looks foreign in most of Europe, for example. I can say for sure that it is not “in all of them”, as I used to live in such a place. The only contact with AM or PM in daily life is in poorly localised software, and is completely foreign.

They use 24 hour time in most contexts, but often use 12 hour time informally and the actual time is understood in context. You might not believe it, but this happens.

It is, in fact, not unreasonable to ask for an option to format time in 12 hours without letters after. (I am not saying the author should do it; they are the one to choose what to do in their free time).

Settings like date and time formatting and physical units should ideally be changed by the user. You cannot expect a single setting to work all the time.

This is such a baffling and hostile response to a request for a widget where the only purpose is to quickly tell time. I just want to be able to quickly tell whether it's past 5pm for my coworker without having to squint or do math in my head.

(Also, for what it's worth, you're objectively incorrect about it being lying; time is measured in 12 hour cycles in most locales, with further bits of information for time zone, before/after noon, day, month, and year. 23:00 is still "ambiguous", missing almost as much of that context, but it's not "lying" if you have the required context)