On 31/05/2025 08:09, Charles Choi wrote:
Interim snapshot of rewrite of Org Protocol page. This is still WIP, but
intended to illustrate direction of changes to this document.
Since it is major rewrite, subthreads for specific topics may be
convenient. I have added "macOS" to the subject of this message.
+++ b/org-contrib/org-protocol.org
...> A commercial offering ([[http://yummymelon.com/scrim][Scrim]]) is
available to serve as a macOS-trusted scheme handler for Org Protocol
requests.
I do not have a macOS machine to test, so I am unaware how to configure
org-protocol for macOS
Recently I noticed:
Ihor Radchenko to emacs-orgmode. [BLOG] #17 [[bbb:OrgMeetup]] on Wed,
Apr 9, 19:00 UTC+3. Tue, 22 Apr 2025 16:27:56 +0000.
https://list.orgmode.org/87ecxkb1pv.fsf@localhost
kickingvegas showcased his new app he is developing
to support Org capture and Org protocol on macOS
- https://fosstodon.org/@kickingvegas@sfba.social/114314588128977624
https://github.com/kickingvegas/Captee
- There is a need in special app because macOS now forbids arbitrary
apps from using URL protocols and a code signed app must be used
instead of emacsclient (which is not code signed and will likely
never be)
Should this project be mention on the Worg page or it is in too early
work in progress stage?
In the proposed variant, details specific to macOS is scattered over
several sections. My impression that it causes repetitions. Have you
considered single section on macOS that discuss variants of Emacs
package and suitable URL scheme handlers for them? This is just a
question, not a request to update the document.
On 31/05/2025 08:09, Charles Choi wrote:
Recent versions of macOS (since Ventura) disallow the use of a local
domain socket for inter-process communication between apps with separate
sandboxes. Users using [[http://yummymelon.com/scrim][Scrim]] can
instead setup a TCP socket.
Is there some kind of authentication for TCP/IP sockets? Otherwise it
can be insecure. Is it assumed that macOS is effectively as single
(humane) user system? Can web pages loaded into a browser connect to it?
Some ports like 25 (SMTP) are banned in browsers. I am unsure in which
stage is the proposal to add low level TCP socket API to JavaScript or
if HTTP "garbage" sent to Emacs server can be dangerous.
