{"action":"created","issue":{"url":"https://api.github.com/repos/tootsuite/mastodon/issues/177","repository_url":"https://api.github.com/repos/tootsuite/mastodon","labels_url":"https://api.github.com/repos/tootsuite/mastodon/issues/177/labels{/name}","comments_url":"https://api.github.com/repos/tootsuite/mastodon/issues/177/comments","events_url":"https://api.github.com/repos/tootsuite/mastodon/issues/177/events","html_url":"https://github.com/tootsuite/mastodon/issues/177","id":190910988,"number":177,"title":"Support account migration","user":{"login":"hach-que","id":504826,"avatar_url":"https://avatars2.githubusercontent.com/u/504826?v=3","gravatar_id":"","url":"https://api.github.com/users/hach-que","html_url":"https://github.com/hach-que","followers_url":"https://api.github.com/users/hach-que/followers","following_url":"https://api.github.com/users/hach-que/following{/other_user}","gists_url":"https://api.github.com/users/hach-que/gists{/gist_id}","starred_url":"https://api.github.com/users/hach-que/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/hach-que/subscriptions","organizations_url":"https://api.github.com/users/hach-que/orgs","repos_url":"https://api.github.com/users/hach-que/repos","events_url":"https://api.github.com/users/hach-que/events{/privacy}","received_events_url":"https://api.github.com/users/hach-que/received_events","type":"User","site_admin":false},"labels":[{"id":330102526,"url":"https://api.github.com/repos/tootsuite/mastodon/labels/enhancement","name":"enhancement","color":"84b6eb","default":true}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":76,"created_at":"2016-11-22T05:30:03Z","updated_at":"2017-04-06T16:53:55Z","closed_at":null,"body":"A lot of people seem to be jumping on https://mastodon.social right now, even though the end goal is to have users separated out across multiple federated instances.  However, if people start putting up a lot of content and getting followers on the primary instance, this will be a disincentive to move providers.\r\n\r\nI think this largely means that Mastodon needs to support two things:\r\n* Account import across providers, which should be authenticated on both ends to prevent people bulk copying another person's account, and\r\n* A \"redirected account\" field against user accounts, which indicates the full URL of the new user account\r\n\r\nWhen users configure a redirect location against their account (whether explicitly on an account page, or implicitly set during a cross-provider account import), the instance on which the account is should _implicitly_ and automatically redirect followers.\r\n\r\nThat is, if I have the account @hq on the primary instance (which I do), and I set up the account @hach-que on another Mastodon service, the @hq should:\r\n* Remain on the primary instance, and not be disabled in any way\r\n* Show posts from @hach-que after the redirection is set up\r\n* Disallow posting from the @hq account while ever the redirection is in place\r\n* Existing followers of @hq should start seeing posts from @hach-que instead\r\n* New followers of @hq should be allowed to follow the account (and internally, they are following @hq, but see posts from @hach-que)\r\n* Followers should **not** actually have their lists updated to follow @hach-que - in the event of a mistaken redirect, removing the redirect should act exactly as if there never was a redirect in the first place\r\n\r\nThis is just my 2c on how I think this should work, but I'm interested to hear other people's thoughts."},"comment":{"url":"https://api.github.com/repos/tootsuite/mastodon/issues/comments/292236514","html_url":"https://github.com/tootsuite/mastodon/issues/177#issuecomment-292236514","issue_url":"https://api.github.com/repos/tootsuite/mastodon/issues/177","id":292236514,"user":{"login":"JPLeBreton","id":263303,"avatar_url":"https://avatars1.githubusercontent.com/u/263303?v=3","gravatar_id":"","url":"https://api.github.com/users/JPLeBreton","html_url":"https://github.com/JPLeBreton","followers_url":"https://api.github.com/users/JPLeBreton/followers","following_url":"https://api.github.com/users/JPLeBreton/following{/other_user}","gists_url":"https://api.github.com/users/JPLeBreton/gists{/gist_id}","starred_url":"https://api.github.com/users/JPLeBreton/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/JPLeBreton/subscriptions","organizations_url":"https://api.github.com/users/JPLeBreton/orgs","repos_url":"https://api.github.com/users/JPLeBreton/repos","events_url":"https://api.github.com/users/JPLeBreton/events{/privacy}","received_events_url":"https://api.github.com/users/JPLeBreton/received_events","type":"User","site_admin":false},"created_at":"2017-04-06T16:53:55Z","updated_at":"2017-04-06T16:53:55Z","body":"> For the fourth point, perhaps it's something that could pop up in Notification feeds or trigger an e-mail alert. To support this, Mastodon would add an \"I'm moving\" button to user profiles that will then push a move notice to your followers.\r\n@tobascodagama I feel pretty strongly that following an existing follow's migrated account shouldn't require any action on the follower's part. Notifications can be missed almost as easily as \"Hey, I'm moving\" toots. In any generic case are there any reasons I *wouldn't* want to follow a friend's migrated account?\r\nIt's another jagged crack to lose followers to and while I personally appreciate Mastodon's de-emphasis of follower counts, it's a huge potential pain point for twitter escapees."}}
{"actor":{"display_login":"JPLeBreton"}}