Search results
  1. 11 Aug 2017

    This is important:

    1 reply 10 retweets 10 likes
  2. 29 Dec 2020

    Day 3 of Thanks for all the great submissions! also works remotely! too!

    2 retweets 8 likes
  3. 11 Aug 2017

    Happy to see the 418 status code is here to stay, at least for now...

    1 reply 3 retweets 9 likes
  4. 7 Apr 2018

    A new purchase. I'm addicted to mint tea.

    1 retweet 3 likes
  5. 5 Oct 2017

    good gifting

    1 reply 2 retweets 10 likes
  6. 11 Aug 2017

    Long live the Teapot \o/

    2 retweets 4 likes
  7. 18 Apr 2018

    Cheers ☕️ on 4.18 at SF HWC ☕️ cc: – at Mozilla San Francisco

    1 reply 3 retweets 4 likes
    Show this thread
    Show this thread
  8. 11 Aug 2017

    Save a Teapot!

    1 retweet 9 likes
  9. 11 Aug 2017

    Enjoying the ease with which lets you define your HTTP response codes ().

    5 likes
  10. Aug 7

    As the RFC says, the resulting entity MAY be short and stout. Now available in v0.22.2 and v0.23.1. 🫖

    I’ve been contributing to open source for a couple of years now, but getting `418 I’m A Teapot` added to is my proudest contribution to date.
    1 reply 5 retweets 21 likes
  11. 11 Aug 2017

    I'm on

    1 retweet 1 like
  12. 11 Aug 2017

    "net/http: remove support for status code 418 I'm a Teapot"

    3 retweets 2 likes
  13. 10 Aug 2017

    Save Error Code 418

    1 reply 1 retweet 4 likes
  14. 7 May 2020

    Just letting you know that the domain 🫖.to (<teapot>.to) is available. Someone needs to register it and make it return 418 I'm a teapot. 🫖.to

    1 like
  15. 11 Aug 2017

    HTTP Error Code "418 I'm a Teapot" is about to be removed from :

    2 retweets 4 likes
  16. 10 Aug 2017

    Any attempt to brew coffee with a teapot should result in Error 418 - I'm a teapot! Save Error 418!

    2 retweets 6 likes
  17. 11 Aug 2017

    As author of RFC 7168, extending Hypertext Coffeepot Control Protocol, I fully endorse and demand action to save our teapots.

    1 reply 6 retweets 13 likes
  18. 10 Aug 2017

    Someone wants to remove HTTP status code 418 support from the popular libraries! Don't let it happen!

    3 retweets 2 likes
  19. 13 Aug 2017

    I think the internet could use a good laugh, given the horror over of the past two days. Here it is:

    2 retweets 5 likes
  20. 11 Aug 2017

    Always thought JavaScripters were a bit of a humorless bunch ;)

    1 reply 2 retweets 2 likes

No results.

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.