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
Currently, if an user is following an account on a service that is not a microblog (such as Peertube, Kbin, or Lemmy) the backfill requests fails, typically with the error message "Error parsing toot URL". Checking on the source code, it seems like the application is hardcoded to support only URLs from Mastodon, Pleroma, and PixelFed. What is required to parse URLs from the other services listed above?
The text was updated successfully, but these errors were encountered:
Thanks for your interest in this. I’d love to see FediFetcher extended for other servers/protocols, so this is something I’d very gladly see any PRs for.
The following is needed, in order to make this possible:
Firstly you need to figure out if peertube, kbin, and lemmy actually support the Mastodon context api? Any server that doesn’t, is impossible to support without major rewrite. (I did look into doing this via the ActivityPub API, but support for that is amazingly even sketchier than for the mastodon api). I’d be open to this, but it would introduce extra complexity.
For any server that supports the mastodon api, it’s really easy to implement:
write a case for extracting status ID from status url in the parse_url function:
I'm really really please to see @Teqed is currently working on a PR to implement Lemmy support for both backfilling profiles and fetching context in #56
Also serves as a good template on how to import posts from software that doesn't support the Mastodon API!
Currently, if an user is following an account on a service that is not a microblog (such as Peertube, Kbin, or Lemmy) the backfill requests fails, typically with the error message "Error parsing toot URL". Checking on the source code, it seems like the application is hardcoded to support only URLs from Mastodon, Pleroma, and PixelFed. What is required to parse URLs from the other services listed above?
The text was updated successfully, but these errors were encountered: