Fediverse

12 readers

3 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

How does the fediverse handle upvotes on different instances? Does each instance have its own count or are upvotes summed up across multiple instances if the upvotes system (upvotes/boosts/likes) is s (kbin.social)

submitted 1 year ago by dandom_rude@kbin.social to c/fediverse@kbin.social

10 comments fedilink hide all child comments

In the latter case, I think it might be feasible to prevent upvotes from being counted multiple times if the username is identical on different instances, since upvotes are public. Is there already a mechanism to do this?

Also, isn't it much more common in the Fediverse than on central platforms for the same user to have multiple accounts with different usernames? This seems likely to me, if only because popular usernames may already be taken on a given instance. In this case it seems to me hardly possible to prevent double counting. I suppose this would only be possible if the different instances would log IP addresses and share this information with other instances. That doesn't seem desirable to me at all, and probably wouldn't be legal, at least in Europe, because of the GDPR. Are there other possibilities? Cookies?

Please excuse the maybe stupid questions - I'm new here and not very good at finding info on my own yet...

you are viewing a single comment's thread
view the rest of the comments

[–] dandom_rude@kbin.social 0 points 1 year ago (3 children)

Upvotes and downvotes could simply balance each other out. Since upvotes and downvotes are public, it should be possible to check the user profiles in question. But of course, besides surely being technically difficult, that would require that it's actually the same person. This seems impossible to prove, as long as the same username can be registered multiple times on different instances.

However, I think it would be possible to keep a central database containing only the information which username has already been registered within the Fediverse - a bit like domain registrars. When a new user joins, the operators of an instance could look up whether the desired username is already occupied on another instance. This would certainly mean losing some autonomy, since the instances would no longer have sovereignty over available usernames. But I think it would be beneficial overall if usernames were only assigned once within the Fediverse.
For example, when it comes to counting upvotes and downvotes. But also to protect users from being discredited: I'm afraid that with the status quo it is quite easy to impersonate another user, since you can register the same username on another instance and do whatever you please with it. But that's a completely different question, which I fear will become more relevant the more popular the Fediverse becomes (unfortunately, not only users with good intentions will join).

But please don't get me wrong: I find the decentralized open source culture of the Fediverse extremely desirable - it is, in a way, a return to the utopia of the early Internet. I am very happy to be here and to witness that exchange among people is indeed possible without the influence of major corporations like Meta or reddit and all their buisiness schemes.

I just think it's important to have a reasonably meaningful "random Internet points" system, whether it's called karma or something else. I think these points are (unfortunately) the central motivation for many users to post content, which is probably why they play an essential role in the mass appeal of any social media plattform.

[–] duringoverflow@kbin.social 0 points 1 year ago (2 children)

I think it would be possible to keep a central database containing only the information which username has already been registered within the Fediverse - a bit like domain registrars. When a new user joins, the operators of an instance could look up whether the desired username is already occupied on another instance. This would certainly mean losing some autonomy, since the instances would no longer have sovereignty over available usernames. But I think it would be beneficial overall if usernames were only assigned once within the Fediverse.

I don't think this is realistic at all. It breaks the current philosophy of the fediverse where each instance can be both autonomous and federated. What would happen if for example an instance wanted to federate after they already had a couple accounts. Would they need to delete these users because the username exists? This is the reason that the second part (after the "@") exists.

Also look at the email. Ofcourse it is possible to have the same name with users in other email services. It would be very weird not to be allowed to get the yourname@yourfavoriteservice.com because the yourname@anotherservice.com already exists.

What you are suggesting introduces and requires a central authority that would be responsible for that, but this again, breaks the philosophy of the fediverse itself.

[–] ram@lemmy.ramram.ink 1 points 1 year ago (1 children)

It'd not just break the philosophy, but the practical use of the fediverse. People use Mastodon, Peertube, and Lemmy privately amongst a friend group, or even on a LAN; maybe a small company uses Lemmy internally. Then they make it federated later, when they want more users, more content, whatever.

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

Yes, you are right - it's not realistic: On the one hand because it would be hard to come to a consensus on which instances should be changing all those usernames that are registered on other instances at a given point in time. On the other hand there would always be the need to change some usernames.

You probably could have some sort of a best practice to check said public database (btw I meant more of a phone book, not a db where passwords are stored) even for unfederated, local or private instances so that the operators of those instances could only register "free" usernames. But it is indeed not acceptable at all to oblige private instances to feed their usernames into a public database as well. Accordingly, it would not be possible to prevent usernames from being assigned multiple times and having to be changed later on when an instances whose usernames were not in the database decides to federate. This probably wouldn't happen all too often, but it would certainly happen regularly. I hadn't thought of that.