Pidster's blog

There's not much to see here, bar the following: 

Git for the lazy - Spheriki

From Spheriki

Jump to: navigation, search

Git is a distributed version control system. No, you don't need to know what that means to use this guide. Think of it as a time machine: Subversion or CVS without the cruft.

If you make a lot of changes, but decided you made a mistake, this will save your butt.

This guide is for people who want to jump to any point in time with their project/game/whatever, and want something to use for themselves.


Contents

[hide]

Install git

Windows

For Windows, you have two options:

msysGit

Download and install msysGit to use Git in Windows's cmd.exe console.

Cygwin

  1. Download Cygwin.
  2. Put setup.exe in a folder of its own in your documents.
  3. Launch setup.exe.
  4. While installing Cygwin, pick these packages:
    • git from the DEVEL category
    • nano (if you're wimpy) or vim (if you know it), both in the EDITORS category

You'll now have a shortcut to launch Cygwin, which brings up something like the Linux terminal.

Linux

Install the git package using your preferred method (package manager or from source).

Introduce yourself to git

Fire up your Cygwin/Linux terminal, and type:

git config --global user.name "Joey Joejoe"
git config --global user.email "joey@joejoe.com"

You only need to do this once.


Start your project

Start your project using the Sphere editor, or from a ZIP file, or just by making the directory and adding files yourself.

Now cd to your project directory:

cd myproject/

Tell git to start giving a damn about your project:

git init

... and your files in it:

git add .

Wrap it up:

git commit

Now type in a "commit message": a reminder to yourself of what you've just done, like:

Initial commit.

Save it and quit (type Ctrl o Ctrl x if you're in nano, :x if you're in vim) and you're done!


Work in bits

When dealing with git, it's best to work in small bits. Rule of thumb: if you can't summarise it in a sentence, you've gone too long without committing.

This section is your typical work cycle:

  • Work on your project.
  • Check which files you've changed:
    git status
  • Check what the actual changes were:
    git diff
  • Add any files/folders mentioned in step 2 (or new ones):
    git add file1 newfile2 newfolder3
  • Commit your work:
    git commit
  • Enter and save your commit message. If you want to back out, just quit the editor.
  • Repeat as much as you like. Just remember to always end with a commit.


    Admire your work

    To see what you've done so far, type:

    git log

    To just see the last few commits you've made:

    git log -n3

    Replace 3 with whatever you feel like.

    For a complete overview, type:

    git log --stat --summary

    Browse at your leisure.


    View changes

    To view changes you haven't committed yet:

    git diff

    If you want changes between versions of your project, first you'll need to know the commit ID for the changes:

    git log --pretty=oneline
    6c93a1960072710c6677682a7816ba9e48b7528f Remove persist.clearScriptCache() function.
    c6e7f6e685edbb414c676df259aab989b617b018 Make git ignore logs directory.
    8fefbce334d30466e3bb8f24d11202a8f535301c Initial commit.

    The 40 characters at the front of each line is the commit ID. You'll also see them when you git commit. You can use it to show differences between commits.

    To view the changes between the 1st and 2nd commits, type:

    git diff 8fef..c6e7

    Note how you didn't have to type the whole thing, just the first few unique characters are enough.

    To view the last changes you made:

    git diff HEAD^..HEAD


    How to fix mistakes

    Haven't committed yet, but don't want to save the changes? You can throw them away:

    git reset --hard


    You can also do it for individual files, but it's a bit different:

    git checkout myfile.txt


    Messed up the commit message? This will let you re-enter it:

    git commit --amend


    Forgot something in your last commit? That's easy to fix.

    git reset --soft HEAD^

    Add that stuff you forgot:

    git add forgot.txt these.txt

    Then write over the last commit:

    git commit

    Don't make a habit of overwriting/changing history if it's a public repo you're working with, though.


    For the not so lazy

    Just some extra reading here. Skip it if you're lazy.


    Writing good commit messages

    The author of Pro Git (an excellent online book) gives this advice for commit messages:

    Getting in the habit of creating quality commit messages makes using and collaborating with Git a lot easier. As a general rule, your messages should start with a single line that's no more than about 50 characters and that describes the changeset concisely, followed by a blank line, followed by a more detailed explanation. The Git project requires that the more detailed explanation include your motivation for the change and contrast its implementation with previous behavior — this is a good guideline to follow. It's also a good idea to use the imperative present tense in these messages. In other words, use commands. Instead of "I added tests for" or "Adding tests for," use "Add tests for." Here is a template originally written by Tim Pope at tpope.net:
    Short (50 chars or less) summary of changes
    
    More detailed explanatory text, if necessary.  Wrap it to about 72
    characters or so.  In some contexts, the first line is treated as the
    subject of an email and the rest of the text as the body.  The blank
    line separating the summary from the body is critical (unless you omit
    the body entirely); tools like rebase can get confused if you run the
    two together.
    
    Further paragraphs come after blank lines.
    
     - Bullet points are okay, too
    
     - Typically a hyphen or asterisk is used for the bullet, preceded by a
       single space, with blank lines in between, but conventions vary here

    If all your commit messages look like this, things will be a lot easier for you and the developers you work with. The Git project has well-formatted commit messages — I encourage you to run git log --no-merges there to see what a nicely formatted project-commit history looks like.


    Ignoring files

    When you check your project status, sometimes you'll get something like this:

    git status
    # On branch master
    # Untracked files:
    #   (use "git add ..." to include in what will be committed)
    #
    #       bleh.txt
    #       module.c~
    nothing added to commit but untracked files present (use "git add" to track)

    If you don't want git to track these files, you can add entries to .gitignore:

    nano .gitignore

    And add the files you want ignored:

    bleh.txt
    *~

    The first line ignores bleh.txt the second line ignores all files and directories ending with a tilde (~), i.e. backup files.

    You can check if you got it right:

    git status
    # On branch master
    # Changed but not updated:
    #   (use "git add ..." to update what will be committed)
    #
    #       modified:   .gitignore
    #
    no changes added to commit (use "git add" and/or "git commit -a")

    Don't forget to commit your changes to .gitignore!

    git add .gitignore
    git commit

    With something like this for your commit message:

    Make git ignore bleh.txt and backup files.

    Use .gitignore to keep your messages clean, and stop git from bugging you about stuff you don't care about. It's a good idea to ignore things like executable binaries, object files, etc. Pretty much anything that can be regenerated from source.


    Branching and merging

    A branch is a separate line of development. If you're going to make a bunch of changes related to a single feature, it might be a good idea to make a "topic branch": a branch related to a topic/feature.

    To make a new branch:

    git branch feature_x

    To view the current branches:

    git branch
    feature_x
    * master

    The asterisk (*) shows your current branch. master is the default branch, like the trunk in CVS or Subversion.

    To switch to your new branch, just type:

    git checkout feature_x

    If you check the branches again, you'll see the switch:

    git branch
    * feature_x
      master

    Now go through the usual edit/commit cycle. Your changes will go onto the new branch.

    When you want to put your branch changes back onto master, first switch to master:

    git checkout master

    Then merge the branch changes:

    git merge feature_x

    This will combine the changes of the master and feature_x branches. If you didn't change the master branch, git will just "fast-forward" the feature_x changes so master is up to date. Otherwise, the changes from master and feature_x will be combined.

    You can see the commit in your project's log:

    git log -n1

    If you're happy with the result, and don't need the branch any more, you can delete it:

    git branch -d feature_x

    Now when you see the branches, you'll only see the master branch:

    git branch
    * master

    You can make as many branches as you need at once.


    Tags

    If you hit a new version of your project, it may be a good idea to mark it with a tag. Tags can be used to easily refer to older commits.

    To tag the current version of your project as "v1.4.2", for example:

    git tag v1.4.2

    You can use these tags in places where those 40-character IDs appear.


    What now?

    git can help with working with other people too. Of course, then you do have to learn about distributed version control. Until then, just enjoy this page.

    But if you want to learn:

    Main git selling points (ripped off the main site):

    • Distributed development, i.e. working with other people.
    • Strong support for non-linear development, i.e. working with other people at the same time!
    • Efficient handling of large projects, i.e. fast!
    • Cryptographic authentication of history, for the paranoid.
    • Scriptable toolkit design, you can script pretty much any git task.


    If something doesn't seem right or is confusing, contact me at my blog. --tunginobi 07:42, 5 August 2009 (IST)

    Comments [0]

    Private DNS

    I've been exploring DNS and came across some mods Apple made to mDNSResponder which enable secure DNS transactions

    Comments [0]

    vimrc

    " Configuration file for vim
    set modelines=0 " CVE-2007-2438

    set nocompatible " Use Vim defaults instead of 100% vi compatibility
    set backspace=2 " more powerful backspacing

    set expandtab " expand tabs to space
    set tabstop=2 " number of spaces per tab
    set softtabstop=2 " ditto
    set shiftwidth=2 " number of spaces per indent
    set autoindent " use indent from current line when starting a
    new one
    set smartindent " use smart indenting when starting a new line
    set hlsearch " highlight search results in buffer

    " set background=dark " enable colouring for dark background terminals

    " set mouse=a " Enabled mouse in console

    set ruler " show the cursor position all the time
    set incsearch " do incremental searching
    set ignorecase smartcase " default to case insensitive unless caps in regex

    set autowrite " auto save
    set showmode " show current mode in status line
    set showcmd " display incomplete commands
    set showmatch " When closing a block, show the matching bracket.
    set laststatus=2 " Make the status line always visible

    set matchpairs+= " Include angle brackets in matching

    set undolevels=1000 " undoing 1000 changes should be enough :-)
    set updatecount=100 " write swap file to disk after each 20 characters
    set updatetime=6000 " write swap file to disk after 6 inactive seconds

    syntax on " Enable syntax highlighting
    filetype on " Enable filetype detection
    filetype indent on " Enable filetype-specific indenting
    filetype plugin on " Enable filetype-specific plugins

    " Don't write backup file if vim is being called by "crontab -e"
    au BufWrite /private/tmp/crontab.* set nowritebackup
    " Don't write backup file if vim is being called by "chpass"
    au BufWrite /private/etc/pw.* set nowritebackup

    Comments [0]

    Openstack: Open source cloud computing software

    Pid Wrote:
    Interesting move by Rackspace

    CommentsComments

    Original Link: http://openstack.org/

    Comments [0]

    Out Of Nowhere, The iPad Has A Real Competitor

    Comments [0]

    Prowl - Home

    Available on the App Store

    Prowl is the Growl client for the iPhone OS. Notifications from your Mac or Windows computer are sent to your iPhone or iPod touch using push. Prowl has an extensive API, which allows your scripts to integrate beautifully.

    I was extremely impressed with Prowl and the elegance with which I was able to view Growl notifications on my iPhone. Aron Trimble, TUAW
    Great idea. This opens up iPhone push notifications for anything you can think of. John Gruber, Daring Fireball
    Best non-IM use of iPhone 3.0's push notifications yet. Matt Buchanan, Gizmodo
    Probably the best $3 I’ve ever spent in the App Store. Darrell Etherington, The Apple Blog

    Push notifications When a Growl notification pops up on your computer, Prowl sends it over Push.

    A Push notification on the iPhone from Prowl

    Simple, elegant list Prowl provides a clean list of all your notifications.

    The list of notifications in Prowl on the iPhone

    Redirections Opening a push notification can launch a different application.

    A sample set of redirection options

    Quiet hours During quiet hours, only the badge count is updated. No sounds, no alerts.

    The quiet hours options display in Prowl.

    Of course, there are those times when things just go bad, so you can allow emergencies through.

    Send only what you want The Growl plugin can be configured to only send under conditions you specify.

    The Prowl plugin's options

    Web services There are a few third-party services which can send notifications for Twitter, Google Voice. There's also a bunch of plugins.

    Send links to your device Phone numbers and websites are linked inside Prowl.

    Infinitely extensible From delivery updates to torrent subscriptions, Prowl is as infinitely expandable as Growl is.


    I've delayed looking at this, but I am officially impressed.

    Comments [0]

    How to use HTML5 to make your CSS look like brainfuck

    Pid Wrote:
    Space characters in escaped CSS ID and class names? Doesn't seem like a good idea...

    CommentsComments

    Original Link: http://mathiasbynens.be/notes/html5-id-class

    Comments [0]

    ImperialViolet - Overclocking SSL

    (This is a write up of the talk that I gave at Velocity 2010 last Thursday. This is a joint work of myself, Nagendra Modadugu and Wan-Teh Chang.)

    The ‘S’ in HTTPS stands for ‘secure’ and the security is provided by SSL/TLS. SSL/TLS is a standard network protocol which is implemented in every browser and web server to provide confidentiality and integrity for HTTPS traffic.

    If there's one point that we want to communicate to the world, it's that SSL/TLS is not computationally expensive any more. Ten years ago it might have been true, but it's just not the case any more. You too can afford to enable HTTPS for your users.

    In January this year (2010), Gmail switched to using HTTPS for everything by default. Previously it had been introduced as an option, but now all of our users use HTTPS to secure their email between their browsers and Google, all the time. In order to do this we had to deploy no additional machines and no special hardware. On our production frontend machines, SSL/TLS accounts for less than 1% of the CPU load, less than 10KB of memory per connection and less than 2% of network overhead. Many people believe that SSL takes a lot of CPU time and we hope the above numbers (public for the first time) will help to dispel that.

    If you stop reading now you only need to remember one thing: SSL/TLS is not computationally expensive any more.

    The first part of this text contains hints for SSL/TLS performance and then the second half deals with things that Google is doing to address the latency that SSL/TLS adds.

    Basic configuration

    Modern hardware can perform 1500 handshakes/second/core. That's assuming that the handshakes involve a 1024-bit RSA private operation (make sure to use 64-bit software). If your site needs high security then you might want larger public key sizes or ephemeral Diffie-Hellman, but then you're not the HTTP-only site that this presentation is aimed at. But pick your certificate size carefully.

    It's also important to pick your preferred ciphersuites. Most large sites (Google included) will try to pick RC4 because it's very fast and, as a stream cipher, doesn't require padding. Recent Intel chips (Westmere) contain AES instructions which can make AES the better choice, but remember that there's no point using AES-256 with a 1024-bit public key. Also keep in mind that ephemeral Diffie-Hellman (EDH or DHE) ciphersuites will handshake at about half the speed of pure RSA ciphersuites. However, with a pure RSA ciphersuite, an attacker can record traffic, crack (or steal) your private key at will and decrypt the traffic retrospectively, so consider your needs.

    OpenSSL tends to allocate about 50KB of memory for each connection. We have patched OpenSSL to reduce this to about 5KB and I understand that the Tor project have independently written a similar patch that is now upstream (although not in any release at the time of writing). Keeping memory usage down is vitally important when dealing with many connections.

    Resumption

    There are two types of SSL/TLS handshake: a full handshake and an abbreviated handshake. The full handshake takes two round trips (in addition to the round trip from the TCP handshake):

    The abbreviated handshake occurs when the connection can resume a previous session. This can only occur if the client has the previous session information cached. Since the session information contains key material, it's never cached on disk so the attempted client resume rate, seen by Google, is only 50%. Older clients also require that the server cache the session information. Since these old clients haven't gone away yet, it's vitally important to setup a shared session cache if you have multiple frontend machines. The server-side miss rate at Google is less than 10%.

    An abbreviated handshake saves the server performing an RSA operation, but those are cheap anyway. More importantly, it saves a round-trip time:

    Addressing round trips is a major focus of our SSL/TLS work at Google (see below).

    Certificates

    We've already mentioned that you probably don't want to use 4096-bit certificates without a very good reason, but there are other certificate issues which can cause a major slowdown.

    Firstly, most certificates from CAs require an intermediate certificate to be presented by the server. Rather than have the root certificate sign the end certificates directly, the root signs the intermediate and the intermediate signs the end certificate. Sometimes there are several intermediate certificates.

    If you forget to include an intermediate certificate then things will probably still work. The end certificate will contain the URL of the intermediate certificate and, if the intermediate certificate is missing, the browser will fetch it. This is obviously very slow (a DNS lookup, TCP connection and HTTP request blocking the handshake to your site). Unfortunately there's a constant pressure on browsers to work around issues and, because of this, many sites which are missing certificates will never notice because the site still functions. So make sure to include all your certificates (in the correct order)!

    There's a second certificate issue that can increase latency: the certificate chain can be too large. A TCP connection will only send so much data before waiting to hear from the other side. It slowly ramps this amount up over time, but a new TCP connection will only send (typically) three packets. This is called the initial congestion window (initcwnd). If your certificates are large enough, they can overflow the initcwnd and cause an additional round trip as the server waits for the client to ACK the packets:

    For example, www.bankofamerica.com sends four certificates: 1624 bytes, 1488 bytes, 1226 bytes and 576 bytes. That will overflow the initcwnd, but it's not clear what they could do about that if their CA really requires that many intermediate certificates. On the other hand, edgecastcdn.net has a single certificate that's 4093 bytes long, containing 107 hostnames!

    Packets and records

    SSL/TLS packages the bytes of the application protocol (HTTP in our case) into records. Each record has a signature and a header. Records are packed into packets and each packet has headers. The overhead of a record is typically 25 to 40 bytes (based on common ciphersuites) and the overhead of a packet is around 52 bytes. So it's vitally important not to send lots of small packets with small records in them.

    I don't want to be seen to be picking on Bank Of America, it's honestly just the first site that I tried, but looking at their packets in Wireshark, we see many small records, often sent in a single packet. A quick sample of the record sizes: 638 bytes, 1363, 15628, 69, 182, 34, 18, … This is often caused because OpenSSL will build a record from each call to SSL_write and the kernel, with Nagle disabled, will send out packets to minimise latency.

    This can be fixed with a couple of tricks: buffer in front of OpenSSL and don't make SSL_write calls with small amounts of data if you have more coming. Also, if code limitations mean that you are building small records in some cases, then use TCP_CORK to pack several of them into a packet.

    But don't make the records too large either! See the 15KB record that https://www.bankofamerica.com sent? None of that data can be parsed by the browser until the whole record has been received. As the congestion window opens up, those large records tend to span several windows and so there's an extra round trip of delay before the browser gets any of that data. Since the browser is pre-parsing the HTML for subresources, it'll delay discovery and cause more knock-on effects.

    So how large should records be? There's always going to be some uncertainty in that number because the size of the TCP header depends on the OS and the number of SACK blocks that need to be sent. In the ideal case, each packet is full and contains exactly one record. Start with a value of 1415 bytes for a non-padded ciphersuite (like RC4), or 1403 bytes for an AES based ciphersuite and look at the packets which result from that.

    OCSP and CRLs

    OCSP and CRLs are both methods of dealing with certificate revocation: what to do when you lose control of your private key. The certificates themselves contain the details of how to check if they have been revoked.

    OCSP is a protocol for asking the issuing authority “What's the status of this certificate?” and a CRL is a list of certificates which have been revoked by the issuing authority. Both are fetched over HTTP and a certificate can specify an OCSP URL, a CRL URL, or both. But certificate authorities will typically use at least OCSP.

    Firefox 2 and IE on Windows XP won't block an SSL/TLS handshake for either revocation method. IE on Vista will block for OCSP, as will Firefox 3. Since there can be several OCSP requests resulting from a handshake (one for each certificate), and because OCSP responders can be slow, this can result in hundreds of milliseconds of additional latency for the first connection. I don't have really good data yet, but hopefully soon.

    The answer to this is OCSP stapling: the SSL/TLS server includes the OCSP response in the handshake. OCSP responses are public and typically last for a week, so the server can do the work of fetching them and reuse the response for many connections. The latest alpha of Apache supports this (httpd 2.3.6-alpha). Google servers will hopefully support this soon.

    However, OCSP stapling has several issues. Firstly, the protocol only allows the server to staple one response into the handshake: so if you have more than one certificate in the chain the client will probably end up doing an OCSP check anyway. Secondly, an OCSP response is about 1K of data. Remember the issue with overflowing the initcwnd with large certificates? Well the OCSP response is included in the same part of the handshake, so it puts even more pressure on certificate sizes.

    Google's SSL/TLS work

    Google is working on a number of fronts here. I'll deal with them in order of deployment and complexity.

    Firstly, simple and deployed, is False Start. All you really need to know is that it reduces the number of round trips for a full handshake from two to one. Thus, there's no longer any latency advantage to resuming. It's a client-side only change and it's live in Chrome (5 on Linux, 6 on Mac and Windows) and Android Froyo.

    Slightly more complex, but still deployed, is Next Protocol Negotiation. This pushes negotiation of the application level protocol down into the TLS handshake. It's how we trigger the use of SPDY. It's live on the Google frontend servers and in Chrome (6).

    OCSP stapling should be coming to the Google frontend servers within the next couple of months. Once we have basic stapling working, we'll need to address its shortfalls (see above). That means that we'll be implementing multi-stapling and compression of certificates and OCSP responses at some point, although we haven't started work on that yet.

    Lastly, and most complex, is Snap Start. This reduces the round trip times to zero for both types of handshakes. It's a client and server side change and it assumes that the client has the server's certificate cached and has up-to-date OCSP information. However, since the certificate and OCSP responses are public information, we can cache them on disk for long periods of time.

    Conclusion

    I hope that was helpful. We want to make the web faster and more secure and this sort of communication helps keep the world abreast of what we're doing.

    Also, don't forget that we recently deployed encrypted web search on https://encrypted.google.com. Switch your search engine!

    Filed under "More old myths dispelled".

    Comments [0]

    Azul Systems To Open Source Significant Technology in Managed Runtime Initiative

    Pid Wrote:
    Interesting stuff about VMs

    CommentsComments

    Original Link: http://www.infoq.com/news/2010/06/azul_ori

    Comments [0]

    CEO Of UK Collection Society: We Don't Want Gov't Handouts, But The Gov't Must Give Us Everything We Ask For!

    Pid Wrote:
    True

    Well, this is nice. Fran Nevrkla, the CEO of PPL, the collection society for performance rights in the UK, recently gave a talk that shows the ridiculous extremes with which some folks in this industry view the very consumers they're failing to serve. Last we checked in on PPL, it was trying to shake down charities for more money and had lost a massive ruling that said it had greatly overcharged multiple venues and owed them refunds. Towards the end of the talk, Nevrkla claims that he's disappointed that capital punishment for file sharing isn't available. Obviously, this is a joke -- but it does show how these people think:Thank you, David, and thank you for putting some of those pirates behind bars. I know that regrettably capital punishment was abolished in this country some 50 years ago, sad it is, but a few years in jail is probably pretty OK...This particular quote was highlighted on Boing Boing, and gets most of the attention, but it is really just a joke (we hope). What I think is a lot more worrisome is much of what he said, which is blatantly false and misleading, in the rest of his talk. It starts with this tidbit (also in the BoingBoing post):To the industry I would say, we would be well advised to delete two or three words from our vocabulary entirely and they are 'promotion' and 'promotional value'. There is no such thing in the 21st Century. There is usage, there are benefits, hopefully often, if not always to both sides but there is no favour in it and no indulgence and no promotion. That's early in the presentation, but he digs in deeper later on:The only thing I would say (to broadcasters) is 'please, stop all that stuff about "promotion."' It really becomes incredibly tiresome and it's grossly overused and it's very old fashioned. It should have no place in the modern era.Yes, please. Let's ignore the facts of what's happening in the market, because it goes against our business model. There absolutely is promotion and promotional value. In fact, many musicians have not just recognized this, but have embraced it. The problem, of course, is that PPL's entire setup is based on there being no promotional value of music. So it has to lie and tell people and itself that there's no such thing, despite mounds of evidence to the contrary. To then claim being factual is tiresome and "old fashioned" isn't just wrong, but insulting to people who actually understand the facts of the situation.

    There's also the fun part where he rails against "free":Now, whether it is the copyright tribunal or society in general, is it now guided by this foolish and, to me, entirely bogus concept of "for free." And, frankly, the music industry is no different than any other business or industry or service. Sir Terry Leahy, the phenomenally successful businessman, business leader and entrepreneur, would see his business in ruins after six weeks as would Lord Sainsbury, Lord Sugar and many others, if they were having to compete with free next door or across the road.Of course, his examples are folks dealing in physical, tangible goods. Leahy and Sainsbury (if I'm getting the people right) both built up supermarket/grocery store-type businesses. Those are businesses that have always had to compete with others at near marginal cost, because they sell commodities. They were not given gov't monopolies, or had a gov't "tribunal" setting an artificially high price, which PPL enjoys.

    And, it seems worth pointing out that PPL appears to have put this particular video out for free, as an attempt to promote its own services. But, I thought that there was no such thing as "for free" or "promotional value." Except, of course, when PPL does it for itself? Hypocrites.Now, with no hostility, but with a touch of sadness, regret and frankly astonishment, I ponder, about the pronouncements of some -- perhaps a small minority -- of academics and various other thinkers and all the digital freedom fighters in terms of their arrogance, hostility -- usually deliberate -- and frankly, gross ignorance and naivete.Um. Wait, you're the guy supporting sending people to jail for "free" and falsely claiming there's no promotional value to music and no legitimate concept of "free." And you blame others? From there he mocks the National Association of Broadcasters for being against the Performance Rights Act, while using copyright itself -- not realizing that just being against a performance tax is not the same thing as being against copyright. This guy basically seems to not actually be honest in his responses to anything.Now, why is copyright so fundamental to performers and record companies? It should be obvious. It's the bedrock of creativity, because it is a property right. Please, don't listen to the demagogues among the digerati who, in a completely false way, try to present copyright as a monopoly right. A nonsense. Every intelligent person and a real legal person will tell you that it is a property right.I'm sorry, but he's lying. Flat out lying. Plenty of very smart "real legal" persons will tell you that it's a monopoly right -- including numerous copyright experts and legal scholars. I recognize that Mr. Nevrkla might not like this fact, and that it contradicts with the way he tries to run his business, but he can't deny reality just because he doesn't like it.

    Next up, he goes on to talk about the 300th anniversary of the Statue of Anne, and reads a selected quote from Daniel Defoe, often credited as being one of the first to use the term "pirates" to describe publishers who reprinted his poems without authorization. Not surprisingly, Nevrkla leaves out many of the important details of that story, including Defoe's statement that he actually had no problem with publishers reprinting his work and even selling it for money, as long as they "print it true according to the copy." That is, Defoe's real worry wasn't that it was taking money from him, but that people were making copies that were not accurate. In fact, Dafoe then figured out how to use the "pirate" copies to his own advantage. He used the widespread copies of his work to build up his own reputation and name recognition, allowing him to make significantly more money on commissions for future works. Dafoe is, in fact, one of the earliest examples of a smart content creator who did not need copyright, and actually learned to use the lack of copyright to his advantage.

    Why do you think Nevrkla would leave all that out?

    Nevrkla then goes on to whine and complain about governments not just rolling over and forcing everyone to give him more money. He does this with a straight face.Now, not only are we desperately short on the copyright protection for sound recordings. Frankly, we are short on the basic PPL public performance rights environment. Several successive governments have failed us to introduce legislation which actually is a mirror image of European law. And we have done something about it. We have taken legal action and will pursue it until we get the right and just result.Ah, the "right and just" result is to tax all music so PPL gets paid. Even if it harms musicians and the public. This is not the "right and just" result. It's the one that most benefits PPL and Nevrkla. Then he complains that most musicians don't make enough money, saying that they should have "the right to proper working conditions" which seems to involve extortionary powers on the part of PPL. Of course, he ignores that the greater fees PPL gets to charge, the fewer venues are willing to play music and the more harm done by PPL. He also ignores the fact that part of the reason so many musicians make so little money is because the way PPL is structured, where it often samples performances, such that larger artists get their songs noted as being performed, but smaller artists may get skipped over entirely. The problem isn't copyright. The problem is PPL.

    Nevrkla then starts talking about copyright extension for performance rights, with a story that is almost certainly made up:It has been said to my face several times, usually out of frustration when these people run out of arguments. So, when musicians get to their old age, can no longer play and exercise their profession, and are losing all their copyrights, just as they get old and infirm and ill. And you know what the answer is? "Let them sell more t-shirts."He's being misleading here as well. I'm curious, when he's old and no longer working for PPL, if he thinks that PPL should keep paying him for the work he did in the past? He's making the false argument that copyright is a welfare system for musicians. It's not. When people get old and retire, they're supposed to have saved up money from back when they were working. And no one is actually saying "sell t-shirts" to make money in their old age. They're saying they should have a decent business model and not expect the gov't to tax everyone just because they did not have a good business model. That these musicians might not have done so is tragic, but is no excuse for copyright extension. And, of course, Nevrkla leaves out that studies have shown extension of performance rights go almost universally to the record labels, not to the musicians. He mentions session players and the like, but most of them were work for hire situations, who got paid for their time and that was it. They're not getting royalties anyway. If he wants to help them, perhaps he should fix that, not lie to everyone about what's actually happening.Record companies need to make money. Let's not get deceived by some of that PC nonsense out there. It is not a crime in the United Kingdom in the year 2010 to make money and make a profit. That profit is not eaten by someone. It is plowed back into the business into new talent and new music. And I am delighted to say that as an industry, we have always been proud, self-reliant, successful industry which also enhances Britain's standing in the world.Wait, what? Just a couple minutes earlier you were whining about how governments aren't giving you enough money, and now you claim you're self-reliant? I do not think that word means what you think it means. It's really quite incredible how he spends so much time demanding more privileges from the government, trashes the copyright tribunal for telling him he's charged too much, and then pretends they're some sort of "self-reliant" business that has any actual business sense. His entire revenue base is from the government forcing people to give him money. He doesn't have to convince anyone to buy, the gov't forces them to. Sickening. And it gets worse:Now we are not, and I hope we never will, ask for subsidies or state handouts.... And please, let's not go down that way.Uh, but you are. And have been, and continue to do so, and then when you don't get them you complain that it's not "just" and mock people who suggest you should have a better business model. Stunning cognitive dissonance.But what we must demand is proper valuation of music and proper commercial valuation of the underlying rights in music. We cannot do DIY in copyright. For that we need the gov't, the civil service, the UK IPO, and other authorities in Brussels. And it is their responsibility at the end of the day to do the right thing, finally, by our community too.Uh, wait. You just said you weren't asking for a government handout, and then immediately turn around and ask for exactly that, claiming that the government must give you a hand out and a subsidy. Your rhetorical trick is to claim that this "handout" is "proper valuation." It's not. Copyright is a subsidy. It's a purposeful breaking of the free market, in order to allow PPL to charge a higher than market price. It's not a "proper" valuation. It's a monopoly valuation.To all those clever, smart, smug, cynical thinkers and others: HANDS OFF OUR COPYRIGHT. Hands off our employment opportunities, our income streams, our livelihoods and our future.Um, ok. How about hands off our privacy. Our culture. Our ability to share and communicate and to express ourselves? Hands off our wallets (via the government). Hands off our ability to use new and smarter business models.

    From there, Nevrkla goes into his "thank yous," naming lots of organizations and people who we normally see in these pages for trying to take away consumer rights and force the government to provide greater monopoly rights and subsidies. That's where the "capital punishment" joke comes in.

    Overall, however, the speech is stunning in its blatant dishonesty and cognitive dissonance, railing against gov't hand outs while not asking for them, but demanding them, as the only "just" way. The capital punishment statement is ridiculous, but at least we think he was joking. The rest of the speech is just dishonest and misleading -- and, for that reason, is much more worrisome.

    If you want to be frustrated by this ridiculousness, you can watch the whole thing (for free, for the "promotional value" of it), below:

    Permalink | Comments | Email This StoryWell, this is nice. Fran Nevrkla, the CEO of PPL, the collection society for performance rights in the UK, recently gave a talk that shows the ridiculous extremes with which some folks in this industry view the very consumers they're failing to serve. Last we checked in on PPL, it was trying to shake down charities for more money and had lost a massive ruling that said it had greatly overcharged multiple venues and owed them refunds. Towards the end of the talk, Nevrkla claims that he's disappointed that capital punishment for file sharing isn't available. Obviously, this is a joke -- but it does show how these people think:Thank you, David, and thank you for putting some of those pirates behind bars. I know that regrettably capital punishment was abolished in this country some 50 years ago, sad it is, but a few years in jail is probably pretty OK...This particular quote was highlighted on Boing Boing, and gets most of the attention, but it is really just a joke (we hope). What I think is a lot more worrisome is much of what he said, which is blatantly false and misleading, in the rest of his talk. It starts with this tidbit (also in the BoingBoing post):To the industry I would say, we would be well advised to delete two or three words from our vocabulary entirely and they are 'promotion' and 'promotional value'. There is no such thing in the 21st Century. There is usage, there are benefits, hopefully often, if not always to both sides but there is no favour in it and no indulgence and no promotion. That's early in the presentation, but he digs in deeper later on:The only thing I would say (to broadcasters) is 'please, stop all that stuff about "promotion."' It really becomes incredibly tiresome and it's grossly overused and it's very old fashioned. It should have no place in the modern era.Yes, please. Let's ignore the facts of what's happening in the market, because it goes against our business model. There absolutely is promotion and promotional value. In fact, many musicians have not just recognized this, but have embraced it. The problem, of course, is that PPL's entire setup is based on there being no promotional value of music. So it has to lie and tell people and itself that there's no such thing, despite mounds of evidence to the contrary. To then claim being factual is tiresome and "old fashioned" isn't just wrong, but insulting to people who actually understand the facts of the situation.

    There's also the fun part where he rails against "free":Now, whether it is the copyright tribunal or society in general, is it now guided by this foolish and, to me, entirely bogus concept of "for free." And, frankly, the music industry is no different than any other business or industry or service. Sir Terry Leahy, the phenomenally successful businessman, business leader and entrepreneur, would see his business in ruins after six weeks as would Lord Sainsbury, Lord Sugar and many others, if they were having to compete with free next door or across the road.Of course, his examples are folks dealing in physical, tangible goods. Leahy and Sainsbury (if I'm getting the people right) both built up supermarket/grocery store-type businesses. Those are businesses that have always had to compete with others at near marginal cost, because they sell commodities. They were not given gov't monopolies, or had a gov't "tribunal" setting an artificially high price, which PPL enjoys.

    And, it seems worth pointing out that PPL appears to have put this particular video out for free, as an attempt to promote its own services. But, I thought that there was no such thing as "for free" or "promotional value." Except, of course, when PPL does it for itself? Hypocrites.Now, with no hostility, but with a touch of sadness, regret and frankly astonishment, I ponder, about the pronouncements of some -- perhaps a small minority -- of academics and various other thinkers and all the digital freedom fighters in terms of their arrogance, hostility -- usually deliberate -- and frankly, gross ignorance and naivete.Um. Wait, you're the guy supporting sending people to jail for "free" and falsely claiming there's no promotional value to music and no legitimate concept of "free." And you blame others? From there he mocks the National Association of Broadcasters for being against the Performance Rights Act, while using copyright itself -- not realizing that just being against a performance tax is not the same thing as being against copyright. This guy basically seems to not actually be honest in his responses to anything.Now, why is copyright so fundamental to performers and record companies? It should be obvious. It's the bedrock of creativity, because it is a property right. Please, don't listen to the demagogues among the digerati who, in a completely false way, try to present copyright as a monopoly right. A nonsense. Every intelligent person and a real legal person will tell you that it is a property right.I'm sorry, but he's lying. Flat out lying. Plenty of very smart "real legal" persons will tell you that it's a monopoly right -- including numerous copyright experts and legal scholars. I recognize that Mr. Nevrkla might not like this fact, and that it contradicts with the way he tries to run his business, but he can't deny reality just because he doesn't like it.

    Next up, he goes on to talk about the 300th anniversary of the Statue of Anne, and reads a selected quote from Daniel Defoe, often credited as being one of the first to use the term "pirates" to describe publishers who reprinted his poems without authorization. Not surprisingly, Nevrkla leaves out many of the important details of that story, including Defoe's statement that he actually had no problem with publishers reprinting his work and even selling it for money, as long as they "print it true according to the copy." That is, Defoe's real worry wasn't that it was taking money from him, but that people were making copies that were not accurate. In fact, Dafoe then figured out how to use the "pirate" copies to his own advantage. He used the widespread copies of his work to build up his own reputation and name recognition, allowing him to make significantly more money on commissions for future works. Dafoe is, in fact, one of the earliest examples of a smart content creator who did not need copyright, and actually learned to use the lack of copyright to his advantage.

    Why do you think Nevrkla would leave all that out?

    Nevrkla then goes on to whine and complain about governments not just rolling over and forcing everyone to give him more money. He does this with a straight face.Now, not only are we desperately short on the copyright protection for sound recordings. Frankly, we are short on the basic PPL public performance rights environment. Several successive governments have failed us to introduce legislation which actually is a mirror image of European law. And we have done something about it. We have taken legal action and will pursue it until we get the right and just result.Ah, the "right and just" result is to tax all music so PPL gets paid. Even if it harms musicians and the public. This is not the "right and just" result. It's the one that most benefits PPL and Nevrkla. Then he complains that most musicians don't make enough money, saying that they should have "the right to proper working conditions" which seems to involve extortionary powers on the part of PPL. Of course, he ignores that the greater fees PPL gets to charge, the fewer venues are willing to play music and the more harm done by PPL. He also ignores the fact that part of the reason so many musicians make so little money is because the way PPL is structured, where it often samples performances, such that larger artists get their songs noted as being performed, but smaller artists may get skipped over entirely. The problem isn't copyright. The problem is PPL.

    Nevrkla then starts talking about copyright extension for performance rights, with a story that is almost certainly made up:It has been said to my face several times, usually out of frustration when these people run out of arguments. So, when musicians get to their old age, can no longer play and exercise their profession, and are losing all their copyrights, just as they get old and infirm and ill. And you know what the answer is? "Let them sell more t-shirts."He's being misleading here as well. I'm curious, when he's old and no longer working for PPL, if he thinks that PPL should keep paying him for the work he did in the past? He's making the false argument that copyright is a welfare system for musicians. It's not. When people get old and retire, they're supposed to have saved up money from back when they were working. And no one is actually saying "sell t-shirts" to make money in their old age. They're saying they should have a decent business model and not expect the gov't to tax everyone just because they did not have a good business model. That these musicians might not have done so is tragic, but is no excuse for copyright extension. And, of course, Nevrkla leaves out that studies have shown extension of performance rights go almost universally to the record labels, not to the musicians. He mentions session players and the like, but most of them were work for hire situations, who got paid for their time and that was it. They're not getting royalties anyway. If he wants to help them, perhaps he should fix that, not lie to everyone about what's actually happening.Record companies need to make money. Let's not get deceived by some of that PC nonsense out there. It is not a crime in the United Kingdom in the year 2010 to make money and make a profit. That profit is not eaten by someone. It is plowed back into the business into new talent and new music. And I am delighted to say that as an industry, we have always been proud, self-reliant, successful industry which also enhances Britain's standing in the world.Wait, what? Just a couple minutes earlier you were whining about how governments aren't giving you enough money, and now you claim you're self-reliant? I do not think that word means what you think it means. It's really quite incredible how he spends so much time demanding more privileges from the government, trashes the copyright tribunal for telling him he's charged too much, and then pretends they're some sort of "self-reliant" business that has any actual business sense. His entire revenue base is from the government forcing people to give him money. He doesn't have to convince anyone to buy, the gov't forces them to. Sickening. And it gets worse:Now we are not, and I hope we never will, ask for subsidies or state handouts.... And please, let's not go down that way.Uh, but you are. And have been, and continue to do so, and then when you don't get them you complain that it's not "just" and mock people who suggest you should have a better business model. Stunning cognitive dissonance.But what we must demand is proper valuation of music and proper commercial valuation of the underlying rights in music. We cannot do DIY in copyright. For that we need the gov't, the civil service, the UK IPO, and other authorities in Brussels. And it is their responsibility at the end of the day to do the right thing, finally, by our community too.Uh, wait. You just said you weren't asking for a government handout, and then immediately turn around and ask for exactly that, claiming that the government must give you a hand out and a subsidy. Your rhetorical trick is to claim that this "handout" is "proper valuation." It's not. Copyright is a subsidy. It's a purposeful breaking of the free market, in order to allow PPL to charge a higher than market price. It's not a "proper" valuation. It's a monopoly valuation.To all those clever, smart, smug, cynical thinkers and others: HANDS OFF OUR COPYRIGHT. Hands off our employment opportunities, our income streams, our livelihoods and our future.Um, ok. How about hands off our privacy. Our culture. Our ability to share and communicate and to express ourselves? Hands off our wallets (via the government). Hands off our ability to use new and smarter business models.

    From there, Nevrkla goes into his "thank yous," naming lots of organizations and people who we normally see in these pages for trying to take away consumer rights and force the government to provide greater monopoly rights and subsidies. That's where the "capital punishment" joke comes in.

    Overall, however, the speech is stunning in its blatant dishonesty and cognitive dissonance, railing against gov't hand outs while not asking for them, but demanding them, as the only "just" way. The capital punishment statement is ridiculous, but at least we think he was joking. The rest of the speech is just dishonest and misleading -- and, for that reason, is much more worrisome.

    If you want to be frustrated by this ridiculousness, you can watch the whole thing (for free, for the "promotional value" of it), below:

    Permalink | Comments | Email This Story

    Original Link: http://techdirt.com/articles/20100614/1410259812.shtml

    Comments [0]