Given the fact that the original comment from the kind @speck seems now fully satisfied, I think there are no problems to land this :) Thanks again to speck for that proposal ( https://we.phorge.it/D25022#768 ) - so, I flag that as "done" very boldly.

In D25022#24491, @Cigaryno wrote:

@speck if you think this thing works properly, you can either resign or click on Accept Revision, because when @valerio.bozzolan accepted the revision, it still appeared as Needs Revision.

@speck if you think this thing works properly, you can either resign or click on Accept Revision, because when @valerio.bozzolan accepted the revision, it still appeared as Needs Revision.

• Improved comment

(Premising that I'm affected by T15985 lol - unrelated)

@speck @valerio.bozzolan @bekay Would you like to review this revision?

I updated this revision so the title will only show the monogram if the user is logged in

• The title will only show the monogram when the post is public

Interesting. I see. Maybe expanding its controller that should be this one:

Note that at least for Phame, http://phorge.localhost/J1 seems to always redirect to http://phorge.localhost/phame/post/view/1/blogpost/ instead of keeping the monogram in the URI.
So the baseURI is already wrong (not being http://phorge.localhost/ only) before concatenating the $ref (monogram and anchor).
As an ugly workardound, could probably make "Quote Comment" work by calling getObjectNamePrefix() in PhamePostRemarkupRule and LegalpadDocumentRemarkupRule and then use them in a preg_match to remove the monogram from the $ref but function is protected and... still ugly.

I'm 99% sure that this only affects Phame and Legalpad. I tested in Audit, Maniphest, Paste, Pholio and Files without issues.