Thank you for your response! For now, I’ve decided not to implement offline tracking. Instead, I'll focus on monitoring file changes while my app is active, which seems to be working well by simply watching for file system events. If I eventually need a more integrated solution, I’ll definitely consider the Replicated File Provider extension API, as you suggested. It makes sense that direct integration with the file system would offer the most reliable tracking. I really appreciate your help, thanks again!

Here’s a refined version of your forum response: First of all, thank you for the prompt response. I understand the potential issues with hardlinks, and I'm now questioning whether they are the best solution for my needs. Let me explain my requirements more clearly, and perhaps you could suggest a better approach. I'm developing an app that functions similarly to Google Drive, with the following basic user flow: The user selects a location on their filesystem where all files from the web platform will be stored. Once the setup is complete, the app continuously monitors all file and folder changes (such as additions, deletions, renaming, moving, and editing). Every minute, the app syncs these changes with the remote platform. The app is built using Electron, with file tracking managed by a Node.js library. The main reason I was considering hardlinks is to preserve file changes when the app is offline, particularly for tracking file moves and renames. However, as you pointed out, hardlinks may not be reliable for handling file updates, as different apps manage updates in various ways, which could break the hardlinks. A key aspect of my application is that files are versioned on the remote platform, and I need to maintain this versioning even when the app is offline. I think bookmarks might fit my use case, but I'd prefer a cross-platform solution, and I'm concerned that bookmarks may not be supported across different operating systems. Do you have any other suggestions on how I could address this issue?