Allow the servers communicating with each other

Anyway I hate creating new and new accounts on new and new diaspora servers.

Why would someone want to do that?

I can only think of two situations in which someone might want to do this:

1. Because they didn’t understand the nature of a distributed network. In which case the answer is better education, not a system of logging in to remote pods.
2. Because the imperfect state of federation in diaspora* meant they were missing out on posts they wanted to see on their home pod, and felt that signing up to another pod was the best way to deal with this. In which case the answer is to improve federation (work which developers are already trying to achieve), rather than a system of signing in to remote pods.

Ok, i will answer the questions.
When I sad about login in any diaspora pod i think about make the diaspora network better and more stronger.
When somebody go to diaspora pods he don't want speculate about which diaspora pod is better for he.
There is many servers and some with closed registrations.
This can access to closed pods too and improve the experience.
How is it possible access to closed pods without registration?
Anyway, when i will create the account on diaspora i must collect many data as: is there chance close this pod?, will this pod be stabile for me?, is the design and UX good for me?, and many more questions...
Now i have closed doors to some pods, but why we can't open the doors for any pod user, why we have there possibility to deny users to some pods?

Max, I think you misunderstand the nature and philosophy of the Diaspora network. The way each pod is run is the choice of the person who runs that pod. If someone wants to run a pod just for themselves and so does not open registrations, that is their right and we have to respect their choice. We can’t justify to force them to accept signins from people they don’t know, can we?

The beauty of a distributed network is that there are many pods, and within those many pods there will be pods run in all sorts of ways, so there are options suitable for everyone.

Your problem seems to be that it is difficult for a new user to find a pod which suits them, and which they can be sure is stable and going to stay open for a long time. The answer to this, as I said above, is better information to help people choose. We’ve got a page on our wiki about choosing a pod, and podupti.me lists how long a pod has been running, which can help find a stable, long-term pod.

What we really don't need is some technically complex method for enabling bad practice in users, which also brings many privacy concerns.

@goob let me add another reason from the German speaking diaspora* community to your list:

1. Privacy concerns.

Since Germany seems to be involved in certain kind of surveillance against the citizens, one user opted to switch to a pod placed in Armenia (no comment, please).

In this case, moving the account details would be fine, too.

Oh, and a fourth reason comes to my mind:

1. Forgot login credentials/hacked account.

I remember a user, who created another account (on a different pod) out of this reason.

But @ryunoki, neither of your examples touch on this at all.

1. In your first example what that person wants is for their account data to be moved in their entirety to the new pod - they wouldn't want their account data to be retained on the old pod in Germany. That is account migration - it's not what's being proposed here, which is for the account data to remain on one home pod but to be able to sign in to that account from another other pod.
2. In your second example, if you couldn't sign in to your home pod because you had forgotten your sign-in details, what use would be the facility to sign in to another pod using those same details that you had forgotten? No, what you need is a means of recovering those sign-in details, not the means to sign in to other pods using those same details.

Uhm, yeah, you're right. Sorry, I should rather go to bed …

@goob thank you for explain.
Maybe me idea isn't an same line as project, but I respect the roadplan. And of course other users.
Second point:
podupti.me is really bad site for check the pods.
Why?
The are security issue with location, maybe bad data about location when is used anonymisation service and other issues.
Design isn't good, but this is me opinion. (maybe for someone other is ok)
I don't understand the ad there. (But maybe when is there need of ad, it will be at bottom...) Me opinion too.

Maybe there would be nice the change, i mean other idea of finding pod.
The information about pod can be stored in pod and when admin enable sending the information to information central, the pod can send the data there.
Or second type, there can be special meta tag or json file which will inform the page about running pod.
When admin setup the file and add pod to the database, the page can be informed as well.
This will be more nicer as current status...