Tag Archives: twitter

Twitter Copyright Notices Have Doubled in Half a Year

Post Syndicated from Ernesto original https://torrentfreak.com/twitter-copyright-notices-have-double-in-half-a-year-191101/

In common with many other online services, copyright holders regularly ask Twitter to remove tweets that link to pirated material.

Whether it’s a tweet from the U.S. President or some random pirate site, the social media platform investigates the claims and takes action, if needed.

A few hours ago Twitter published a new update to its transparency report, highlighting the latest takedown trends. This reveals that the number of copyright notices received during the first half of the year skyrocketed compared to the previous six months.

“We received a 101% increase in DMCA takedown notices since our last report,” Twitter reports, noting that this includes a high volume of fraudulent DMCA notices from Turkey and Japan.

From January to June of this year a total of 106,951 DMCA notices were received, compared to 53,094 during the last half of 2018. This is a notable increase. However, it doesn’t directly translate to an equal change in removed tweets or withheld content.

The number of tweets that were removed increased by 46% to 113,015. At the same time, there was a 4% decrease in withheld media in the same period, 266,699 files in total.

This suggests that the average notice today includes fewer tweets and media files.

The percentage of notices for which Twitter took action also dropped significantly. On average, less than half of the notices (45%) resulted in material being removed, down from 62% last period.

The above applies to notices that were sent to Twitter, but the company also owns and operates Periscope. The number of copyright notices received by the streaming platform increased by roughly ten percent to 26,331 over the past six months.

Taken together, more than a third of the Twitter and Periscope copyright notices were sent in by a handful of reporters. Music industry group IFPI is the most prolific sender, followed by Netresult, LeakID, Athletia Sports and LaLiga.

The most spectacular increase we see in the report is the number of counternotices that were submitted by people who disputed a copyright claim. This number jumped 285% to 3,966.

This uptick is in part linked to an increase in fraudulent DMCA notices, which Twitter also highlights in its report. The company says that it will continue to keep a close eye on this trend and has put safeguards in place to help protect people on Twitter and Periscope.

Earlier this year TorrentFreak was also hit by inaccurate DMCA takedown complaints, targeting our news coverage. American entertainment giant Starz removed ours and several other tweets, pointing to an article about leaked TV-shows.

While Twitter accepted these takedowns, the reporting organization lifted the claim after we and many others complained.

Twitter’s complete transparency report, which also addresses trademark notices, information requests, rules enforcement, and other removal requests, is available here.

Source: TF, for the latest info on copyright, file-sharing, torrent sites and more. We also have VPN reviews, discounts, offers and coupons.

Twitter Suspends Trump Meme Creator…But Not For the ‘Kingsman’ Bloodbath Video

Post Syndicated from Andy original https://torrentfreak.com/twitter-suspends-trump-meme-creator-but-not-for-the-kingsman-bloodbath-video-191015/

There was uproar in the media this past weekend after a violent video meme was reportedly shown at a pro-Trump conference.

The video, a doctored version of the famous church scene from the movie Kingsman, depicts Trump killing his critics, from both the media and politics.

The video was made by TheGeekzTeam, an entity that creates content for a website run by Carpe Donktum, a prolific pro-Trump supporter and meme-maker. During the fallout on Monday, Carpe Donktum’s Twitter account was suspended, an event which led various media outlets to connect the events of the weekend with the suspension.

A Twitter spokesperson effectively confirmed that the suspension was DMCA related, noting that it responds to “valid copyright complaints sent us by a copyright owner or their authorized representatives.”

Twitter made no mention of which content had caused the suspension but the actual DMCA notice obtained by TorrentFreak confirms it had nothing to do with the ‘Kingsman’ meme published over the weekend.

The DMCA notice, served not only against Carpe Donktum’s Twitter account but also around two dozen others, was actually filed by Universal Music Group. The offending Twitter URL is highlighted below.

The Tweet in question dates back to February 5, 2018, and remains online, along with the text “In case you missed the T-Mobile Superbowl Commercial. Here it is!” However, the embedded video has been removed, indicating that this was the source of the DMCA complaint.

Comparing uploads on Carpe Donktum’s YouTube account on the very same day we find a video entitled “T-Mobile Superbowl Commercial Fixed“, which is a doctored version of T-Mobile’s official Superbowl commercial.

It’s pretty clear why Carpe Donktum’s video was taken down. While it contains other copyrighted music throughout not contained in the original video (a lullaby rendition of Nirvana’s ‘All Apologies’ according to Shazam), it’s the last 14 seconds of the 80-second video causing the problems.

With Trump wearing a ‘Thug Life’ hat, obligatory sunglasses and sporting a huge joint in his mouth, the track ‘Ultimate’ by Denzel Curry booms from the video. This isn’t what Universal Music wanted and judging by comments made by Curry in 2017, it probably isn’t what he wanted either.

“I felt like I was part of the problem honestly. Being disillusioned and thinking, ‘nah, that’s not gonna happen, this nigga ain’t gonna be president.’ Then this nigga became president. So what the fuck just happened? I don’t get all the choices I want, but I definitely didn’t want this nigga to be my president,” Curry said.

One copyright complaint isn’t usually enough for Twitter to suspend an account but Carpe Donktum now has at least three against his. In addition to the notice sent Monday, two others are on record, one sent in April and another in June. Only the one sent by Universal Music has a listed sender, the other two have their details redacted.

Carpe Donktum’s Twitter account has now been restored but for how long remains open to question and probably dictated by future conduct.

Source: TF, for the latest info on copyright, file-sharing, torrent sites and more. We also have VPN reviews, discounts, offers and coupons.

Trump’s Sons, Attorney, & Social Media Chief All Got DMCA Notices Over ‘Photograph’ Meme

Post Syndicated from Andy original https://torrentfreak.com/trumps-sons-attorney-social-media-chief-all-got-dmca-notices-over-photograph-191008/

Last week, US President Donald Trump made headlines when he tweeted a short video meme aimed at discrediting political rival Joe Biden.

It contained a clip of Nickelback’s video ‘Photograph’ which resulted in the tweet being taken down for copyright infringement.

Soon after, a copy of the DMCA notice that caused the takedown was published on the Lumen Database, which revealed that the sender was Warner Music Group. However, TF has learned that wasn’t the only takedown notice to target Trump and his supporters over the now-controversial clip.

Trawling through the latest notices sent to Lumen by Twitter we can see that not only were some of Trump’s closest allies also sent takedowns for copyright infringement, but also that other music companies got in on the act too.

The original complaint against Trump’s account (here) was quickly followed by another against the account of his attorney, Rudy Giuliani. The notice was sent by Nickelback’s management at Union Entertainment Group on behalf of Roadrunner Records, which in turn is owned by Warner.

As the DMCA notice below shows, the cited copyrighted material is “The Master Recording of ‘Photograph’ by Nickelback and the accompanying music video.”

Two other DMCA complaints were also filed at Twitter detailing a pair of allegedly-infringing tweets posted Trump’s son, Donald Trump Jr. and Dan Scavino, the White House Director of Social Media and Assistant to the President.

These were sent on October 3, 2019 by anti-piracy company GrayZone on behalf of Warner Music. In common with the complaint filed against their father’s account, YouTube was cited as the source of the material.

Finally, the second son of Donald Trump, Eric, also received an additional notice from Union Entertainment Group, again on behalf of RoadRunner Records.

While plenty of other people tweeted and retweeted the allegedly-infringing video, a flood of additional takedown notices doesn’t appear to be in the archives at Lumen. That doesn’t mean to say they don’t exist, however, since it’s certainly possible Twitter doesn’t pass everything on.

Interestingly, there is an ongoing debate as to whether the use of the video in the clip was actually fair use, with many Trump supporters claiming that as a parody, it should be protected from takedowns. Countering firmly, former RIAA executive vice president of communications Jonathan Lamy believes otherwise.

“This one was a clear cut no-brainer,” he said on Twitter. “On copyright grounds and also perhaps falsely implied endorsement.”

Since Giuliani also got a notice and presumably a strike against his Twitter account, it would be very interesting if – as an attorney – he decided to send a counter-notification. As fair use battles go it might get a little messy but things are pretty messy already.

Source: TF, for the latest info on copyright, file-sharing, torrent sites and more. We also have VPN reviews, discounts, offers and coupons.

DMCA Notice Confirms Trump Tweet Was Taken Down By Warner Music

Post Syndicated from Andy original https://torrentfreak.com/dmca-notice-confirms-trump-tweet-was-taken-down-by-warner-music/

President of the United States Donald Trump is well-known for his love of Twitter.

He currently has well in excess of 65 million followers and regularly uses the platform to promote himself and attack his critics.

Earlier today, Twitter erupted when a tweet by the President, which contained a video attacking the integrity of political rival Joe Biden, received some serious editing thanks to Twitter.

While the words “LOOK AT THIS PHOTOGRAPH!” remained, the actual video had been removed following a copyright infringement complaint.

No photograph to see…

Trump’s tweet contained a video that has been doing the rounds featuring a photograph central to the recent Biden/Ukraine controversy. However, the photograph itself wasn’t the reason the video was taken down by Twitter.

The viral video contains a clip from Nickelback’s 2005 video ‘Photograph’, prompting speculation that the band itself was behind the takedown sent to Twitter. While they may have had a hand in it, the actual DMCA served on Twitter and obtained by TorrentFreak reveals that the notice was sent by Warner Music.

The DMCA notice sent to Twitter by Warner Music (Lumen Database)

The cited source material for the takedown indeed points to the ‘Photograph’ video on YouTube, confirming the Nickelback link to the takedown.

Unfortunately, if Trump wanted to legally use the track in a political context, this would usually mean requesting permission from not only the publisher but also Nickelback, who may or may not wish to be associated with the effort. The copyright takedown suggests that the required pieces probably weren’t in place.

Perhaps the most interesting thing when one ignores the political angle of Trump’s tweet is that the President has been in this and similar positions several times before.

The Lumen Database, a repository to which Twitter sends its takedown notices, currently lists at least seven DMCA complaints filed against Trump this year alone, all of which have resulted in the removal of content.

On the other hand, people receiving DMCA notices from the IFPI, which acts as a copyright enforcer for Warner on Twitter and elsewhere, get their accounts terminated for fewer strikes. Perhaps there’s a presidential exemption from the DMCA repeat infringer policy at Twitter.

Notices filed against Trump on Twitter in 2019 can be found here 1,2,3,4,5,6,7 (pdf)

Source: TF, for the latest info on copyright, file-sharing, torrent sites and more. We also have VPN reviews, discounts, offers and coupons.

The age of the Twitter bot

Post Syndicated from Alex Bate original https://www.raspberrypi.org/blog/the-age-of-the-twitter-bot/

Despite changes to the process, setting up a Raspberry Pi as a Twitter bot is a fairly easy process. And while many such bots simply share time-lapse snapshots, or change the colour of LEDs across the globe, we know some that fill our timelines with fun, random joyfulness of a daily basis. Here are a few of them:

@DaphneFlap

Celebrated by cat worshippers the world over, Daphne’s Catflap documents the comings and goings of Daphne, the fluffy feline housemate of Kate Bevan. While my own cat is now too big to fit through his catflap, Daphne uses her catflap several times a day, and thanks to the Raspberry Pi connected to it, the catflap does a marvellous job of celebrating Daphne every time she graces us with her presence.

Daphne’s Catflap on Twitter

Adored Daphne, graceful empress of floof, floofybum. No adoring catflap could possibly be more blessed than me.

@raspberrypi_otd

Ben made a thing.

The Raspberry Pi OTD Twitter bot shares past posts from this very blog you are reading RIGHT NOW, and thus traces the evolution of Raspberry Pi through its tweets. One day, probably in twelve months, this very blog post will resurface on the Raspberry Pi OTD timeline, and then we shall all meet back here and say hi.

Raspberry Pi OTD on Twitter

On this day in 2015: Raspberry Pi Zero: the $5 computer https://t.co/1GRhq0TYuz

@randspberrypi

Sharing posts generated by Rand’s Raspberry Pi, this twitter bot posts random GIF-packed tweets, usually with a retro 1980s vibe and the hashtags #80s, #MusicVideo, #GIF, and #raspberrypi

Rand’s RaspberryPi on Twitter

Random #80s #MusicVideo #GIF #raspberrypi https://t.co/ieraOHGFjr

@falalala_la

Though it seems to be taking a hiatus right now, the Deck the Halls bot searches Twitter for tweets that fit perfectly to the tune of Deck the Halls, and retweets these with the classic “Falalalala, la la, la la!” as a comment. Be warned, a few of the tweets it recovers may be NSFW, but on the whole, it’s a joyful, joyful experience.

Deck the Halls on Twitter

Falalalala, la la, la la! https://t.co/r2dkE8wMFm

@bert_the_plant

I promise we haven’t killed him.

Bert is a ficus tree that lives in one of the meeting rooms here at Pi Towers. When connected to the internet, his Raspberry Pi and moisture monitor update followers about whether he needs watering, alongside a photo of his current state. And while his last tweet, dated 10 June 2017, claims he’s “so thirsty”, accompanied by a photo of pure darkness, I assure you this is simply because the light was off…and the Pi has since been unplugged…and Bert’s alive, I swear it, I swear!

Hold on, I just need to go for a walk to Meeting Room 5. No reason. *runs*

Bert Plant on Twitter

I’m so thirsty!

Connecting your Raspberry Pi to Twitter

The process of setting up a Developer Account so you can build your own Twitter bot has changed recently. But once you follow their new steps, you can still use our free resources for connecting your Raspberry Pi to Twitter.

In our Tweeting Babbage resource, you will learn how to write code that sends images from your Pi to the Twittersphere.

And if you’re a more experienced coder, you could try your hand at our Naughty and nice resource, which will walk you through creating a program that checks whether a Twitter user is in Santa’s good or bad books. After all, Christmas is just under a month away!

Santa angrily staring at a Twitter account

And from there, the world (the Twitter world at least) is your oyster.

The post The age of the Twitter bot appeared first on Raspberry Pi.

AWS Resources Addressing Argentina’s Personal Data Protection Law and Disposition No. 11/2006

Post Syndicated from Leandro Bennaton original https://aws.amazon.com/blogs/security/aws-and-resources-addressing-argentinas-personal-data-protection-law-and-disposition-no-112006/

We have two new resources to help customers address their data protection requirements in Argentina. These resources specifically address the needs outlined under the Personal Data Protection Law No. 25.326, as supplemented by Regulatory Decree No. 1558/2001 (“PDPL”), including Disposition No. 11/2006. For context, the PDPL is an Argentine federal law that applies to the protection of personal data, including during transfer and processing.

A new webpage focused on data privacy in Argentina features FAQs, helpful links, and whitepapers that provide an overview of PDPL considerations, as well as our security assurance frameworks and international certifications, including ISO 27001, ISO 27017, and ISO 27018. You’ll also find details about our Information Request Report and the high bar of security at AWS data centers.

Additionally, we’ve released a new workbook that offers a detailed mapping as to how customers can operate securely under the Shared Responsibility Model while also aligning with Disposition No. 11/2006. The AWS Disposition 11/2006 Workbook can be downloaded from the Argentina Data Privacy page or directly from this link. Both resources are also available in Spanish from the Privacidad de los datos en Argentina page.

Want more AWS Security news? Follow us on Twitter.

 

Pravda-та на Мъск

Post Syndicated from nellyo original https://nellyo.wordpress.com/2018/06/02/pravda/

Елон Мъск споделя в Twitter идеята да създаде нова медия – “crowdsourced site”, наречен Pravda – който според Мъск би позволил на обществеността  “да оцени  истината във всяка статия и  доверието към всеки журналист, редактор и публикация.” Дори репортери са открили заявление за вписване на търговско дружество Pravda Corp.

Мнозина правят паралел между Мъск и Тръмп – заради определянето на негативни новини за тях като фалшиви  и отрицателната оценка за новинарските медии като цяло.

Pravda е много, много лоша идея, се казва в коментар на The Verge: Мъск, както и Тръмп, може да не харесва начина, по който го представят – или като жертва, или като провал – но вие не можете да законодателствате достоверността, нито да  я подлагате на гласуване – и да очаквате някакъв друг резултат, освен дистопия. Неинформираното общество е общество, което може да бъде подведено  да вярва в каквото и да е – че земята е плоска и че човек не е кацал на Луната –  и това е много опасно нещо в ръцете на мотивиран субект.  Особено ако се съчетае с ехо-ефекта на платформите, може да подкопае доверието във всеки източник, който си позволява  да влезе в конфликт с този субект.

Голямата тема не е Мъск,  голямата тема е манипулирането на общественото мнение – и възможното противодействие.

Обществена оценка какво е вярно  е на една крачка от  обществената оценка какво е правилно да се направи – и обяснява резултатите от някои избори и референдуми.

Protecting coral reefs with Nemo-Pi, the underwater monitor

Post Syndicated from Janina Ander original https://www.raspberrypi.org/blog/coral-reefs-nemo-pi/

The German charity Save Nemo works to protect coral reefs, and they are developing Nemo-Pi, an underwater “weather station” that monitors ocean conditions. Right now, you can vote for Save Nemo in the Google.org Impact Challenge.

Nemo-Pi — Save Nemo

Save Nemo

The organisation says there are two major threats to coral reefs: divers, and climate change. To make diving saver for reefs, Save Nemo installs buoy anchor points where diving tour boats can anchor without damaging corals in the process.

reef damaged by anchor
boat anchored at buoy

In addition, they provide dos and don’ts for how to behave on a reef dive.

The Nemo-Pi

To monitor the effects of climate change, and to help divers decide whether conditions are right at a reef while they’re still on shore, Save Nemo is also in the process of perfecting Nemo-Pi.

Nemo-Pi schematic — Nemo-Pi — Save Nemo

This Raspberry Pi-powered device is made up of a buoy, a solar panel, a GPS device, a Pi, and an array of sensors. Nemo-Pi measures water conditions such as current, visibility, temperature, carbon dioxide and nitrogen oxide concentrations, and pH. It also uploads its readings live to a public webserver.

Inside the Nemo-Pi device — Save Nemo
Inside the Nemo-Pi device — Save Nemo
Inside the Nemo-Pi device — Save Nemo

The Save Nemo team is currently doing long-term tests of Nemo-Pi off the coast of Thailand and Indonesia. They are also working on improving the device’s power consumption and durability, and testing prototypes with the Raspberry Pi Zero W.

web dashboard — Nemo-Pi — Save Nemo

The web dashboard showing live Nemo-Pi data

Long-term goals

Save Nemo aims to install a network of Nemo-Pis at shallow reefs (up to 60 metres deep) in South East Asia. Then diving tour companies can check the live data online and decide day-to-day whether tours are feasible. This will lower the impact of humans on reefs and help the local flora and fauna survive.

Coral reefs with fishes

A healthy coral reef

Nemo-Pi data may also be useful for groups lobbying for reef conservation, and for scientists and activists who want to shine a spotlight on the awful effects of climate change on sea life, such as coral bleaching caused by rising water temperatures.

Bleached coral

A bleached coral reef

Vote now for Save Nemo

If you want to help Save Nemo in their mission today, vote for them to win the Google.org Impact Challenge:

  1. Head to the voting web page
  2. Click “Abstimmen” in the footer of the page to vote
  3. Click “JA” in the footer to confirm

Voting is open until 6 June. You can also follow Save Nemo on Facebook or Twitter. We think this organisation is doing valuable work, and that their projects could be expanded to reefs across the globe. It’s fantastic to see the Raspberry Pi being used to help protect ocean life.

The post Protecting coral reefs with Nemo-Pi, the underwater monitor appeared first on Raspberry Pi.

Amazon Neptune Generally Available

Post Syndicated from Randall Hunt original https://aws.amazon.com/blogs/aws/amazon-neptune-generally-available/

Amazon Neptune is now Generally Available in US East (N. Virginia), US East (Ohio), US West (Oregon), and EU (Ireland). Amazon Neptune is a fast, reliable, fully-managed graph database service that makes it easy to build and run applications that work with highly connected datasets. At the core of Neptune is a purpose-built, high-performance graph database engine optimized for storing billions of relationships and querying the graph with millisecond latencies. Neptune supports two popular graph models, Property Graph and RDF, through Apache TinkerPop Gremlin and SPARQL, allowing you to easily build queries that efficiently navigate highly connected datasets. Neptune can be used to power everything from recommendation engines and knowledge graphs to drug discovery and network security. Neptune is fully-managed with automatic minor version upgrades, backups, encryption, and fail-over. I wrote about Neptune in detail for AWS re:Invent last year and customers have been using the preview and providing great feedback that the team has used to prepare the service for GA.

Now that Amazon Neptune is generally available there are a few changes from the preview:

Launching an Amazon Neptune Cluster

Launching a Neptune cluster is as easy as navigating to the AWS Management Console and clicking create cluster. Of course you can also launch with CloudFormation, the CLI, or the SDKs.

You can monitor your cluster health and the health of individual instances through Amazon CloudWatch and the console.

Additional Resources

We’ve created two repos with some additional tools and examples here. You can expect continuous development on these repos as we add additional tools and examples.

  • Amazon Neptune Tools Repo
    This repo has a useful tool for converting GraphML files into Neptune compatible CSVs for bulk loading from S3.
  • Amazon Neptune Samples Repo
    This repo has a really cool example of building a collaborative filtering recommendation engine for video game preferences.

Purpose Built Databases

There’s an industry trend where we’re moving more and more onto purpose-built databases. Developers and businesses want to access their data in the format that makes the most sense for their applications. As cloud resources make transforming large datasets easier with tools like AWS Glue, we have a lot more options than we used to for accessing our data. With tools like Amazon Redshift, Amazon Athena, Amazon Aurora, Amazon DynamoDB, and more we get to choose the best database for the job or even enable entirely new use-cases. Amazon Neptune is perfect for workloads where the data is highly connected across data rich edges.

I’m really excited about graph databases and I see a huge number of applications. Looking for ideas of cool things to build? I’d love to build a web crawler in AWS Lambda that uses Neptune as the backing store. You could further enrich it by running Amazon Comprehend or Amazon Rekognition on the text and images found and creating a search engine on top of Neptune.

As always, feel free to reach out in the comments or on twitter to provide any feedback!

Randall

Директивата за авторско право: ход на ревизията: да се действа сега

Post Syndicated from nellyo original https://nellyo.wordpress.com/2018/05/26/copyright-5/

Ново развитие в ревизията на авторското право в ЕС – става ясно от  съобщенията на българското председателство, участници в ревизията и Юлия Реда – защото тя имаше много ясен възглед какво иска да се промени в правната рамка (общ режим на изключенията, актуализиране – за да имаме правна рамка, адекватна на технологичното развитие) – и сега следи ангажирано законодателния процес.

Правителствата на държавите от ЕС  са приели позиция  относно реформата на авторските права  без съществени промени по чл.11 (новото право за издателите)  и чл.13 (филтрите на входа), проектът е на сайта на Реда,  Politico дава измененията, засягащи правото на издателите, в цвят.

Сега Парламентът трябва да ги спре, пише Реда.

 Сега имате шанса да окажете влияние – шанс, който ще изчезне след две години, когато всички “изведнъж” ще се сблъскат с предизвикателството да се  внедряват филтри   и link tax.  Експертите почти единодушно се съгласяват, че проектът за реформата на авторското право е наистина лош.

Update: Member State governments have just adopted their position on #copyright, with no significant changes to the #CensorshipMachines and #LinkTax provisions. It is now up to Parliament to stop them and #FixCopyright. https://t.co/1JwNvQn24n pic.twitter.com/KAgqV3YYG1

https://platform.twitter.com/widgets.js

Две графики от сайта на Реда – за двата текста,  против които се събира подкрепа (вж и преподавателите) – за  отношението по държави и по партии в ЕП:

 

 

Прозрачност на политическата реклама

Post Syndicated from nellyo original https://nellyo.wordpress.com/2018/05/26/polit_ad_fb_twitter/

Как решавате проблем като този с руската пропаганда? Как  предпазвате от намеса в изборите? c|net информира за нови стъпки на интернет компаниите.

Отговорът на Facebook и Twitter е повече прозрачност относно политическата реклама: двете компании предприемат мерки да се вижда кой плаща политическа реклама. Google също се подготвя за подобна политика на прозрачност.

Facebook създава и архив на данните за политическа реклама на адрес facebook.com/politicalcontentads . Подобен  Ads Transparency Center  предстои да бъде създаден и в Twitter.

В САЩ има проект за закон –  the Honest Ads Act –  ако бъде приет,  прозрачността на политическата реклама онлайн ще е законово задължение.

Текст и обяснение от сайта на Конгреса, мотивите: Законът за честните реклами би попречил на чуждестранните участници да повлияят върху нашите избори, като гарантира, че политическите реклами, продавани онлайн, ще бъдат обхванати от същите правила като рекламите, продавани по телевизията, радиото и сателита.  Въвежда

  •  изискване на цифрови платформи с най-малко 50 000 000 месечни зрители да поддържат публичен архив  – всеки файл  ще съдържа цифрово копие на рекламата, описание на аудиторията, която рекламата цели, броя на генерираните показвания, датите и часовете на публикуване, таксуваните тарифи и информацията за връзка на купувача;
  • изискване  онлайн платформите да положат всички разумни усилия, за да гарантират, че чуждестранни физически и юридически лица не купуват политически реклами, за да повлияят на американския електорат.

 

Fully-Loaded Kodi Box Sellers Receive Hefty Jail Sentences

Post Syndicated from Andy original https://torrentfreak.com/fully-loaded-kodi-box-sellers-receive-hefty-jail-sentences-180524/

While users of older peer-to-peer based file-sharing systems have to work relatively hard to obtain content, users of the Kodi media player have things an awful lot easier.

As standard, Kodi is perfectly legal. However, when augmented with third-party add-ons it becomes a media discovery powerhouse, providing most of the content anyone could desire. A system like this can be set up by the user but for many, buying a so-called “fully-loaded” box from a seller is the easier option.

As a result, hundreds – probably thousands – of cottage industries have sprung up to service this hungry market in the UK, with regular people making a business out of setting up and selling such devices. Until three years ago, that’s what Michael Jarman and Natalie Forber of Colwyn Bay, Wales, found themselves doing.

According to reports in local media, Jarman was arrested in January 2015 when police were called to a disturbance at Jarman and Forber’s home. A large number of devices were spotted and an investigation was launched by Trading Standards officers. The pair were later arrested and charged with fraud offenses.

While 37-year-old Jarman pleaded guilty, 36-year-old Forber initially denied the charges and was due to stand trial. However, she later changed her mind and like Jarman, pleaded guilty to participating in a fraudulent business. Forber also pleaded guilty to transferring criminal property by shifting cash from the scheme through various bank accounts.

The pair attended a sentencing hearing before Judge Niclas Parry at Caernarfon Crown Court yesterday. According to local reporter Eryl Crump, the Court heard that the couple had run their business for about two years, selling around 1,000 fully-loaded Kodi-enabled devices for £100 each via social media.

According to David Birrell for the prosecution, the operation wasn’t particularly sophisticated but it involved Forber programming the devices as well as handling customer service. Forber claimed she was forced into the scheme by Jarman but that claim was rejected by the prosecution.

Between February 2013 and January 2015 the pair banked £105,000 from the business, money that was transferred between bank accounts in an effort to launder the takings.

Reporting from Court via Twitter, Crump said that Jarman’s defense lawyer accepted that a prison sentence was inevitable for his client but asked for the most lenient sentence possible.

Forber’s lawyer pointed out she had no previous convictions. The mother-of-two broke up with Jarman following her arrest and is now back in work and studying at college.

Sentencing the pair, Judge Niclas Parry described the offenses as a “relatively sophisticated fraud” carried out over a significant period. He jailed Jarman for 21 months and Forber for 16 months, suspended for two years. She must also carry out 200 hours of unpaid work.

The pair will also face a Proceeds of Crime investigation which could see them paying large sums to the state, should any assets be recoverable.

Source: TF, for the latest info on copyright, file-sharing, torrent sites and more. We also have VPN reviews, discounts, offers and coupons.

AWS GDPR Data Processing Addendum – Now Part of Service Terms

Post Syndicated from Chad Woolf original https://aws.amazon.com/blogs/security/aws-gdpr-data-processing-addendum/

Today, we’re happy to announce that the AWS GDPR Data Processing Addendum (GDPR DPA) is now part of our online Service Terms. This means all AWS customers globally can rely on the terms of the AWS GDPR DPA which will apply automatically from May 25, 2018, whenever they use AWS services to process personal data under the GDPR. The AWS GDPR DPA also includes EU Model Clauses, which were approved by the European Union (EU) data protection authorities, known as the Article 29 Working Party. This means that AWS customers wishing to transfer personal data from the European Economic Area (EEA) to other countries can do so with the knowledge that their personal data on AWS will be given the same high level of protection it receives in the EEA.

As we approach the GDPR enforcement date this week, this announcement is an important GDPR compliance component for us, our customers, and our partners. All customers which that are using cloud services to process personal data will need to have a data processing agreement in place between them and their cloud services provider if they are to comply with GDPR. As early as April 2017, AWS announced that AWS had a GDPR-ready DPA available for its customers. In this way, we started offering our GDPR DPA to customers over a year before the May 25, 2018 enforcement date. Now, with the DPA terms included in our online service terms, there is no extra engagement needed by our customers and partners to be compliant with the GDPR requirement for data processing terms.

The AWS GDPR DPA also provides our customers with a number of other important assurances, such as the following:

  • AWS will process customer data only in accordance with customer instructions.
  • AWS has implemented and will maintain robust technical and organizational measures for the AWS network.
  • AWS will notify its customers of a security incident without undue delay after becoming aware of the security incident.
  • AWS will make available certificates issued in relation to the ISO 27001 certification, the ISO 27017 certification, and the ISO 27018 certification to further help customers and partners in their own GDPR compliance activities.

Customers who have already signed an offline version of the AWS GDPR DPA can continue to rely on that GDPR DPA. By incorporating our GDPR DPA into the AWS Service Terms, we are simply extending the terms of our GDPR DPA to all customers globally who will require it under GDPR.

AWS GDPR DPA is only part of the story, however. We are continuing to work alongside our customers and partners to help them on their journey towards GDPR compliance.

If you have any questions about the GDPR or the AWS GDPR DPA, please contact your account representative, or visit the AWS GDPR Center at: https://aws.amazon.com/compliance/gdpr-center/

-Chad

Interested in AWS Security news? Follow the AWS Security Blog on Twitter.

Roku Displays FBI Anti-Piracy Warning to Legitimate YouTube & Netflix Users

Post Syndicated from Andy original https://torrentfreak.com/roku-displays-fbi-anti-piracy-warning-to-legitimate-youtube-netflix-users-180516/

In 2018, dealing with copyright infringement claims is a daily issue for many content platforms. The law in many regions demands swift attention and in order to appease copyright holders, most platforms are happy to oblige.

While it’s not unusual for ‘pirate’ content and services to suddenly disappear in response to a DMCA or similar notice, the same is rarely true for entire legitimate services.

But that’s what appeared to happen on the Roku platform during the night, when YouTube, Netflix and other channels disappeared only to be replaced with an ominous anti-piracy warning.

As the embedded tweet shows, the message caused confusion among Roku users who were only using their devices to access legal content. Messages replacing Netflix and YouTube seemed to have caused the greatest number of complaints but many other services were affected.

FoxSportsGo, FandangoNow, and India-focused YuppTV and Hotstar were also blacked out. As were the yoga and transformational videos specialists over at Gaia, the horror buffs at ChillerFlix, and UK TV service BritBox.

But while users scratched their heads, with some misguidedly blaming Roku for not being diligent enough against piracy, Roku took to Twitter to reveal that rather than anti-piracy complaints against the channels in question, a technical hitch was to blame.

However, a subsequent statement to CNET suggested that while blacking out Netflix and YouTube might have been accidental, Roku appears to have been taking anti-piracy action against another channel or channels at the time, with the measures inadvertently spilling over to innocent parties.

“We use that warning when we detect content that has violated copyright,” Roku said in a statement.

“Some channels in our Channel Store displayed that message and became inaccessible after Roku implemented a targeted anti-piracy measure on the platform.”

The precise nature of the action taken by Roku is unknown but it’s clear that copyright infringement is currently a hot topic for the platform.

Roku is currently fighting legal action in Mexico which ordered its products off the shelves following complaints that its platform is used by pirates. That led to an FBI warning being shown for what was believed to be the first time against the XTV and other channels last year.

This March, Roku took action against the popular USTVNow channel following what was described as a “third party” copyright infringement complaint. Just a couple of weeks later, Roku followed up by removing the controversial cCloud channel.

With Roku currently fighting to have sales reinstated in Mexico against a backdrop of claims that up to 40% of its users are pirates, it’s unlikely that Roku is suddenly going to go soft on piracy, so more channel outages can be expected in the future.

In the meantime, the scary FBI warnings of last evening are beginning to fade away (for legitimate channels at least) after the company issued advice on how to fix the problem.

“The recent outage which affected some channels has been resolved. Go to Settings > System > System update > Check now for a software update. Some channels may require you to log in again. Thank you for your patience,” the company wrote in an update.

Source: TF, for the latest info on copyright, file-sharing, torrent sites and more. We also have VPN reviews, discounts, offers and coupons.

Седем мита за GDPR

Post Syndicated from Bozho original https://blog.bozho.net/blog/3105

GDPR, или новият Общ регламент относно защитата на данните, е гореща тема, тъй като влиза в сила на 25-ти май. И разбира се, публичното пространство е пълно с мнения и заключения по въпроса. За съжаление повечето от тях са грешни. На база на наблюденията ми от последните месеци реших да извадя 7 мита за Регламента.

От края на миналата година активно консултирам малки и големи компании относно регламента, водя обучения и семинари и пиша технически разяснения. И не, не съм юрист, но Регламентът изисква познаване както на правните, така и на технологичните аспекти на защитата на данните.

1. „GDPR ми е ясен, разбрал съм го“

Най-опасното е човек да мисли, че разбира нещо след като само е чувал за него или е прочел две статии в новинарски сайт (както за GDPR така и в по-общ смисъл). Аз самият все още не твърдя, че познавам всички ъгълчета на Регламента. Но по конференции, кръгли маси, обучения, срещи, форуми и фейсбук групи съм чул и прочел твърде много глупости относно GDPR. И то такива, които могат да се оборят с „Не е вярно, виж чл. Х“. В тази категория за съжаление влизат и юристи, и IT специалисти, и хора на ръководни позиции.

От мита, че познаваме GDPR, произлизат и всички останали митове. Част от вината за това е и на самия Регламент. Дълъг е, чете се трудно, има лоши законодателни практики (3 различни хипотези в едно изречение??) и нито Европейската Комисия, нито някоя друга европейска институция си е направила труда да го разясни за хората, за които се отнася – а именно, за почти всички. Т.нар. „работна група по чл. 29 (от предишната Директива)“ има разяснения по някои въпроси, но те са също толкова дълги и трудно четими ако човек няма контекст. При толкова широкообхватно законодателство е голяма грешка то да се остави нерязяснено. Да, в него има много нюанси и много условности (което е друг негов минус), но е редно поне общите положения да бъдат разказани ясно и то от практическа гледна точка.

Така че не – да не си мислим, че сме разбрали GDPR.

2. „Личните данни са тайна“

Определението за лични данни в Регламента може би характеризира целия Регламент – трудно четима и „увъртяно“:

„лични данни“ означава всяка информация, свързана с идентифицирано физическо лице или физическо лице, което може да бъде идентифицирано („субект на данни“); физическо лице, което може да бъде идентифицирано, е лице, което може да бъде идентифицирано, пряко или непряко, по-специално чрез идентификатор като име, идентификационен номер, данни за местонахождение, онлайн идентификатор или по един или повече признаци, специфични за физическата, физиологичната, генетичната, психическата, умствената, икономическата, културната или социална идентичност на това физическо лице;

Всъщност лични данни са всичко, което се отнася за нас. Включително съвсем очевидни неща като цвят на очи и коса, ръст и т.н. И не, личните данни не са тайна. Имената ни не са тайна, ръстът ни не е тайна. ЕГН-то ни не е тайна (да, не е). Има специални категории лични данни, които могат да бъдат тайна (напр. медицински данни), но за тях има специален ред.

Разграничаването, което GDPR не прави ясно, за разлика от едно разяснение на NIST – има лични данни, на база на които хората могат да бъдат идентифицирани, и такива, с които не могат, но се отнасят за тях. По цвят на косата не можем да бъдем идентифицирани. Но цветът на косата представлява лични данни. По професия не можем да бъдем идентифицирани. (По три имена и професия обаче – евентуално може и да можем). И тук едно много важно нещо, посочено в последните изречения на съображение 26 – данни, които са лични, но не могат да бъдат отнесени към конкретно лице, и на база на които не може да бъде идентифицирано такова, не попадат в обхвата на регламента. И съвсем не са тайна – „имаме 120 клиента на възраст 32 години, които са си купили телефон Sony между Април и Юли“ е напълно окей.

Та, личните данни не са та тайни – някои даже са съвсем явни и видни. Целта на GDPR е да уреди тяхната обработка с автоматизирани средства (или полуавтоматизирани в структуриран вид, т.е. тетрадки). С други думи – кой има право да ги съхранява, за какво има право да ги използва и как трябва да ги съхранява и използва.

3. „GDPR не се отнася за мен“

Няма почти никакви изключения в Регламента. Компании под 250 души не са длъжни да водят едни регистри, а компании, които нямат мащабна обработка и наблюдение на субекти на данни нямат задължение за длъжностно лице по защита на данните (Data protection officer; тази точка е дискусионна с оглед на предложенията за изменения на българския закон за защита на личните данни, които разширяват прекалено много изискванията за DPO). Всичко останало важи за всички, които обработват лични данни. И всички граждани на ЕС имат всички права, посочени в Регламента.

4. „Ще ни глобят 20 милиона евро“

Тези глоби са единствената причина GDPR да е популярен. Ако не бяха те, на никого нямаше да му дреме за поредното европейско законодателство. Обаче заради плашещите глоби всякакви консултанти ходят и обясняват как „ами те глобите, знаете, са до 20 милиона“.

Но колкото и да се повтарят тези 20 милиона (или както някои пресоляват манджата „глоби над 20 милиона евро“), това не ги прави реалистични. Първо, има процес, който всички регулатори ще следват, и който включва няколко стъпки на „препоръки“ преди налагане на глоба. Идва комисията, установява несъответствие, прави препоръки, идва пак, установява взети ли са мерки. И ако сте съвсем недобросъвестни и не направите нищо, тогава идват глобите. И тези глоби са пропорционални на риска и на количеството данни. Не е „добър ден, 20 милиона“. Според мен 20-те милиона ще са само за огромни международни компании, като Google и Facebook, които обработват данни на милиони хора. За тетрадката с вересиите глоба няма да има (правото да бъдеш забравен се реализира със задраскване, но само ако магазинерът няма легитимен интерес да ги съхранява, а именно – да му върнете парите :)).

Тук една скоба за българското законодателство – то предвижда доста високи минимуми на глобите (10 хил. лева). Това се оспорва в рамките на общественото обсъждане и е несъразмерно на минимумите в други европейски държави и се надявам да спадне значително.

5. „Трябва да спрем да обработваме лични данни“

В никакъв случай. GDPR не забранява обработката на лични данни, просто урежда как и кога те да се обработват. Имате право да обработвате всички данни, които са ви нужни, за да си свършите работата.

Някои интернет компании напоследък обявиха, че спират работа заради GDPR, защото не им позволявал да обработват данни. И това в общия случай са глупости. Или те така или иначе са били на загуба и сега си търсят оправдание, или са били такъв разграден двор и са продавали данните ви наляво и надясно без ваше знание и съгласие, че GDPR представлява риск. Но то това му е идеята – да няма такива практики. Защото (както твърди Регламентът) това представлява риск за правата и свободите на субектите на данни (субект на данните – това звучи гордо).

6. „Трябва да искаме съгласие за всичко“

Съгласието на потребителите е само едно от основанията за обработка на данните. Има доста други и те дори са по-често срещани в реалния бизнес. Както отбелязах по-горе, ако можете да докажете легитимен интерес да обработвате данните, за да си свършите работата, може да го правите без съгласие. Имате ли право да събирате адреса и телефона на клиента, ако доставяте храна? Разбира се, иначе не може да му я доставите. Няма нужда от съгласие в този случай (би имало нужда от съгласие ако освен за доставката, ползвате данните му и за други цели). Нужно ли е съгласие за обработка на лични данни в рамките на трудово правоотношение? Не, защото Кодекса на труда изисква работодателят да води трудово досие. Има ли нужда банката да поиска съгласие, за да ви обработва личните данни за кредита? Не, защото те са нужни за изпълнението на договора за кредит (и не, не можете да кажете на банката да ви „забрави“ кредита; правото да бъдеш забравен важи само в някои случаи).

Усещането ми обаче е, че ще плъзнат едни декларации и чекбоксове за съгласие, които ще са напълно излишни…но вж. т.1. А дори когато трябва да ги има, ще бъдат прекалено общи, а не за определени цели (съгласявам се да ми обработвате данните, ама за какво точно?).

7. „Съответсвието с GDPR е трудно и скъпо“

…и съответно Регламентът е голяма административна тежест, излишно натоварване на бизнеса и т.н. Ами не, не е. Съответствието с GDPR изисква осъзната обработка на личните данни. Да, изисква и няколко хартии – политики и процедури, с които да докажете, че знаете какви лични данни обработвате и че ги обработвате съвестно, както и че знаете, че гражданите имат някакви права във връзка с данните си (и че всъщност не вие, а те са собственици на тези данни), но извън това съответствието не е тежко. Е, ако хал хабер си нямате какви данни и бизнес процеси имате, може и да отнеме време да ги вкарате в ред, но това е нещо, което по принцип e добре да се случи, със или без GDPR.

Ако например досега в една болница данните за пациентите са били на незащитен по никакъв начин сървър и всеки е имал достъп до него, без това да оставя следа, и също така е имало още 3-4 сървъра, на които никой не е знаел, че има данни (щото „IT-то“ е напуснало преди 2 години), то да, ще трябват малко усилия.

Но почти всичко в GDPR са „добри практики“ така или иначе. Неща, които са полезни и за самия бизнес, не само за гражданите.

Разбира се, синдромът „по-светец и от Папата“ започва да се наблюдава. Освен компаниите, които са изсипали милиони на юристи, консултанти, доставчици (и което накрая е имало плачевен резултат и се е оказало, че за един месец няколко човека могат да я свършат цялата тая работа) има и такива, които четат Регламента като „по-добре да не даваме никакви данни никъде, за всеки случай“. Презастраховането на големи компании, като Twitter и Facebook например, има риск да „удари“ компании, които зависят от техните данни. Но отново – вж. т.1.


В заключение, GDPR не е нещо страшно, не е нещо лошо и не е „измислица на бюрократите в Брюксел“. Има много какво да се желае откъм яснотата му и предполагам ще има какво да се желае откъм приложението му, но „по принцип“ е окей.

И както става винаги със законодателства, обхващащи много хора и бизнеси – в началото ще има не само 7, а 77 мита, които с времето и с практиката ще се изяснят. Ще има грешки на растежа, има риск (особено в по-малки и корумпирани държави) някой „да го отнесе“, но гледайки голямата картинка, смятам, че с този Регламент след 5 години ще сме по-добре откъм защита на данните и откъм последици от липсата на на такава защита.