Dropbox is taking suggestions on new features, vote for resource fork support!

Gotta have resource fork support or it will give annoying errors on a Mac when using synced files. If the files were updated, it would propagate back and kill the original.

Selective folders would be a nice-to-have. One could share the Documents folder with another system.

I vote for webdav support.

Yes, cheaper would be better. I am a huge Mac fan yet I dissed my .mac account because it's not a $99 value. And their service, which rules of course, is another $99 a year which I am not willing to pay. Flickr, at $100 for two years, gets my money much faster. I've suggested this to them and they said sorry...

My suggestion is lower the price. I'm not paying $99 a year for it and that's just the way the cookie crumbles.

I could use a couple more referrals if anyone still needs an account: https://www.dropbox.com/referrals/NTY4MTE4MTk

Let's try that link again:
https://www.dropbox.com/referrals/NTEwNDQ3MTU5

Dropbox is a great, free system. It replaces the need for a flashdrive, with no chance of losing it. I can work on the same files from my PC at work and my Mac at home.
If you sign up through a referral, you get 250MB extra storage for free.
Here is a link to get an additional 250 MB free storage when you sign up:
Get Dropbox

Is that resource fork thang the reason my Scrivener folders won't sync correctly if I put them in Dropbox? I tried it a few times (both originating a project in Dropbox and placing it in there after originating elsewhere), and changes got lost from machine to machine.

Of course, this would only happen with the one writing program I use. Grr.

You can voter up to 5 times, by the way...

I vote they don't waste their time or resources developing a feature that many of us, including Apple, don't need or want. Most of my work is going to be used or viewed by PC people or on web sites where the extension is key. Going back to resource forks will enable Mac users to to the same typical newby mistake of keeping files around that can't be used with other OS's, and probably future versions of MacOS.

Erm, Matt, I'm afraid you aren't really up to the most recent developments regarding the resource fork: while it is still in existence, Apple no longer uses it.

*None* of the metadata you mention is stored in the resource fork but in invisible files like the notorious .DS_Store.

So why ask for support something that is basically deprecated?