@
thisisacesAre bridged networks Fediverse too, or Fedi-extensions?
I guess you're only thinking of Bluesky and Nostr.
But technically speaking, both Hubzilla and (streams) are bridged to ActivityPub, too, because neither is based on ActivityPub. I'm replying to you via a bridge right now.
Granted, this bridge named Pubcrawl is an official Hubzilla add-on, it's installed on this hub, and each channel has actually got its own bridge. But it's a bridge.
So if the definition of the Fediverse excludes anything that's bridged in some way in an attempt to keep Bluesky and Nostr out, it also excludes these two, although Hubzilla is as old as the Fediverse itself. Not doing so would amount to a double standard.
The main difference between Bluesky and Nostr on the one hand and Hubzilla and (streams) on the other hand is: Bluesky and Nostr are connected through one third-party bridge each. Hubzilla and (streams) bring their own official bridges.
So one could argue that both
do have their own ActivityPub support. Not as their base protocol, through a bridge instead, but that bridge is an official add-on and therefore officially part of the project.
However, one could just as well argue that only Pubcrawl is part of the Fediverse because it "speaks" ActivityPub. The parts of Hubzilla and (streams)
beyond Pubcrawl, on Pubcrawl's "far" side, their cores included, are not part of the Fediverse because they're bridged, and they don't run natively on ActivityPub.
Thus, the Fediverse's outer border would cut through Hubzilla and (streams) with the ActivityPub bridge inside the Fediverse and the core and all the other add-ons outside.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Fediverse #
Bluesky #
BlueskyBridge #
Nostr #
Hubzilla #
Streams #
(streams) #
Pubcrawl
Stuart Bain 
