I was just reading through Google+'s Terms of Service because I was interested to see what was to happen to my images, should I upload them to Google+. I am weary to upload photos to Facebook, because Facebook claims rights to my images and may do with them whatever it pleases. This bothers me, and I wanted to see if Google+ was going to be the same.

If you read Section 9, it states:

9.4 Other than the limited license set forth in Section 11, Google acknowledges and agrees that it obtains no right, title or interest from you (or your licensors) under these Terms in or to any Content that you submit, post, transmit or display on, or through, the Services, including any intellectual property rights which subsist in that Content (whether those rights happen to be registered or not, and wherever in the world those rights may exist).

Sounds peachy, doesn't it? I would propose that Google's betting you're lazy and, if you read the TOS at all, you sure as hell won't follow the references. Well, I did. Here's Section 11:

11.2 You agree that this license includes a right for Google to make such Content available to other companies, organizations or individuals with whom Google has relationships for the provision of syndicated services, and to use such Content in connection with the provision of those services.

Hm. Not so good. I would really prefer that the stated "other companies, organizations or individuals" not have access to my content. But there's that phrase where, if you're not in the business, you wouldn't understand: syndicated services. Hm. What is that?

Well, I have an answer for you. From TechTarget's definition:

For many years mainly a feature of print media, today content syndication is the way a great deal of information is disseminated across the Web. Reuters, for example, provides online news content to over 900 Web sites and portals, such as Yahoo and America Online.

So Google or any of its affiliates who fall into the above category are allowed to disseminate my information across the Web.

No, thank you. I think I'll post them somewhere else.

I was recently cleaning out my room at home (I'm back from college for the summer) and found an old git cheat-sheet. I thought I would electronically log it for future reference (as though I don't use git every day or something...).

git init
git clone git://github.com/username/repo.git
git add filename
git status [-s]
git diff [--cached] [HEAD] [--stat]
git commit [-a] [-m "commit message"]
git reset [HEAD]
git rm [--cached] filename
    # (by adding --cached, the file that's deleted
   # will be left in your local directory)
 
git branch branchname
git checkout branchname
git checkout -b branchname
git branch -d branchname # (delete)
 
git merge branchname # (merges 'branchname' to current branch)
git mv file newfile
git log [--oneline] [--graph] [branchname] [^compared_branch_name]
git tag -a msg commit_shortcode
 
git remote [-v]
git remote add alias [email protected]:username/repo.git
git fetch alias