Instances that defederate with threads wont see content from threads even on other instances that may federate with them.
As an example here lemmy.ml federates with hexbear and world but hexbear and world dont federate with each other. On lemmy.ml threads world users cant see any comments made from people on hexbear and vice versa
A post in the view of .world: lemmy.world/post/9466410 (282 comments) The same post in the view of hexbear: hexbear.net/post/1304992 (76 comments) The same post in the view of lemmy.ml: lemmy.ml/post/9207671 (306 comments)
So they wont have to deal with them indirectly
pinkdrunkenelephants@lemmy.world 1 year ago
The fact that this guy’s only rebuttal is “well, just go to tankie instances” is all you need to know.
mac@programming.dev 1 year ago
Didnt say to go anywhere, just said that people on .world cant see content from hexbear on lemmy.ml posts even though it federates with hexbear shown by those comment counts above. (hexbear used since its the best example of a large blocked instance that can showcase this well)
Same logic would apply to .world federating with threads. People on lemmy.dbzer0 for example wont see content from threads on .world even if .world federates with threads
Just wanted to put a counterpoint to you saying people would need to deal with it indirectly in this paragraph below which isnt true proven by the above. You dont need to strawman it by making it a different point
pinkdrunkenelephants@lemmy.world 1 year ago
Denial ain’t just a river in Egypt.
Since you’re obviously one of the shills arguing in bad faith about it, know that you can’t manipulate everyone into accepting corporate fists up their assholes. We will stop you one way or another.