Now? The person who is receiving the link has to go to a web page, then click download. It's an unnecessary extra step and a downgrade in the user experience.
Even worse, it's now harder to keep track of what you have shared and what you don't.
From DB's perspective this is most likely to force additional eyeballs onto their product by forcing them to hit a webpage before download, but it's a lousy user experience for all involved. To the receiver of the link DB just looks like an old fashioned file-sharing site a la megaupload and not something special.
How do the direct links help DB look "special"? To me, they scream "generic CDN".
https://dl.dropbox.com/u/9910153/20111022_131203.jpg
looks more or less identical to:
http://i1.kym-cdn.com/entries/icons/original/000/000/720/180...
Both are direct links, and neither tell you much about the site that you're downloading the pictures from. The indirect link actually tells people that Dropbox exists as a service. Whether that's better for the end user or not isn't relevant to what I said.
https://www.dropbox.com/s/s3wlvb7h36o5uvb/20111022_131203.jp...
There are your two links. One is a public folder the other is not.
One takes you to a web browser before you can even get the link. One does not.
Guess which one I would rather have. And now guess which one they are removing :(
But clearly a) if it ends on .jpg it should be an image and not html and b) the direct link should be on the html page with a fancy "Copy to Clipboard" button next to it.
But instead of (b) they are actively preventing getting a link to the image by hijacking the context menu.
https://www.dropbox.com/s/s3wlvb7h36o5uvb/20111022_131203.jp...
Magic!
https://photos-5.dropbox.com/si/xl/Y-dAUouiiTV2IbOuAMZKe2t7k...
I am not sure if it could work at all times, but you can check for the URL of the picture within the new-style dropbox page.
Which is of course not same as Public folders.