1. Exquisite Tweets from @swankmotron, @RevengeanceQD, @SnokesLegs, @JonnyHanukkah, @Momnishambles, @threadreaderapp, @LitheraPrime, @nevermindjody, @MrIanMacIntyre, @CanonChronicler, @Kwehttamm, @BarbotRobot, @AVSmovies, @nickarkis, @JumpedAShark, @blabbate, @thezombiejose, @IcarusDei, @baradit, @Behemous, @TheJoeSlepski, @davidgaffen, @MaybeItsSteve, @TheEclectic, @GC9X, @GreyDuck, @mburchett, @damianbruced, @MajorTomCom, @joshquixote, @Roacendar, @DB_Grimwalker, @Cach_Indomitus, @michaellorg, @chriscloudlmao, @TonyPrintezis, @StoryWonker, @phxarchangelus, @GillianDN, @CurrentlyNerdy, @_Omegez_, @AdamMMasin, @nicopintoheck, @superashbro86, @AmalgramVirgo, @BoxingAsylumWhy, @Mister_c_smoove, @AmytisofMedia, @bbattleready, @ReeseCole17, @amJeoff, @hatecitynights, @_BonFigli, @DiamondDaveDude, @dankourny, @ravewithravi, @cfischer83, @ScaryJBlige_, @UhOhDomano, @nick_nuckle, @DionApollo, @kaeae, @karen01387555, @amynorthgeorgia

    snydezCollected by snydez

    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
    )