There are a number of traditional Facebook alternatives in the fediverse... if that's what you seek. Don't expect the same level of commercial focus as the Twitter alternatives. The Facebook-based platforms are usually more focused on online safety, family-friendly spaces, and identity management/resilience.

https://codeberg.org/streams/streams
https://framagit.com/hubzilla/core
https://github.com/friendica/friendica
https://github.com/grishka/smithereen
https://codeberg.org/fortified/forte

Events only:
https://github.com/framasoft/mobilizon

Now I'm waiting for the first second to set up Forte as a daily driver.

@Jupiter Rowland I guess we‘ll be able to ask @pascal for some testemonials on Forte after some time.

@Ema エマ DAFUG?!

This could be one of the Rules of the Fediverse: If it exists, someone daily-drives it.

I didn't know about Smithereen. It's a VK alternative created by a Russian guy. Interesting.

Not gonna lie, I'm considering moving from Streams to Forte. I just need to check how this can be done. Would be great if a simple Streams channel basic export was enough.

@Papa Dragon In fact, since (streams) understand nomadic identity via ActivityPub, maybe it also speaks it well enough to make a nomadic move from (streams) to Forte possible.

I may have missed an episode, but is Forte set to succeed Streams? And if so, what does it bring to the table?

I guess that cloning a Streams channel into a Forte channel is not the way it should be done. I may have missed it but I don't remember seeing a post describing how to move an identity from a plaform to another.

I may have missed it but I don't remember seeing a post describing how to move an identity from a plaform to another.

I think it was the case between Zap and Streams. I had imported my Zap identity into a new Streams account.

Forte does pretty much everything streams does, but it only supports the ActivityPub protocol.

There is no succession plan.

The export compatibility restriction is hopefully temporary. We'll see... Most of the compatibility issues have been addressed already, but this keeps random people from corrupting their instance database until the remaining inconsistencies are worked out.

The primary changes involve differences in the storage of private keys, and the fact that the primary channel identifier is now an ActivityPub portable id and not a Nomad portable id.

So all portable ids and private keys in the incoming data from streams will need to be converted prior to storage. There's also a sync issue - Forte only sends sync packets over ActivityPub and streams only sends sync packets over Nomad.

The receiving end has already been modified to work with either.  The sending side just needs to figure out which clones support Nomad and which do not - so that it will use the correct protocol to send the sync packets.

Once these things are finished, the compatibility restriction can be removed.