We shouldn't cover those API-accessing data. One rule: data that could be fully downloaded directly, such as in .tar.gz, .zip formats. Original license should be attached and DMC requests are also accepted to remove data from public source. Any idea?
@caesar0301 commented on GitHub (Dec 19, 2016):
We shouldn't cover those API-accessing data. One rule: data that could be fully downloaded directly, such as in .tar.gz, .zip formats. Original license should be attached and DMC requests are also accepted to remove data from public source. Any idea?
Have you thought about using something like https://data.world?? I know there are other platforms similar to it, but something to think about.
@pgensler commented on GitHub (Jan 14, 2017):
Have you thought about using something like https://data.world?? I know there are other platforms similar to it, but something to think about.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @caesar0301 on GitHub (Dec 18, 2016).
@embatbr commented on GitHub (Dec 18, 2016):
Amazon S3? What about the licenses?
@caesar0301 commented on GitHub (Dec 19, 2016):
We shouldn't cover those API-accessing data. One rule: data that could be fully downloaded directly, such as in .tar.gz, .zip formats. Original license should be attached and DMC requests are also accepted to remove data from public source. Any idea?
@pgensler commented on GitHub (Jan 14, 2017):
Have you thought about using something like https://data.world?? I know there are other platforms similar to it, but something to think about.
@maurice-schleussinger commented on GitHub (Aug 25, 2017):
One could also consider http://academictorrents.com or https://archive.org.
@mfaheemakhtar commented on GitHub (Oct 28, 2017):
Maybe you can use Torrent - distributed and decentralized.
@KOLANICH commented on GitHub (Dec 19, 2018):
also IPFS