A migration message needs to be signed with both keys (the new AND the old account) … so unless you have both private keys, you can’t migrate anything … and if you have the private keys, you can do whatever you want with these accounts.
Hey, I just wanted to mention that despite being quiet those last weeks I still plan to work on the UI, I’m sorry July is a busy month, I will be back on it beginning of August.
2 Likes
@flaburgan
I have had a nice and productive talk to Benjamin. We managed to merge the missing blocks - data. ()Import and export)
And he had some ideas for fixing validating issues, but at last… I failed. Fixing validation/importing issues is quite hard to dive deep into the multiple levels of inheritence and keep tests running.
But:
I moved on unpacking a zip file Migration: Import compressed archive file handling by tclaus · Pull Request #8260 · diaspora/diaspora · GitHub on import
And even have a working file upload based on Fla’s UI concept:
Migration: Upload migration files from profile settings and start processing by tclaus · Pull Request #8274 · diaspora/diaspora · GitHub
It was requested to import file on user creation, a UI is still missing for this.
The importing user will also not get any information about finished migration and no information for any error.
Any Ideas for this?
I’d like to thank you guys for working on this! I have no technical expertise, so I really appreciate people who can tinker with code and come up with such amazing, useful, wonderful stuff! A GUI for a fully functional account migration feature will really make Diaspora even more awesome.
1 Like
Okay so quick draft, my proposition would be that when the visitors are clicking on the registration link in the header, instead of going directly to the /users/sign_up they arrive on an intermediary page looking like that:
where two options are proposed. The first button is a link to the actual registration form, and the second button start the migration wizard (I mean, the popup similar to the second image in Backup and restore – account migration - #115 by flaburgan except that it’s about import and not merge). Does that sound OK to you?
Another question, should we ask the users a new username in any cases, or should we try to keep the one from the archive and only ask for a new one if it is already taken? For the e-mail, I think we can take the one in the archive and only ask if it is already taken.
The design of diaspora* starts to feel outdated (fonts are too small, buttons and colors feel old…) but I don’t think I should start changing that in this work, should i?
Edit: Mobile view:
2 Likes
Does it need to be that prominent, is that really that common? Wouldn’t a link on the sign up form suffice?
It may. I don’t know. I know that many people will want to migrate because Framasphere is closing, but if they create a new account anyway they still can do the “import with merge”, that isn’t a problem. To add, we also don’t want to scare the real new users, so that new step with possibly them not knowing what this is about may be a bad move indeed. Let me try a new draft then.
On that point, the best solution probably is to still display the form fields, but prefilled with what was in the archive.
1 Like
Looks pretty clear to me. If a migrate button scares someone, let them create an issue and it can be dealt with then.
How about this?
If someone clicks on the registration link, this screen appears:
If they then click the ‘Create a new account’ button, the registration form appears in place of the two buttons:
If, instead, they click the ‘Migrate my account’ button, they get taken to the migration page.
(These are very rough mock-ups, and part in English and part in French – I just did some cutting and pasting on Fla’s images…)
People who want to migrate an account to a pod will have to know that they first need to click the ‘sign up’ button to get to this page before they can migrate. This can be made clear on the pod they are leaving when they complete the export process.
On language, I don’t think there’s any need to include the pod name on the buttons – it’s obvious which pod the person wants to sign up or migrate to, because they’re on that domain. Also, some pod names are very long…
And perhaps ‘Move an account to this pod’, instead of ‘Migrate my account’ on the button is less technical, and might be more easy to understand. What do you think?
2 Likes
I like Fla’s proposal more, no extra Step I have to decide. Most new user might go ahead with registration, but If I (the user) want to import something the user will finde the registration link in the short text.
There is no extra step I can see: in Fla’s initial proposal, you still have to click the ‘sign-up’ button to get to the two options. My version gives those two options on the sign-up page, in response to Jonne’s suggestion.
I actually discovered years ago that this is not obvious at all for the users. I can’t tell how many friends of mine called me saying “I can’t log in on diaspora* it’s broken!”. They registered on my pod, but then when wanting to come back, they simply entered “diaspora” in there the address bar and clicked the first link google gave them, ending on joindiaspora.com … For something as “no revert possible” as an account migration, I feel like we should remind the pod URL once again.
Yeah wording can definitely be improved, that was a quick draft to start discussion. But IMO Jonne made a good point, we should probably keep the registration form right on the first page, and then allow visitors to access the migration page if they want to. I will propose a more polished draft about this.
1 Like
So, staying with the idea of a simple link, we would have a flow like that:
The visitors click on Sign up:
They then click on the “Migrate your existing account” link and arrive on something like that:
Then they upload the archive, and the validation is done. If it’s a success, then can process with the migration:
If that step is a success, then they would arrive on a the stream with a confirmation message.
Is that flow enough, or am I missing some steps / information needed to be collected?
I will try to look at it in an hour, I hope that is early enough.
1 Like
I’ve just had a thought, and it’s more about the UX than the UI – sorry I’m bringing this at such a late stage.
Someone brought up the point earlier about whether it would be possible to choose a new account name/Diaspora ID when migrating to a new pod. If the migration feature allows a user to do this and still connect with old contacts, then the following might work better:
Keep the same registration page, adding just a note that ‘You will be able to migrate an account from another pod at the next stage.’
Once someone has chosen an ID and password, the next page has ‘Do you want to migrate another account to this one?’ YES / NO.
If the user selects YES, then the migration UI kicks in.
1 Like
About the UI in the latest mock-ups:
There’s quite a lot of small text on the migration screen. I’d like to think of ways to reduce that.
I’d also like to see the buttons and success flag conform with Diaspora’s design rather than using default button design. I’m sure this is something you’ll work on.
The text could use some editing. Could you paste it into a comment here? I could then see if I can simplify it a bit.
Regarding this, an idea that would help with this and with a new sign-up:
Once someone completes the sign-up page, and before going to the ‘Welcome/let’s get started’ screen,
Have a screen that reads, in big type:
Obviously [username] will be replaced with the user name just entered in the sign-up form.
Then a 'confirm I have made a note of this address and will not be so stupid as to google ‘diaspora’ button to get to the next screen.
Obviously needs some refining, but an idea to help new users?
(Someone migrating should probably know about this already – it’s really brand-new users who will be ignorant of it.)
@flaburgan, as an example of this, could you possibly provide quick help to this new French user? How do I get back to my account? I could, but my French would not be good.
1 Like