

3·
3 hours agoIMO bridgy is not well designed. The fact that it requires both the follower and the followee to specifically opt in basically makes it DOA. Both Mastodon and BlueSky are completely open and public in terms of post visibility, so bridgy should have been designed to require explicit opt outs from anyone who didn’t want their content bridged.
LW definitely can’t handle more traffic than it already has. It already (thanks to the admins’ refusal to update to the latest version of Lemmy, which fixes this issue) takes multiple days for LW content to get federated to other instances properly, which is why I’ve had to switch over to this alt account of mine because there are zero comments on this post in my main instance. With more users, that delay would grow from days to potentially weeks.