A qualification on the Blink Files provider

I started using the Blink sftp Files.app provider a little while ago, and while it is very cool, there is also something odd about it for apps that expect to access more than just the starting level in a file hierarchy, so I'm feeling a little bit of blogger's remorse over my initial enthusiasm:

With it managing my Journelly file, for instance, I was constantly getting nagged for permissions to access a resource iOS would only name with a cryptic hash value of some kind, and that seemed to do with storing the photo attachments for a given entry, which it does in a subdirectory. Every time I'd reload Journelly, it'd ask for permission to access a file it wouldn't provide a real name for, I'd grant it access to what I'd guess it meant, and then the permissions nag would go away for a while before coming back. 

So I've switched back to leveraging what I get with Tailscale anyhow: My NAS providing a Samba share to Files. No more nagging for permissions, and it all seems very smooth. The main challenge is just back to "remember to close that buffer when you're done with it." Journelly and its use of the Files ecosystem is very reliable about saying "hey, this file seems to have changed at the source" and reloading appropriately.