This WEEK in GOOGLE 158

From The Official TWiT Wiki
Jump to: navigation, search


This WEEK in GOOGLE
Episode 158

Contents

This WEEK in GOOGLE 158: Forking the Meatball

Panel

Topics

  • NBC and the Olympics: the responsibility of a big platform
    • It is about stewardship. NBC has a bigger responsibility then normal when it comes to the Olympics.
    • Jeff was on CNN talking about NBC's coverage of the Olympics
    • He also compares NBC responsibility to Twitter's role in the case of Guy Adams: Twitter is more then just a service. Jeff blogged about it later: The responsibilities and opportunities of the platform.
    • Leo mentions App.net which is trying to build a Twitter-type service, but user-focused and without ads.
    • In a blog post titled The difficult challenge of media alignment Seth Godin suggested Twitter could let its top users pay.
    • Jeff believes in an advertising model and at the same time companies have to maintain their users trust. If NBC would broadcast the Olympics live, the superfans would watch and created more social buzz, leading to more viewers.
    • Leo: they are never going to change unless forced to by viewer finding other ways to get that content. Jeff: yes, as for instance using Tunnelbear to watch the Olympics ad free on the BBC.










  • Matt Honan got hacked
    • He blogs about this: Yes, I was hacked. Hard.
    • Does using Google's two step verification help?
    • Leo pointed out that the "Application specific passwords" are a weakness, as they can be used without the second factor. It's worth pointing out that the are no weaker than having two-factor two factor switched off, and is in fact more secure in many ways:
      • The password is only showed once - there is no way to get Google to show you it again
      • It is in essence a strong password because it is randomly generated
      • You only ever type it in once, from then on it is stored (hopefully encrypted) in the application that uses it (Outlook, Android whatever, iPhone etc).
      • Once you've typed it, that password is no longer vulnerable to keylogger attacks, because you'll never type it again.
      • You've already forgotten it. You probably didn't even type it - you cut-and-paste it
      • It can be revoked. If you suspect that password has been compromised, revoke it and create a new one. No need to change your master password and reconfigure everything.
      • Social engineering can't be used to extract it from you.
      • It's never going to get re-used on dodgy forums like many peoples Google password is.
      • Basically applications don't need to do two-factor between themselves, because they don't have the same flaws as humans.
    • But Google 2 step verification can also be hacked as the Cloudflare incident shows: CloudFlare Security Breach: The Result Of Smart Social Engineering, Flaw In Google’s Account Recovery System
    • Security Questions: The Biggest Joke in Online Identity Verification
    • Matt Cutts on Lifehacker writes Please Turn On Two-Factor Authentication
    • Facebook also has 2 step verification, called Login Approvals
    • and Lastpass uses Google Authenticator too



Segments

"We Do A Little Thing At The End"

External Links

Sponsors

Stamps.com

ting

Production Information

  • Produced & Edited by:
  • Links/Wiki Input by:
Info.png This area is for use by TWiT staff only. Please do not add or edit any content within this section.
Personal tools