The bmannconsulting.com website
bmann.ca
1---
2tags:
3 - Twitter
4 - Bluesky
5 - ATProtocol
6 - archive
7---
8Turns 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.
9
10I tried using the [twitter-to-bluesky](https://github.com/marcomaroni-github/twitter-to-bluesky) script but kept running into errors.
11
12I ended up using [[Cyd]] with the local Twitter archive I had to migrate to my [@bmannconsulting.com](https://bsky.app/profile/bmannconsulting.com) account. This is on my self-hosted [[BringYourOwn.Computer]] PDS.
13
14I have deleted tweets older than 180 days.
15
16I am still cross-posting to Twitter from my [journal](/journal/) using [[Fedica]].
17
18## Cyd
19
20Cyd doesn't support replies. I would actually like to have my replies! This has been [filed as an issue in the cyd github repo](https://github.com/lockdown-systems/cyd/issues/449).
21
22A few other feature requests:
23
24Use Bluesky's rich text to link @-mentions
25* @oldtwitterhandle would look like this `[@oldtwitterhandle](https://x.com/oldtwitterhandle)` (obviously not Markdown, but shown that way to show the link)
26* Could also use [[Tweetback]]'s canonical JSON to parse where to point this
27* As people migrate to Bluesky in particular, keep track of where people are heading. So, `@bmann` has archived to Bluesky as `@bmannconsulting.com`
28
29Support reply imports
30* just like linking @-mentions, deeplink into reply parents
31* So, if my post is @-someaccount, that @-mention is linked to the tweet I'm replying to
32
33## PDS Archive
34
35I wrote this up [as a GH Discussion](https://github.com/orgs/ATProtoApps/discussions/6).
36
37The premium version of a Twitter archiver would be:
38
39- a PDS, with a custom domain name
40- everyone gets a user name with their original Twitter handle
41- upload your Twitter archive to import, including all media
42
43Possible features:
44
45- 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](https://github.com/tweetback/tweetback-canonical)
46- if original web links are dead, attempt to get a wayback machine link version
47- a specialized client that does display / search / other custom Twitter features that Bsky doesn't have, or somehow maps between them
48
49## Twitter Lexicon
50
51A Twitter Lexicon would support metadata that isn't supported by the base bsky post Lexicon.
52
53It could also store things like likes, where it would be a "like" -> pointing to the `x/twitter.com/` original post URI.