Hacker News new | past | comments | ask | show | jobs | submit login

Small test. Uploaded 2 files from my mac. Output from shasum:

  bead69d062c53436f19b6577ec7b524b9aa54445  DSC_0010.JPG
  83ade975de96b81d272642740e06480fbc1484e1  DSC_0010.NEF
Downloaded each file from Amazon Prime Photos. Filenames preserved. Filesizes the same. Output from shasum:

  bead69d062c53436f19b6577ec7b524b9aa54445  DSC_0010.JPG
  83ade975de96b81d272642740e06480fbc1484e1  DSC_0010.NEF
Lock-in and missing features aside, preserving the binary data is pretty cool, and it's honestly the most important thing when picking a place to store photos (for me).

The most annoying thing was it treated the NEF and JPG files separately, and showed pictures twice in the UI.

For anyone interested, on iCloud Photo Library beta:

Downloaded off device that image was taken with via Image Capture

  3942cf85f43282ece05ee01ef82f3b245e1638e6  IMG_2273.JPG
Downloaded via iCloud.com/photos

  0271267eb3fe02a27398e20e285cf14a26333510  IMG_2273.JPG
But probably the better test will be to see how files differ between iOS devices, and the Mac Photos.app when that is released.


Running this through exiftool, the image downloaded via icloud.com/photos has the following EXIF stripped which is the likely cause of the above change:

  GPS Latitude Ref          
  GPS Longitude Ref         
  GPS Altitude Ref          
  GPS Time Stamp            
  GPS Speed Ref             
  GPS Speed                 
  GPS Img Direction Ref     
  GPS Img Direction         
  GPS Dest Bearing Ref      
  GPS Dest Bearing          
  GPS Date Stamp            
  GPS Altitude  
  GPS Date/Time 
  GPS Latitude  
  GPS Longitude 
  GPS Position

Try stripping locally and see if the checksum matches.

Oddly enough, I tried but was unsuccessful:

  exiftool -gps:all= IMG_2273.JPG
ended up changing the Thumbnail Offset within that file, which is a protected EXIF item that I don't know how to change.

.NEF files are not an included extension and are not included in the unlimited storage.


I uploaded a .NEF and in the usage panel it shows I'm using 0 bytes of my 5GB and 1 photo of my unlimited photo storage.

I have nothing else on my cloud drive.

While not on that list, it seems raw files are supported

Interesting. I emailed Amazon and received this reply:

Currently the unlimited photo storage benefit includes most major image file types: JPEG, GIF, (both animated and non-animated), most common TIFFs, RAW, PNG, and BMP.

This means at this time the .nef, .rw2 and .orf will be considered as unsupported format and will count against cloud drive storage limit.

For more information about Cloud Drive Photos & Videos file requirements, go to:


I've forwarded your comments as feedback to our Amazon Cloud Drive team that you want .NEF file type images to be included in the unlimited photo storage benefit so that they aren't counted against your Cloud Storage quota. We're adding more file types to the unlimited photo storage feature, and file types not compatible now may become compatible in the future.

I just looked at http://www.amazon.com/gp/help/customer/display.html?nodeId=2... and the "Note" mentions NEF as a supported format. I am still seeing errors "File size larger than remaining quote" when I try to upload NEF files, but JPG works fine. Not sure what the disconnect is.

I'm pretty sure Dropbox doesn't change the binary data. What service changes it?

Some time ago someone posted that SkyDrive (now OneDrive) did

Disclaimer: MSFT-employed.

It's OneDrive for Business (i.e. SharePoint) that sometimes modifies uploaded files. To the best of my knowledge, OneDrive Consumer (http://onedrive.com) operates no differently than `rsync` would.


They are completely unrelated products, except for branding.

Yeah, I know. Sigh.

I've seen Microsoft employees across the web have to point this out a dozen times.

"The New Microsoft" seems to be making better decisions overall, but it apparently didn't learn anything from the early-2000s ".net branding clusterfuck" which conflated their runtime platform, development tools, consumer-facing single-sign-on, and a few dozen other things in the mind of the public.

I think you nailed it.

Perhaps out of hope but more likely Stockholm syndrome, over the last decade I seem to have got stuck in a cycle of: Blind love and hope for a new product of theirs, utter disappointment at the resulting clusterfuck after a week, hatred, switch to something else, miss it, go crawling back.

Only just broken out of this loop but to be honest it knackered my productivity badly over the years.

Ultimately I'm a sucker I suspect but the revelation that FreeBSD hadn't actually poked me in the eye once in the last decade had turned my hand finally. That and ruby.

Yes I got tangled in DNA, ATL etc as well. Nothing but regret.

because onedrive for business runs on top of SharePoint document libraries and well.. they can do some "interesting" things to files.

Same with OneNote. It has a lot of great features... and a metrick fuckload of legacy creepy crawlies under the hood.

I think the rationale was some kind of Sharepoint tagging abomination.

IIRC only OneDrive for Business (née SharePoint) did that, not the OneDrive consumers use.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact