Wie das Werkzeug. Aber kaputt.
(Bitte keine lustigen Replys.)
| Datenzeug | https://vis.social/@Luca |
| Bot | @pv |
| Pronomen | er/ihm |
Wie das Werkzeug. Aber kaputt.
(Bitte keine lustigen Replys.)
| Datenzeug | https://vis.social/@Luca |
| Bot | @pv |
| Pronomen | er/ihm |
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.).
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.
Surprisingly, there was only one bug in the script (sometimes Tweets have a "reply_to_screen_ma,e" field, but no "in_reply_to_status_id" field.
An issue I could have expected: I used a lot of twitpic and imgly in the early days. Those aren't in my archive. But I think I still have a backup of them somewhere. Will have to look into manually or automatically adding them through an edit.
Currently 20k of 70k imported.
Because alt-texts weren't added until 2016, I started with importing earlier posts and was quickly reminded that Mastodon has rate-limits as well. 300 posts per 5 minutes. 30 media uploads per 30 minutes.
Should I mod Mastodon further or slow down the import script?
Maybe just put what I have on Github and spend more time with my family.
Last federation test. I added an if-condition to prevent posts from being pushed to the local timeline or other servers if it was created with a created_at parameter.
app/services/post_status_service.rb
if not @options[:created_at]
DistributionWorker.perform_async(@status.id)
ActivityPub::DistributionWorker.perform_async(@status.id)
end
Works. And posts show up when searched for by URL.
Third test: What happens with backdated posts, if federation isn't turned off.
The post is pushed to all subscribed servers. And shows up at the top of the timelines there. With the old date. This is what I want to prevent.
Second test: Creating a backdated post through the API.
In the file "app/controllers/api/v1/statuses_controller.rb" I added "created_at: status_params[:created_at]" in PostStatusService.new.call and ":created_at" to "params.permit" (Missed this for quite some time and was confused why I can't even log the timestamp.).
In the file "app/services/post_status_service.rb" I added "created_at: @options[:created_at]" to "status_attributes".
Works mostly. Timezone is off.