Re:Condoleezza Rice Joins Dropbox’s Board As It Names New CF...
by donatj on Thursday April 10, 2014 @09:43AM
(#7565960)
Do any Dropbox alternatives support Mac resource forks? That's the biggest reason I stick with them, as even Google Drive doesn't.
[ Parent
| on HN ]
Re:Condoleezza Rice Joins Dropbox’s Board As It Names New CF...
by peerbreed on Thursday April 10, 2014 @11:20AM
(#7566904)
You may want to look into Owncloud. It's opensource. You can run it from your own server or host it elsewhere. They do have clients for MAC and IOS. I'm not a MAC user personally, but I do believe they support MAC resource forks. You can also access your information through any web browser as well. I've been running it off my personal server for a while now. I am completely satisfied with the software.
Re:Condoleezza Rice Joins Dropbox’s Board As It Names New CF...
by jonstewart on Thursday April 10, 2014 @09:56AM
(#7566071)
Is there any Mac software that actually uses resource forks these days???
Re:Condoleezza Rice Joins Dropbox’s Board As It Names New CF...
by donatj on Thursday April 10, 2014 @10:57AM
(#7566667)
Finder. Tags / Colors / File comments are stored in resource forks. I tag a lot of my work with things like "done" and "in progress" etc. It's really important to my workflow.
Re:Condoleezza Rice Joins Dropbox’s Board As It Names New CF...
by jonstewart on Thursday April 10, 2014 @11:16AM
(#7566862)
Oh. Huh. Didn't realize that.
Re:Condoleezza Rice Joins Dropbox’s Board As It Names New CF...
by mhurron on Thursday April 10, 2014 @12:53PM
(#7567790)
Everything? Aren't file associations on OS X still stored in the resource fork?
I remember trying to move some designers to a NFS share off of a netatalk fileserver and they flipped out when neither they nor their Mac knew what to open files in.
Re:Condoleezza Rice Joins Dropbox’s Board As It Names New CF...
by jonstewart on Sunday April 13, 2014 @09:50AM
(#7581297)
netatalk, hooboy, that brings back memories.
Classic MacOS X stored the type and creator codes in the resource fork. Early versions of MacOS X discouraged this, but preserved and respected the codes if they were present. 10.6 Snow Leopard killed them off with the UTI (an unfortunate acronym) framework.
http://www.roughlydrafted.com/2009/09/22/inside-snow-leopard...