You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
export "follows" using csv download on the setting page
import the following_accounts.csv into other account
Expected behaviour
The hashtags I follow should be exported with the rest of followed things
Actual behaviour
The followed hashtags do not appear in the csv file
Detailed description
Migrating to a new instance, I downloaded my follows (following_accounts.csv) and imported them to the new account as instructed. The accounts I follow of course were fine, but I was surprised to find the hashtags I follow had disappeared.
I understand following hashtags is a very new feature. Perhaps the export/import aspect has been overlooked.
Specifications
Mastodon v4.0.2
The text was updated successfully, but these errors were encountered:
The importer code will also need to be updated to support this.
For reference, hashtag following was implemented in #18809.
I think one major problem is that you'll need to export the raw text names of the hashtags, rather than their tag IDs. Which is fine, but if a smaller instance has never seen a given hashtag before, it'll need to create it as part of the import. I think that's fine, just a bit of a weird implementation quirk that'll need to be considered.
Steps to reproduce the problem
Expected behaviour
The hashtags I follow should be exported with the rest of followed things
Actual behaviour
The followed hashtags do not appear in the csv file
Detailed description
Migrating to a new instance, I downloaded my follows (following_accounts.csv) and imported them to the new account as instructed. The accounts I follow of course were fine, but I was surprised to find the hashtags I follow had disappeared.
I understand following hashtags is a very new feature. Perhaps the export/import aspect has been overlooked.
Specifications
Mastodon v4.0.2
The text was updated successfully, but these errors were encountered: