Based on the comment, I think that what is wanted is a little different than what people are assuming.
First, it sounds like there is a desire to implement enough of the Mastodon API that various mobile Mastodon clients can connect to kbin.social and interact with that side of things. I have no idea how difficult this would be, but I suspect that it would be an interesting undertaking.
And second, unrelated, but it came up in the comments, and I think it would be an excellent idea, there is definitely a desire to implement a Mastodon-like way to export and import enough of your account information to easily migrate to another instance.
In my opinion, there needs to be an option that can both import and export a fully Mastodon compatible format, so that people can migrate from Mastodon to kbin, and can migrate back from kbin to Mastodon, at least for stuff where that makes sense.
At the same time, I am unsure if that format would be sufficient for everything required to migrate from one instance of kbin to another, or between kbin and lemmy.
And given that last point, it should come as no surprise that I think that if another format is needed, or even an extension to the existing format, that should really be coordinated with Lemmy, so that it is easier to move around the entire ecosystem.
Also, being able to export your data and dowload it to your computer is a GDPR requirement in Europe, as far as I know. Even Reddit supports this. Not complying with this is risky.
It would be great if the same download could be used to migrate the account, making use of signature verification and so.
But I don’t think that the full export would be very practical as an account migration tactic. There’s no value uploading previously made posts/comments/toots to the new instance, because it can’t do anything with them.
Why not?
I thought the point of migrating from one instance to another was to keep your entire post/comments/toots history (at least whenever possible).
The followers/follows too… but that’s only important if you are an influencer with a lot of followers, otherwise it would not be a big deal to rebuild it. It might actually be desirable to clean it up.
If the content isn’t migrated, then just creating an account in the new instance would be good enough for me. I don’t see much value in doing a migration beyond that if I can’t carry over the content.
Based on the comment, I think that what is wanted is a little different than what people are assuming.
First, it sounds like there is a desire to implement enough of the Mastodon API that various mobile Mastodon clients can connect to kbin.social and interact with that side of things. I have no idea how difficult this would be, but I suspect that it would be an interesting undertaking.
And second, unrelated, but it came up in the comments, and I think it would be an excellent idea, there is definitely a desire to implement a Mastodon-like way to export and import enough of your account information to easily migrate to another instance.
In my opinion, there needs to be an option that can both import and export a fully Mastodon compatible format, so that people can migrate from Mastodon to kbin, and can migrate back from kbin to Mastodon, at least for stuff where that makes sense.
At the same time, I am unsure if that format would be sufficient for everything required to migrate from one instance of kbin to another, or between kbin and lemmy.
And given that last point, it should come as no surprise that I think that if another format is needed, or even an extension to the existing format, that should really be coordinated with Lemmy, so that it is easier to move around the entire ecosystem.
Also, being able to export your data and dowload it to your computer is a GDPR requirement in Europe, as far as I know. Even Reddit supports this. Not complying with this is risky.
It would be great if the same download could be used to migrate the account, making use of signature verification and so.
You make a great point about GDPR requirements.
But I don’t think that the full export would be very practical as an account migration tactic. There’s no value uploading previously made posts/comments/toots to the new instance, because it can’t do anything with them.
Why not?
I thought the point of migrating from one instance to another was to keep your entire post/comments/toots history (at least whenever possible).
The followers/follows too… but that’s only important if you are an influencer with a lot of followers, otherwise it would not be a big deal to rebuild it. It might actually be desirable to clean it up.
If the content isn’t migrated, then just creating an account in the new instance would be good enough for me. I don’t see much value in doing a migration beyond that if I can’t carry over the content.