Co-head of fallen streaming site Grooveshark dead at 28

Cause of death remains unclear, no signs of suicide


Afp July 21, 2015
Cause of death remains unclear, no signs of suicide. PHOTO: FACEBOOK

NEW YORK: A co-founder of Grooveshark, an early leader in music streaming that recently closed under threat of crushing financial penalties to record labels, has died at 28, police said Monday.

Josh Greenberg died at his home Sunday evening in Gainesville, Florida, the university town where he helped launch the site in 2006.
The cause of death was unclear but there was no evidence of foul play or suicide, the Gainesville Police Department said on Twitter.

Greenberg, who lived with a girlfriend who was away for the weekend, had been planning new projects and was "more relieved than depressed" by the end of Grooveshark, his mother, Lori Greenberg, was quoted saying by The Gainesville Sun newspaper.

Grooveshark was one of the pioneering sites that offered unlimited, on-demand music, but, unlike later platforms such as Spotify, the company initially had few licensing deals with record labels.
With its young, entrepreneurial spirit, Grooveshark had often been described as the Facebook of music, but its trajectory was far less smooth.

Read: Dead man found in Demi Moore's pool

Greenberg and Grooveshark's other top executive, Sam Tarantino, had faced $736 million in penalties after a judge last year ruled that the bosses actively encouraged employees to upload copyrighted material.

Rather than go to trial, Grooveshark -- which claimed 30 million monthly users -- went dark on April 30 in a settlement with major record labels.

Read:

As part of the deal, Greenberg and Tarantino offered a public apology and handed back copyrighted files.

A third founder, Colombian-born Andres Barreto, left Grooveshark before its end and has been involved in start-ups in the United States and Latin America.

COMMENTS

Replying to X

Comments are moderated and generally will be posted if they are on-topic and not abusive.

For more information, please see our Comments FAQ