Live data from Hacker News

RIAA Takedowns Backfire as Pirated MP3s Now Surface on GitHub

torrentfreak.com

141–150 of 197 posts

Re: RIAA Takedowns Backfire as Pirated MP3s Now Surface on GitHub

#141
post #99

Earlier quoted context omitted.

I see where you're coming from, but that does create a big barrier to decentralization. The youtube-dl source code is safe and sound but as far as I know all the issues, discussions, unmerged PRs and more are lost forever. I suppose the ideal would be if git somehow provided a low level API that could be used to build these types of solution and then everybody would be free to build their own solution on top of it. M…

> all the issues, discussions, unmerged PRs and more are lost forever I don't see your argument here. Any decentralized solution wouldn't really help here if it wasn't used. And if it was used any decentralized solution would have helped even if it wasn't built into git. Is the argument that if we bundled it together people would be more likely to use it?

Of course, that's precisely the argument. Currently cloning a git repository is trivial, you can have different branches targeting different remotes etc... It's decentralized at the core. An issue solution that built on top of this architecture would be very powerful and "just work" while a solution built on the side will face an uphill battle for adoption.

Basically my point is that I consider issues to be an integral part of a repository's history, and it's a weakness of VCSs not to integrate it. A lot of the time I find Github comments on a feature/issue to be vastly more interesting and important than the resulting commit message.

Re: RIAA Takedowns Backfire as Pirated MP3s Now Surface on GitHub

#142
post #106
post #63

Earlier quoted context omitted.

The problem is that git is not feature complete to replace github. In hindsight I wish it had gone the Fossil route: integrate issue management in the distributed repo. If issues, wiki and code review were integrated in git proper it would be trivial to change host on a dime. Unfortunately it doesn't work that way (yet?).

Actually, why couldn't you keep issues as text files in a folder in the repo... I mean, you've got your CI stuff and documentation and everything else in there.

You could, but that would get messy quick since it would add a new commits to be merged/rebased every time somebody wants to comment. I guess the easiest solution would be to make it a submodule so that it could evolve at its own pace, but then you still want to be able to reference specific versions of the code in the comments, so maybe it would make more sense to make the code a submodule of the issue repo.

Maybe with good tooling that would be workable with git as it is.

Re: RIAA Takedowns Backfire as Pirated MP3s Now Surface on GitHub

#143
post #102

Earlier quoted context omitted.

the problem is lot of the incentive to contribute for free is the name recognition. Lot of dev see it as a way to show what they can do (portfolio) because that can’t share the code they produce at work

Is is good for name recognition if you contribute to software of somewhat dubious legal status such as youtube-dl?

Youtube-dl has a lot of legal applications!

Re: RIAA Takedowns Backfire as Pirated MP3s Now Surface on GitHub

#144
post #141

Earlier quoted context omitted.

> all the issues, discussions, unmerged PRs and more are lost forever I don't see your argument here. Any decentralized solution wouldn't really help here if it wasn't used. And if it was used any decentralized solution would have helped even if it wasn't built into git. Is the argument that if we bundled it together people would be more likely to use it?

Of course, that's precisely the argument. Currently cloning a git repository is trivial, you can have different branches targeting different remotes etc... It's decentralized at the core. An issue solution that built on top of this architecture would be very powerful and "just work" while a solution built on the side will face an uphill battle for adoption. Basically my point is that I consider issues to be an integr…

That makes sense. My counter argument is that even if it was built in it is unlikely to be good enough to be used by the majority of projects. But maybe I'm over estimating the difficulty of making a top quality issue tracker and code review tool.

Re: RIAA Takedowns Backfire as Pirated MP3s Now Surface on GitHub

#145
post #90

Earlier quoted context omitted.

Mozilla jumped the shark when they relented to supporting EME and packaging Widevine and OpenH264 with an otherwise-FOSS product. It's not as though a fork couldn't have added those. And despite adding those the user share of Firefox continues to decline.

Mozilla is not GNU. They may compromise on their values because it allows them to stay relevant and get anything done at all.

Stay relevant? Firefox is stuck at around 4% of market share. They're as relevant as a statistical aberration.

Re: RIAA Takedowns Backfire as Pirated MP3s Now Surface on GitHub

#146

Earlier quoted context omitted.

How Mozilla has changed in the last years hurts the most. I do think the leadership just wants to profit from the name and it will at one point cease to exists. It has done much for the net though, it should not be forgotten.

they are just trying to stay alive

They're doing a poor job of it. They've been stuck at around 4% market share for over a year now.

Re: RIAA Takedowns Backfire as Pirated MP3s Now Surface on GitHub

#147

Earlier quoted context omitted.

Is is good for name recognition if you contribute to software of somewhat dubious legal status such as youtube-dl?

“Dubious legal status” defined by whom? All GitHub got was a take down request (which they were required to act on), not proof of anything being illegal (which requires a court case to prove)

> Dubious legal status” defined by whom?

A potential employer.

Re: RIAA Takedowns Backfire as Pirated MP3s Now Surface on GitHub

#148

> This request wasn't well-received by developers, many of whom retaliated by posting copies of the code. Yesterday, things went from bad to worse when a user with the name 'F * T RIAA' uploaded three MP3s of the songs the RIAA mentioned in its takedown notice RIAA couldn't care less. As far as I understand, they practically are just a team of lawyers whose job is to attack whoever they can reach, take whatever they…

Can someone explain what is so hard here to go ahead and host your own Git repository? I mean how hard is it to run git instaweb --httpd=webrick Also there are tons of options GNU Savannah, Gogs,Gitea , Git Bucket ...

It’s trivial.

What is hard is managing the identity/ authentication process of large numbers of developers.

Even harder is actually covering your costs, i.e. running a going concern.

Re: RIAA Takedowns Backfire as Pirated MP3s Now Surface on GitHub

#149
post #33

Earlier quoted context omitted.

Not necessarily. If this situation goes viral and leads to an overall increase in piracy, someone at RIAA will have to answer for it.

Napster was viral. oink.cd was viral. PopcornTime is viral. The Pirate Bay was/is viral. RIAA doesn't care. Their main business is extortion racket. And it's extremely lucrative. And it's extortion on all sides . They extort money from DMCA and copyright lawsuits. They extort money from artists. They extort money from music services.

How could someone kill RIAA?

Re: RIAA Takedowns Backfire as Pirated MP3s Now Surface on GitHub

#150
post #35

Copyright laws and their consequences have been a disaster for the human race.

What laws haven't been a disaster? People are still murdered. The environment is still polluted. Taxes are still squandered. Healthcare has become unaffordable.
Post reply on HN