Allow date range filtering when importing into Bluesky

[mlissner]

Is your feature request related to a problem? Please describe.

I've been using Bluesky for a little while now, but because I run a business, I have kept cross-posting over on X, at least for the time being.

I'd like to import all of my old tweets into Bluesky, but I don't want to import the cross posts.

Describe the solution you'd like

One solution is to do de-duplicating. If posts are substantially similar, don't import them. This is hard, and, alas, because of link shortening and the differences in allowed characters, it is probably doomed to failure. (I regularly tweak the messages I cross post based on length.)

So another solution is to use date filtering. This could be done two ways:

1. Don't import tweets created after you created your Bluesky account
2. Don't import tweets created after _________________

The latter is more flexible and probably better. Maybe there's a way to guide users into figuring out when they created their BS account, so they can look it up.

The former, of course, is more automatic, which is nice sometimes.

Describe alternatives you've considered

• Create a different BS account for the old stuff?
• Just import it all and have some dups (maybe delete them later by hand?)
• Tweak the archive by hand to remove dups

Thank you!

[mlissner]

I found another way to pull this off. Once the import began, I sat by and pressed the cancel button at the correct moment. More or less worked, though I had to set timers for the BlueSky API throttles.