Twitter Issues

Comments

7 comments

  • Avatar
    Miranda Scarlata

    Hi Nadine,

    We've had this happen too! Generally we've found it helpful to capture twitter accounts using brozzler rather than a standard capture. If we still have the issue then we just delete that crawl and recrawl the account with a brozzler again. For whatever reason, the captures almost always work when we just crawl a second time. Hope this helps!

    1
    Comment actions Permalink
  • Avatar
    Ella Hitchcock

    Hi Nadine, 

    We've been having this problem recently as well. 

    0
    Comment actions Permalink
  • Avatar
    Nicole Greenhouse

    Yes, I am also having a similar problem.

    0
    Comment actions Permalink
  • Avatar
    Katherine (Edited )

    Has anyone found a solution to this problem? I've been running into the same thing for the past couple of months—crawled Twitter feeds won't load in Wayback, and I get this error message instead:

    I've tried repeat crawls with Brozzler, per Miranda's suggestion, but that hasn't made a difference, and I've confirmed we're following all of the recommended scoping guidelines, so I'm not sure whether it's a capture or a replay issue.  

    1
    Comment actions Permalink
  • Avatar
    Karl Blumenthal

    Hi all! We've added the "Something went wrong..." error message issue to our platform status tracker here. We also saw an uptick in this error reported across the board, so our engineers are on the case. I will report back just as soon as we have more helpful information or better yet a fix for everyone's review.

    Every indication so far is that this is an issue with replay rather than capture, meaning that you don't need to change any of your crawl settings at this time and we hope to apply any fix to the existing captures that you have already made. It looks like an unrelated update to our Wayback software code might be confusing an archived Twitter script that is kind of self-destructing in replay like you see, so we are testing the best tweaks or reversions to help everything replay more like you expect it to. 

    0
    Comment actions Permalink
  • Avatar
    Katherine

    Thanks, Karl! It's great to hear that engineers are on the case and this is looking like a replay issue—that makes me less hesitant to go ahead with time-sensitive captures in the meantime.

    0
    Comment actions Permalink
  • Avatar
    Karl Blumenthal

    Thanks all for your patience! I'm happy to report that you should no longer see those perfunctory error messages in place of archived Twitter profile feeds going forward. We are still at work on two related issues that you should be aware of when you plan to run your next crawls.

    1. Captures might looks a little big. Twitter frequently serves its content at a lower browser window size than we want it for Wayback replay, so your captures might look enlarged like mine does here:

    2. Hashtag and search seeds are blocked. Twitter is redirecting all automated access to its trending topics or keyword searches to a login challenge like this one:

    Our team is still at work on both issues and I will report back again on our progress. In the meantime you can always get the most current status for social media and other platforms here.

    0
    Comment actions Permalink

Please sign in to leave a comment.