Difference between revisions of "SoundCloud"

From Archiveteam
Jump to navigation Jump to search
(Change status to halted due to force-halt)
(13 intermediate revisions by 7 users not shown)
Line 5: Line 5:
| URL = {{url|1=http://soundcloud.com}}
| URL = {{url|1=http://soundcloud.com}}
| project_status = {{endangered}}
| project_status = {{endangered}}
| archiving_status = {{notsavedyet}}
| archiving_status = Halted, see [[SoundCloud#Project status|Project status]]
| irc = soundclown
| source = https://github.com/ArchiveTeam/soundcloud-grab
| tracker = http://tracker.archiveteam.org/soundcloud
| irc = soundbutt
}}
}}


Line 15: Line 17:
In February 2016, a report casted “significant doubt on the company’s ability to continue as a going concern.”<ref>http://www.factmag.com/2016/02/11/soundcloud-financial-report-44m-losses/</ref>
In February 2016, a report casted “significant doubt on the company’s ability to continue as a going concern.”<ref>http://www.factmag.com/2016/02/11/soundcloud-financial-report-44m-losses/</ref>


Upon these news, Archive Team now considers SoundCloud a service in danger, and as it hosts a lot of original content, finds it important to prepare to save it selectively (a full grab would be too big and would raise concerns of mass copyright infringement).<ref>http://archive.fart.website/bin/irclogger_log/archiveteam?date=2015-08-27,Thu&sel=180#l176</ref><ref>http://archive.fart.website/bin/irclogger_log/archiveteam?date=2016-02-11,Thu&sel=131#l127</ref>
In July 2017, SoundCloud announced that they are firing 173 staff members to get "on [their] path to profitability".<ref>https://blog.soundcloud.com/2017/07/06/note-alex-ljung/</ref> Later in July, leaks from within the company revealed that it was "fully funded into Q4", yet was uncertain about future survival, giving it an estimated shutdown date of September 1st. <ref>https://techcrunch.com/2017/07/12/soundshroud/</ref>


Thus, a discussion has started in the {{IRC|soundclown}} channel.
Archive Team considers the SoundCloud service in danger and, as it hosts a lot of original content, finds it important to prepare to save it selectively (a full grab would be too big and would raise concerns of mass copyright infringement).<ref>http://archive.fart.website/bin/irclogger_log/archiveteam?date=2015-08-27,Thu&sel=180#l176</ref><ref>http://archive.fart.website/bin/irclogger_log/archiveteam?date=2016-02-11,Thu&sel=131#l127</ref>
 
Thus, a discussion has started in the {{IRC|soundbutt}} channel.
 
SoundCloud stored 2.5 PB of data on Amazon Glacier in May 2014.<ref>https://aws.amazon.com/solutions/case-studies/soundcloud/</ref> As of April 2017, the 128 kbit/s MP3 streams of all public tracks on SoundCloud total 855 TB. The best current estimate, based on an API grab from mid-July 2017, is 900.1 TiB in 134.6 million tracks totalling a playtime of 17.2 million hours.
 
== Project status ==
* '''07/20/2017''': IA disclaims the project and SketchCow/Jason Scott uses his influence toward ending any official AT project. He says he is prevented from public discussion of the reasons. <ref>https://twitter.com/textfiles/status/888093838107189249</ref>
* '''07/19/2017''': API Grab completed, We are now pre-processing the data to get all the jobs ready for the big pull. We should be ready to go and downloading music by 07/24/2017
* '''07/18/2017''': API grab from all comment and misc data is underway. SC is throttling our User Agent heavily. Code is being worked on to resolve this.
 
* '''07/14/2017''': We are currently working on getting all the API data. So far, rate limiting has not had an effect. We also are writing the scripts to get a good grab of everything we can. The warrior project is expected to start on July 18th.


As of April 2017 the 128k MP3 streams of all public tracks on SoundCloud total 855TB.


== References ==
== References ==

Revision as of 09:46, 21 July 2017

SoundCloud
SoundCloud logo
Soundcloud screenshot.png
URL http://soundcloud.com[IAWcite.todayMemWeb]
Status Endangered
Archiving status Halted, see Project status
Archiving type Unknown
Project source https://github.com/ArchiveTeam/soundcloud-grab
Project tracker http://tracker.archiveteam.org/soundcloud
IRC channel #soundbutt (on hackint)

SoundCloud is a global online audio distribution platform that enables its users to upload, record, promote, and share their originally-created sounds.[1]

In August 2015, SoundCloud was threatened to be pursued through the courts for unpaid royalties.[2]

In February 2016, a report casted “significant doubt on the company’s ability to continue as a going concern.”[3]

In July 2017, SoundCloud announced that they are firing 173 staff members to get "on [their] path to profitability".[4] Later in July, leaks from within the company revealed that it was "fully funded into Q4", yet was uncertain about future survival, giving it an estimated shutdown date of September 1st. [5]

Archive Team considers the SoundCloud service in danger and, as it hosts a lot of original content, finds it important to prepare to save it selectively (a full grab would be too big and would raise concerns of mass copyright infringement).[6][7]

Thus, a discussion has started in the #soundbutt (on hackint) channel.

SoundCloud stored 2.5 PB of data on Amazon Glacier in May 2014.[8] As of April 2017, the 128 kbit/s MP3 streams of all public tracks on SoundCloud total 855 TB. The best current estimate, based on an API grab from mid-July 2017, is 900.1 TiB in 134.6 million tracks totalling a playtime of 17.2 million hours.

Project status

  • 07/20/2017: IA disclaims the project and SketchCow/Jason Scott uses his influence toward ending any official AT project. He says he is prevented from public discussion of the reasons. [9]
  • 07/19/2017: API Grab completed, We are now pre-processing the data to get all the jobs ready for the big pull. We should be ready to go and downloading music by 07/24/2017
  • 07/18/2017: API grab from all comment and misc data is underway. SC is throttling our User Agent heavily. Code is being worked on to resolve this.
  • 07/14/2017: We are currently working on getting all the API data. So far, rate limiting has not had an effect. We also are writing the scripts to get a good grab of everything we can. The warrior project is expected to start on July 18th.


References