Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Federation established by dual consent #24

Open
AleziaKurdis opened this issue Jan 18, 2023 · 0 comments
Open

Federation established by dual consent #24

AleziaKurdis opened this issue Jan 18, 2023 · 0 comments

Comments

@AleziaKurdis
Copy link

Let say we have a Federation of Directory Servers. But one day, one of these Directory Servers start to host unethical content,
at the point that it has become a problem for the reputation of the whole federation.

This is why any automatic participation to a federation could be a problem. Since such a federation has none in authority to manage it. (and we don't want that)

One way to avoid this, could be to push this responsibility to every Directory Server's owners. But if everyone is responsible for all the server of a federation, this becomes difficult to manage.

To reduce that range of responsibility, to an acceptable and humanly manageable solution. Maybe we can go with a kind of limited number of relationship that can be turn off by a decision from any of the both side.

When a Directory Server's owner would want to be part of a federation, all it would take is to establish N native relationship to start to be known by the whole federation.
If those Relationship get cut, then the Directory Server would rapidly get disconnected from the whole federation.

I have already do a prove of concept for that. All it need to a Directory Server is at least 2 connections to other Directory Servers part of that federation.

The establishment of those native relationship would be done by simple request that need to be approved by the other owner.
Then each of the 2 owners could terminate the native relationship at any moment.
Those native relationship would be public information. So anyone could know who to contact to complain.
I think that if a Directory Server start to be problematic, it won't be long before the exclusion to happen.

The responsibility would be to each Directory Server owner to manage with whom they accepts to be in the federation.

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant