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
yoshuawuyts's profile
yosh
yosh
yosh
@yoshuawuyts

Tweets

yosh

@yoshuawuyts

Software researcher. he/they

Berlin, UTC+2
blog.yoshuawuyts.com
Joined May 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. yosh‏ @yoshuawuyts Jan 29
      • Report Tweet
      • Report NetzDG Violation

      New post: Tide Channels This is a design proposal for WebSocket and Server Sent Event support in Tide. I don't usually post about things at this stage on my blog, so this is me trying something new. (Also this was drafted in a day which is unusual, heh) https://blog.yoshuawuyts.com/tide-channels/ pic.twitter.com/6KfOms8mXC

      let mut app = tide::new();
app.at("/sse").get(tide::sse());
app.at("/").get(async |req| {
    req.sse().send(b"hello chashu").await?;
    Response::new(200)
});
app.listen("127.0.0.1:8080").await?;
      5 replies 16 retweets 92 likes
      Show this thread
    2. Daniel Carosone ⬡  🇸🇪  🇮🇹  🇦🇺‏ @redtwitdown Jan 29
      • Report Tweet
      • Report NetzDG Violation
      Replying to @yoshuawuyts

      I like a lot of this, especially footnotes 2&3, BUT ⚠️ "Matching channels with remote peers" is just not possible without authentication and session management. You are standing at the precipice of a session hijacking / injection trap ⚠️ Happy to discuss further if needed

      1 reply 0 retweets 1 like
    3. yosh‏ @yoshuawuyts Jan 29
      • Report Tweet
      • Report NetzDG Violation
      Replying to @redtwitdown

      Heh, yeah that section used to be called "security" and I guess it should've still left it at that 😅😅

      1 reply 0 retweets 1 like
    4. yosh‏ @yoshuawuyts Jan 29
      • Report Tweet
      • Report NetzDG Violation
      Replying to @yoshuawuyts @redtwitdown

      But yes, would love to chat more. Want to make sure we get this right

      1 reply 0 retweets 1 like
    5. Daniel Carosone ⬡  🇸🇪  🇮🇹  🇦🇺‏ @redtwitdown Jan 29
      • Report Tweet
      • Report NetzDG Violation
      Replying to @yoshuawuyts

      So hopefully the gap is clear: req1 to /ws establishes persistent server state (an open socket), req2 to some other page wants to give automatic access to that state. This is unambiguously a server-side session management job: req.session().ws() also: >1 open socket?

      1 reply 0 retweets 1 like
      yosh‏ @yoshuawuyts Jan 29
      • Report Tweet
      • Report NetzDG Violation
      Replying to @redtwitdown

      Ah yeah this makes a lot of sense! It seems the non-request API wouldn't be affected by this tho, which is nice. Maybe the right step is to start by defining a session API after that to enable per-endpoint handlers?

      3:02 PM - 29 Jan 2020 from Berlin, Germany
      2 replies 0 retweets 0 likes
        1. New conversation
        2. yosh‏ @yoshuawuyts Jan 29
          • Report Tweet
          • Report NetzDG Violation
          Replying to @yoshuawuyts @redtwitdown

          Also >1 open socket: most common use for this seems multiple tabs of the same site. Was thinking we just send the message to both. Can't think of cases where that's not desired?

          1 reply 0 retweets 0 likes
        3. Daniel Carosone ⬡  🇸🇪  🇮🇹  🇦🇺‏ @redtwitdown Jan 29
          • Report Tweet
          • Report NetzDG Violation
          Replying to @yoshuawuyts

          Common case for browsers might well be multiple tabs, general internet races / reload. my use is more api client than browser. I certainly can see opening multiple ws for separate purposes / streams. Each would be from a different endpoint, so could key on that. Some ZST magic?

          0 replies 0 retweets 1 like
        4. End of conversation
        1. Daniel Carosone ⬡  🇸🇪  🇮🇹  🇦🇺‏ @redtwitdown Jan 29
          • Report Tweet
          • Report NetzDG Violation
          Replying to @yoshuawuyts

          yes, I think I agree for non-req. I think that's also the only way I can see to handle client->server ws events? This might be the first use case for sessions. Not sure what tides intentions were for that, but once done, the rc'd ws can just be stashed there (w/ name for n>1?)

          0 replies 0 retweets 1 like
          Thanks. Twitter will use this to make your timeline better. Undo
          Undo

      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