I might be able to set something up with the InstanceAssistant browser extension. It would be nice to have it in the main UI, but this could help temporarily.

I’ll send a PM :)

This is amazing, thank you for reaching out to the dev!

This was on the list of ideas for InstanceAssistant, but I didn’t know where to start. It is great news that it was added to the original extension.

I think the issue here is

they don’t show up under “posts” on your own profile

It makes sense to hide read posts on the main feed, but not when you’re looking at a particular user?

Yep I think the defederation point is the big one which causes the idea to break down. I’ll edit the post to better reflect my thoughts now

Thank you!

Hope it helps :)

Look, honestly: if you want Facebook ot Twitter, go back to them.

This post was to talk about the merits/drawbacks of a potential change, and the constructive comments on the post have been helpful for that. Some of the other ‘solutions’ that have been posted here feel even more antithetical to the idea of decentralization (ex. redirecting upvotes, having communities follow other communities) so I was looking for a compromise that would address some of the annoyances without making the site another centralized platform. The intent was to allow users to choose how they want to link cross posts together, rather than having the community (or an app/frontend) make the decision for them. We’ve also been seeing users naturally gravitate to a few instances/communities, so I was looking for ways to redirect some of that traffic back to lesser known spaces.

Regardless, I appreciate the comment. Reading the perspectives on this post helped me see how locking the post completely would cause more issues and annoyances than it would help with. A simple “we are discussing X over on this post, feel free to join” seems like the better compromise.

that’s fair :)

Everyone who’s subscribed to the same communities will see all of each others’ comments.

This still relies on everyone using the same app/front-end.

I guess I’m thinking about how it would be helpful in more general cases. If someone has an issue with a FOSS app, and they ask about it in two small communities, it would be much better to have the troubleshooting discussion in one place rather than have both communities missing part of the context.

Ultimately in your example, the user can still make both posts, this doesn’t change that. It just directs the comments to one post’s comment section rather than having it spread out.

Still it’s good to think about cases where OP tries to abuse the system. Would a good middle ground just be the first implementation then? For OP to link to the post that they want to be the main discussion thread, but people are free to ignore that if they want.

I agree, instance assistant (our extension actually!) handles this, but it would be much better to have it exist natively.

this proposal would give more controls to the bigger communities

what are the concerns that come to mind?

I’d rather just have different communities

All the individual communities would continue to exist as they do right now. When it makes sense for a post to have a deeper discussion, users can lock and redirect accordingly

This works for viewing all the comments so far, but it doesn’t solve the discussion aspect since commentors from each community won’t be seeing or responding to the other comments. This is a bigger issue with smaller communities, where they’d mostly be top level comments / chains with minimal depth from each smaller community. Yes you can see all the comments, but the discussion quality is poor.

It’s also not as helpful when the automation fails. Something I’ve found is that the ‘crosspost’ field starts to get crowded on posts that link to a popular website. Combining comment sections from ALL of those posts isn’t as useful as having some intentional action from the OP.

A key aspect about this proposal is that it requires the OP to do something. If it doesn’t make sense for a community (ex. different intents behind the Politics communities), then OP shouldn’t lock their post. If OP does it anyway, then you can downvote that post.

You could try from this

https://lemmy.world/post/1289432

Ideally try for a smaller size, else it takes time to load and wastes people’s data

We actually have an extension for this, it’s one of the more popular extensions for Lemmy&Kbin, going by the counts on chrome/firefox stores:

[email protected]

It was originally made to solve this problem, but we’ve been adding other features as well. Right now you can redirect communities and posts, and redirect links by right clicking on them.

Let me know if it works, and also where it doesn’t so that we can improve it :)

I personally find a lack of downvotes to be annoying and harmful. People don’t go through the trouble of reporting problem content, and it usually leads to poor quality inflammatory content rising to the top.

If you’re new and haven’t really set up yet, explore other instances. You can find one that aligns with what you want out of Lemmy without jumping through hoops.

If you have set up, there are account migration tools for you. They just aren’t perfect yet

Hope it helps!

For sure, I’ll incorporate a TLDR in future posts :)

That’s really great to hear, thank you for the comment :)

Image size manipulation is something that’s on the list, and it’s one of the features that myself and the dev for LemmyTools was working to bring over from the userscript

Here is the specific issue, although I’m not sure when I’ll be getting to it: https://github.com/cynber/lemmy-instance-assistant/issues/28

In the meantime, you could also try out the userscript itself and see if it does the job, and also what could be improved when we do bring the feature over: https://github.com/howdy-tsc/LemmyTools

Good to know, could you share what website you were trying to post from?

I think one thing I should implement is a little toast message that explains what went wrong (ex. No title contents found)

Hope it works for you!

Hope it helps :)