Federation is a two-way connection. Beehaw shut off the incoming stream, essentially, so anyone commenting or posting on spaces from that instance will not be seen by users logged into Beehaw. However, the outgoing stream is still active so anything posted there that you subscribe to or visit from another instance can still be seen. Users on other instances can even comment in those threads, but users on Beehaw would not see those comments.
For me it helps to think of the instance you are logged into as the place you trust the most. Content from other sources can always come in, but you can choose to simply not see things you don’t want. This is a fundamental part of how the Fediverse works, for better or worse.
Yeah, but small correction: Beehaw only defederated from two specific instances of Lemmy, not the entire system. If you were engaging with a Beehaw community from lemmy.one or other instances that Beehaw is still federated with, everyone sees everything on both sides.
Also, if the Beehaw user really wanted to engage with the lemmy.world or other defederated instances, nothing is stopping them form creating an account on that instance (or any other instance federated with the desired community) and commenting or posting from there.
The user need to be conscient of that. Otherwise its really unfair.
If he doesn’t know the server he choose did that, he will be restrain without being aware of this.
And in an other hand, if I have to check why someone don’t respond to me (example), to be sure where this someone is, is federated, that would be really painful and discouraging. That can lead to a lot of misunderstood too.
Cooool, I was wondering this. I had been curious if it was 1 party or 2 party federation; so someone can defederate, but it doesn’t “block” receipt of content, only the interaction with the blocked platform?
Federation is a two-way connection. Beehaw shut off the incoming stream, essentially, so anyone commenting or posting on spaces from that instance will not be seen by users logged into Beehaw. However, the outgoing stream is still active so anything posted there that you subscribe to or visit from another instance can still be seen. Users on other instances can even comment in those threads, but users on Beehaw would not see those comments.
For me it helps to think of the instance you are logged into as the place you trust the most. Content from other sources can always come in, but you can choose to simply not see things you don’t want. This is a fundamental part of how the Fediverse works, for better or worse.
That’s interesting. What happens if a lemmy user replies to a beehaw user’s comment from a lemmy instance? Does the beehaw user just never see it?
Yeah, but small correction: Beehaw only defederated from two specific instances of Lemmy, not the entire system. If you were engaging with a Beehaw community from lemmy.one or other instances that Beehaw is still federated with, everyone sees everything on both sides.
Also, if the Beehaw user really wanted to engage with the lemmy.world or other defederated instances, nothing is stopping them form creating an account on that instance (or any other instance federated with the desired community) and commenting or posting from there.
The user need to be conscient of that. Otherwise its really unfair. If he doesn’t know the server he choose did that, he will be restrain without being aware of this.
And in an other hand, if I have to check why someone don’t respond to me (example), to be sure where this someone is, is federated, that would be really painful and discouraging. That can lead to a lot of misunderstood too.
Cooool, I was wondering this. I had been curious if it was 1 party or 2 party federation; so someone can defederate, but it doesn’t “block” receipt of content, only the interaction with the blocked platform?
I believe that instances can independently choose whether to accept incoming or allow outgoing data, so there are multiple possible combinations.
Makes sense! Thanks!