I thought, importing Mastodon data would be easier, but it's not. Instead of getting the text in the same form it was posted, it's html and now I have to convert usernames back to the @<username>@<server> format before converting the rest to text with BeautifulSoup.

And I had to increase the delete limit as well because I noticed my misunderstandings too late. At least I had a list of the broken posts to easily delete them.

Now that Twitter works, let's try the same with Mastodon.

And then #Instagram, #Path and #Vine, Maybe #Google+ and #Facebook, but I will have to look at the archives first, if those should even be saved.

Path will be added as "only me". Once again, I would love to make it visible to a list of people, but #Mastodon isn't up to that task (I will probably do the same dance in a yet when I move to #GoToSocial.).

@vyr works on extending #search: https://github.com/VyrCossont/mastodon/pull/2

Would be nice to allow others to search my posts. I won't test it yet, but keep an eye on it.

Something went wrong with the alt texts. They are shown as "#<ActionDispatch::Http::UploadedFile:0x0000151f32ec4b98>" instead of the text.

Oh. I put them into the files field instead of the data field. Let's try again.

I wanted to go the easy route and use a library for the Twitter API stuff. Turns out, I currently don't have the capacity to understand the design decisions of the libraries. I guess, I will use requests for that as well.

(It's funny because working with the Twitter API was a crucial part of my work for the last ten years.)