putting colons in your filenames are almost as weird as alternate data streams.
Long extensions and multiple dots are perfectly valid in Windows filenames. I use them all the time.
They're not like colon which has a special meaning referencing alternate streams.
Even in managed code tools, it's this way. For instance, in C#, a statement like this:
File.WriteAllText(@"c:\test.txt:teststream", "AFS test");
Will error with "path format is not supported". There's no way to access ADS natively in .NET. The only way to access ADS is to evoke native Win32 methods.
e.g. Get-Content -Path foo -Stream bar