dmaz

Reading the complaint, it's clear their focus is not on generic tracker source code but on copyrighted file metadata being preloaded into the tracker source code:

> The identified files and code are preconfigured to find and provide infringing copies of our Members’ film and tv content to Nyaa.si users in violation of copyright law.

This is a larger factor for me than is given weight by car reviewers (with the exception of Consumer Reports' negative reviews of Ford SYNC). Knowing how much better car interfaces can and will be, I have steered clear of the current crop.

Excellent! I had this same idea in 2011, kudos on the execution! The size difference between animated GIF and actual video codecs is vast and the idea seemed obvious. I made a quick mashup with ffmpeg+Django (I'd use Go/MongoDB for web instead of Django these days.)

HTML5 video wasn't uniformly supported across browsers (and remember Google announced Chrome would drop h.264 around that time) and I didn't get positive responses on the idea. Maybe with more tools to support HTML5 video in animated GIF use cases and educational tools showing the difference in loading times and encoding algorithms this idea could take hold.

Also the WebP engineers have developed an animated WebP format which I disagree with but could be a step toward breaking GIF's monopoly on short animations.

It also prints to the log upon starting a 32-bit server.

For Linux the script is doing "if chrome, else if firefox". Better to use xdg-open.

Skimming through the page, Amazon is going for a landgrab too with 76 gTLDs. Interesting to see how the major web player prioritized this. Microsoft went for 11 highly relevant gTLDs and Facebook for none.

Go can be debugged with gdb > 7.1 and is profiled with pprof.