tags:

• Twitter
• Bluesky
• ATProtocol
• archive

Turns out I didn't have a copy of my Twitter archive available any more, so I requested it again, and now have it backed up elsewhere as of February 2025.

I tried using the twitter-to-bluesky script but kept running into errors.

I ended up using [[Cyd]] with the local Twitter archive I had to migrate to my @bmannconsulting.com account. This is on my self-hosted [[BringYourOwn.Computer]] PDS.

I have deleted tweets older than 180 days.

I am still cross-posting to Twitter from my journal using [[Fedica]].

Cyd#

Cyd doesn't support replies. I would actually like to have my replies! This has been filed as an issue in the cyd github repo.

A few other feature requests:

Use Bluesky's rich text to link @-mentions

• @oldtwitterhandle would look like this [@oldtwitterhandle](https://x.com/oldtwitterhandle) (obviously not Markdown, but shown that way to show the link)
• Could also use [[Tweetback]]'s canonical JSON to parse where to point this
• As people migrate to Bluesky in particular, keep track of where people are heading. So, @bmann has archived to Bluesky as @bmannconsulting.com

Support reply imports

• just like linking @-mentions, deeplink into reply parents
• So, if my post is @-someaccount, that @-mention is linked to the tweet I'm replying to

PDS Archive#

I wrote this up as a GH Discussion.

The premium version of a Twitter archiver would be:

• a PDS, with a custom domain name
• everyone gets a user name with their original Twitter handle
• upload your Twitter archive to import, including all media

Possible features:

• old content is updated over time to "repoint" to the location of archived content / usernames -- e.g. either on the same service or somewhere else (e.g. Tweetback Canonical mapping
• if original web links are dead, attempt to get a wayback machine link version
• a specialized client that does display / search / other custom Twitter features that Bsky doesn't have, or somehow maps between them

Twitter Lexicon#

A Twitter Lexicon would support metadata that isn't supported by the base bsky post Lexicon.

It could also store things like likes, where it would be a "like" -> pointing to the x/twitter.com/ original post URI.