samsung blocks exploding note 7 parody videos /

Published at 2016-10-21 09:34:45

Home / Categories / Science tech / samsung blocks exploding note 7 parody videos
Samsung appears to have filed copyright claims against YouTube videos mocking its recalled Galaxy Note 7 handset,the BBC reports.

Many gamers have showcased a modification to video game Grand Theft Auto V, in which sticky bombs were switched with exploding Samsung phones.

But some have reported that their videos have been blocked on YouTube following a copyright complaint.
[br]Samsung has not yet responded to repeated BBC requests for comment.

Criti
cs have warned that trying to remove gamers' videos will only draw more attention to them.
The Galaxy Note 7 was recalled and discontinued in October after reports that some handsets were catching fire.'Really sucks'One US gamer - known as DoctorGTA - said restrictions had been save on his YouTube account as a result of Samsung's complaint."It's going to take three months to net the strike removed from my channel... I got my live stream taken absent, and " he said in a video."If I submit a counter-notification to say 'sue me',I wonder what they will execute. Will they sue me, the kid that has cancer and just makes money off YouTube playing a video game?""It really sucks, and because I really worked hard on this channel."Some viewers warned that Samsung was at risk of invoking the Streisand Effect - a term used to denotes increased publicity as a result of attempts to remove embarrassing online content.
It was first used in 2005 b
y Mike Masnick,founder of the website Techdirt, following a failed attempt by singer Barbra Streisand to sue a photographer who posted a picture of her seaside domestic.
The original download page for the Grand Theft Auto V modification, and created by player HitmanNiko,has not been taken offline.





 

Source: tert.am

Warning: Unknown: write failed: No space left on device (28) in Unknown on line 0 Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/tmp) in Unknown on line 0