You can kindof think of the fediverse stuff as being similar to email. You and I both signed up to create an account with kbin.social. This is where our account lives and it will show up in our full username (hover over any username) after the second @. You are @autumnplains@kbin.social and I am @sxt@kbin.social.
OP created their account with reddthat.com so that is where their account lives.
Unlike email however, we aren’t sending messages directly to each other - we are instead sending them to a particular “community” which happens to live on the lemmy.ml server. This is possible since each of these hosts are running software which can communicate in a common manner (this is what ActivityPub defines the rules for). You probably got to this thread from kbin’s general “threads” page which is able to list posts from other hosts due to them being federated (can communicate what posts they have to each other).
As for kbin.social being put next to the right of the title for this thread, I’m not sure. I think that might just be part of kbin’s UI showing where we are viewing the thread from?
The problem is that every “magazine” or “community” or whatever you want to call them (each one using a different name is also a bit of an issue) is part of their own decentralized network. Yes, you might be able to read them from other services, but it still causes a lot of fragmentation. For example when I look into something akin to a news sub for international news, I find worldnews@lemmy.ml as well as news@beehaw.org. Both basically do the same thing topically, but both have different submitted content, different users, and oddly in this case even the same owner.
This now begs the question for me as a user: Which one do I subscribe to if I want to stay informed? An article on one side could be submitted or gain traction when it does not on the other. But subbing to both could lead to a lot of duplicate articles being fed to me.
I think this is a huge issue in the whole design philosophy of the fediverse that will hamper the growth of those services. Deciding where to make an account might be something a new user gets around to, but being then confronted by this is very quickly going to turn away the absolute majority of potential users. There needs to be at least a little bit centralization to form major default communities that at least start as a gathering hub for new people. If there’s issues with them then people can still create alternatives if the user numbers are high enough, but in its current form I’d have to decide between several places that are essentially the same thing.
But is it really a Problem exclusive to the fediverse? there is several large news communities on reddit as well, and you have to pick or see duplicates. Also, this is only an issue in heavily aggregation-focused communities, not in those where content is generated (memes, hobby communities) as those do not have the issue of duplicates so you can just sub to all the ones you are interested in, even if several of them have the same subject.
This now begs the question for me as a user: Which one do I subscribe to if I want to stay informed? An article on one side could be submitted or gain traction when it does not on the other. But subbing to both could lead to a lot of duplicate articles being fed to me.
Theres nothing stopping the client from offering a different or entirely customizable view to the content.
For example the client could allow user to place those communities under a common News category in their client. Then the client would combine all identical links in the category according to some criteria (e.g same link posted in the same day would count as identical) and either merge the comments or let the user pick which communitys comments to see, or preferably both. So comments section could have a buttons for “Comments at news@beehaw.org”, “Combine comments” etc.
I think it should be possible to build a client that hides most of the details about different instances and such so it would function almost the same as traditional RSS readers.
As for kbin.social being put next to the right of the title for this thread, I’m not sure. I think that might just be part of kbin’s UI showing where we are viewing the thread from?
It seems that if kbin federates a post that doesn’t have a link or image and just points to itself, it fills in (kbin.social) as the link pointer, when you view it on kbin. It’s a bit confusing at first, should probably be replaced by something that indicates it’s a federated “self”-post.
This is a post to linux community (@linux@lemmy.ml) by user falcoignis (@falcoignis@reddthat.com). You’re reading it on kbin since it has federated this post. The default “front page” shows federated feed (Threads).
OP is on reddthat (@falcoignis@reddthat.com), which is a Lemmy instance, and the community this post is on is !linux@lemmy.ml. Not sure what’s up with kbin appearing next to OP’s name for you, might be incidental because of kbin’s UI or something.
Edit: just looked on kbin for myself, no idea what is up with that honestly, but I see what you’re talking about as well.
Yeah I’m still pretty confused tbh! So I’m on kbin, you have kbin next to your name too OP, but then the sidebar has reddthat.com and linux@lemmy.ml?
Does this mean we both signed up at kbin but the subreddit equivalent is linux (on Lemmy.ml)? But then how does reddthat.com come into it?
You can kindof think of the fediverse stuff as being similar to email. You and I both signed up to create an account with
kbin.social. This is where our account lives and it will show up in our full username (hover over any username) after the second @. You are@autumnplains@kbin.socialand I am@sxt@kbin.social.OP created their account with
reddthat.comso that is where their account lives.Unlike email however, we aren’t sending messages directly to each other - we are instead sending them to a particular “community” which happens to live on the
lemmy.mlserver. This is possible since each of these hosts are running software which can communicate in a common manner (this is what ActivityPub defines the rules for). You probably got to this thread from kbin’s general “threads” page which is able to list posts from other hosts due to them being federated (can communicate what posts they have to each other).As for kbin.social being put next to the right of the title for this thread, I’m not sure. I think that might just be part of kbin’s UI showing where we are viewing the thread from?
The problem is that every “magazine” or “community” or whatever you want to call them (each one using a different name is also a bit of an issue) is part of their own decentralized network. Yes, you might be able to read them from other services, but it still causes a lot of fragmentation. For example when I look into something akin to a news sub for international news, I find worldnews@lemmy.ml as well as news@beehaw.org. Both basically do the same thing topically, but both have different submitted content, different users, and oddly in this case even the same owner.
This now begs the question for me as a user: Which one do I subscribe to if I want to stay informed? An article on one side could be submitted or gain traction when it does not on the other. But subbing to both could lead to a lot of duplicate articles being fed to me.
I think this is a huge issue in the whole design philosophy of the fediverse that will hamper the growth of those services. Deciding where to make an account might be something a new user gets around to, but being then confronted by this is very quickly going to turn away the absolute majority of potential users. There needs to be at least a little bit centralization to form major default communities that at least start as a gathering hub for new people. If there’s issues with them then people can still create alternatives if the user numbers are high enough, but in its current form I’d have to decide between several places that are essentially the same thing.
But is it really a Problem exclusive to the fediverse? there is several large news communities on reddit as well, and you have to pick or see duplicates. Also, this is only an issue in heavily aggregation-focused communities, not in those where content is generated (memes, hobby communities) as those do not have the issue of duplicates so you can just sub to all the ones you are interested in, even if several of them have the same subject.
Theres nothing stopping the client from offering a different or entirely customizable view to the content.
For example the client could allow user to place those communities under a common News category in their client. Then the client would combine all identical links in the category according to some criteria (e.g same link posted in the same day would count as identical) and either merge the comments or let the user pick which communitys comments to see, or preferably both. So comments section could have a buttons for “Comments at news@beehaw.org”, “Combine comments” etc.
I think it should be possible to build a client that hides most of the details about different instances and such so it would function almost the same as traditional RSS readers.
You can subscribe to both! Reddit has multiple subreddits per topic too.
My first kbin ELI5!
It seems that if kbin federates a post that doesn’t have a link or image and just points to itself, it fills in (kbin.social) as the link pointer, when you view it on kbin. It’s a bit confusing at first, should probably be replaced by something that indicates it’s a federated “self”-post.
This is a post to linux community (@linux@lemmy.ml) by user falcoignis (@falcoignis@reddthat.com). You’re reading it on kbin since it has federated this post. The default “front page” shows federated feed (Threads).
Oh of course that all makes perfect sense now….
OP is on reddthat (@falcoignis@reddthat.com), which is a Lemmy instance, and the community this post is on is !linux@lemmy.ml. Not sure what’s up with kbin appearing next to OP’s name for you, might be incidental because of kbin’s UI or something.
Edit: just looked on kbin for myself, no idea what is up with that honestly, but I see what you’re talking about as well.