this post was submitted on 13 Jul 2023
23 points (100.0% liked)
/kbin meta
2 readers
1 users here now
Magazine dedicated to discussions about the kbin itself. Provide feedback, ask questions, suggest improvements, and engage in conversations related to the platform organization, policies, features, and community dynamics. ---- * Roadmap 2023 * m/kbinDevlog * m/kbinDesign
founded 1 year ago
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Take it easy. Kbin is only a few months old, and the developer works on this in their spare time.
There are lots of optimizations to make.
People need to stop cross-posting news 5x across the entire fediverse. It makes it impossible to have any discussion.
So yes, but no, unfortunately... The problem is with defederation. Those of us that are federated with everyone see all of those links, but if one or more of those instances is defederated from others (Like BeeHaw) then they are excluded - and it makes sense to post that link on their instance as well.
This isn't going to be solved by not posting news articles, it will have to be mitigated through a grouping of some sort, like a multireddit for fedi.
I disagree because how do you know where to post? It is unclear at the moment. And why post if nobody will read it?
It is within your power to subscribe only to a single community.
It's a hard problem though - those are three different communities on tree different instances after all. The topic is "valid" for each of them and the local population of the instance, so it's not like the servers can refuse the submission.
Doing filtering on the client would maybe be an option, but how would the client know which one of those three communities is the "main" and which other two should be filtered away.
The easiest would be to unsubscribe from two of them. Or even better, if people could stop cross-posting.
But we know people aren't going to stop.
Except cross-posting has a purpose. In that example, one of the posts was to beehaw while another was to lemmy.world. Beehaw defederated from lemmy.world so users on beehaw are only going to potentially see two of the three cross-posted posts. If they also defederate from lemmy.ml, those users would only see one.
So yeah, the solution is to unsubscribe from two of those communities because they're essentially 3 completely different groups that just happen to have the same name and general focus. Either that or just get used to it.
Imho, it should not "filter away" any of the entries. But rather merge all in the same "meta-post" (or whichever term is chosen). Show those posts a bit differently by aggregating the authors (with a clickable "..." ellipsis if the list is too long but that allows to show them if wanted), and when viewing the content either aggregate the comment threads or maybe add tabs to alternate between instances.
I think this is kind of unfair.
Probably the local-most iteration followed by the time of posting/federating.
OP asked a question:
Answer: unsubscribe from 2 of the >3 substantially similar communities.
OP is that every bakery is selling bread.
Maybe instead of filtering the client could do a merge and list the comment trees under one header grouped by the community/magazine they are posted to?
Fair enough. It's just unfortunate because the content Pips is posting is good content, it's just that posting it absolutely everywhere all at once undermines the point of being federated with other tech communities. By making it spammy, it discourages people from wanting to follow more than one tech group at a time, which isn't fair to those tech groups. If Pips just stuck to posting in the tech group they like, that could be a good incentive for more federated users to just follow that specific group.
I'm not endorsing their behaviour, but I can imagine myself doing something similar to Pips. I'm just hoping to show an alternative perspective here, maybe it'll make the spam more tolerable for you lol.
I follow basically all the warhammer hobby magazines/communities I come across. They're all still growing, some a little quicker, but honestly there isn't a single clear winner. Since they basically all would benefit from more content and activity, shouldn't I post to several admittedly very overlapping groups?
There's only so much content I can contribute as a single user. I either make an OC post when I've painted something up, or I'll link like the one or two noteworthy news articles for this week lmao. I can't create bespoke content for each instance.
I do want them all of them to succeed, or any one of them to succeed. They're all starving for content most days. But right now, the fediverse just doesn't have the critical mass yet. So how should we grow it?
Eventually, a clear winner will emerge, and I'll probably prune my subscriptions list. But we're in the spring of the fediverse, it's just too early to tell which sprouts will flower best.
Yes... I honestly wish using and subscribing to tags was a more of a thing, since those are cross-instance, and multiple communities with overlapping topics could just make use of overlapping tags. And they also have the advantage that you can add multiple tags to the same post, no need to repeat the post.
Right now you can visit https://kbin.social/tag/technology/threads and see all threads tagged as technology, cross instance and cross magazine, but you cant subscribe to that (but it should be possible to implement at some point though, Mastodon does it).
Well, if you think it's good content then comment on it. If OP sees that he has no traction in xyz instance then he will probably leave it behind and stop cross posting.
Again the best option is to sort through a script and select one based on your own settings.