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.
  • 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
slightlylate's profile
Alex Russell
Alex Russell
Alex Russell
@slightlylate

Tweets

Alex Russell

@slightlylate

Chrome Project 🐡 & Web Standards TL; Blink API OWNER Named PWAs w/ @phae; probably making her ☕ DMs open. Tweets my own; press@google.com for official comms.

San Francisco, The Internet
infrequently.org
Joined December 2010

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. Alex Russell‏ @slightlylate 19 Jun 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @sintaxi @joemccann

      That's a bit orthogonal. Notifications are possible w/o Push, and browser choice is A Thing (outside iOS, at least).

      1 reply 0 retweets 0 likes
    2. Brock Whitten‏ @sintaxi 19 Jun 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @slightlylate @joemccann

      I can see why you say that given the design choices that were made. I understand the landscape at the time and the goal was to match what native offers. With that said, would you say I'm providing inaccurate or unnecessary information with respect to the question?

      1 reply 0 retweets 0 likes
    3. Brock Whitten‏ @sintaxi 19 Jun 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @sintaxi @slightlylate @joemccann

      Alex, shoot me any relevant information you might have on this if you think I got the wrong idea. Also, I'm not entirely sure what you mean by notifs w/o push, if you can clarify on that I'd appreciate it.

      1 reply 0 retweets 0 likes
    4. Alex Russell‏ @slightlylate 19 Jun 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @sintaxi @joemccann

      Sorry, wasn't meaning to be argumentative! Was only noting that the push backend can be whatever service the browser chooses, so browser choice allows for different implementations.

      2 replies 0 retweets 0 likes
    5. Alex Russell‏ @slightlylate 19 Jun 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @slightlylate @sintaxi @joemccann

      Regarding notifications without push, if you have a document open, the `new Notification(...)` API still works: https://developer.mozilla.org/en-US/docs/Web/API/notification …

      1 reply 0 retweets 0 likes
    6. Brock Whitten‏ @sintaxi 19 Jun 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @slightlylate @joemccann

      Thank you! So if I understand this correctly one could poll for messages in the worker thread and notify the user without the need for a push provider? If so that is really fantastic and addresses my concerns.

      1 reply 0 retweets 0 likes
    7. Brock Whitten‏ @sintaxi 19 Jun 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @sintaxi @slightlylate @joemccann

      To further my concerns a big factor for me with web notifs is the developer experience. Seems less than ideal that developers have to register projects with all the browser their users might be using. Its also an additional disadvantage to new browsers that lack marketshare.

      1 reply 0 retweets 0 likes
    8. Stuart Langridge‏ @sil 19 Jun 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @sintaxi @slightlylate @joemccann

      As I understand this, and I really may not, the way it's _meant_ to work is, the page says "do you want push notifications?", user says yes, browser API returns a push URL and token, page sends that to server, server hits the page URL with the token to send a notification, done.

      2 replies 0 retweets 0 likes
    9. Brock Whitten‏ @sintaxi 19 Jun 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @sil @slightlylate @joemccann

      I'm guessing each browser has a consolidated socket that routes the push notifications for all the domains the user has accepted push notifications for - which is why the projects need to be registered by the publishers with each browser vendor. 1 socket = better battery life.

      2 replies 0 retweets 1 like
    10. Stuart Langridge‏ @sil 19 Jun 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @sintaxi @slightlylate @joemccann

      I don't _believe_ that's the case. AIUI (and again I may be wrong), Firefox listens to a Mozilla endpoint, sure, but the push notification API gives your client side js just a URL which you send to your server. Your server doesn't care where that URL is.

      2 replies 0 retweets 0 likes
      Alex Russell‏ @slightlylate 19 Jun 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @sil @sintaxi @joemccann

      Brock is right. The URL is for servers to route messages to the push provider, which then does last-mile over the consolidated socket.

      3:45 PM - 19 Jun 2018
      1 reply 0 retweets 0 likes
        1. New conversation
        2. Stuart Langridge‏ @sil 19 Jun 2018
          • Report Tweet
          • Report NetzDG Violation
          Replying to @slightlylate @sintaxi @joemccann

          Agreed with that, but I don't think servers have to "register" at all, do they? They just get, for each user who wants push notifications, a URL/token for that user, and to send a push notification they send standard JSON to that URL. No registration required.

          1 reply 0 retweets 0 likes
        3. Brock Whitten‏ @sintaxi 19 Jun 2018
          • Report Tweet
          • Report NetzDG Violation
          Replying to @sil @slightlylate @joemccann

          If I'm not mistaken what Alex has just shown me is that alternatively you can have the user grant notification permission to the worker thread and the worker thread can poll any backend. This eliminates the need for project registration but you have to BYOB (backend).

          2 replies 0 retweets 0 likes
        4. 3 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