I think I would prefer this to be done when extracting the data rather than on display time, mostly for consistency across the various clients.

Would there be any downsides to doing it this way?

@renchap I don't think there is a downside to doing it that way, as long as the record doesn't need to be a faithful recreation of the original content. I can't think of a scenario where you would do anything with that retained whitespace (other than trim it off). Plus then the instance doesn't have to carry around those extra bytes.

If there are no objections I'll update this and instead make the change in the extraction code.

I've reverted the change to how card renders and instead trimmed the offending whitespace when link_details_extractor first fetches the title. The only downside to this is that previously fetched link titles will still have any extraneous whitespace, but given this only happens when a site has a weirdly formatted <title> tag I can't imagine that is super prevalent.