For the Azure Blob backend, rclone "creates an empty object ending with "/", to persist the folder. This object also has the metadata "hdi_isfolder = true" to conform to the Microsoft standard." However, both blobfuse (v1) and blobfuse2 use empty objects with no trailing slash to indicate a directory. rclone's approach appears to be consumable by blobfuse (v1) and Azure Storage Explorer (though that one still has a couple bits of wonky behavior), but it is outright incompatible with blobfuse2 which shows turns all of rclone's directories into empty nested directories of the same name as its parent. There's an argument to be made for blobfuse2 being the buggy software here, but given that all three of these official Microsoft products assume directory markers do not have a trailing slash, is there a compelling reason why rclone breaks that established pattern? Does anyone have any good workarounds for interoperability between rclone and blobfuse2?