I have a directory with 102 files in them, all of them of the markdown (sort of)
variety. 94 of them, when inspected through the Dropbox API, present an
text/plain mime type.
However the other 8 files were transmitting a
mime type, which as a result prevented them from being uploaded/synced properly
within my application. Why was the mime type being rendered as such, despite
them containing simple Markdown? I have no idea. Maybe Dropbox's mime type
interpreter is seeing something in those documents that make it believe it's a
Lisp or Pascal file.
When I check the mime type on OSX through the command:
file --mime filename
I get what I would assume:
I'm not sure where the disconnect is. It could be on Dropbox's side. It could be
during the transmission of the file. But something to consider when filtering or
mime property through the