Replied Reply to Storify Bites the Dust. If You Have WordPress, You Don’t Need Another Third Party Clown Service (Chris Aldrich | BoffoSocko)
Better than relying on the auto-embed handled by WordPress, actually copy the entire embed from Twitter to capture the text and content from the original.
I really like your point Chris in regards to the difference between the shortcode and the embed code. I wonder if there is a potential to build on Martin Hawksey’s TAGS work to smash the different parts together in Sheets rather than manually copying the embed code for each Tweet. Something like this:

=“<blockquote class="twitter-tweet" data-lang="en"><p dir="ltr" lang="en">”&text&” — (@”&from_user&”) “&source&” “&created_at” <script async src="" charset="utf-8">”

I still need to think about how to accommodate “twitter-tweet” so that Sheets reads this as text too.

Doing it this way would allow users to download a list of their tweets and potentially paste the IDs into tags and then generate the embed code.

Mariana, just wondering where you have stored your archived lists? I was notified of there deletion via ‘Broken Links’. I really liked your Storify on GIFs.

I am in fear if this is a start of a series of dominoes. My Tumblr posts are all POSSE’d, however I really need to think about my Flickr collection. Must admit it has really sparked me to reconsider a number of practices and processes, which is probably good.

Replied Storify Bites the Dust. If You Have WordPress, You Don’t Need Another Third Party Clown Service by Alan Levine (CogDogBlog)
There are two kinds of people or organizations that create things for the web. One is looking to make money or fame and cares not what happens once they get either (or none and go back to flipping burgers). The other has an understanding and care for the history and future of the web, and makes every effort to make archived content live on, to not leave trails of dead links. Storify is Type 1. After getting enough of a value based on the free labor of grunts like you and me who built content in it, they got bought by Adobe, and swept up into some enterprise product
Thank you Alan for your investigation into alternatives to Storify. By chance, I had gone down a similar rabbit hole wondering how I could store a set of Tweets. I was under the impression that being embedded if the original tweet were deleted then they would not show up in the blog. It was for this reason that I explored pasting the text. I am assuming from your discussion(s) that this is not the case?

I still like the idea of using TAGS to collect the links, but rather than pasting the text:

The book traces the changing focus of the history of second wave feminism over the 20th/21st centuries. Providing essays situated in each of the three ‘Acts’. I’m live tweeting Fraser’s overview of the history and spirit of the wave
“Second wave feminism came out of the New Left after WW2.

Act1 – Began life as an insurrectionary force that challenged male domination in state organised capitalist societies”

Act2 – the feminist imagination turned from redistribution of power/economy to recognition of difference – identity/cultural politics dominated

Act3 – still unfolding but we are seeing the reinvigoration of feminist and other emancipatory forces to demand that the runaway markets be subjected to democratic control

A user could just paste the URLs:

Will continue to think about this, especially as I do not always want the parent tweet necessarily embedded. I also have to investigate your Storify Embeddable Link Extractor, but it looks to be a great tool for all situations.