Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Add profile directory #9427
Directory opt-in checkbox in "Edit profile":
Admin UI for hashtag moderation:
This should answer the question "how do I find worthwhile users from x without signing up and lurking there?" as well as "how do i find people interested in y?"
Toot asking for initial feedback on the idea: https://mastodon.social/@Gargron/101168486745315315
Haven't actually read it, but there appears to be some leftover from your other PR regarding
Otherwise, I have two main worries:
Looking at this, I'm not sure if this is really the right approach. I think we're trying to solve two problems at once here.
One is how do I know this is a good instance for me? And the other is how do I find people I'd like to follow?
For the former, we could just do same aggregate stats around hashtags and profile hashtags; "Members of this instance use the hashtags of ABC, DEF, MNO, and XYZ", and "In the past week members have been tooting about #freedom, #tumblr, #winter. The hashtags that lead to the most interactions this month were #abc, #foo, #bar" (where interactions is likes + replies + boosts)
This way we're letting people know what they'll find here, without highlighting specific users.
For the second question, I think we she focus more around: who toots similar things to me and how may I know (friends of friends).
Admittedly this doesn't help with the cold start problem; but perhaps we could change onboarding to give you a six random hashtags to choose from, and then surface up random users who have used those hashtags and have more than a certain amount of toots / non-default avatars / followers.
Of course, as part of role out of this feature, I think we should do a mailout or other notification allowing people to opt-out of this functionality, explaining why we're adding it.
In order for mastodon to be successful, people have to be able to find their communities and engage with people who are interested in the same topics. Otherwise it becomes a very isolative experience, where people feel kinda lost & their home feed doesn't update often, so they don't check back or become sticky.
Additionally, I think Mastodon should build in the features of the friend finder from other networks, perhaps there's a way to do this with zero-knowledge of who the users are between instances (as to preserve privacy and still be decentralized)
@ThisIsMissEm Thank you for your feedback, but I think that's not what I was going for here at all.
First of all, the friends-of-friends, "who to follow" stuff is not something I want to go back into right now, so this feature is not intended to touch that topic at all. It's not about personalized results, but about finding people in general.
Nor is it about getting a feel for what a server is like. I want to reduce the need to sign up on different servers to experience their community (since that is a side-effect of the local timeline feature anyway). It's about you knowing that cybre.space exists and wanting to get some of the cybre.space vibes into your home feed on another server. How do you know who to follow? Here, look at this directory of cybre.space users who want to be found.
Oh, I think I get it. So the idea is that a user wouldn't check their own instance's profile directory, because that's what the local timeline is for, but they would instead check other instances' profile directories for people to follow from there?
Dec 6, 2018
11 checks passed
That's fair, I know personalization of results is a very contentious topic, and one that'll spark much debate. However, I think it's something people expect, especially populations from mainstream social networks. Is there an issue for this, or should we start one?
Do people really do this? To me, it seems that people pick an instance and roll with it, especially given the promotion of certain instances within certain communities (e.g., switter.at and sex workers on twitter)
I'm speaking only from personal experiences here, but I don't know anyone who's signed up to another instance just "to experience their community", as you can't experience a community without being part of it (to some degree) — I'm sure anthropologists have a phrase for this.
How does the new user of Mastodon know that cybre.space exists in the first place? Even when viewing a profile from a remote instance, it's not particularly highlighted in anyway. (Other than the "this information may be incorrect" warning)
Would it perhaps make sense to surface the ability to add the local timeline of other instances to your own set of timelines? This seems like it'd probably be more useful than the full federated timeline of all instances.
I think we've still a lot of education to do with regards to instances and how they work for the mainstream internet population.
I know this is really desired by many but there's no good way to do it. All current Mastodon features relating to other servers use ActivityPub. Viewing another instance's local timeline would require using the Mastodon REST API, which would play weird with Pleroma, Misskey, and any potential future project. Third-party apps can afford to do this because they are Mastodon apps and their decisions are very localized. If the Mastodon server started to use its API for federation, that would be worse. That's the showstopper for that feature in my eyes...
I'm not saying doing this via server implementation, just via the client; or perhaps just add a way to get a filtered federated timeline by instances? i.e., only federated toots are available via the instance timeline?
This is just an idea, but really we've first to address the education about instances & introduce people to the fact that not all people are on the same instance as you.
pushed a commit
this pull request
Dec 6, 2018
This was referenced
Dec 7, 2018