ElfWord

joined 1 year ago
 

Egg on my face for not realizing this sooner, but because I've been primarily using lemmy through Sync I didn't realize until yesterday that my current home instance has downvoting disabled. Apparently with lemmy that's a universal setting -- no one can downvote content in any community on the instance, but also accounts on that instance can't downvote content anywhere else.

Sync still displays the downvote button regardless, and will still highlight it in blue if you click it. It wasn't until I learned about Reddthat's policy and started testing how Sync was handling it that I saw the downvote doesn't "stick" -- a refresh shows the downvote button no longer highlighted and no change in the score's content. It's silently failing while in the moment looking like it succeeded.

[–] ElfWord@reddthat.com 1 points 1 year ago (1 children)

Sorry, I don't agree. Telling people they need to "fix" something that is a universal standard everywhere else across the web is poor framing, and its explanation as to what issues it's actually trying to address is pithy and unclear.

I have no issue with there being a better way to internally link to communities within lemmy; it's essentially a lemmy-specific handles format for communities. But I don't think this bot does a good job of communicating that, especially to new users who have every reasonable expectation that a link is a good way to point to any place on the web.

[–] ElfWord@reddthat.com 4 points 1 year ago

Thank you; much appreciated!

[–] ElfWord@reddthat.com 4 points 1 year ago (3 children)

Thank you for the explanation, it's much more helpful than the bot's message.

In this case specifically, the point of the URLs in my post is to show how the difference in how the subscriber stat for a community is displayed when it's viewed from instances other than your home instance.

[–] ElfWord@reddthat.com 6 points 1 year ago* (last edited 1 year ago) (2 children)

If someone who already has a GitHub account wants to post this there, feel free. 🙂 It would be really weird if LJ were not also monitoring their own community the day after launch. 😕

 

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.

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?

Thanks for your work on Sync! Excited to make it one of my daily go-tos again.