acanby

Looks good and all... but I'm interested in the story on how it leaked on Twitter. The link just goes to the Github repo now.

I'll chime in here with my experience.

I am not someone who generally suffers from claustrophobia, but as a tall person (6ft 5in) who is by no means fat, I can honestly say it was one of the worst things I've had to do. My shoulders are broad enough that it felt as if I was uncomfortably wedged within the machine, and that I was far enough inside the machine that should something go wrong it would be impossible for me to get out unassisted.

Perhaps it wasn't so much claustrophobia in my case, more my total dependence on someone else to get out. I am definitely not looking to go through that experience again any time soon.

I think there are definitely things that can be done to improve the experience.

Also worth noting: I do realise that these machines come in different sizes, but they are also expensive to purchase (replace), so I am not holding my breath for regular updates at every hospital when they can add another inch to the diameter of the chamber.

You can shorten it even further to typing 'fori' then triggering the expansion by pressing tab.

Best shortcut that every IntelliJ user should know is "Find Action" (ctrl + shift + a on Win), press and start typing what you want to do. Will even present shortcuts in the list for next time.

I might be missing something here, but where is the passphrase negotiated? Apart from calling or talking to the other person, the only way to define this common key that I can see would be electronically. Isn't this a bit of a problem?

Japan uses them at airport check ins for their ticketing.

What is the best way to establish optimal pool size? The article seems to gloss over this and instead mentions 'you need to set pool: 25', but I doubt this is a one size fits all solution.

Anyone have any experience profiling these sorts of things that can share some info?

> If you’re using Twitter and Facebook for signup too you’ve got a bigger problem. A user’s credentials are then bound to another account on another service that could be canceled at any time, breaking access to your app without the user knowing

I'd never really thought about this. What do people suggest doing to handle this sort of use case?

> Now with hundreds of millions of map views across thousands of subscribers, the stability and scalability wins are clear

I'd also be interested to see a write up on these aspects, what are the gains here... 10%? 10x? 100x?

One problem I have with the current 2FA on Google Apps is that there is no way to enforce 2FA for all users before everyone sets up their mobile device. If you've set the requirement for all to have 2FA, then new users can never log in.

You're then left in this limbo of some with/some without 2FA, and unless you actively pursue those without it setup, you can never change that system wide setting in the control panel.

As someone who uses Terminal.app, what are the benefits of using iTerm2? After looking at the features of iTerm2[1], I see a lot of it as superfluous.

That said I can see a usecase in the Growl notification feature for testing etc.

[1] http://www.iterm2.com/#/section/features

I'd like to mention SourceTree[0] for a GUI DVCS. I typically drop to the terminal for git usage, but every so often use SourceTree when I need something that is easier achieved with a mouse.

[0] http://sourcetreeapp.com/

These decisions typically have much wider reaching ramifications, like an existing tech stack which relies on some quirk of IE6, or activeX. Yes, it's simple to upgrade a browser, but the potential impact must be evaluated, and this takes time (more than 10 mins to install a new browser).

I think this really depends on your target market. Big corps such as banks are typically slow to move and I know of at least one which is only just moving from IE6 now.

I think this stems from the memory these people hold that the item (whatever it is, doughnut, site access etc) was once free. People will wonder "why did this change?". It could be many things, but people will most likely jump to the easiest conclusion, the seller is greedy.

Using the doughnuts analogy, I wonder how things would have worked out if they continued to give away the plain doughnuts for nothing, but added a new line of premium iced doughnuts which attracted a charge? Personally I wouldn't mind, and I think that a lot of people would be ok with this.

Stemming from this, you really need to have a good reason to charge people for something they were previously using for free.

Personally, I don't think you can start charging for something that was previously free (without significant value add). By all means offer a paid upgrade with particular value add, but never do the wrong thing by your (thus far) loyal users.

Definitely another criteria we would like to have. Will try and source the info and add it in the future. Cheers!

Thanks for raising this, will take a look.

We plan on adding a reporting system into the site so people can flag inaccuracies, but that is still a little while off.

Dropdowns are a bit more intuitive now, hope that clears up any confusion :)

Ha - yeah I wouldn't be surprised. We haven't looked to make it mobile friendly yet, but it is on the list. Thanks for checking it out!

Appreciate the feedback! We're working to add the field labels now so stay tuned.

With regard to price, its a tough one. We purposefully left it out initially because it's subjective. If we use RRP - should a 2000MY Suzuki 650F be filtered because a brand new (2013) one is outside your price bracket? Obviously there are going to be differences, but we're thinking hard for a way to include this. I agree it would be a big helper!

Yep definitely more info required here isn't there :)

This targets the Australian market, and more specifically the state of New South Wales.

Some of the bikes may be expensive (or not worth learning on), but this list is provided by the Roads authority (RMS) as to what you can ride, not necessarily what you should ride.

Thanks for the feedback!

As a bit of background, in most states of Australia you can only ride restricted motorbikes (commonly referred to as LAMS bikes) when on your learner or provisional license. As motorcycle riders, we wanted to help people find out what bikes were out there.

We plan on growing the site into a place where all riders can discuss the pros and cons of each Learner Approved motorbike.

Lots of places we're looking improve on this, (ie the initial page load). We'd love to hear any other thoughts you have!

This is a good way for Facebook to leverage existing mobile App infrastructures without stepping on too many people’s toes. Developers are responsible for developing an app, and putting it on as many stores etc as they like. In this sense, there is no additional lock in by using the Facebook App Center if you are already using Facebook Connect.

I think the big question is - what happens for paid apps? Will Facebook be asking for a cut of any referrals? Take Draw Something for instance, which is $1.99 (or free). I know Facebook gets benefit from people playing and using Facebook Connect, but they have essentially handed that store the sale. I would think they would want to monetize this, and will be interested to see how this plays out. I wouldn’t be surprised if agreements are in place - as it would really be of mutual benefit.

FTA: "if a mobile app requires installation, they will be sent to download the app from the App Store or Google Play".

This would lead me to believe it is going to run like some existing iOS apps, such as Bejeweled 2. If you click that menu item from the Facebook iOS app, it will launch the Bejeweled application instead of running inside any FB container.

It's great to see you reaping a reward for going out on a limb - congratulations!

How do you think your pitch would have been received had this been in a more traditional forum? Do you think you would have achieved the same results, or would you have pitched a completely different angle?