Hi Romanz, thanks very much for the explanation. Paragon implementing it that way makes sense so it's a properly compliant implementation. What would be good then, is for BTSync to know about the filesystems that are in play and utilise the correct behaviour. I assume that if the destination was running on OSX, then BTSync would use an appropriate method for alternate streams and things would work? Maybe there's a feature idea there. To handle accessing streams differently if the destination filesystem does not adhere to the ":stream" format. That would require some other way to access alternate streams on Windows and I'm not sure there is one. I really, really wanted to use BTSync but this is sort of buggering me up a bit. If I went and made sure my filenames were NTFS compatible, would all the extended attributes sync and restore correctly? Thanks