The problem of cross-community posting
Fediverse
56
Posts
23
Posters
139
Views
-
I don't want it to be combined. Different communities have VERY different conversations on the same content.
-
Hmm... that's nice, but the comments are still separated.
It would be better if the separate reply chains were integrated but I know there are potential issues that need to be thought through.
-
Nah, because if if there's a post that's of interest to more than one community, and I'm only in one of those, then I probably don't want to see comments from those other communities, because they will be related to topics/aspects that I'm not here for (otherwise I'd also be subscribed to those communities).
From a discoverability standpoint it would be beneficial to see other communities' conversations on the same post.
-
How does moderation work in this case?
That's one of the issues that need to be worked through. It's a totally legitimate concern.
In cases where communities with polarising viewpoints discuss the same topic, it would lead to inter-community disputes and exacerbate some instance relationships.
One solution would be to have the original community be responsible for moderation, and moderation actions from cross-posted communities only affect their "view", so to speak.
I don't know what the answer is quite yet.
-
That's one of the issues that need to be worked through. It's a totally legitimate concern.
In cases where communities with polarising viewpoints discuss the same topic, it would lead to inter-community disputes and exacerbate some instance relationships.
One solution would be to have the original community be responsible for moderation, and moderation actions from cross-posted communities only affect their "view", so to speak.
I don't know what the answer is quite yet.
and moderation actions from cross-posted communities only affect their “view”, so to speak.
But then if someone posts insults (just to take a simple example), then the original community mods would have to moderate it, and can't rely on the cross-posted communities mods? Wouldn't that lead to cross-posted communities mods just consider that the original community mods are the ones responsible for the moderation, and leave it up to them?
And in that case, then the OG community mods would probably just prefer all the comments to happen on their community where they can delete comments and ban people.
-
Are the posts and communities so strictly structured that a post cannot be a part of multiple communities?
That's my understanding. If I understand correctly, a post belongs to a single community, but two posts referring to the same URL will be identified as such by Piefed, which is how the crossposts community consolidation happens.
In NodeBB categories and topics are all distinct elements, and the fact that a topic belongs in a category is contrived. A topic could be part of a user (pinned topics anyone?), a group (group only conversations?), or in this case… multiple categories.
Interesting, there's definitely discussions to have about how to map that with the Piefed/Lemmy structure
-
They are separated because communities have different rules and different moderation teams.
I know as a user that the same comment on instance A and instance B would be perceived differently. I also know that if I report a comment, it will be reviewed by different mod teams.
As a mod, having a clear view of what comments have been made in my community and which ones have not also helps.
-
From a discoverability standpoint it would be beneficial to see other communities' conversations on the same post.
You can already do that in Lemmy and piefed - crossposts are listed at the top
-
The different communities on Piefed are still separated within the post. You can still see which community you would be replying to
I'm thinking more about less clutter while reading
-
I'm thinking more about less clutter while reading
It's not that cluttered. Have you looked at how it looks on piefed?
-
Fediverse projects are maturing and adoption of them is trending up. I'm excited for the further development of the underlying technologies as well as the apps being built to leverage those technologies into even more integrated, user-friendly experiences.
With any developing tech, small annoyances are found and ultimately patched or worked around. It's to be expected that no user experience is ever perfect, even for matured ecosystems. Typically, some smaller annoyances are tolerated when balanced with the overall utility and usefulness of the tech.
One of the issues I've noticed (and I'm sure I'm not the first or only), is that when posts are relevant enough that the OP decides to cross-post into multiple communities, the comments and engagement stays with each community post leading to separate conversations.
The existance of separate conversations itself isn't necessarily a bad thing. Maybe you post a recipe for Pot Roast in a general cooking community and also a community that helps refine recipes to improve them. It may be that the two separate conversations make more sense as the nature of discourse is focused on two different aspects of the content posted. If they were combined, it would be more difficult to sift through chatter to get at the discussion you were looking for.
This concept is true for different communities as well as different instances. Maybe the Pot Roast recipe conversation generated on lemmy.carnivores is substantly different from the conversation at lemmy.vegan-curious and the existance of both is bolstered by the cultures and seneabilities of the different instance/communities. That could create usefull and/or thoughtful discourse that maybe wouldn't have happened if everyone was mixed together and talking past each other.
However, there are plenty of informative posts attached to very similar communities on a given instance as well as posted to mirror-communities across separate instances. Each individual post is a separate entity and i find myself jumping in to different conversations of the same content to see what's being said in each. In addition to general replies often asking the same questions across all of the posts, unique engagement is diffuse and not connecting.
I imagine that an OP would have trouble keeping up with all of these different interactions and likely defaulting to paying their attention to only one or two while the remaining posts are left to fend for themselves. Even if the OP stayed on top of them all, I assume they'd often have to answer the same questions multiple times.
_The question I pose is: _
What is the solution to myriad and diffuse conversations around cross-posts? Is there a way to handle this situation thru lemmy-ettiquette or does it require a technological solution?
Maybe we handle it thru culture and expectation. If the decided upon method was to post once and then link that post to other communities for exposure, maybe that funnels everyone into one post to interact (when that's what OP wants).
Is there a software solution on the app developer level that combines like posts together? Is it a protocol level solution thats required? Maybe something that allows a single post to essentially 'tag' different communities for exposure, while only posting once? Can we associate posts to an individual user rather than associating the post to a community, so all replies come to the user post rather than in a community?
I don't know what the solution looks like and I'm not savvy enough to understand the protocol/software side to know if any of my examples are realistic. I also don't know if this is an issue for anyone else, or at least one that lemmy-ites actuallly care about enough to try and solve.
Does anyone know if work is being done to address this? Am I focusing on something that is simply not a priority? I welcome your thoughts.
...I tried to choose what I thought was the best place for this post, but I'm open to moving it if I was in error. (Ironically, something that might be easier if posts were handled differently). :)
From what I recall, I believe that Reddit handles crossposts in a similar manner, that is, comments in one crosspost in one subreddit don't show in other crossposted subreddits.
Like Blaze mentioned in another comment, one of the problems with putting all the comments together is that different communities have different rules, so a comment that would be fine in one community might get you in trouble in a different community. People already get confused by this as it is. If all the comments from different crossposts get aggregated in one place, I think it would cause complete confusion and more work for mods.
-
From what I recall, I believe that Reddit handles crossposts in a similar manner, that is, comments in one crosspost in one subreddit don't show in other crossposted subreddits.
Like Blaze mentioned in another comment, one of the problems with putting all the comments together is that different communities have different rules, so a comment that would be fine in one community might get you in trouble in a different community. People already get confused by this as it is. If all the comments from different crossposts get aggregated in one place, I think it would cause complete confusion and more work for mods.
Piefed splits up the comment boxes based on community when a thread is crossposted, so you can still distinguish between the comment boxes on different communities despite them being visible.
That said, a potential future option here would be a community opt-out of crosspost functionality in this way
-
From what I recall, I believe that Reddit handles crossposts in a similar manner, that is, comments in one crosspost in one subreddit don't show in other crossposted subreddits.
Like Blaze mentioned in another comment, one of the problems with putting all the comments together is that different communities have different rules, so a comment that would be fine in one community might get you in trouble in a different community. People already get confused by this as it is. If all the comments from different crossposts get aggregated in one place, I think it would cause complete confusion and more work for mods.
What if upon cross-posting the default is separation, but a request is sent to the original community to request a comment tree merge?
Then you don't have to share comment space with the tankies unless you wish it
-
Alternative suggestion - allow communities to block crossposting functionality with specified communities in the community settings.
-
Every instance should simply just stop thinking they should have their own version of X community.
Doesn’t PieFed merge communities with the same name?
Shall we keep memes on Beehaw or .ml?
-
As mentioned in another comment, as a mod there's not a lot of value mixing other comments I cannot mod about to the ones I can mod. Seems like an easy way to abuse the system and avoid moderation
-
the conversations should be combined
Disagree. As OP points out, there is value in separating the discussions as well.
-
Different conversations in different moods and cultures on the same subject are something completely human and normal, and tech should not work to undo this. When we have seen tech undo this is with social media silos, after all.
Which is to say, any "solution" that integrates those conversations into one view should be, where possible, client-side only. That way I can opt in to view some conversations as unified or not, depending on eg.: how well do I know the context, or whether the OP is a person known for cross-posting (and to where), while at the same time not forcing everyone else to have their culture of conversation subsumed into essentially an attempt to make topical subreddits.
Finally someone who gets it. This "problem" is in fact a total non-issue. Different groups talk about the same thing all the time. This is good, not bad.
-
Fediverse projects are maturing and adoption of them is trending up. I'm excited for the further development of the underlying technologies as well as the apps being built to leverage those technologies into even more integrated, user-friendly experiences.
With any developing tech, small annoyances are found and ultimately patched or worked around. It's to be expected that no user experience is ever perfect, even for matured ecosystems. Typically, some smaller annoyances are tolerated when balanced with the overall utility and usefulness of the tech.
One of the issues I've noticed (and I'm sure I'm not the first or only), is that when posts are relevant enough that the OP decides to cross-post into multiple communities, the comments and engagement stays with each community post leading to separate conversations.
The existance of separate conversations itself isn't necessarily a bad thing. Maybe you post a recipe for Pot Roast in a general cooking community and also a community that helps refine recipes to improve them. It may be that the two separate conversations make more sense as the nature of discourse is focused on two different aspects of the content posted. If they were combined, it would be more difficult to sift through chatter to get at the discussion you were looking for.
This concept is true for different communities as well as different instances. Maybe the Pot Roast recipe conversation generated on lemmy.carnivores is substantly different from the conversation at lemmy.vegan-curious and the existance of both is bolstered by the cultures and seneabilities of the different instance/communities. That could create usefull and/or thoughtful discourse that maybe wouldn't have happened if everyone was mixed together and talking past each other.
However, there are plenty of informative posts attached to very similar communities on a given instance as well as posted to mirror-communities across separate instances. Each individual post is a separate entity and i find myself jumping in to different conversations of the same content to see what's being said in each. In addition to general replies often asking the same questions across all of the posts, unique engagement is diffuse and not connecting.
I imagine that an OP would have trouble keeping up with all of these different interactions and likely defaulting to paying their attention to only one or two while the remaining posts are left to fend for themselves. Even if the OP stayed on top of them all, I assume they'd often have to answer the same questions multiple times.
_The question I pose is: _
What is the solution to myriad and diffuse conversations around cross-posts? Is there a way to handle this situation thru lemmy-ettiquette or does it require a technological solution?
Maybe we handle it thru culture and expectation. If the decided upon method was to post once and then link that post to other communities for exposure, maybe that funnels everyone into one post to interact (when that's what OP wants).
Is there a software solution on the app developer level that combines like posts together? Is it a protocol level solution thats required? Maybe something that allows a single post to essentially 'tag' different communities for exposure, while only posting once? Can we associate posts to an individual user rather than associating the post to a community, so all replies come to the user post rather than in a community?
I don't know what the solution looks like and I'm not savvy enough to understand the protocol/software side to know if any of my examples are realistic. I also don't know if this is an issue for anyone else, or at least one that lemmy-ites actuallly care about enough to try and solve.
Does anyone know if work is being done to address this? Am I focusing on something that is simply not a priority? I welcome your thoughts.
...I tried to choose what I thought was the best place for this post, but I'm open to moving it if I was in error. (Ironically, something that might be easier if posts were handled differently). :)
What about making crossposts look like a quote post? Reddit already does that.
-
Fediverse projects are maturing and adoption of them is trending up. I'm excited for the further development of the underlying technologies as well as the apps being built to leverage those technologies into even more integrated, user-friendly experiences.
With any developing tech, small annoyances are found and ultimately patched or worked around. It's to be expected that no user experience is ever perfect, even for matured ecosystems. Typically, some smaller annoyances are tolerated when balanced with the overall utility and usefulness of the tech.
One of the issues I've noticed (and I'm sure I'm not the first or only), is that when posts are relevant enough that the OP decides to cross-post into multiple communities, the comments and engagement stays with each community post leading to separate conversations.
The existance of separate conversations itself isn't necessarily a bad thing. Maybe you post a recipe for Pot Roast in a general cooking community and also a community that helps refine recipes to improve them. It may be that the two separate conversations make more sense as the nature of discourse is focused on two different aspects of the content posted. If they were combined, it would be more difficult to sift through chatter to get at the discussion you were looking for.
This concept is true for different communities as well as different instances. Maybe the Pot Roast recipe conversation generated on lemmy.carnivores is substantly different from the conversation at lemmy.vegan-curious and the existance of both is bolstered by the cultures and seneabilities of the different instance/communities. That could create usefull and/or thoughtful discourse that maybe wouldn't have happened if everyone was mixed together and talking past each other.
However, there are plenty of informative posts attached to very similar communities on a given instance as well as posted to mirror-communities across separate instances. Each individual post is a separate entity and i find myself jumping in to different conversations of the same content to see what's being said in each. In addition to general replies often asking the same questions across all of the posts, unique engagement is diffuse and not connecting.
I imagine that an OP would have trouble keeping up with all of these different interactions and likely defaulting to paying their attention to only one or two while the remaining posts are left to fend for themselves. Even if the OP stayed on top of them all, I assume they'd often have to answer the same questions multiple times.
_The question I pose is: _
What is the solution to myriad and diffuse conversations around cross-posts? Is there a way to handle this situation thru lemmy-ettiquette or does it require a technological solution?
Maybe we handle it thru culture and expectation. If the decided upon method was to post once and then link that post to other communities for exposure, maybe that funnels everyone into one post to interact (when that's what OP wants).
Is there a software solution on the app developer level that combines like posts together? Is it a protocol level solution thats required? Maybe something that allows a single post to essentially 'tag' different communities for exposure, while only posting once? Can we associate posts to an individual user rather than associating the post to a community, so all replies come to the user post rather than in a community?
I don't know what the solution looks like and I'm not savvy enough to understand the protocol/software side to know if any of my examples are realistic. I also don't know if this is an issue for anyone else, or at least one that lemmy-ites actuallly care about enough to try and solve.
Does anyone know if work is being done to address this? Am I focusing on something that is simply not a priority? I welcome your thoughts.
...I tried to choose what I thought was the best place for this post, but I'm open to moving it if I was in error. (Ironically, something that might be easier if posts were handled differently). :)
What if a post was its own separate thing, detached from the communities. You then "attach" the post to one or more communities.
When a user comments on a post, the comment "comes from community xyz" but all comments are attached to the post not the community.
Lemmy applications can choose to filter comments from one or more communities or show them all.
Gli ultimi otto messaggi ricevuti dalla Federazione
-
I think there's definitely an underserved space for academics on the fediverse.
Feed-based mechanics are not good for archival or slower (read: not always online) readers, so NodeBB actually works really well to collect that stuff and present it in less of a firehose-y format.
For example, here's a NodeBB forum that follows the #medicine tag: https://postcall.pub
Here on ActivityPub.Space the discussion is all ActivityPub focused and it is really really good at keeping up to date with the latest topics.
I'd be happy to work with you to start a general science (or more topic-focused) board if you're interested...
-
you may also find a slack channel dedicated to your field.
-
I think a lot of them moved to bluesky
facepalm
-
I think a lot of them moved to bluesky.
Here, I would just hang out in the science communities and other relevant ones, post relevant things and follow people you're interested in.
-
Create/join communities in your field, on Mastodon follow the hashtags and most importantly feed them with posts even if no one answers or interacts, someday you’ll reach the audience you’re looking for
-
The academic meme community here is absolutely ace! But what I would also like is to communicate with other academics in my field and share the latest publication and talk about it a bit if possible with peers.
I used to use Twitter (back when it was called Twitter) to post about my new publications. Now I use Mastodon.
Say what you wish about the negative aspect of algorithm based feeds, I am currently finding it hard to connect with other academics whose profiles may be dispersed in the wide fediverse.Long story short: How do I disseminate my work and connect with other academic peers in my field on the fediverse?
I'm study biosystems and circular economy.
-
Good on you Rimu. If NodeBB implements Activity Intents it'll be because of you.
-
There is a FEP for this - https://codeberg.org/fediverse/fep/src/branch/main/fep/3b86/fep-3b86.md it's not something dansup came up with originally. We'll see how close Pixelfed adheres to it.
PieFed has implemented basic support for that FEP since August 2025 and I just added more today.
