Textedit local links

Grant, credentials are essential security, for sure. Here’s my 2016 StackOverFlow post, when TextEdit links only opened folders with linking to a contained file. Today, 2024 improved by Apple to work with link to any (?) file or folder on multiple systems, in many ways deploying the TextEdit file:///path linking method. When does it appear in the User’s Guide?

Uniform System Locator. Thank you, Grant. Got exactly same two links from Michael at Apple Care this morning (we had a rather lengthy discussion)..

Now, between us I have no idea what more Apple Apple is planning for file:///path, or file-path local link technology, ergo fpllt. 2016-2024 extension is compelling. In this thread's StackOverflow review.

As we all agree, Apple's existing extension 2016-2024, likely has significant implications. As Michael said, "How the classroom institution uses the feature might determine how fpllt will be made to appear in the TextEdit User Guide. Apple is very particular about how it introduces new technologies."

Truly exciting, Michael agrees that fpllt could be launch ready at any time, yes. Where 'launch' includes macOS integration across all system apps. System requirements could fit together nicely. For certain, the macOS future involves URL's and USL's.

Seems that is where we are at right now. User Guide support always helpful. We have to familiarize ourselves with the new USL Language.

Note that the right click Quick Actions Copy Path workflow is the same as ⌘⌥C (command-option-c), when copying the TextEdit Finder path. Copy Path helps with Accessibility in creating TextEdit links to files or folders. However, link syntax is the really important thing to remember. TextEdit links to files or folders in Mac are typed in ⌘K link dialog as file://path

Also notice that the Finder path always includes a leading forward slash, so each completed working TextEdit link to Finder file or folder includes 3 forward slashes. e.g., file:///Users/username/Documents/ToDo.rtf

Not sure how this works with iCloud in Finder.

How does this work with iCloud in Finder? btw I am on a Mac Pro, but for Microsoft Windows, I think local links are called 'machine' links. Which might indicate that iCloud, being a different machine, will not link this way. Not sure how to test that, either.

iCloud ⌘⌥C and Copy Path workflows both work fine with iCloud. ⌘⌥C copy path in Finder iCloud Drive, TextEdit text selected, ⌘K insert link, type file:// and paste copied link.

file:///Users/username/Library/Mobile Documents/com~apple~CloudDocs/Documents/DATA SET/Any file name.rtfd

or

file:///Users/mark/Library/Mobile Documents/com~apple~CloudDocs/Documents/DATA SET/Any folder name

Now, how does this work with files on my other devices, like the MacBook Pro or iPhone? How do I test this between this Mac and my other devices?

Further, for Finder location Network, we can use the TextEdit links to login to another Mac’s Time Capsule to access specific Time Macine files and folders, thus: double click someone’s AirPort in Finder (macOS provides no way to copy AirPort links in Finder). Enter the appropriate AirPort password to continue. Now select files or folders to link in TextEdit. Use Finder menu Paste and Match Style with ⌘⌥c copy.

file:///Volumes/Time Machine Backups/Backups.backupdb/someone’s MacBook Pro/2024-06-28-094611/someone’s MacBook/Users/someone/Desktop/How-To/someone’s A B C

opens ’someone’s ABC’ folder in Finder, showing foolder contents. Further,

file:///Volumes/Time Machine Backups/Backups.backupdb/someone’s MacBook Pro/2024-06-28-094611/s’omeone’s MacBook/Users/someone/Desktop/How-To/someone’s A B C/A. StyleSheet.rtfd

opens Finder parent folder ‘someone’s ABC' window with the ‘A. StyleSheet.rtfd’ file selected, which can then be managed and updated on related devices using Finder local device and/or Finder Network access.

Conclusion, TextEdit can easily link to files and folders in our home networks using file:///path links through iCloud and through Apple Airport (or other similar connected hardware). This means that all Apple empowered software can share and support every Apple device on every Apple home network. From one device on the Apple home network, all devices can be accessed and supported with Apple macOS Textedit links to files on those systems, to share and to maintain and to demonstrate device data. Active user files are protected by the Apple Airport, but the Airport content can be managed to allow secure data management (share and maintain and demonstrate data) between any Apple Mac device using TextEdit with Airport access on the secure Apple Home Network.

No way would I remove our AirPort security, but yes of course I wonder if without Airport protection can TextEdit Finder links as modestly discussed here link through Macintosh HD disks on the home side of any Apple Network Mac device?

Grant Bennet-Alder,

We did try sharing around macOS High Sierra, but since then made sure with Apple that our professionally independent patient medical care systems NEVER connect/share IN ABSOLUTELY ANY WAY WHAT-SO-EVER. So however we independently operate through two isolated AirPorts on a 5K security fiber optic network that routes cross-device file:///path through roaming servers on other continents, we are never active together. Obviously an Engineer-level l concern, file:///path devicing encompasses far more than local passwords. Each of my query marks (?) point to global protocols, where individual activity becomes somewhat redundant. From a scientific perspective, signal parsing and sequence isolation /// standards are where all of our diverse activity must matter most. Otherwise, we are all just letters floating around in cyberspace. Makes me giddy, every day, all day. Thanks for your activity dedication. Physical chemistry in device electronics is something else, eh!

Yes thank you, the Policy is also well explained on the Apple corporate website. The Policy is why Apple is what we all enjoy today. As a health care professional, the Policy for us all feels very customary and appraise.

Actively been Shared with... in our case involves running separate device AirPorts for each User Mac behind a fiber optic friendly modem. That multi-AirPort multi-Network home network fibre environment establishes its own interesting restrictions that handily establish easily maximized AirPort bandwidth on that network. So I would caution you that actively Shared should also include the with full bandwidth restriction. For example, if you used only one AirPort for multiple devices, then compromised bandwidth will cut off file:///path connection before it even starts due to basic security on the new fiber optic system connections. AirPort bandwidth limitations on multi-AirPort-Networks make file:///path connections simple and easy. The AirPort Extreme containers literally contain shared data where Users have full control over secure access to shared data. Further, RS45 Network plugs between AirPorts and hubs and the Home Network Modem provide physical hardware isolation for each AirPort, reinforcing independent Networks under that Modem. Hardwire connections run at ten times the speed of wireless and thus default hardwired AirPorts' isolation within their unique User environments. Our world is truly Apple by design.

Just to be clear, 'Finder:' paragraph above... Type the text in TextEdit that will link to the Finder target file or folder, then select that TextEdit text link.

And Michael stresses this very clearly. Familiarization is a cultural process.

Now imagine a macOS app for browsing file:///path on the Home Network! With associated privacy controls, naturally. A new take on sibling rivalry? Teen ANGST! Ugh, it's coming.