Yesterday I read the excellent article by Cory Doctorow: Let the Platforms Burn and this particular anecdote The thing is, network effects are a double-edged sword. People join a service to be with the people they care about. But when the people they care about start to leave, everyone rushes for the exits. Here’s danah [...]
(2/2)
Now lets look at Beehaw’s technology community from lemmy.world:
On the one hand, this is not blocking 100% of the content from this community, which seems consistent with what I originally thought. Lemmy.world is not defederated with beehaw, so lemmy.world can see new content from Beehaw’s communities.
But on the other hand, there is a ton of content missing. And it’s not just federated content taking awhile to move from instance to instance, as I’m seeing posts from the last 24 hrs from Kbin that are not showing up on lemmy.world. So it appears that there is content that’s being blocked from getting to lemmy.world. But it’s not 100% of the content that’s being blocked?
To make matters more confusing, I can see content published by Beehaw users on a Beehaw community from lemmy.world. Wtf is going on.
I appreciate the effort and have also verified your analysis myself to be true. However, and I don’t know if it’s just me, but I don’t see any images attached to your comments.
Thanks for calling that out. It looks like attaching images directly to a comment only works for kbin instances. This is what it looks like from kbin.social. I just tried viewing this thread from lemmy.world and the images were not showing up.
To be honest, I don’t want to go through the effort of editing my comments to correct it right now. But in the future I’ll go back to hosting images and linking them in my comments, so anyone from any instance can see them. That’s a shame, because attaching images to comments in Kbin is super convenient. Oh well! Thanks again for letting me know.