Skip to content
By using Twitter’s services you agree to our Cookies Use. We and our partners operate globally and use cookies, including for analytics, personalisation, and ads.

This is the legacy version of twitter.com. We will be shutting it down on June 1, 2020. Please switch to a supported browser, or disable the extension which masks your browser. You can see a list of supported browsers in our Help Center.

  • Home Home Home, current page.
  • About

Saved searches

  • Remove
  • In this conversation
    Verified accountProtected Tweets @
Suggested users
  • Verified accountProtected Tweets @
  • Verified accountProtected Tweets @
  • Language: English
    • Bahasa Indonesia
    • Bahasa Melayu
    • Català
    • Čeština
    • Dansk
    • Deutsch
    • English UK
    • Español
    • Filipino
    • Français
    • Hrvatski
    • Italiano
    • Magyar
    • Nederlands
    • Norsk
    • Polski
    • Português
    • Română
    • Slovenčina
    • Suomi
    • Svenska
    • Tiếng Việt
    • Türkçe
    • Ελληνικά
    • Български език
    • Русский
    • Српски
    • Українська мова
    • עִבְרִית
    • العربية
    • فارسی
    • मराठी
    • हिन्दी
    • বাংলা
    • ગુજરાતી
    • தமிழ்
    • ಕನ್ನಡ
    • ภาษาไทย
    • 한국어
    • 日本語
    • 简体中文
    • 繁體中文
  • Have an account? Log in
    Have an account?
    · Forgot password?

    New to Twitter?
    Sign up
pcwalton's profile
Patrick Walton
Patrick Walton
Patrick Walton
@pcwalton

Tweets

Patrick Walton

@pcwalton

Research engineer at Mozilla

San Francisco, CA
pcwalton.github.io
Joined November 2009

Tweets

  • © 2020 Twitter
  • About
  • Help Center
  • Terms
  • Privacy policy
  • Imprint
  • Cookies
  • Ads info
Dismiss
Previous
Next

Go to a person's profile

Saved searches

  • Remove
  • In this conversation
    Verified accountProtected Tweets @
Suggested users
  • Verified accountProtected Tweets @
  • Verified accountProtected Tweets @

Promote this Tweet

Block

  • Tweet with a location

    You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more

    Your lists

    Create a new list


    Under 100 characters, optional

    Privacy

    Copy link to Tweet

    Embed this Tweet

    Embed this Video

    Add this Tweet to your website by copying the code below. Learn more

    Add this video to your website by copying the code below. Learn more

    Hmm, there was a problem reaching the server.

    By embedding Twitter content in your website or app, you are agreeing to the Twitter Developer Agreement and Developer Policy.

    Preview

    Why you're seeing this ad

    Log in to Twitter

    · Forgot password?
    Don't have an account? Sign up »

    Sign up for Twitter

    Not on Twitter? Sign up, tune into the things you care about, and get updates as they happen.

    Sign up
    Have an account? Log in »

    Two-way (sending and receiving) short codes:

    Country Code For customers of
    United States 40404 (any)
    Canada 21212 (any)
    United Kingdom 86444 Vodafone, Orange, 3, O2
    Brazil 40404 Nextel, TIM
    Haiti 40404 Digicel, Voila
    Ireland 51210 Vodafone, O2
    India 53000 Bharti Airtel, Videocon, Reliance
    Indonesia 89887 AXIS, 3, Telkomsel, Indosat, XL Axiata
    Italy 4880804 Wind
    3424486444 Vodafone
    » See SMS short codes for other countries

    Confirmation

     

    Welcome home!

    This timeline is where you’ll spend most of your time, getting instant updates about what matters to you.

    Tweets not working for you?

    Hover over the profile pic and click the Following button to unfollow any account.

    Say a lot with a little

    When you see a Tweet you love, tap the heart — it lets the person who wrote it know you shared the love.

    Spread the word

    The fastest way to share someone else’s Tweet with your followers is with a Retweet. Tap the icon to send it instantly.

    Join the conversation

    Add your thoughts about any Tweet with a Reply. Find a topic you’re passionate about, and jump right in.

    Learn the latest

    Get instant insight into what people are talking about now.

    Get more of what you love

    Follow more accounts to get instant updates about topics you care about.

    Find what's happening

    See the latest conversations about any topic instantly.

    Never miss a Moment

    Catch up instantly on the best stories happening as they unfold.

    1. Marcos Cáceres‏ @marcosc 31 May 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @tobie

      I don’t think so. Mozilla looked at using Blink/Electron a few years ago, but decided to all in on Gecko, Rust, etc. instead. Although engine is important, it’s not the limiting factor here.

      1 reply 0 retweets 6 likes
    2. Tobie Langel‏ @tobie 31 May 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @marcosc

      I'm not suggesting Gecko is the limiting factor, just that keeping it competitive with Chromium at the platform level is guzzling resources which could be used to innovate in areas closer to Mozilla's mission (and more impactful).

      2 replies 0 retweets 5 likes
    3. John Wilander‏ @johnwilander 2 Jul 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @tobie @marcosc

      I’m joining late, I know. I think the framing is wrong here. Chrome, and through the lack of protections also Blink, are becoming the example of what *not* to do with the web platform. Hopefully, they’ll change but joining that project now is the opposite of being progressive.

      2 replies 0 retweets 11 likes
    4. Tobie Langel‏ @tobie 2 Jul 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @johnwilander @marcosc

      I understand those considerations, but it seems Edge is able to add privacy-protecting mechanisms on top of Blink/Chromium, no? Or am I missing pieces.

      1 reply 0 retweets 2 likes
    5. BrendanEich‏Verified account @BrendanEich 3 Jul 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @tobie @johnwilander @marcosc

      We’ve been doing it a lot longer at @Brave — it is adversarial, even ignoring intentions, because chromium is big and hard to audit and rearchitect incrementally downstream, while upstream adds features that may weaken or subvert privacy.

      2 replies 1 retweet 14 likes
    6. Tobie Langel‏ @tobie 3 Jul 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @BrendanEich @johnwilander and

      Well, precisely. Wouldn’t bringing Mozilla’s strong, privacy-orientated engineering culture to Chromium potentially help with this, not only for Firefox users but for users across the board?

      3 replies 0 retweets 1 like
    7. Yehuda Katz  🥨‏Verified account @wycats 3 Jul 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @tobie @BrendanEich and

      I think that what @brave is doing is what you are suggesting, and @BrendanEich is testifying that the relationship is adversarial. I think you're deeply discounting the power of controlling your own implementation. Remember the original Blink fork?

      3 replies 0 retweets 11 likes
    8. Robin Berjon‏ @robinberjon 3 Jul 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @wycats @tobie and

      I don't think that what Brave is doing is what Tobie suggested though. He talked of taking Chromium to an open governance model, evidently this would have to remove it from Google, not to involve working downstream.

      3 replies 0 retweets 4 likes
    9. Yehuda Katz  🥨‏Verified account @wycats 3 Jul 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @robinberjon @tobie and

      What leverage does Mozilla have to force Google to relinquish more control over Chromium?

      2 replies 0 retweets 0 likes
    10. Patrick Walton‏ @pcwalton 3 Jul 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @wycats @robinberjon and

      I've been hesitant to wade into this whole topic but I think it's fascinating how the conversation has shifted from "Mozilla should adopt Blink" (few years ago) to "Mozilla should adopt Blink *if* Chromium changes its governance" (today).

      2 replies 0 retweets 8 likes
      Patrick Walton‏ @pcwalton 3 Jul 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @pcwalton @wycats and

      (to be clear, I think the latter is so extraordinarily unlikely to happen that it's not even worth discussing)

      12:16 PM - 3 Jul 2019
      • 10 Likes
      • Brendan Zabarauskas Rhaladriel Kris Siegel Tobie Langel qualia are a fuck Ryan Cragun BrendanEich Manish eddyb, thriving in isolation,
      1 reply 0 retweets 10 likes
        1. New conversation
        2. Yehuda Katz  🥨‏Verified account @wycats 3 Jul 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @pcwalton @robinberjon and

          Yes, this is so evident to me that I'm feeling a bit of vertigo that it's even something we're discussing. I could imagine some technical governance changes, but nothing that would substantially relinquish Google control.

          2 replies 0 retweets 5 likes
        3. Tobie Langel‏ @tobie 3 Jul 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @wycats @pcwalton and

          Interesting. I feel like it could have a ton of benefits for Google. Also the risk is actually very limited: if it doesn’t work out, you fork and you’re back with the current status quo, and potentially even with a good story if you spin it properly.

          1 reply 0 retweets 0 likes
        4. 11 more replies

      Loading seems to be taking a while.

      Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.

        Promoted Tweet

        false

        • © 2020 Twitter
        • About
        • Help Center
        • Terms
        • Privacy policy
        • Imprint
        • Cookies
        • Ads info