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. Chris Dickinson‏ @isntitvacant 24 Mar 2019
      • Report Tweet
      • Report NetzDG Violation

      this is attainable in JS too. The ServiceWorkers spec has you instantiating Response types that have status, headers, and a body which can be an opaque-to-js stream

      2 replies 0 retweets 2 likes
      Show this thread
    2. obviously a fucking cat‏ @whale_eat_squid 24 Mar 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @isntitvacant

      I had heavily considered this when writing the second version of take-five (which uses entirely promised-based route handlers), but I wasn't sure how you'd signal to the framework "i'm done processing this request" (allowing you to short-circuit middleware processing)

      2 replies 0 retweets 1 like
    3. Chris Dickinson‏ @isntitvacant 24 Mar 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @whale_eat_squid

      I landed on “it’s important to maintain the invariant that all middleware runs in order” & dropped the constraint that the application be able to opt out of further processing.

      2 replies 0 retweets 1 like
    4. obviously a fucking cat‏ @whale_eat_squid 24 Mar 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @isntitvacant

      interesting. i ended up "dropping" middleware -- routes are arrays of async funs you run (and they run in order thanks to how js ends up processing arrays). you can short-circuit this by either calling a function on the `ctx` object to emit a value or not return a then-able

      1 reply 0 retweets 1 like
    5. Chris Dickinson‏ @isntitvacant 24 Mar 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @whale_eat_squid

      I went the route of saying “per handler middleware should be implemented as a higher order function”, ripped off from Django ca. v1.19 days

      2 replies 0 retweets 2 likes
    6. obviously a fucking cat‏ @whale_eat_squid 24 Mar 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @isntitvacant

      lol just looked up tide and of course @yoshuawuyts is involved. i swear they're like 5 miles ahead of where ever i am

      1 reply 0 retweets 2 likes
    7. yosh‏ @yoshuawuyts 24 Mar 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @whale_eat_squid @isntitvacant

      Haha, hi! :D Also in case you missed it: a big Tide rewrite was PRd last Thursday https://github.com/rustasync/tide/pull/156 …. It'll hopefully smooth out some of the bumps Tide has, making it a lot easier to use. If you have any thoughts on it, we'd love to hear them!

      1 reply 0 retweets 1 like
    8. Chris Dickinson‏ @isntitvacant 24 Mar 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @yoshuawuyts @whale_eat_squid

      oh i was thinking in particular of this PR. such great work, & so well explained! 🎉🎉

      1 reply 0 retweets 1 like
    9. yosh‏ @yoshuawuyts 24 Mar 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @isntitvacant @whale_eat_squid

      Yay, glad to hear you're into the new design! I'll pass the feedback along to the rest of the team ^^

      1 reply 0 retweets 1 like
    10. Chris Dickinson‏ @isntitvacant 24 Mar 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @yoshuawuyts @whale_eat_squid

      Something I noticed while working on spife that _might_ be useful for tide: defining body processing as a middleware lifecycle (That way you could define separate middleware for handling JSON / multipart / body length & mix and match at the app level)

      1 reply 0 retweets 1 like
      yosh‏ @yoshuawuyts 24 Mar 2019
      • Report Tweet
      • Report NetzDG Violation
      Replying to @isntitvacant @whale_eat_squid

      Ohh, interesting! What kind of middleware are you referring to? The concept of extractors still lives on inside the Context argument. E.g. ctx.body_json() can convert the incoming body stream to a typed struct. And it can be extended with custom impls! Or is that different?

      3:00 PM - 24 Mar 2019
      1 reply 0 retweets 0 likes
        1. New conversation
        2. Chris Dickinson‏ @isntitvacant 24 Mar 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @yoshuawuyts @whale_eat_squid

          Hm, it's tricky (I'm still new to Rust so it might not translate!) In spife there's a middleware list; each mw can provide "lifecycle" functions – for "startup", "incoming request", and "handler accessed request body data". That last one is on `request.body` access.

          1 reply 0 retweets 1 like
        3. Chris Dickinson‏ @isntitvacant 24 Mar 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @isntitvacant @yoshuawuyts @whale_eat_squid

          The goal was to decouple "My application wants structured data" from "The framework knows how to decode the underlying request format" – the handler doesn't know if it's talking JSON, multipart, tarball, etc & doesn't care. Middleware can handle that (& fail with a 400 if not)

          1 reply 0 retweets 1 like
        4. 4 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