Shared posts

16 May 14:18

Comcast Users Sued After Ignoring Piracy Notices

by Andy

comcast-newThrough various programs, such as the “six strikes” scheme in the United States and the fledgling Canadian program launched earlier this year, warning notices are delivered to BitTorrent users suspected of distributing content online.

While most are relatively benign, other warning notices come with a price tag attached. The most common are sent by anti-piracy outfit Rightscorp which routinely adds $20 settlement demands to ISP-delivered infringement notices.

The key with these notices is that Rightscorp and its clients don’t know the identities of the people they’re targeting so in the vast majority of cases these cash demands can be ignored. However, it now transpires that’s not always the best strategy.

In a lawsuit filed at the United States District Court for the District of New Jersey, Rightscorp client Rotten Records is suing a Comcast user who allegedly downloaded and shared When the Kite String Pops, the 1994 debut album from sludge metal band Acid Bath.

In a second filed at the United States District Court for the District of Massachusetts, Rotten Records is suing another Comcast user who allegedly downloaded and shared Definition, the sixth album from crossover thrash band D.R.I.

According to both lawsuits, Rotten Records hired Rightscorp to monitor BitTorrent networks for infringement. The company connected to the defendants’ BitTorrent clients and downloaded a full copy of each of the albums, later verifying that they were identical to the original copyright works.

Distancing themselves from any accusations of wrongdoing, the lawsuits state that neither Rotten Records nor Rightscorp were the original ‘seeders’ of the album and at no point did Rightscorp upload the albums to any other BitTorrent users. However, the company did send warnings to the Comcast users with demands for them to stop sharing the album.

“Rightscorp sent Defendant 11 notices via Defendant’s ISP Comcast Cable
Communications, Inc. from March 26, 2015 to April 4, 2015 demanding that Defendant stop illegally distributing Plaintiff’s work. Defendant ignored each and every notice and continued to illegally distribute Plaintiff’s work,” the Acid Bath lawsuit reads.

While eleven notices is significant, that number pales into insignificance when compared to the D.R.I case.

“Rightscorp sent Defendant 288 notices via their ISP Comcast Cable Communications, Inc. from December 14, 2014 to May 12, 2015 demanding that
Defendant stop illegally distributing Plaintiff’s work. Defendant ignored each and every notice and continued to illegally distribute Plaintiff’s work,” the complaint reads.

In closing, Rotten Records demands an injunction forbidding further online infringement in both cases in addition to the deletion of both albums from each Comcast user’s computer.

Unsurprisingly the record label also wants statutory damages (potentially $150K per work if any infringement is deemed willful) plus attorneys’ fees.

The cases are interesting ones for a number of reasons, not least the decision to target Comcast customers. The ISP routinely strips settlement demands from notices sent by Rightscorp, so it’s possible a message is being sent here.

The other angle is money. Sure, Rotten Records can probably come away with a few thousand dollars by way of settlement, but for Rightscorp the cases could prove much more valuable.

Despite warning that not settling for $20 could have a much worse outcome for an alleged pirate, it’s become relatively common knowledge that the company hardly ever shows its teeth. Victory in a case like this could be just what it needs to force settlements from greater numbers of notice recipients.

Keep an eye out for forthcoming (and noisily high-value) settlement announcements. They could make $20 sound like a bargain and boost Rightscorp’s failing bottom line.

Source: TorrentFreak, for the latest info on copyright, file-sharing, torrent sites and anonymous VPN services.

27 Sep 08:58

Enhedslisten forudser: Vi får forsøg med e-valg inden for nogle år

by 1385
http://www.version2.dk/artikel/enhedslisten-forudser-vi-faar-forsoeg-med-e-valg-inden-nogle-aar-54205

Det var først og fremmest lovforslaget om e-valg, der var noget galt med, ikke e-valg som sådan, lyder det fra Enhedslisten.

Version2
13 Sep 23:30

You Can't Make This Stuff Up: FinnAir's Flight 666 Flies to Helsinki (IATA Airport Code "HEL") on Friday the 13th

You Can't Make This Stuff Up: FinnAir's Flight 666 Flies to Helsinki (IATA Airport Code "HEL") on Friday the 13th

That's right:

Flight 666 to HEL on Friday the 13th.

Despite being a superstitious person's worst nightmare, the flight was reported to be "almost full," said Juha-Pekka Keidasto the pilot who flew the Airbus A320 from Copenhagen to Helsinki. Keidasto also stated that he is not a superstitious man and that it was "just another flight" for him.

I'm betting he had a lucky rabbit's foot in the storage box next to him, though.

The flight arrived three minutes early in Helsinki without incident.

Would you fly on Flight 666 to HEL on Friday the 13th?

Submitted by: Unknown (via flightaware)

20 May 07:01

Use PowerShell to Copy Only Folders that Contain Files

by The Scripting Guys

Summary: Microsoft Scripting Guy, Ed Wilson, talks about using Windows PowerShell to copy only folders that contain files.

Microsoft Scripting Guy, Ed Wilson, is here. In some respects, it seems like I have been using Windows PowerShell for a long time. In other respects, it seems like the journey begun only a short while ago. I mean, after writing five books about Windows PowerShell, it would seem that I know the product pretty well. And yet, I continue to amaze myself with the power of Windows PowerShell.

What am I talking about? Well, a few months ago, I created a whole bunch of folders based on dates in preparation for the Scripting Wife’s and my trip to Europe. Unfortunately, due to certain time issues, I did not always upload pictures every day into the folders. This caused some folders to not have pictures in them. Now when you are talking about 40 or so folders, it is annoying to click and not see anything. So I decided to delete folders that were not being used. At first I was going to do it by hand, but that was painful. I thought the code to clean up the empty folders might be too difficult to write, but in the end, it was not.

Delete empty folders

I opened the Windows PowerShell ISE, and created two variables to hold the source path and to hold the destination path. These two variables are shown here (note that you will not have these directories unless you have created them):

$path = 'C:\data\mypics\2012'

$destination = 'e:\data\mypics\archive\2012’

Now I use the Get-ChildItem cmdlet to collect all of my directories. I use the Directory switch that is available in Windows PowerShell 3.0 to do this. I send the directory objects down the pipeline. This is shown here.

Get-ChildItem $path -Directory |

Now I use the Foreach-Object cmdlet to work with each directory object. I call the EnumerateFiles method from the DirectoryInfo object to see if there are any files. I send the results to Measure-Object to count the files. I am sure this code could be cleaner, but it works:

Foreach-Object  {if (($_.enumeratefiles() | measure).count -gt 0)

If there are files, I copy the folder (and files) to the destination as shown here:

Copy-Item -path $_.fullname -Destination $destination -Recurse}

That is it. It did not take me very long at all to create the script. And it saved a whole lot of clicking. Here is the competed CopyOnlyFoldersWithFiles script.

CopyOnlyFoldersWithFiles.ps1

$path = 'C:\data\mypics\2012'

$destination = 'e:\data\mypics\archive\2012’

Get-ChildItem $path -Directory |

Foreach-Object  {if (($_.enumeratefiles() | measure).count -gt 0)

  {

   Copy-Item -path $_.fullname -Destination $destination -Recurse}

  }

Join me tomorrow when I will talk about more cool Windows PowerShell stuff.

I invite you to follow me on Twitter and Facebook. If you have any questions, send email to me at scripter@microsoft.com, or post your questions on the Official Scripting Guys Forum. See you tomorrow. Until then, peace.

Ed Wilson, Microsoft Scripting Guy