Fun fact: the "EnablePasteboardPrivacyDeveloperPreview" defaults flag on macOS doesn't just enable confirmation for accessing the clipboard, it moves the responsibility for an app's main menu from the app's own process into a separate system process (TrustedUIService). This means that the contents of the menus have to be serialized to be sent over XPC to that system process, breaking things such as custom SF Symbols in menu icons. I guess that's part of why it's still just a developer preview.

@_inside just saw that a couple days ago, was a nightmare figuring out why our custom SF Symbol menus weren't working on some of our machines. Really amazed at how many things that setting breaks.

/cc @todd

@paul @todd it didn't fit within the character limit, but the reason I was looking into it was because of Todd's post in a Slack group
@_inside @todd so much for kismet. 🤪
@_inside thanks for digging into it and figuring out what was going on. Makes sense I guess. That user default has been nothing but trouble for us in more ways than one.
@paul

@_inside That’s a poorly named flag! I am sort of weird in that moving system UI, like the global menu bar, out of the address space of the current process seems like a good choice. It causes chaos, is awful for very many reasons, but seems like a proper separation of concerns. Apps advertise their functions declaratively. The OS presents them. Actions are then sent back to the app.

But, wow, are MenuViews gonna get convoluted and weird. 25 years of Mac menu bar being so very weird and special.