local bios get corrupted when resolving a profile or status URI

[nightpool]

If you use the "search" feature to resolve a local URI (such as https://cybre.space/@nightpool/58041) it automatically fetches the bio from retrieved atom representation and updates the local user model accordingly.

however, the bios returned via atom are HTML-formatted, while local users do not have html formatted bios, only plain-text formatted ones. This ambiguity in storage formats leads to the bios being corrupted with escaped versions of the html formatting. In extreme cases, they can get corrupted multiple times, as seen below:

(s/o to @0x1f415@mastodon.social for the screenshot)

the correct resolution here is one or both of:

• don't resolve local URI searches using a http request—just return the correct information automatically

• store both local and remote bios in the database as the same format, to avoid the whole class of bugs where we forget to treat local and remote bios differently

[nightpool]

@Gargron were you going to take this and work on it? I got that impression from the convo we had, but if no-one is working on this I might be able to poke at it a little