Browsed by
Author: matt

Point Break Live!

Point Break Live!

This is crazy. These guys tour around the US and live re-enact the classic 80’s Keanu Reeves’ movie “Point Break”. But even better, they come with no lead actor. They grab a few willing fans out of the audience who quickly do 3 different audition quotes, the audience votes for the best one, and that person becomes agent Johnny Utah for the next hour and a half.

It’s a pretty hilarious time – totally recommend it.

Model wooden roller coaster

Model wooden roller coaster

Model maker Adam Throgmorton shows off an incredible build – a fully functioning, massively intricate HO-scale replica of an old-school wooden rollercoaster. He reports he worked on it over the course of 6 years.

I’m also going to bet he’s not married since it seems to have its own table in the house. 🙂

Saltscapes

Saltscapes

Australian photographer Murray Fredericks journeys to the center of Lake Eyre, a desert salt lake. Fredericks drags all of his equipment out into the barren landscape, capturing the dramatic sky reflected in both the inch-deep water and his rectangular mirror. The images are breathtaking color-based works.

The failure of Coin and why gadget ventures often fail

The failure of Coin and why gadget ventures often fail

Ben Einstein does an excellent analysis of the failure of many smart gadget companies.

His analysis breaks down like this:

First generation products are always plagued with bugs, fail whales, and even the occasional mass-recall – most companies can bounce back from these setbacks. But other companies do not. It boils down to risk.

Technical Risk and Product Risk

When it comes to hardware startups, there are two types of risk. They are manageable on their own, but together often spell failure. These risks are: technical risk and product risk.

Technical risk is the chance you can’t deliver a product due to an engineering or manufacturing constraint. Examples from Coin: getting an e-Ink screen, Bluetooth antenna, battery, and microprocessor all working in a 0.76mm thick PVC card.

Product risk, however, is the risk that many overlook. Most products have low product risk. They routinely fail in small ways, but those failures are viewed as mere annoyances. A pop top that breaks off once every 1000 cans of Coke, the Roomba that occasionally misses a spot, an Alexa that mistranslates your command and you try again. Not big deals. But an automated door lock that fails might leave one stranded outside at 2am in a bad part of town or opens the door to robbers, a website that exposes your address and bank accounts for emptying, or your sole payment method that fails you at a fancy dinner are another matter.

You likely have high product risk if any of these are true:

  1. If a small number (one or two) of failures over the lifetime of your product create a negative interaction (like door locks or sole payment methods).
  2. If users would pay significantly more for a product that is guaranteed to work 100% of the time (like wireless routers).
  3. If users rely on your product for critical business operations (like point-of-sale systems).
  4. If failure could wreak massive havoc on personal security or safety (like home security systems or cars).

The Goal:

Your goal then is to only have high risk in one of the two risk classifications. Very few companies that have both kinds of risk survive. Tesla and SpaceX are notable exceptions, which should give you an idea of the efforts you will need to go to in order to overcome these risks. The other method is to reduce your feature set to minimize technical complexity or lower user expectations in case of product failure.

Long haul overnight pilot from Europe to South America sets up 10+ hour time lapse…

Long haul overnight pilot from Europe to South America sets up 10+ hour time lapse…

Sales Wick is a long haul pilot and photographer. He was piloting a massive 10+ hour overnight flight from Switzerland to Rio de Janeiro. The route takes them across the Sahara and the Atlantic Ocean. While most people will be settling in for a night of sleep, he sets up his camera and captures this transcendent video. I won’t do it justice, so just read his words:

“(We go) …past the bright city light of the capital of Algeria towards the Sahara. Tonight will be a special night, since its one of the few nights every August where countless shooting stars will be seen all over the night sky. Deriving from the constellation of Perseus, these meteor showers will guide us through the night.

 Just as the bright city lights are vanishing behind us, the Milky way starts to become clearly visible up ahead. It’s now pacing us, at almost the speed of sound, along the invisible highway and the pitch-black night sky above this surreal landscape. Ahead of us are another eight hours flight time, but we already stopped counting the shooting stars. And we got already to a few hundred.”

If you ever doubt there is beauty in the world – watch this.

VNC-ing into Ubuntu 14.04

VNC-ing into Ubuntu 14.04

Some VNC functionality was broken in Ubuntu 14.04 due to Vino, but fortunately, it’s fixable:

 

Using a combination of clues from http://discourse.ubuntu.com/t/remote-desktop-sharing-in-ubuntu-14-04/1640 (which is all about VNC access) and https://bugs.launchpad.net/ubuntu/+source/vino/+bug/1281250 (which discusses the bug introduced into Vino) I have managed to resolve the matter.

Essentially you have to disable encryption on remote desktop access in Gnome due to a bug that has come to surface in Vino. However, some threads tell you to uncheck it in the wrong place. Follow these guidelines and you should be able to resolve it quickly.

Specifically it’s

dconf > org > gnome > desktop > remote-access > require-encryption – uncheck

and NOT

dconf > desktop > gnome > remote-access > enabled – uncheck

Here is how you do it:

  1. First make sure Desktop Sharing is set up properly.
  2. Download dconf-tools by typing in Terminal sudo apt-get install dconf-tools
  3. Run dconf-Editor
  4. Expand org
  5. Expand gnome
  6. Expand Desktop
  7. Select Remote Access
  8. Uncheck Require Encryption (don’t click on Set to Default as it rechecks it)
  9. Exit dconf-Editor

It should now work. Tested through a reboot and all good.

Hope it helps.

(I have got a screen shot of dconf but don’t have enough points on here to post it – I am sure everyone can work it out for themselves though! 🙂 )