For now, I just block people who spam like that. Curating my feed is necessary for my sanity.
Kbin should include instance domain in community names not from the local instance, so the difference is clear.
'technology' does not name a single community, even though it looks so.Id like to see instance names eveywhere it is relevant. Usernames, communities etc.
Tagging @Jajcus so they see it.
There is at least for now a userstyle script that allows that (showing the domain beside usernames, communities/magazines)and it's included in kbin Enhancement Suite (/m/enhancement) at the very least.
I reckon things like that will stop as either a) one community/magazine starts being the main one and people start paying mainly to that or b) kbin and lemmy develop a culture that discourages so much cross posting because people signing up for multiple communities/magazines across platforms rather than sticking to their own platform. Both lemmy and kbin are too new for either of those to have occurred.
You might want to comment to the pride that do it how spammy it makes the feed. They might not realize how annoying it can get, in their excitement to post and wanting to get the most eyes on it.
There's also c) have people start using tags like #technology more frequently in their technology related posts, and implement support for subscribing to a tag (that's something Mastodon already has, so it should be possible).
Tag thread feeds (like https://kbin.social/tag/technology/threads ) show content cross-instance and cross-magazine, and they also have the advantage that you can add multiple tags to the same post, no need to repeat the post to have it appear in multiple tag feeds.
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.would the client know which one of those three communities is the "main" and which other two should be filtered away.
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.
The easiest would be to unsubscribe from two of them.
I think this is kind of unfair.
how would the client know which one of those three communities is the "main" and which other two should be filtered away.
Probably the local-most iteration followed by the time of posting/federating.
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?
The easiest would be to unsubscribe from two of them. Or even better, if people could stop cross-posting.
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.
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.
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.
If you are subscribed to the same mag 3 times, well it's on you. You want volume you have it.
What is possible is to filter through a script and only show the local one.
A possibly nice UX could be clients grouping all crossposts from the same author together in a little stack, but showing the local or oldest version "on top"
Initially I thought you were saying they subscribed to a single magazine from the same instance three times and was thinking "Is that even possible?".
Then I had a closer look and realised they were 3x different magazines on different instances but all with the same name.
Makes sense that it would appear 3x times.
I'm hoping eventually there will be a 'merged' view for this situation, so all the comments are amalgamated, and the article appears once only. Whether that can happen server side or will need to be an app-specific feature, I guess time will tell.
I was thinking that the platform should display a "Also found in..." text that'd take you to the other related communities.
This, definitely. Reddit's always had an "Other Discussions" button in posts, and I've actually found a lot of good small subs over time from clicking through and reading comments in other subreddits.
That's a great idea. What if it showed you a side by side of the most active thread along with the thread on your local instance (if it exists). Then include an "other discussions" button to see all instances with the post. As well as a "merge comments" button to view every comment in one page ranked by upvotes.
The url is the same for each post - something on cnbc.com - so theoretically it should be possible to de-duplicate them. One day.
The source is the same, but the communites are different, which will also mean a different set of comments for each link.
I agree that this looks annoying. But maybe the trick is not to think of it as the same article as being posted three times, but rather as the same prompt being used to spark conversations in three different communities. If you find that you see substantively the same content in multiple instances, both in terms of thread starters and ensuing conversation, then maybe that's a sign you can safely prune the communities you subscribe to.
I reached the same conclusion on reddit where I would see the same article posted to related subreddits, eg news, politics, uspolitics, bipartisanpolitics, neutralpolitics etc.
I hope you cursed each and every one of those reposts and unloaded accordingly 😡
I decided that for some subreddits, seeing the same article posted was okay because the community discussion was quite different. In other subreddits the discussion was basically the same, or there was minimal/no discussion, so those subreddits fell off my list.
It’s similarly unpleasant browsing All from lemmy.world. 70% non-English (no hate, I just literally cannot engage), 25% spam crossposts, and 5% porn.
It’s like a ghost town. At least do more than dropping a link with zero discussion.
I do hope the Kbin team can implement something akin to Lemmy's cross posting but even more involved; like stacking similar posts with the same source URL into one post on a feed, or grouping communities with the same name in with matching hashtags
I'm not sure that's even a problem in the first place.
You're subscribed to 3 different "technology" communities, and that's a big tech story. You can simply scroll past it or just unsub 2/3 of those communities.
Maybe there is some way that these different posts on different servers could be merged together and treated as one, but that sounds technically challenging to me and might be a bit overdesigned.
