Clément VILLISEK
Hello!
I have a question about #MITRA , and more specifically about the experimental #feature "Follows import".
Is there a limit in how many follows can be imported at once? How much time can it take to import all follows? Is there a specific CSV format to respect, like (column(s) name(s)?
I tried to import my followers from my Iceshrimp instance but only a very few accounts seem to have been imported.
I don't know where the logic behind the imports is in the source code :-X
Thank you!
silverpill
@clemv The CSV should have one fediverse address per line (Mastodon export format), 500 items max. The process may take 5-10 minutes.
But there is a difference between "import follows" and "move followers" features. You should be able to import follows from anywhere. Followers can only be moved between Mitra instances (because no other software supports this feature).
silverpill
@clemv It shouldn't stop if one profile is not available, but maybe there is some other error. This feature is experimental, after all :)
The server imports follows from your CSV one by one. Could you tell me the address of the first follow that wasn't imported?
>I'm redirected straight to my profile with no further info on its state.
That is expected.
@nimda grep ERROR on mitra log may provide some info
Clément VILLISEK
@silverpill
Well, I tried that but only a very few follows were imported for some reason. I wonder if the import fails in its entirety (and stops) if Mitra can't retrieve one of the profiles?
When clicking on the "Import" button I'm redirected straight to my profile with no further info on its state.
silverpill
@nimda @clemv I'll make importer ignore this error in the next release, but it would be nice to know what fediverse address causes this.
Nimda
@silverpill @clemv I'll be back this evening, but got this output:
$ sudo journalctl --unit=mitra --grep=ERROR May 09 15:37:16 mitra mitra[293576]: 2024-05-09T15:37:16 mitra::job_queue::scheduler [ERROR] ImporterQueueExecutor: actor ID is not found in JRD May 09 15:38:26 mitra mitra[293576]: 2024-05-09T15:38:26 mitra::job_queue::scheduler [ERROR] ImporterQueueExecutor: actor ID is not found in JRD May 09 16:15:56 mitra mitra[293576]: 2024-05-09T16:15:56 mitra::job_queue::scheduler [ERROR] ImporterQueueExecutor: actor ID is not found in JRD May 09 16:18:01 mitra mitra[293576]: 2024-05-09T16:18:01 mitra::job_queue::scheduler [ERROR] ImporterQueueExecutor: actor ID is not found in JRD May 09 16:26:41 mitra mitra[293576]: 2024-05-09T16:26:41 mitra::job_queue::scheduler [ERROR] ImporterQueueExecutor: actor ID is not found in JRD May 09 16:34:13 mitra mitra[293576]: 2024-05-09T16:34:13 mitra::job_queue::scheduler [ERROR] ImporterQueueExecutor: actor ID is not found in JRD
silverpill
@clemv @nimda The problem has been fixed in Mitra v2.19.0 (wait for update)
Clément VILLISEK
@silverpill @nimda
Thank you for the help guys!
I took a look at my CSV, and it seems that there doesn't seem to be a specific time when accounts are no longer imported: Accounts in the 350+ lines seem to have been imported, but not earlier ones (including accounts on largest mastodon instances)...?
BTW, I tested both CSVs from Iceshrimp (just the account address, one per line), as well as with the Mastodon format (first CSV column being the address, and other columns being booleans about notifications "show boosts", "notify on new posts" and the empty "language" column).
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.