this post was submitted on 21 Jun 2023
125 points (100.0% liked)

Fediverse

19 readers
2 users here now

This magazine is dedicated to discussions on the federated social networking ecosystem, which includes decentralized and open-source social media platforms. Whether you are a user, developer, or simply interested in the concept of decentralized social media, this is the place for you. Here you can share your knowledge, ask questions, and engage in discussions on topics such as the benefits and challenges of decentralized social media, new and existing federated platforms, and more. From the latest developments and trends to ethical considerations and the future of federated social media, this category covers a wide range of topics related to the Fediverse.

founded 2 years ago
 

Seeing stuff about reddit being posted to 10 different technology boards, plus reddit-themed ones, then reposted further just makes this whole idea a mess. Reposts have to be consolidated into a single comment thread.

you are viewing a single comment's thread
view the rest of the comments
[–] sik0fewl@kbin.social 8 points 1 year ago (2 children)

I don't think the architecture has anything to do with it. The algorithms just need improving.

[–] useful_idiot@lemmy.eatsleepcode.ca 9 points 1 year ago (2 children)

Even if it just shows the post with most activity once, links to other communities versions inside with comments. Uniqueness determined by url and or title similarity.

[–] vadsamoht@kbin.social 9 points 1 year ago

Essentially this - just (as much as anything is 'just' in software dev) have any posts pointing to the same link from any community in a collapsible list under the top instance, perhaps prioritizing ones that the user is subscribed to for convenience. Users could then expand the list to see where it is being discussed if desired.

[–] insomniac_lemon@kbin.social 1 points 1 year ago* (last edited 1 year ago) (1 children)

I have said it before, I'd like a universal comment section for the link itself (or maybe topic or timeline specific, mod-linked as well) and a separate one for each article (ideally something longer than a paragraph) that can be easily switched.

Even better if the feed showed the URL and grouped the articles based site-wide stats and user-specific preferences.

[–] bionicjoey@lemmy.ca 0 points 1 year ago (1 children)

The only problem is that sometimes the same link will be posted to different communities for both positive and negative reasons.

Reddit used to have the "other discussions" tab for that sort of thing.

[–] insomniac_lemon@kbin.social 1 points 1 year ago* (last edited 1 year ago)

But that's what I'm saying about (Kbin) articles. As in I expect each community to add their thoughts/perspective (or even a break-down) in the form of an article (and then people in said community comment on that). Multiple people maybe, if takes are different enough.

Also I'm saying it should be a faster switch than "other discussions" (which requires going to a separate page first).

[–] 0xtero@kbin.social 9 points 1 year ago (1 children)

There's no algorithm in the fediverse. That's one of the main selling points.

[–] Kara@kbin.social 25 points 1 year ago (2 children)

The feed present on Kbin and Lemmy that delivers content that is "hot" is still an algorithm, it just isn't a hyper-specific one like you'd see on Tik Tok

[–] quandoquando 8 points 1 year ago (1 children)

Sorting by new also is an algorithm.

Not trolling here: I think this is something the fediverse will need to decide at some point. What are the acceptance criteria for timeline presentations? But this would also be a perfect example of diversity: don’t like the way our instance sorts your timeline? No problem, here’s some instances that do it differently.

[–] zalack@kbin.social 5 points 1 year ago (1 children)

The goal should be to allow users to choose their own algorithm, including third party algorithms you can install yourself or something.

[–] quandoquando 2 points 1 year ago (1 children)

Sure, but the algorithms themselves will have to be provided by the instance, so I guess different instance might make different choices, for example due to privacy concerns etc.

[–] zalack@kbin.social 1 points 1 year ago

You could engineer it so users could provide their own algorithm.

It would be a HARD engineering problem, but not impossible, IMO.

[–] 0xtero@kbin.social 3 points 1 year ago* (last edited 1 year ago)

Yes, I meant "recommendation algorithm" or "based on dataming algorithm" - I should have been more clearer.
We have various "sorting", "time" and "weight/vote" based algorithms of course.