Reblogged by fromjason ("fromjason.xyz 🖤"):
There's an interesting discussion at the bottom of bridgy docs about how different social networks have different interaction details.
For instance, it would appear if you have follow requests enabled on mastodon if you're bridged... that's not supported yet so they just auto-accept all followers 🙃
Attachments:
- 8ea4645ec9cd8039.png (remote)
- How are activities routed? A bridge does more than just translate protocols and formats. It processes activities (events) based on domain-specific logic and semantics. The domain Bridgy Fed currently handles is public social microblogging, the kind popularized by Twitter. There are many other related social domains, with fuzzy boundaries and lots of overlap, eg forums (Reddit), questions and answers (StackOverflow), project trackers (GitHub), and many more, but here we're currently focused on microblogging. Even within that domain, behavior logic varies. Twitter follows are one way, but Facebook friends are bidirectional. Your Bluesky timeline (skyline) includes your followings' replies, but your fediverse timeline generally doesn't. LinkedIn...honestly I have no clue how LinkedIn works, but I'm sure it has its own logic, workfluencers and all. Here's what Bridgy Fed's activity router does. I've tried to make it follow "least common denominator" logic, ie do the most common and least surprising thing, and I've explicitly tried not to innovate or invent anything new here. It's a bridge, not a product, after all. (remote)