No, I was wanting to go the step further and target "offline first" to avoid the need for too many "always on" services. From a philosophical perspective, I think our internet should be able to function without the resources required to run something 24hrs/day.

You can absolutely build a LinkedIn clone on top of something like ActivityPub for example, but I'm not sure how one might do that from an "offline first" perspective though.

Edit: I just remembered my primary objection to this argument: most people aren't nerds. You can't have a properly distributed web if federating requires access to (a) an always on server, and (b) the skills to maintain it yourself. I'd argue that this is precisely why the fediverse is so dominated by Free software nerds like me. No, it has to be easy: install an app on my phone, start writing. Let the app figure out how to connect everything, and if I get on a boat/plane/train or my phone runs out of battery, connectivity should Just Work™. This is what I love about SSB: whatever we build on top of it, the protocol was already designed on this assumption.