I think this will have the opposite effect. Account portability means that being banned on one site can ban you on another if you try to use the same ID. Being persistently recognized across accounts seems like a net-negative for all of these things.
I imagined trying to explain to my mom why she'd have to signup for Mastadon again because the server she signed up with is gone or she got on one of the massive blacklists for engaging with the 'wrong' accounts.
Not to be overly cynical, but I just don't care. Things change. When mega-corps and investors come knocking with 10-figure checks... 99.9% of humans will cash out. It's human nature. I've invested my time and energy in many things that have been taken over and destroyed by bad/incompetent actors, virtually all of which had promising starts, or I wouldn't have gotten involved.
Page and Brin explicitly spelled out how advertising could change the incentives of a search engine. That didn't stop them from selling out immediately and letting the VCs install a CEO to 'businessify' the company.
I can’t predict the future. We may screw it up. I’m trying to protect the community from us if we do.
As for why people might want to use it instead of ActivityPub, I think it's just... different from ActivityPub. Even though ActivityPub is an available option I don't see why it should be the last word.
Bluesky's answer is this
> Account portability is the major reason why we chose to build a separate protocol. We consider portability to be crucial because it protects users from sudden bans, server shutdowns, and policy disagreements. Our solution for portability requires both signed data repositories and DIDs, neither of which are easy to retrofit into ActivityPub. The migration tools for ActivityPub are comparatively limited; they require the original server to provide a redirect and cannot migrate the user's previous data.
> Other smaller differences include: a different viewpoint about how schemas should be handled, a preference for domain usernames over AP’s double-@ email usernames, and the goal of having large scale search and discovery (rather than the hashtag style of discovery that ActivityPub favors).
https://atproto.com/guides/faq#why-not-use-activitypub