1. Exquisite Tweets from @dj_mckeown, @sciencehackday, @Stuart_Lynn, @mikamckinnon, @adactio, @SciEllen, @adllewellyn, @seanherron, @jdunck, @PatrikD, @marisfessenden, @HelenShenWrites, @JacobShiach, @bioCURIOUSlab, @BasilLeaf, @arielwaldman, @junaxup, @SciHackSA, @arfon, @briansuda, @r_hian, @skytland, @davidtlang, @mattb, @jonjohns65, @kevinrohling, @rocket_bala, @carolune, @eshagh, @meganmansell, @erigentry, @Sofarocean, @jjremond, @andrewxhill, @CARTO, @jatorre, @physicsdavid, @rachelannyes, @sd, @tag_fablab, @bonkydog, @ReaderMeter, @roguelynn, @lolya, @rafaelsidi, @wreinhardt, @8iterations, @chrismentzel, @LynJ, @openscience, @RalfLippold, @modernscientist, @OGuunter, @gever, @tokumin, @wdonohue, @ianholmes, @pherron, @TadashiOkoshi, @astrobaby2012, @alias_amanda, @verbal, @t, @caseorganic, @HealthCulture, @volcanitastic, @mko, @JuliaClaud, @gourneau, @mulderc, @tsherrygeo, @erinjo, @saleiva, @iamTRA, @sai_path, @radar, @lhuga

    arielwaldmanCollected by arielwaldman

    HTTP request error

    Oops, something went exquisitely wrong. Try again?

    HTTP request error

    Bad Request

    Debug info

    (400) GET https://twitter.com/twitter

    Request headers

    Array
(
    [0] => 0=accept%3A%20application%2Fjson
    [1] => 1=x-overlay-request%3A%20true
    [2] => 2=Cache-Control%3A%20max-age%3D0
    [3] => 3=Content-Length%3A
    [4] => 4=Expect%3A
)