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.
I've looked at all the "infringing" files that they link to, from a bundled zip download from the web archive, and I don't see anything that's "preconfigured to find and provide infringing copies of our Members’ film and tv content".
The most iffy is the list of categories in utils/api_uploader_v2.py but there's no category that doesn't contain works out of copyright or under a license permitting redistribution, and even if that were not the case, that would still not be tantamount to being "preconfigured to find" anything in particular.
There's also the URL of the pirate site, but google also provides it, as do some comments here...
In the defense of the falsely-assuming people the actual legally actionable bits are all the way at the end of the complaint, and the first few paragraphs sound like the MPA is alleging that merely publishing the source code of a BitTorrent tracker is itself infringement.
I swear, it's almost as if the people who work for these publisher trade groups are trying to pull aggro and look crazy.
> 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.
could easily be interpreted as "oh MPA took it down because sharing files = bad", not necessarily "their code is very specificlaly designed to analyze and collect pirated media". The companies behind this are very loose with their wording so it looks terrible.
The point of this post is to call attention to the fact that while Objective C is actually a 30-year-old language that is the foundation of the entire Apple development ecosystem, some journalist misunderstood Objective C to be something that Microsoft had produced, and his or her mistake propagated wildly across the internet.
To update that number, the new turbocharged engines required in Formula 1 since 2014 are much quieter (to some fans' dismay), maxing out around 100 dB.
Still I'd rather be listening to a 80db combustion motor spinning up and turbo whining, occasional back fires, flames from exhaust etc.. than a 80db electric buzz box ;-) I'm sure most race-car fans would agree.
Not me. I used to go to the Sinapore F1. Even with ear plugs it was painful next to the track. It wore me out and really reduced my enjoyment. I for one welcome our new electric masters. I hope Singapore is one of the first to host. I'd definitely attend.
Have you heard one? They sound pretty good - more like the scream of a gas turbine than a "buzz box".
I grew up near a F1 track during the "big bang" turbo era (1,350+HP from a 1.5 litre engine that would only last 3 alps in qualifying trim)[1]. I'm pretty sure we'll never hear engines like those in circuit races again, and I'm not sure that's a bad thing.
They are not a "Japanese company." Sony is a massive corporation in the US. Any company that wants to do business in the US needs to setup US-registered entities. There is no question of jurisdiction here.
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.
>HTML5 video wasn't uniformly supported across browsers
It's still the case, IMHO. For example, mobile devices are a lost battle, in my experience, when it comes to HTML5 video (with autoplay and without controls). So MC ends up serving the straight up GIF to them.
I hope animated WebP becomes a thing but I have my doubts. I'm not sure whether the three major browsers will support it to an extent that it's actually sensible to use animated webp.
> 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.