I’m not aware how fediverse works, can someone explain why when I look at the same post through lemm.ee instance and through hexbear instance they have different amount of comments? There are some overlapping comments, but those ones have different amount of likes and dislikes. I’m a bit confused
Some servers choose not to connect with each other.
Those servers have users and since they choose not to connect, there will be disparity.
Let’s say I’m on server ‘a’ and you are on server ‘b’ and this post is on server ‘c’
In this example, we can say that a and b connect with c, but a and b don’t connect with each other.
We would both independently see the post on server c, and we could both leave a comment. But since a and b don’t connect, we wouldn’t be able to see each other’s comments. The people on server c would be able to see both of our comments though.
This connection is called federation and it allows individual servers to control who they interact with.
Lemmy is just a piece of software, the people running the software on their servers control who they connect with. you could for example have multiple federations that comprise tons of servers that have no direct connection at all, resulting in two totally different networks.
@ma1w4re It’s because it works similar to email. When someone posts, it sends out copies of the message to all of the followers. But some don’t arrive, or some people have blocks in place, or something is not configured right. As a result, not all servers get the complete conversation.
But some people are working to fix that so that all of the servers that support threaded conversations can download the complete conversation.
I’m not aware how fediverse works, can someone explain why when I look at the same post through lemm.ee instance and through hexbear instance they have different amount of comments? There are some overlapping comments, but those ones have different amount of likes and dislikes. I’m a bit confused
Hexbear has been defederated by a number of instances and this will cause such a disparity.
I see, thanks
Hexbear lmao
Some servers choose not to connect with each other.
Those servers have users and since they choose not to connect, there will be disparity.
Let’s say I’m on server ‘a’ and you are on server ‘b’ and this post is on server ‘c’
In this example, we can say that a and b connect with c, but a and b don’t connect with each other.
We would both independently see the post on server c, and we could both leave a comment. But since a and b don’t connect, we wouldn’t be able to see each other’s comments. The people on server c would be able to see both of our comments though.
This connection is called federation and it allows individual servers to control who they interact with.
Lemmy is just a piece of software, the people running the software on their servers control who they connect with. you could for example have multiple federations that comprise tons of servers that have no direct connection at all, resulting in two totally different networks.
I see, thanks
@ma1w4re It’s because it works similar to email. When someone posts, it sends out copies of the message to all of the followers. But some don’t arrive, or some people have blocks in place, or something is not configured right. As a result, not all servers get the complete conversation.
But some people are working to fix that so that all of the servers that support threaded conversations can download the complete conversation.
I see, interesting. Thank you
Different defeserated instances, problems with content being federated due to network latency. There are a bunch of possible reasons.
Can you give an example of such post?
Recent post about Linus on Linux@lemmy.ml, if I typed the instance right
!linux@lemmy.ml