PC Tech World: responds

Showing posts with label responds. Show all posts

Monday, April 8, 2013

Sony responds to Red lawsuit with its own patent claims, seeks damages, injunction

If we've learned anything from the patent wars it's that lawsuits beget lawsuits, and Red and Sony's budding spat is no exception. In response to allegations that Sony's F5, F55 and F65 cameras violate a pair of Red camera patents, the Japanese manufacturer is filing a suit of its own. The company says that the Red One, Epic and Scarlet cameras infringe on seven Sony patents, and is seeking damages and a sales injunction on the offending products. Accessories like the REDMOTE are headed to the courtroom, too. Sony's demands aren't as specific as Red's, which originally sought to have its competitor's camera's destroyed -- but we'll sure things will heat up when litigation starts. Take a peek at Sony's brief statement after the break.

Show full PR text

Sony Comments re Patent Suit Filed Against Red Digital Cinema

On April 5, 2013, Sony Corporation ("Sony") sued Red Digital Cinema ("Red") for infringing 7 of Sony's patents in the United States District Court for the Central District of California. Sony believes that the Red ONE, EPIC and SCARLET cameras, various digital still and motion camera modules, and various accessories such as the REDMOTE infringe our patents. Sony is seeking both money damages and an injunction to stop the continued sale of Red's infringing products. Sony makes significant investments into the research & development of technology related to the cinema camera industry and intends to protect those investments against companies that infringe our patents.

Via: Verge, Sony Alpha Rumors

Source: Sony

Friday, February 15, 2013

NYT reporter responds to Tesla Model S data logs, impropriety accusations

Data logs of the Model S that left New York Times reporter John Broder stranded revealed a "violation of common sense" according to Tesla CEO Elon Musk, but Broder is now offering his side of the story to help make sense of the information. According to the journalist, he wasn't provided with "detailed instructions on maximizing the driving range" before his trip, and he placed roughly a dozen calls to the folks at Tesla about how he could address the car's declining range and make it to his destination. Apparently, some of the doubt-instilling data was caused by following the advice of Tesla representatives on how to maximize the vehicle's charge. For example, Broder says the auto lost a drastic amount of juice while parked in the cold over night, and a low-power one-hour charge was recommended by Tesla reps in conjunction with driving at a moderate speed to "restore" the lost power.

Broder also mentions that he didn't drive around a parking lot to run down the battery, but did so since he couldn't find the poorly-lit and unmarked Supercharger at night. New York Times Public Editor Margaret Sullivan called Musk several times throughout the day and couldn't get ahold of him, but plans to ask the company's founder to open source the logs and other information. Come Friday, Sullivan expects to have some conclusions on the matter. Click the bordering source link to see Broder's entire point-by-point response to the logs for yourself.

Source: The New York Times (1), (2)

Saturday, January 26, 2013

Facebook responds to recent app blocking criticism with policy 'clarification'

After the whole Vine kerfuffle and Yandex situation, Facebook clearly feels it has some explaining to do. Over at the site's Developer Blog, director, platform partnerships and operations Justin Osofsky would like to set some things straight about the social network's platform policies. He begins by assuring developers that most can just keep on keeping on.

Osofky adds, however,

For a much smaller number of apps that are using Facebook to either replicate our functionality or bootstrap their growth in a way that creates little value for people on Facebook, such as not providing users an easy way to share back to Facebook, we've had policies against this that we are further clarifying today

Those developers (and interested civilians) who'd like to drill down a bit further into those newly clarified policies can check the fine print in the source link below.

when.eng("eng.perm.init")