I’m The Robot In The Back of the Room

Your Conference
Robot Overlord

My post earlier this week about Stanford’s CodeX program got me an invite to the conference being held there today. Since I didn’t have enough time (or money) to make an immediate flight to the Bay Area, the conference organizers were willing to “Beam” me into the conference. I have to admit, I was assuming this just meant that they had some type of WebEx or video broadcast that I would use to attend the meeting. I had no idea that I would actually be a movable video projecting, interacting “robot” meandering my way through the other attendees. When I realized this, I completely started geeking out and immediately started telling all my friends that I was now a robot at Stanford.

There’s a lot of good discussions going on in the conference, and I’ll write more about it later, but I wanted to put out a quick post on my experience controlling a device that was 1,900 miles away. I immediately thought I was Howard from Big Bang Theory controlling the Mars Rover (see… geeking out!)

The device is about 100 lbs., and about 5’3″ tall. So, I’m thinner, but shorter. It is really sturdy and very balanced. It moves around at a top speed of 2 mph, and you can control it either from your keyboard (arrow keys or game style left-hand keys), through the mouse, or if you’ve connected a game controller, you can control it through that. It’s actually really easy to move around. I’ve found my way to the back of the room, and was able to find a space and back my way against the wall.

You have two screens to “see” what’s going on. The big screen is landscape and is your main view of what’s going on. The bottom screen is more square and is pointed down so that you can see the base of the device as well as a more horizontal view of the main screen. This enables you to see someone that is standing in front of you from head to toe. It’s really a great way to feel like you are really in front of the person you’re talking.

You get sound from all around. This is probably the part that is the hardest to deal with, especially when there is a lot of room noise. Sometimes the sound is jumbled, but almost all the time I was able to hear what was being said, but you have to focus a bit more than you would if you were there in person.

Battery life on the device is a max of 8 hours. Unfortunately, mine didn’t start off with a full charge today, so I had to put it back on the charging base for about 30 minutes to an hour. Luckily, that’s long enough for me to write this post, and go grab some Thai food for lunch before beaming back to Stanford this afternoon.

My overall experience so far? This is really amazing. I can see a number of uses for this at conferences and meetings all over the world. Eventually, I’d think that conference centers would start having these set up at their facilities and charging people to use them, or allotting a number of devices to the conference presenters to allow people that cannot travel to the conference to still “be there.”

Being Interviewed by Mike Swift of MLex

I’ve been asked already how people are reacting to the device. I’d say that at first I was very reluctant to “meet” people because I wasn’t sure about the “space” I was taking, or how loud I would be, or how I would be able to hear them. Sarah Glassmeyer was gracious enough to help me walk around, and after just a few moments, people were coming up to me. David Curle said I was “creepy” but I’m hoping he was talking about the machine, and not me… I really hope that’s the case! People very quickly adapted to seeing the machine zipping around, and while it was probably still creepy, curiosity overwhelmed some and they came up and started chatting with me.  My quest for this afternoon is to attend a session, and then ask the presenters a question at the microphone. I’m very curious as to how the audience will react to the Robot Overlord coming up to speak at the mic.

I’d like to thank Erin Rapacki, Director of Marketing, and Klaudia Warren, also from suitabletech.com for setting me up with their Beam device. And to Nicole Shanahan, CodeX Fellow and Founder/CEO at ClearAccessIP for their help in allowing me to attend the CodeX conference remotely.

Original URL: http://feedproxy.google.com/~r/geeklawblog/~3/m8C0ArOWMTU/im-robot-in-back-of-room.html

Original article

Improving the GitHub Workflow for the Microsoft Community

At Microsoft Build 2015, we announced deep GitHub integration in Visual Studio 2015, along with GitHub Enterprise 2.2.0. This release will help developers who work with the Microsoft stack make GitHub Enterprise a seamless part of their existing workflow. If you’d prefer to skip the summary, you can see a full list of new features in the release notes. If you’re interested in the highlights, read on.

GitHub Enterprise now supported on Hyper-V and available on Microsoft Azure

It’s important to be able to deploy and run GitHub Enterprise wherever you want. If your team works on the Microsoft stack, we have great news. With the 2.2.0 release, you can now host GitHub Enterprise in the Windows ecosystem using Hyper-V for local hosting or Azure for cloud hosting.

Powerful Collaboration - GitHub Enterprise

To request a 45-day trial of GitHub Enterprise on Azure just let us know.

GitHub Extension for Visual Studio

The new GitHub Extension for Visual Studio lets you work on GitHub repositories within Visual Studio 2015. Once you download the latest version of Visual Studio, you can log in to GitHub, clone and create repositories, and publish your local work without leaving your IDE. To see a walkthrough of the features, check out this video on Microsoft’s Channel 9.


Microsoft Developer Assistant

In case you missed it, Microsoft also announced the availability of the Microsoft Developer Assistant for Visual Studio 2015—a way for developers to search for code on GitHub.com from Visual Studio. Just enter your query and you will see links to public code on GitHub.com, along with information about the project.

Wait, there’s more!

Beyond the Microsoft integration you’ll find lots more to like in Enterprise 2.2.0 including:

  • PDF rendering
  • Mobile web notifications
  • Quick pull requests
  • Xen hypervisor support

For a full list of what’s new, check out the release notes.

If you already use GitHub Enterprise, you can download the latest release from enterprise.github.com.

If you are attending Build 2015 and want to learn more, visit the GitHub booth on the third floor.

Original URL: http://feedproxy.google.com/~r/feedsapi/BwPx/~3/-tAbOOwbHi4/1989-improving-the-github-workflow-for-the-microsoft-community

Original article

Deprecating Non-Secure HTTP

Today we are announcing our intent to phase out non-secure HTTP.

There’s pretty broad agreement that HTTPS is the way forward for the web.  In recent months, there have been statements from IETF, IAB (even the other IAB), W3C, and the US Government calling for universal use of encryption by Internet applications, which in the case of the web means HTTPS.

After a robust discussion on our community mailing list, Mozilla is committing to focus new development efforts on the secure web, and start removing capabilities from the non-secure web.  There are two broad elements of this plan:

  1. Setting a date after which all new features will be available only to secure websites
  2. Gradually phasing out access to browser features for non-secure websites, especially features that pose risks to users’ security and privacy.

For the first of these steps, the community will need to agree on a date, and a definition for what features are considered “new”.  For example, one definition of “new” could be “features that cannot be polyfilled”.  That would allow things like CSS and other rendering features to still be used by insecure websites, since the page can draw effects on its own (e.g., using ).  But it would still restrict qualitatively new features, such as access to new hardware capabilities.

The second element of the plan will need to be driven by trade-offs between security and web compatibility.  Removing features from the non-secure web will likely cause some sites to break.  So we will have to monitor the degree of breakage and balance it with the security benefit.  We’re also already considering softer limitations that can be placed on features when used by non-secure sites.  For example, Firefox already prevents persistent permissions for camera and microphone access when invoked from a non-secure website.  There have also been some proposals to limit the scope of non-secure cookies.

It should be noted that this plan still allows for usage of the “http” URI scheme in legacy content. With HSTS and the upgrade-insecure-requests CSP attribute, the “http” scheme can be automatically translated to “https” by the browser, and thus run securely.

Since the goal of this effort is to send a message to the web developer community that they need to be secure, our work here will be most effective if coordinated across the web community.  We expect to be making some proposals to the W3C WebAppSec Working Group soon.

Thanks to the many people who participated in the mailing list discussion of this proposal.  Let’s get the web secured!

Richard Barnes, Firefox Security Lead

Original URL: http://feedproxy.google.com/~r/feedsapi/BwPx/~3/wn1KZBUiN7k/

Original article

How to build nginx with Google PageSpeed module on Debian 8 (Jessie)

This tutorial explains how to build nginx with the latest version of the Google PageSpeed (nginx_pagespeed) module on Debian Jessie. The PageSpeed module applies web performance best practices to pages, and associated assets (CSS, JavaScript, images) and therefore speeds up your web site and reduces load times.

Original URL: https://www.howtoforge.com/tutorial/nginx-with-ngx_pagespeed-on-debian-8-jessie/

Original article

Proudly powered by WordPress | Theme: Baskerville 2 by Anders Noren.

Up ↑

%d bloggers like this: