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.

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.

This is a bit of a tangent, but I’m curious who runs this website: http://www.edwaittimes.ca/WaitTimes.aspx

It’s always been slow for me, and it doesn’t feel that accessible (text is hard to read etc.). A quick upgrade and refresh might make it a lot smoother for people. If we wanted to go more fancy with it, it could have a dashboard page just for hospitals to display in their ERs, like they do (did?) at MSJ.

I know BC has a Github with open source projects, and this seems like a relatively simple upgrade if we knew what the API / data source was. I’m noticing some AJAX & jquery. Could something like Vue/Nuxt work as a replacement? The pages could be rendered server side, and then every 5 minutes it could be refreshed with the new data.

I like this one

https://canadiangeographic.ca/wp-content/uploads/2023/08/36835094-Northwest_Passage_Wall.jpg

deleted by creator

Hope it helps :)

Oh ok thank you I’ll look into it!

Thank you! I’m happy that people find it helpful :)

thank you!

I will fix the generated code so that the copy and paste works as well. I was mostly focussing on the button and… clearly didn’t test the codes enough.

The “type unknown” refers to the type of instance (lemmy vs. kbin), and you can use the “Toggle home instance type” to change it. It exists because lemmy uses “/c/” for community links, while kbin uses “/m/”, and the extension needs to know what kind of link to generate. By default, it generates Lemmy style links.

I am planning to add a little (?) help icon to each button, which might help with confusing bits like this in the future.

Hope that helps, and thank you for the feedback!

Hope it works well, feedback is welcome :))