It's not a feature yet for most users. As possibilities expand, the "ATmostphere" can be improved. Maybe in two years everyone wants to go to a new Personal Da

It's not a feature yet for most users. As possibilities expand, the "ATmostphere" can be improved. Maybe in two years everyone wants to go to a new Personal Data-Store that offers new features X or Y, or Bluesky is sucking because of Z... This architecture of making users sovereign is what's really at stake with the 'user = site' idea; the meaning of that is powerful & clear to techies for what it ongoingly unlocks & enables, but most users arent expected to share that technical fervor. It insures the ATmosphere doesn't get trapped or corralled into some local maxima, can't be enshittified since there isn't the same switching cost as all other networks. And it enables growth & extension of the ATmosphere, by allowing innovation at the edge. More generally, I'd argue that users don't have to be familiar with and attracted to features for them to be features. No one knows every function in their spreadsheet software and there's some they probably will never use, but the spreadsheet is known & respected because it has such a broad library of functions to enable so so much calculating, in so many different ways. Users can grow & change where they are in the adoption curve over time. Features evolve on healthy & fetile platforms. Giving users sovereignty & mobility enables new platform to be created off-Bluesky/main: it is a meta-feature to allow new features.