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.
I signed up for an account through a smaller instance that felt like it suited me, and I’m trying to build out my feed and subscribe to communities across the federated network. But it’s a pain that in the search summary and in the header of viewing an individual community, the number of subscribers shown isn’t actually a count of how many people are subscribed to it. It’s how many people are subscribed to it, from my local instance.
Obviously being on an instance with fewer users this means the number is small on just about everything, but even for users on larger instances looking to sub to communities on federated instances, this count is underreporting. The RPG community on ttrpg.network has 1.96k subscribers, but viewed through lemmy.world it would appear to only have 301. Viewed through my local instance, it shows as only having 13. 🙁
The subscriber count is the only stat provided in Sync’s search listings view and in the header of an individual sub. It should be a useful metric for determining which communities across the network are getting good traction, but under this current setup, it’s not.
Describe the solution you'd like
Would it be possible to display the total number of subs each community has, on its native instance or across all instances (does anyone more familiar with Lemmy’s technical architecture know if federated subscriptions are included in this count)? Or, would you consider replacing this stat with a more useful metric to gauge the sub’s popularity, like the active users per week, which seems(?) to be a community stat that is federated across all instances?
The text was updated successfully, but these errors were encountered:
The field community_view.counts.subscribers shows the number of community followers across all instances. There was a bug before 0.19 where this would only show local followers in case of a local community but that is fixed. In 0.19.4 there will also be a new field local_subscribers which shows the number of local followers only.
taken from: https://lemmy.world/post/2643284
Is your feature request related to a problem? Please describe.
I signed up for an account through a smaller instance that felt like it suited me, and I’m trying to build out my feed and subscribe to communities across the federated network. But it’s a pain that in the search summary and in the header of viewing an individual community, the number of subscribers shown isn’t actually a count of how many people are subscribed to it. It’s how many people are subscribed to it, from my local instance.
Obviously being on an instance with fewer users this means the number is small on just about everything, but even for users on larger instances looking to sub to communities on federated instances, this count is underreporting. The RPG community on ttrpg.network has 1.96k subscribers, but viewed through lemmy.world it would appear to only have 301. Viewed through my local instance, it shows as only having 13. 🙁
The subscriber count is the only stat provided in Sync’s search listings view and in the header of an individual sub. It should be a useful metric for determining which communities across the network are getting good traction, but under this current setup, it’s not.
Describe the solution you'd like
Would it be possible to display the total number of subs each community has, on its native instance or across all instances (does anyone more familiar with Lemmy’s technical architecture know if federated subscriptions are included in this count)? Or, would you consider replacing this stat with a more useful metric to gauge the sub’s popularity, like the active users per week, which seems(?) to be a community stat that is federated across all instances?
The text was updated successfully, but these errors were encountered: