@julian IMO there's no reason why a web browser should understand where to open fedi links, without having any other type of app properly address those links as well.

What if someone in an instant messenger or email app sends you a link to fedi content?

Defining it at the system level (again, as is done with email) removes critical uncertainties.

Fedi has other big UX issues as well. Celebrities don't like it here because the TL mechanics make them unintentionally annoying... users follow then later mute them because their posts are popular for a while and we have to see them each and every time they're boosted (or manually silence those posts). Allowing the selection of some transparent algorithms could fix this.

@julian @fediversereport AP is an ugly duckling.

Maybe it shouldn't be a Web standard, but sit apart from (and inter-operate with) it instead. Maybe the right org is the IETF...

@fediversereport If they are smart they will fix a raft of fundamental UX pitfalls in current ActivityPub by defining a protocol handler for it.

Email needed its protocol handler spec while it was getting established – and arguably still does – and I do think this is one of the ways in which ActivityPub is "like email".