Re-work macOS sysnotify implementation to remove code-signing requirement and multiple API's

1 files changed, 2 insertions, 19 deletions

diff --git a/doc/sysnotify.n b/doc/sysnotify.n
index 8951cf0..e375c7a 100644
--- a/doc/sysnotify.n
+++ b/doc/sysnotify.n
@@ -32,25 +32,8 @@ accompany the text.
 .TP
 \fBmacOS\fR
 .
-The macOS version embeds two separate under-the-hood implementations
-using different notification APIs.  The choice of which one to use
-depends on which version of the OS is being run and the state of the
-Tk application code. The newer API, introduced in macOS 10.14,
-requires that the application accessing the API be code-signed, or the
-notification will not display.  (A self-signed certificate seems to be
-sufficient.) The older API was deprecated but not removed in macOS
-11.0. Tk uses the newer API only for signed applications running on
-macOS 10.14 or newer.  Otherwise it falls back to the older API.  A
-quirk which developers should be aware of is that if an unsigned
-version of Wish (or an application derived from it) is installed on
-top of a signed version after the signed version has been registered
-with System Preferences then neither API will be allowed to show
-notifications, making Tk's automatic fallback to the older API
-ineffective.  To re-enable notifications the application must be
-deleted from Apple's System Preferences Notifications section. (There
-is no removal button, so this is done by selecting the application and
-pressing the Delete key.)
-.
+The macOS version will request permission from the user to authorize 
+notifications. This must be activated in Apple's System Preferences Notifications section.
 .TP
 \fBWindows\fR
 .