e dot dot dot
a mostly about the Internet blog by

June 2018
Sun Mon Tue Wed Thu Fri Sat
         


PUBG Corp. Sues Epic Games In S. Korea Over Gameplay Similarities That Probably Aren't Copyrightable

Furnished content.


The last time we checked in with PUBG Corp., the company behind the popular PlayerUnknown's Battlegrounds video game, creator Brendan Greene was remarking on how video games are afforded no intellectual property rights at all, despite that absolutely not being the case. This confused take on a key aspect of his industry came on the heels of the developer of PUBG suggesting that it was considering suing Epic Games, the makers of Fortnite, for copyright infringement because Epic had updated its own game with a "battle royale" mode. Like PUBG, this mode pits 100 people against each other in a last-man-standing battle format. It was at that time that we tried to remind PUBG Corp. that the idea/expression dichotomy in copyright law is a thing. While specific expression gets copyright, general concepts, such as generic game-modes and genres, do not. A battle royale game format is no more deserving of copyright than the first-person shooter genre.It seems that the lesson didn't take, however, as it was recently revealed that PUBG went ahead and filed a lawsuit in South Korea way back in January.

After suggesting it might take action, the developer of PUBG has filed a lawsuit against the creator of Fortnite on the ground of copyright infringement. PUBG Corp., which is based in Korea, filed its lawsuit against US-based Epic Games with the aim of getting the courts to decide if Fortnite represents some kind of copy of PUBG. A PUBG Corp. representative told Korea Times that its lawsuit against Epic was actually filed back in January in the Seoul Central District Court. Epic Games Korea, a division of Epic Games, is the defendant.
How this lawsuit flew under the radar for five months is an incredibly irritating mystery to this writer, but it should be noted that no lawsuit has been likewise filed in the United States. While the press doesn't seem to be able to get any specific claims PUBG is making against Epic out of any filings in the South Korea courts, it's likely that the suit was filed there because the claims will rest largely on Fortnite's mimicry of the battle royale format. Again, in the US, it is clear that this is not copyright infringement.There are a couple of other items adding to the strangeness of the lawsuit. For starters, PUBG and Epic have an existing business relationship. PUBG was developed in Epic's Unreal Engine, after all. On top of that, Greene's first comments about Fortnite's battle royale mode were downright supportive before he began complaining about so-called "copying."
In March, PUBG creator Brendan Greene--the Playerunknown from the game's title--said Fortnite is good for the battle royale genre overall. "It's great that the battle royale space is expanding and Fortnite is getting battle royale game mode in the hands of a lot more people," he said, as reported by The Verge.
So, what explains the change of heart and the sudden move to file a lawsuit? It seems that Greene and the PUBG people don't like that Fortnite is simply doing better than them in the market.
This time last year, PUBG was seen as the No. 1 battle royale game, but a lot of attention and awareness currently is around Fortnite. Epic's game has exploded in popularity, and is reportedly a money-making juggernaut. A recent report said the free game brought in almost $300 million in revenue during April alone from its various microtransactions.
Suing the competition because they're successful isn't a great look for any company. Add to that the lawsuit sure seems as though it's over content and mimicry that is generally not afforded copyright protection and this all seems much to do about sour grapes.

Permalink | Comments | Email This Story


Read more here

posted at: 12:05am on 01-Jun-2018
path: /Policy | permalink | edit (requires password)

0 comments, click here to add the first



ICANN's Pre-emptive Attack On The GDPR Thrown Out By Court In Germany

Furnished content.


The EU's General Data Protection Regulation (GDPR) has only just started to be enforced, but it is already creating some seriously big waves in the online world, as Techdirt has reported. Most of those are playing out in obvious ways, such as Max Schrems's formal GDPR complaints against Google and Facebook over "forced consent" (pdf). That hardly came as a shock -- he's been flagging up the move on Twitter for some time. But there's another saga underway that may have escaped people's notice. It involves ICANN (Internet Corporation for Assigned Names and Numbers), which runs the Internet's namespace. Back in 2015, Mike memorably described the organization as "a total freaking mess", in an article about ICANN's "war against basic privacy". Given that history, it's perhaps no surprise that ICANN is having trouble coming to terms with the GDPR.The bone of contention is the information that is collected by the world's registrars for the Whois system, run by ICANN. EPAG, a Tucows-owned registrar based in Bonn, Germany, is concerned that this personal data might fall foul of the GDPR, and thus expose it to massive fines. As it wrote in a recent blog post:

We realized that the domain name registration process, as outlined in ICANN's 2013 Registrar Accreditation Agreement, not only required us to collect and share information we didn't need, it also required us to collect and share people's information where we may not have a legal basis to do so. What's more, it required us to process personal information belonging to people with whom we may not even have a direct relationship, namely the Admin and Tech contacts [for each domain name].
All of those activities are potentially illegal under the GDPR. EPAG therefore built a new domain registration system with "consent management processes", and a data flow "aligned with the GDPR's principles". ICANN was not happy with this minimalist approach, and sought an injunction in Germany in order to "preserve Whois data" -- that is, to force EPAG to collect those administrative and technical contacts. A post on the Internet Governance Project site explains why those extra Whois contacts matter, and what the real issue here is:
The filing by ICANN's Jones Day lawyers, which can be found here, asserts a far more sweeping purpose for Whois data, which is part of an attempt to make ICANN the facilitator of intellectual property enforcement on the Internet. "The technical contact and the administrative contact have important functions," the brief asserts. "Access to this data is required for the stable and secure operation of the domain name system, as well as a way to identify those customers that may be causing technical problems and legal issues with the domain names and/or their content."
As the tell-tale word "content" there reveals, the real reason ICANN requires registrars to collect technical and administrative contacts is because the copyright industry wants easy access to this information. It uses the personal details provided by Whois to chase the people behind sites that it alleges are offering unauthorized copies of copyright material. This is precisely the same ICANN overreach that Techdirt reported on back in 2015: the organization is supposed to be running the Internet's domain name system, not acting as a private copyright police force. The difference is that now the GDPR provides good legal and financial reasons to ignore ICANN's demands, as EPAG has noted.In a surprisingly swift decision, the German court hearing ICANN's request for an injunction against EPAG has already turned it down:
the Court said that the collection of the domain name registrant data should suffice in order to safeguard against misuse the security aspects in connection with the domain name (such as criminal activity, infringement or security problems).The Court reasoned that because it is possible for a registrant to provide the same data elements for the registrant as for the administrative and technical contacts, ICANN did not demonstrate that it is necessary to collect additional data elements for those contacts. The Court also noted that a registrant could consent and provide administrative and technical contact data at its discretion.
However, as ICANN rightly notes, that still leaves unanswered the key question: would collecting the administrative and technical contact information contravene the GDPR? ICANN says it is "continuing to pursue the ongoing discussions" with the EU on this, and a clarification of the legal situation here would certainly be in everyone's interests. But there is another important angle to this. As the security researcher Brian Krebs wrote on his blog back in February:
For my part, I can say without hesitation that few resources are as critical to what I do here at KrebsOnSecurity than the data available in the public WHOIS records. WHOIS records are incredibly useful signposts for tracking cybercrime, and they frequently allow KrebsOnSecurity to break important stories about the connections between and identities behind various cybercriminal operations and the individuals/networks actively supporting or enabling those activities. I also very often rely on WHOIS records to locate contact information for potential sources or cybercrime victims who may not yet be aware of their victimization.
There's no reason to doubt the importance of Whois information to Krebs's work. But the central issue is which is more important for society: protecting millions of people from spammers, scammers and copyright trolls by limiting the publicly-available Whois data, or making it easier for security researchers to track down online criminals by using that same Whois information? It's an important discussion that is likely to rage for some time, along with many others now being brought into sharper focus thanks to the arrival of the GDPR.Follow me @glynmoody on Twitter or identi.ca, and +glynmoody on Google+

Permalink | Comments | Email This Story


Read more here

posted at: 12:05am on 01-Jun-2018
path: /Policy | permalink | edit (requires password)

0 comments, click here to add the first



June 2018
Sun Mon Tue Wed Thu Fri Sat
         







RSS (site)  RSS (path)

ATOM (site)  ATOM (path)

Categories
 - blog home

 - Announcements  (0)
 - Annoyances  (0)
 - Career_Advice  (0)
 - Domains  (0)
 - Downloads  (3)
 - Ecommerce  (0)
 - Fitness  (0)
 - Home_and_Garden  (0)
     - Cooking  (0)
     - Tools  (0)
 - Humor  (0)
 - Notices  (0)
 - Observations  (1)
 - Oddities  (2)
 - Online_Marketing  (0)
     - Affiliates  (1)
     - Merchants  (1)
 - Policy  (3743)
 - Programming  (0)
     - Bookmarklets  (1)
     - Browsers  (1)
     - DHTML  (0)
     - Javascript  (3)
     - PHP  (0)
     - PayPal  (1)
     - Perl  (37)
          - blosxom  (0)
     - Unidata_Universe  (22)
 - Random_Advice  (1)
 - Reading  (0)
     - Books  (0)
     - Ebooks  (0)
     - Magazines  (0)
     - Online_Articles  (5)
 - Resume_or_CV  (1)
 - Reviews  (2)
 - Rhode_Island_USA  (0)
     - Providence  (1)
 - Shop  (0)
 - Sports  (0)
     - Football  (0)
          - Cowboys  (0)
          - Patriots  (0)
     - Futbol  (0)
          - The_Rest  (0)
          - USA  (0)
 - Technology  (1173)
 - Windows  (1)
 - Woodworking  (0)


Archives
 -2024  April  (109)
 -2024  March  (179)
 -2024  February  (168)
 -2024  January  (146)
 -2023  December  (140)
 -2023  November  (174)
 -2023  October  (156)
 -2023  September  (161)
 -2023  August  (49)
 -2023  July  (40)
 -2023  June  (44)
 -2023  May  (45)
 -2023  April  (45)
 -2023  March  (53)


My Sites

 - Millennium3Publishing.com

 - SponsorWorks.net

 - ListBug.com

 - TextEx.net

 - FindAdsHere.com

 - VisitLater.com