Skip to main content

Boing Boing: How copyright is killing culture

Interesting post that shows copyright issues are starting to hurt education needs as well.

I think, for purely education reasons, things like this should be more a matter of courtesy after x number of years. (I don't know what "x" should be but I think there is likely a useful number). Who owns the rights to the Zapruder JFK shot? If someone was doing an educational (i.e. no money being made for it - and YES that includes documentaries!) broadcast/video, then common sense should prevail, ensuring that valuable footage is never lost.

Boing Boing: How copyright is killing culture

Comments

Anonymous said…
While this seems like a shame, the broader question is a tough one. There is a limit on copyright--what's out of synch here is that the limit keeps getting extended. (Pretty much everytime Mickey Mouse is about to enter the public domain.)

As someone who creates intellectual property (both software and writing) for a living, I view copyright as providing me with a way to protect my income. On the other hand, the things I create tend to have a fairly short shelf life--no one today has much interest in the articles I wrote about FoxPro 2.6 ten years ago.

What we really need is a reasonable limit on copyright and it may turn out that the limit should vary with the form of the creation.

Tamar E. Granor
Andrew MacNeill said…
Agreed, Tamar.

I, too, make my living on software and consulting and think there is DEFINITELY a reason for having those items protected but there needs to be a reasonable limit or the ability (and willingness) for an owner to say "after this period, this is now available for all."

Popular posts from this blog

Blogs and RSS come to Microsoft.com

MS has just introduced their portal and it's pretty comprehensive. Nothing quite like learning that some people use AIM instead of MSN messenger, or that there really may be a need for supporting 4 monitors ( Cyrus Complains ) However, it's really a great sign that MS is serious about supporting the blogging community which seems to have um, exploded in size in the past year. Blogs and RSS come to Microsoft.com

Elevating Project Specifications with Three Insightful ChatGPT Prompts

For developers and testers, ChatGPT, the freely accessible tool from OpenAI, is game-changing. If you want to learn a new programming language, ask for samples or have it convert your existing code. This can be done in Visual Studio Code (using GitHub CoPilot) or directly in the ChatGPT app or web site.  If you’re a tester, ChatGPT can write a test spec or actual test code (if you use Jest or Cypress) based on existing code, copied and pasted into the input area. But ChatGPT can be of huge value for analysts (whether system or business) who need to validate their needs. There’s often a disconnect between developers and analysts. Analysts complain that developers don’t build what they asked for or ask too many questions. Developers complain that analysts haven’t thought of obvious things. In these situations, ChatGPT can be a great intermediary. At its worst, it forces you to think about and then discount obvious issues. At best, it clarifies the needs into documented requirements. ...

Programmers vs. Developers vs. Architects

I received an email this morning from Brandon Savage 's newsletter. Brandon's a PHP guru (works at Mozilla) but his newsletter and books have some great overall perspectives for developers of all languages. However, this last one (What's the difference between developers and architects?) kind of rubs me the wrong way. Either that, or I've just missed the natural inflation of job descriptions. (maybe, it's like the change in terminology between Garbage man and Waste Engineer or Secretary and Office Administrator) So maybe it's just me - but I think there's still a big difference between Programmer, Developer and then of course, architect. The key thing here is that every role has a different perspective and every one of those perspectives has value. The original MSF create roles like Product Manager, Program Manager, Developer, Tester, etc - so every concept may pigeon hole people into different roles. But the statements Brandon makes are often distinction...