/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 2 years ago

Suggestion: Thread Entanglement, or automatic merging of duplicate threads (media.kbin.social)

submitted 2 years ago* (last edited 2 years ago) by Chozo@kbin.social to c/kbinMeta@kbin.social

15 comments fedilink hide all child comments

See the quick inspect-element mockup I put together for an example. I'm bad at design, but I think it gets the point across. Current implementation on left, suggested on right. Also, I'm using Kbin Enhancement Suite for the modifications to instance names, but I think they are even more useful for this demonstration.

How it could work: If the same link is submitted across multiple communities in your current view (subscribed, favorites, all, etc) within a certain time period (probably 24 hours), then have them automatically group themselves into the same box, along with a brief list of the duplicate threads and instances. Use whichever of the threads has the highest score as the one to fill the title and thumbnail for the grouped thread.

I didn't make a mockup for this, but when clicking the thread, it could then import the comments from each of the grouped instances. Options on the sidebar could show you each of the instances whose comments are being shown on that page, along with an option to filter them out of your current feed, and options to add your votes to each instance's thread.

EDIT: To add, as I'm seeing some confusion in the comments: I'm envisioning this as a strictly user-side bundling of threads. This would only bundle threads as they are displayed to the user in their own feed based on communities you're subscribed to. So if the same link were to be posted to 5 different communities you subscribe to, when you view the feed, you'll see those 5 links all bundled together. Though perhaps an option could also include seeing non-subscribed duplicates, as well.

top 11 comments

sorted by: hot top controversial new old

[–] Eggyhead@kbin.social 1 points 2 years ago* (last edited 2 years ago)

I LOVE THIS.

I imagine the experience playing out like this:

Thread Entanglement is a toggle in a user's settings menu.
The comments section of an entangled thread merges all comments from every iteration of the thread entangled. Each comment would have some indication of which entangled community it actually belongs to. Replying to a comment will of course federate your reply to that community's thread.
Posting a new top-level comment offers something like a drop-down box to determine which community a user specifically wishes to affiliate that comment with, but could otherwise default to the local-most, earliest, most populated iteration of the thread, or even a general hashtagged post -depending on user settings.
A community filter/toggle within an entangled thread would allow users to instantly remove all comments from one or more communities.
Communities blocked or not subscribed to by a user will of course not appear in entangled threads unless directed to do so in settings.
Entanglement-exemption options in a user's settings menu could include which communities or users to omit from entanglement, or if any specific communities should be omitted from consideration when posting a new comment in an entangled thread.

[–] hariette@kbin.social 0 points 2 years ago (1 children)

Might have to play with this idea in the Artemis app 👀

[–] RheingoldRiver@kbin.social 1 points 2 years ago* (last edited 2 years ago) (2 children)

oh hi

there's a couple issues to consider with this that come to mind immediately

large difference in subscriber count, and intentionality of posting to a smaller community, not wanting larger traffic (e.g. /m/TrueTrueTrueTrueWorldNews doesn't want the traffic from /m/AnimeTitties or /m/WorldNews or whatever the main one is called)
the same link can be posted to different communities for drastically different reasons, e.g. a headline "Alot of new fantasy releases this summer" gets posted to /m/alot for the grammar mistake, /m/fantasy for book reviews, and /m/journalism for critiquing the writing. All three could be similar size (I can only pretend /m/alot is this popular) but no one wants to see grammar purists on /m/fantasy, and no one on /m/journalism actually cares about the book recs themselves, just the article format

edit wow /r/ is a deeply ingrained muscle memory

[–] ContentConsumer9999@kbin.social 0 points 2 years ago (1 children)

Maybe you could make it so that people/communities can opt out of it. Maybe add a hashtag to comments made on merged threads?

[–] RheingoldRiver@kbin.social 0 points 2 years ago (1 children)

if it were a first-class kbin feature that would be a good solution. but, this is a discussion about Artemis 3rd-party app

also this is only a solution for A, not B.

[–] ContentConsumer9999@kbin.social 1 points 2 years ago* (last edited 2 years ago)

The opting out part should also partially cover subs that mostly react to other posts but you're right. This is probably only possible as an instance feature. Though, the best way to handle this is probably some repost features. Like a way to just link to a post on another magazine and everyone who clicks the post gets redirected to the magazine and/or a post with a custom title which only has another another post as their content like with Reddit reposts.

[–] hariette@kbin.social 0 points 2 years ago (1 children)

Great points! Maybe not so much merging into a single thread then. Maybe a tab view that lets you swipe between other posts of the link. Could have the header show the community info and rules. Could help users find new communities. Just spitballimg tho, lots to think about here 😜

[–] Eggyhead@kbin.social 1 points 2 years ago* (last edited 2 years ago)

I say go for it. Merge them into a single thread.

Unless my comprehension skills aren't all that great (which is actually pretty likely), I think these concerns are easily abated by simply requiring a user to determine which entangled community they want their new comment to be affiliated with before they can post in an entangled thread. Besides, communities that a user isn't already subscribed to or has blocked won't be showing up in an entangled thread anyway, right? So smaller communities aren't likely to appear in very many entangled threads in the first place.

Then just add Entanglement options into the settings menu to allow users to toggle it and add various exemptions.

(I actually was going to reply with this, but instead just moved it to a top level comment for the thread.)

[–] jon@kbin.social 0 points 2 years ago (1 children)

I think something like this is necessary at some point, since duplicate posts across duplicate communities is an inconvenience when compared to more centralized communities in Reddit. Some thoughts:

When you go to the comments, which instance's comments are we seeing? If we make a comment, which instance is our comment posted to? My idea would be to throw everyone's comments into a singular bucket as you said, but then you'll have to select which instance you're posting to when commenting. This does introduce an issue with moderation though, as different communities may have different rules. So there may need to be a moderation option on whether you'll allow post collation across other communities.

Aside from grouping duplicate posts like this, we could also group different communities. If we have a kbin.social/m/technology and lemmy.world/c/technology, we could just combine the posts from both communities into one group. This could be done automatically for communities with the same name, but a better option may be for moderators to add "sister communities" whose posts will appear in the magazine. That way, from the user's perspective, there is just one technology magazine that assembles content from multiple instances.

[–] Chozo@kbin.social 0 points 2 years ago (1 children)

I think the base Lemmy project needs to have some better, built-in support for cross-instance posting. That would make it easier for serial posters to treat communities more like hashtags when submitting links, but still keep feeds clean for the users by keeping the clutter nice and tidy.

In fact, that could help smaller communities grow, too, as you could have it show you "mirrored" versions of that thread from other communities/instances. For example, the same link could be posted to tech@instance.one and gaming@instance.two, but I'm only subscribed to tech, but seeing an option to view the comments from the gaming community's version of that thread would help me discover more content I may be interested in.

[–] luna@kbin.social 1 points 2 years ago* (last edited 2 years ago)

Actually, Lemmy already does crossposts, Kbin doesn't. This user just crossposted their post, and interestingly, they just show up as separate posts to us. I'd think Lemmy would use the protocol's boost feature, but maybe there's some limitation that prevents this

load more comments