You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
In order to discover labeling services, users must seek out seek out lists on third-party websites. I believe this results in under-utilization of labeling services.
in https://bsky.app/moderation > Advanced a "Discover Labelers" could be added
just like in https://bsky.app/feeds "Discover New Feeds" and the search field can scan both the Description(Bio) + labels + label descriptions
Our intention is to add in-app discovery of labelers eventually, similar to feeds (as you mention).
However, for moderation tooling specifically, we feel it is more important to go slowly: we don't want a large number of abuse or inactive labelers to appear in the discovery section. A huge influx of subscribers and reports to the "top" labelers could also overwhelm them. The current mechanism of sharing/recommending labelers by embedding them in quote-posts allows folks to recommend labelers to their individual communities.
I'd love to see how many users are subscribing any given labeler and how many labels has each given labeler issued. Since not all are labels are "negative" (e.g. you can get a flag label from kickflip), a decision should be made on whether this data is public, embraced, and easily discoverable, or not.
Is your feature request related to a problem? Please describe.
In order to discover labeling services, users must seek out seek out lists on third-party websites. I believe this results in under-utilization of labeling services.
Describe the solution you'd like
Create an in-app directory of labelers, sorted by number of likes, similar to the in-app directory of feeds.
Describe alternatives you've considered
Maintain the status quo if this feature is believed to give labelers too much power.
The text was updated successfully, but these errors were encountered: