@lauti@bonfire.cafe Yes, but.
I did this and I found that some remote servers don't set the Accept header correctly when fetching the server actor. They get tangled up in the content negotiation.
I eventually made the server actor use the same routes as the other actors on the server, except with the domain name as its preferredUsername. This seems to work really well, especially with default Webfinger lookup.
@evan@activitypub.space Interesting! Do you rememeber with which software had troubles?
Regarding preferredUsername did you configure it so that you could search for @instance?