mimemagic VS mimemagic

If you're curious, here's how I solved it for ruby back in the day. Still used magic bytes, but added an overlay on top of the freedesktop.org DB: https://github.com/mimemagicrb/mimemagic/pull/20

Get it directly from github commit.

[AO3-6152] - Due to a licensing incident with a Rails dependency known as mimemagic, we had to update Rails to 5.2.5 and mimemagic to 0.3.6.

I don't think mimemagic works on Windows after the drama. I opened a PR for that a month ago but no one seems to care: https://github.com/mimemagicrb/mimemagic/pull/141

"License, motherfucker"

I know the vulgarity of the statements is tongue in cheek, but this one has been reinforced lately by the "MIME Magic" debacle[1], mama mia.

[1] https://github.com/mimemagicrb/mimemagic/issues/98

it has a licensing issue

https://github.com/mimemagicrb/mimemagic/commit/749a7e59de480b7c0373acc4f8ceb4444352ba46#diff-2ea7e2364883967953ab518a8316b639e612b8a6f20eadb7b97939d91c8e2612

On the other hand mimemagic provides by_magic https://github.com/mimemagicrb/mimemagic#usage which does detection by heuristic. It's a radically different method for a radically different use case.

Anyway, I created a PR addressing new Mimemagic not working on Windows https://github.com/mimemagicrb/mimemagic/pull/141

Someone broke the internet for rails https://github.com/mimemagicrb/mimemagic/issues/98

As such I think some sort of agreement along the lines of "please give me some time" could've worked. To further illustrate that, there's a similar issue for a different project, created on February 22nd. It wasn't until 2 days ago, one month after creating said issues, that a DMCA notice was filed. And based on the discussion, the only reason for this was the authors of zRedShift not cooperating.