(Lemmy bug) cannot cross-post to [email protected] b/c the pull-down list is clusterfucked with Cloudflare sites
(Lemmy bug) cannot cross-post to [email protected] b/c the pull-down list is clusterfucked with Cloudflare sites
This is likely a Lemmy bug but infosec.pub is related because there are so many Android communities that are federated from bad places so I thought I would mention it here as well.
cross-posted from: https://infosec.pub/post/11060800
The cross-post mechanism has a limitation whereby you cannot simply enter a precise community to post to. Users are forced to search and select. When searching for “android” on infosec.pub within the cross-post page, the list of possible communities is totally clusterfucked with shitty centralized Cloudflare instances (lemmy world, sh itjust works, lemm ee, programming dev, etc). The list of these junk instances is so long [email protected] does not make it to the list.
The workaround is of course to just create a new post with the same contents. And that is what I will do.
There are multiple bugs here:
① First of all, when a list of communities is given in this context, the centralized instances should be listed last (at best) because they are antithetical to fedi philosophy.
② Subscribed communities should be listed first, at the top
③ Users should always be able to name a community in its full form, e.g.:
[email protected]hilariouschaos.com/android④ Users should be able to name just the instance (e.g. hilariouschaos.com) and the search should populate with subscribed communities therein.
2, 3, and 4 are brilliant suggestions.
1 is ridiculous. You're actively asking for a worse user experience. When ordering a search, after 2–4 have been accounted for, order should be descending order of size.
order should be descending order of size.
If bigger is better, why are you here instead of Facebook and Twitter? Fedi principles and philosophy have completely escaped you. In the fedi, we consider power imbalances, privacy abuses, and exclusivity resulting from centralization to not only worsen UX but to be an injustice. Encouraging disproportionate growth in the fedi is to advocate the destruction of what brings us here.
You might prefer smaller instances; I see a lot of value in that. I myself am on an instance that's almost identical in size to yours.
I do not see the value in smaller communities being prioritised when they each cover the same topic. If there's [email protected] with 10,000 subscribers and [email protected] with me and my twelve mates, lemmy.world is the one the app should show people first. It wouldn't matter to me whether that 10,000 is on lemmy.world or midwest.social, it makes sense to show users the place they're likely to have the most interaction.
I actually didn't realise which community I was in when I posted that previous comment, and as a user of a different instance I might not have weighed in had I done so. However I will say that:
- This part of it is clearly not a bug, however you put it. It is a difference of preference. There is a worthwhile bug to report here, but it's around the inability to view more than some number of communities when you search. I think you do yourself a massive disservice by conflating two essentially unrelated issues, one of which is your personal preference.
- It's not instance-related at all. This belongs in discussion around lemmy-ui, the various Lemmy apps & alternative front-ends, or in Lemmy itself with what gets returned by its search API.