@thenexusofprivacy@infosec.exchange
Agreed that both bridging and cross-posting are useful. In practice I think of it more as a continuum than a sharp distinction. Bridged conversations can be less fragmented, but what if Eve and/or Frank aren't bridged? And as @mackuba@martianbase.net was jsut discussing on Bluesky, client support is really needed to make bridging smooth as well ... a good example of @laurenshof@indieweb.social's point that "ferdation is in the client."
Of course there are similar dynamics with federation, once you take instance blocking and incompatible software into account. In fact when I was experimenting with Discord/Mastodon/NodeBB federation a couple of days ago I was thinking how similar it was to the lossiness of BridgyFed conversations.
I almost wonder if bridging isn't the general way of looking at it, with direct federation over a shared protocol as one special case, cross-posting (automatically, via cliants, or via the low-tech cut-and-paste method) as another, cross-protocol adapers like BridgyFed and Hubzilla as a third.
@quillmatiq@mastodon.social @anewsocial@mastodon.social @snarfed.org@fed.brid.gy
@jonny@neuromatch.social
@thenexusofprivacy@infosec.exchange @laurenshof@indieweb.social @quillmatiq@mastodon.social
Smart clients are how we p2p the fedi :)