Believe it or not, a lot of driving takes place in heavily driven territory :)
And I'm sure the autonomous vehicle will have a go-very-slowly mode for navigating people's driveways and similar places the mapping cars haven't been yet.
The world is pretty well mapped at this point I don't think this will be a showstopper.
And the nice thing about driver less cars is that they can drive wherever and whenever pretty cheaply. There's no driver to pay. Just the electricity bill for charging the vehicle and some servicing/vehicle depreciation and other fixed cost. That's a race to the bottom in terms of cost.
There's no good economical reason to limit this to just small areas. You might charge passengers a bit extra if they are further out or even for the distance the car has to drive to pick them up. But there's no good reason for that to be very expensive as it would be with a paid driver.
Mastodon seems to be the most versatile app of all of them.
With Mastodon account you can follow people from BlueSky (if they use BridgyFed) and people from Threads (if they turn on fediverse sharing).
Using Mastodon you can follow people from Bluesky and Threads if they only turn on sharing or use Bridgy Fed option as well. Mastodon is the most versatile piece of software.
Neat thing about BlueSky using DNS TXT record is I don't actually have to host a landing page. The way mastodon does it feels like a quid pro quo way of making you put a mastodon icon on your website. Bluesky is really good for corporate and government users who can get an @name.whitehouse.gov account or @name.npr.org etc without polluting the npr.org markup with a thousand "rel" links for each of their employees. I think bluesky is thinking about a different audience than mastodon.
Also I took a look at https://mastodonapp.uk/@stephenfry as an example of a verified profile and the UX is quite bad. Green check in a green box with a green border. The title tag just says "Website" and there's no indication of what it means.
I could run a Mastadon instance for bradgessler.com, but I have no desire to spend even 3 minutes figuring out how to set all that up. Maintaining my own instance sounds even worse.
Bluesky gets the ergonomics of this right: the usernames feel like they occupy a global namespace and I can point the aliases at my domains in a few minutes without having to worry about a bunch of standards that I don’t really care about.
For some reason I can’t explain, it also really bothers me that I have to @ people on Mastadon via @[email protected]. I don’t want to say “@“ twice if I’m verbally telling somebody where to find me when presenting and “@me@bradgessler” is weird too. Much easier to say “Follow me @bradgessler.com”
Am I lazy? Yes, but most people are. Bluesky strikes a nice balance of control and identity that I’m comfortable with for the amount of time and effort I’m willing to put into it.
Maybe think about people who (deliberately or not) have neither chosen their domain(s) to read like their real name or online handle. I agree that yours kinda works, but I wouldn't want to be addressed by @<any of my domains>, that's why I use a handle (and have not chosen a matching domain since 1999 or so). And yes, I know you don't have to go that route, and I actually like that it works, I'm just saying it's not a universally good feature. It can be pretty useless.
