August 2011 archive

Dulwich – a native python way to access Git repositories

Ever wanted to manipulate Git repositories directly in python? Well, okay… I haven’t really myself, but in writing about Google Code’s support for git yesterday, I noticed that they are using Dulwich, a native python implementation of git. Rather than wrapping command-line git with python scripts, Dulwich is a python module giving you direct access to a git repository. As shown in the Dulwich tutorial, creating a new repo is simply this:

>>> from dulwich.repo import Repo
>>> from os import mkdir
>>> mkdir("myrepo")
>>> repo = Repo.init("myrepo")
>>> repo
<Repo at 'myrepo'>

Once a repo is created (or you connect to an existing repo), you can do what you would do with git at the command line: adding files to the repo, committing files, and changing files.

While I don’t know that I personally will use this… it’s very cool that Dulwich is out there for python programmers who want to interact with git repos. Very cool to see!

European Union Security Agency Releases Report Analyzing HTML5 Security

Html5logo 200ComputerWorld today reports that the European Network and Information Security Agency (ENISA) has released a detailed report analyzing the security of HTML5 and related web protocols.

While not directly related to Unified Communications, the reality is that many UC web interfaces, particularly for mobile devices, may turn to HTML5 as a way to create a web interface that provides an excellent user interface and works across all mobile devices.

Perhaps more importantly, the work of the RTCWEB/WebRTC working groups within the IETF and W3C, which I've written about over on Voxeo's blogs, is aimed at bringing the "real-time communications" functionality directly into the web browser. In other words, you wouldn't need a browser plugin or additional program on your computer to make voice, video or chat connections… it could happen entirely within the browser.

At that point every browser potentially can become a UC endpoint… and therefore a concern for communications security.

It's a lengthy document from ENISA, but worth a read as it dives into both analysis and recommendations for greater HTML5 security.

Google Code Now Supports Git for Hosted Projects

Being a big fan of Git for version control, I was very pleased to see the announcement last week that projects hosted at Google Code can now use git in addition to subversion and mercurial (see also Google Code’s GitFAQ). I had looked at hosting projects on Google Code in the past, but chose not to specifically because git was not an option. While I personally am quite happy using Github for project hosting, it’s always good to see other services supporting git:

Googlecodeandgit

Way to go, Google Code!

XKCD’s Brilliant – And Sad – Comic About Cancer…

Someone recently pointed this XKCD comic out to me and it is both brilliantly done ... and hits home at the tragedy of where we are at as a society with cancer:

Xkcd cancer

The scary part is exactly what the strip shows... you don't know if or when it may ever return. :-(

And yeah... F___ Cancer!

Walled Garden Deja Vu: Facebook Provides "facebook.com" Email Addresses

Over the weekend, I had a severe case of deja vu... and found myself humming that song from Styx that includes the line "Haven't we been here before...".

Why?

Because Facebook followed through on its earlier statement around letting people receive email to a "facebook.com" email address:

Facebook email

So yes, indeed, because clearly I need more email addresses, you can now send me email to:

dyork@facebook.com

[On a side note, I will be very curious to see what kind of anti-spam measures Facebook puts in place as these addresses get out there. Consider this my little test... putting that email address out here on a public blog site where it can be easily scraped.]

The deja vu part is that ... we've been here before. Remember AOL? CompuServer? Prodigy? Delphi? MCI Mail? GENIE?

Remember all those "walled gardens" of the original "computer information services"?

And remember those glorious days when you could FINALLY get an email address so that you could send and receive to people outside the walls of whatever service you used? (Even if those addresses were sometimes hard to write or remember? ex. CompuServe's numerical addresses.)

While I realize that some % of readers of this post in 2011 were probably not born in the heydey of those services, for those of us who were around those were big days when we finally got those email addresses.

Soon everyone had an open Internet email address... the walls came down... and communication happened across all services.

Over time, though, the walls started coming back up. I wrote about this four years ago in a May 2007 post, "Facebook, MySpace, Twitter and the Return of the Walled Gardens of E-Mail" and drew my view of the evolution of email:

Evolutionofemail

[Another side note: Notice how things change in 4 years and some of the services I mentioned on the right that are no longer around or relevant...]

And so now we Facebook giving us a way to receive email messages. We've had the ability to send email messages out of Facebook for some time now, but it was sent from cryptic, ugly addresses that changed. Now we have a "regular" email address... and indeed an outbound message from Facebook to my "dyork@voxeo.com" address looks fine in my regular email client:

Fbemailmsg

Note, of course, that since Facebook does not let you set a "Subject" line on an outbound message you create, the subject is simply "Conversation with Dan York".

When a message is initially received from the outside, the subject line of that email is preserved, as you can see here:

Fbemailinbound

The "Hidden Text" in this case was my normal Voxeo email signature.

All in all it works quite well. I'm not naive enough to think that this is some great idea by Facebook to open up to the outside world... the simple fact is that they want to keep you inside of Facebook where you interact with people on Facebook... and, oh, yes, view all the advertising.

If Facebook can convince you to use the site as your email portal, instead of, oh, GMail, then Facebook and their advertisers win against Google and its advertisers.

Of course, Facebook still has its incredibly onerous Terms of Service that basically says all your email - and any other content - belong to Facebook... so I don't see me personally using my "dyork@facebook.com" email account all that often outside of the regular FB messaging I'll be doing there.

Still, all cynicism and deja vu aside, as an advocate for the open Internet I am pleased to see this move by Facebook. Some people have made Facebook their portal of choice... and this now lets people choose other sites as their portals of choice, yet still communicate with Facebook users.

In the end, this openness - and ability for us to control our choice of communication - is exactly what we need.

Have you "claimed" your Facebook email address yet? Will you use it?


If you found this post interesting or useful, please consider either: