Live data from Hacker News

The /bin/true Command and Copyright (2009)

trillian.mit.edu

11–20 of 86 posts

Re: The /bin/true Command and Copyright (2009)

#11
post #3

The one confusing thing to me about this is that you're not supposed to append copyright years to a notice when the contents have not changed, yet this script got copyrighted all the way to 1989.

> you're not supposed to append copyright years to a notice

It shouldn't matter because the date of actual first publication would control, not what is on one particular notice.

Re: The /bin/true Command and Copyright (2009)

#12
That's fair use, not a copyright violation.

Google: "(in US copyright law) the doctrine that brief excerpts of copyright material may, under certain circumstances, be quoted verbatim for purposes such as criticism, news reporting, teaching, and research, without the need for permission from or payment to the copyright holder.".

Re: The /bin/true Command and Copyright (2009)

#13
post #9

Adding copyright notices to every source code file is reasonable because it costs next to nothing. Figuring out what is copyrightable, on the other hand, is expensive, because it requires lawyers, and a waste of time because lawyers' answers are always "it depends". You never actually know how enforceable your copyright claim is until you actually litigate, which is REALLY expensive.

Adding copyright notices to every source code file is also pointless, since copyright notices are no longer required to obtain copyright protection.

Re: The /bin/true Command and Copyright (2009)

#14
post #9

Adding copyright notices to every source code file is reasonable because it costs next to nothing. Figuring out what is copyrightable, on the other hand, is expensive, because it requires lawyers, and a waste of time because lawyers' answers are always "it depends". You never actually know how enforceable your copyright claim is until you actually litigate, which is REALLY expensive.

Adding copyright notices to every source code file is also pointless, since copyright notices are no longer required to obtain copyright protection.

It might help to prove intent when somebody does violate a license (they cannot say "oh wow this was copyrighted? i totally didn't know!")

Re: The /bin/true Command and Copyright (2009)

#16
post #9

Adding copyright notices to every source code file is reasonable because it costs next to nothing. Figuring out what is copyrightable, on the other hand, is expensive, because it requires lawyers, and a waste of time because lawyers' answers are always "it depends". You never actually know how enforceable your copyright claim is until you actually litigate, which is REALLY expensive.

> Adding copyright notices to every source code file is reasonable because it costs next to nothing.

Yes, if your integrity is worthless.

Re: The /bin/true Command and Copyright (2009)

#17
post #9

Adding copyright notices to every source code file is reasonable because it costs next to nothing. Figuring out what is copyrightable, on the other hand, is expensive, because it requires lawyers, and a waste of time because lawyers' answers are always "it depends". You never actually know how enforceable your copyright claim is until you actually litigate, which is REALLY expensive.

Adding copyright notices to every source code file is also pointless, since copyright notices are no longer required to obtain copyright protection.

Copyright notices are useful the same way written contracts are: you legally do not need a notice (written contract) to establish copyright protection (enter into a contract), but if a dispute arises it helps establish the fact that the user was notified (the other party agreed to this contract).

A question of 'law' vs 'facts'

Re: The /bin/true Command and Copyright (2009)

#19

Earlier quoted context omitted.

Adding copyright notices to every source code file is also pointless, since copyright notices are no longer required to obtain copyright protection.

Copyright notices are useful the same way written contracts are: you legally do not need a notice (written contract) to establish copyright protection (enter into a contract), but if a dispute arises it helps establish the fact that the user was notified (the other party agreed to this contract). A question of 'law' vs 'facts'

Those aren't at all analogous.

The automatic state for content is "protected by copyright," unless a different arrangement is made.

The automatic state for contract terms is "not agreed to," unless a different arrangement is made.

tl;dr You need proof (written or otherwise) that a contact happened; not so with copyright protection.

Re: The /bin/true Command and Copyright (2009)

#20
post #15

See also https://www.telegraph.co.uk/culture/music/rockandjazzmusic/3... ( https://archive.is/sjYJG ), where the rumored settlement payment was £100,000.

Sometimes parties pay what seems like a lot of money to settle dubious claims because it's cheaper and less time-consuming than fighting them. That can be completely rational. But paying £100,000 for infringing one minute of silence is just ridiculous.
Post reply on HN