-
-
Notifications
You must be signed in to change notification settings - Fork 256
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Readable Names #157
Comments
Only if there is an automated method to get these names from somewhere else; I'm not interested in maintaining them by hand or arguing with folks on what their names should be. |
Fair enough, I'll look into that. |
This site is pretty comprehensive, what if we scraped it from here: |
Probably not without making some kind of arrangement with the site owners first. From their terms of use (https://fileinfo.com/terms):
|
😢 good catch. Ok I'll look into it more. |
Found a few more, nothing as good as the first one yet though:
And we'd have to make sure scraping is ok with those sites as well too. I also sent a message to the maintainers of the first site to see if they'd be open to sharing. |
I think I found the most promising candidate yet: https://github.com/lukaszsliwa/friendly_mime The license seems like it would allow for our purposes. |
Would you be open to PRs adding the generally accepted "readable name" for each mime-type declaration? By that I mean something similar to the
Kind of Document
column here, for example:db.json
This package (and the associated
mime-types
package) are best thing I've found as far as mapping mime types or extensions to one another and I think it would be great if we could addextension => name
andmime-type => name
to the list of available features.The text was updated successfully, but these errors were encountered: