What does an ActivityPub client look like when the server does NOT support the proxyUrl endpoint?
Imagine having to visually parse a URL to guess who a post is from...
An inbox or home feed with some posts scrolling by, there are skeleton loaders where profile info would normally reside (avatar, display name, etc), instead of a webfinger style user id, the literal actor id url is displayed
