My current boilerplate on the issue:
The entire #Bluesky <--> #Fediverse #Bridge issue can be distilled down to:
1) Bryan writes a Bluesky <--> Fediverse bridge application
2) Bryan has total administrative control over said bridge application
3) Bryan effectively has a man-in-the-middle viewport into all bi-directional traffic through his bridge - don't try to claim this isn't true
4) What does Bryan do with the participant IDs and traffic content he can view?
5) Is there any notice or consent involved other than opt-in re: Bryan's monitoring and potentially using said bridge traffic?
6) Is there any option to opt-out for --> third parties <-- who are participating in a public Mastodon conversation *they* believe is on one end only and do not want to be bridged over to the opposite side of Bryan's bridge?
This has boiled over on the Bluesky #Github (where it's the most recent post in a *very* long thread):
"Interoperability with Mastodon/ActivityPub #1716"
Here: https://github.com/bluesky-social/atproto/discussions/1716