Beefy Boxes and Bandwidth Generously Provided by pair Networks
good chemistry is complicated,
and a little bit messy -LW
 
PerlMonks  

Comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
Thank you for writing this sample email. I would like permission to create a derived version for my own use. Perhaps you would consider licensing this under the GNU GPL or an open content license? *grin*

The SSSCA is about one thing: helping media studios sell us more stuff. In fact, as Godwin points out, the process of complying with this law would require all of us to buy new stuff, often stuff we already own! In fact, I see nowhere discussed any reason why the Philips audio CD standard will be exempted (am I wrong? please?!), as audio CDs are digital and there players will need to be equipped to protect (as in racket) the contents thereof.

And because this isn't terribly on-topic yet, I will mention the potential drastic impact this has on Perl. This law will not be the immediate death of free software, GNU/Linux and Perl, but it is a surefire start down that path. If common general-use computer hardware is required to protect "creative" content, it can only really do this well in conjunction with software. Not too slowly this leads to a situation where first operating systems and of course applications and then even programming languages must be designed to restrict usage (especially in consumer machines). This would effectively end free software, where source code availability makes any protective routines written into either the OS, the applications, or the programming languages as easy to route around as using the Delete Key.

<spam>At ichimunki.com I have mirrored Fritz Hollings' opening statements from yesterday's hearing (which are open to annotation by all comers-- the site is a wiki) and started collecting links and thoughts about free speech, fair use, and technology.</spam>

In reply to (ichimunki) Re: The SSSCA considered harmful by ichimunki
in thread The SSSCA considered harmful by tilly

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.
  • Log In?
    Username:
    Password:

    What's my password?
    Create A New User
    Chatterbox?
    and all is quiet...

    How do I use this? | Other CB clients
    Other Users?
    Others chilling in the Monastery: (9)
    As of 2017-10-20 18:30 GMT
    Sections?
    Information?
    Find Nodes?
    Leftovers?
      Voting Booth?
      My fridge is mostly full of:

















      Results (266 votes). Check out past polls.

      Notices?