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

Show remote users on profile directory #10738

Open
Gargron opened this issue May 9, 2019 · 1 comment

Comments

Projects
2 participants
@Gargron
Copy link
Member

commented May 9, 2019

It is time to make the directory more useful by also including opted-in remote users on it. Perhaps there could be "local"/"federated" tabs on it. One complication is that the opted-in-ness is not currently federated.

@Gargron Gargron created this issue from a note in v3.0 (To do) May 9, 2019

@Gargron Gargron added the TODO label May 10, 2019

@mynameismonkey

This comment has been minimized.

Copy link

commented May 13, 2019

The directory is a great tool for surfacing content, discovering people to follow, and I agree it could be more effective. I like the idea of showing non-local users on my local directory but I would want some form of administrative control.

As an instance admin, I have a set of policies I enforce on my userbase. What option would I have for removing someone from my directory if I felt they do not represent or adhere to those policies? I may not want to silence them as they may be perfectly fine people for my local users to interact with, but I may also at the same time not want that federation user representing the community in the community directory.

Separately, what control would I have as an admin of a smaller instance than many to ensure my directory doesn't become majority federation users? Having the two tabs mitigates this, but can also confound directory browsers - I would prefer a single view of the community you can participate with, local and federated. However, one of the joys of running a federated community is being able to demonstrate to potential new members the idiosyncratic style or culture of the community they are joining. If the local directory members are over-diluted by federation members, this might weaken the value proposition for new members, or effectively dilute the vertical pull of many of the relatively specific verticals some of the instances attract.

I believe curating the directory such that not every federated connection with an opt-in would be listed, but instead include only those federation members who have interacted with toots from the instance via public boost or reply. This would demonstrate a larger, more useful and more representative directory without flooding it with federation input nor needing much input from the instance admins.

Of course, this all presumes opt-in status being federated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.