@utzer [Friendica] It’s the second time this month that people reports encoding issues with Friendica output. It should have been simple, Friendica always outputs UTF-8 text, even if it doesn’t say so explicitly. But some platforms defaults to ISO 8859-1, a remnant of a distant path, when they don’t get explicit encoding information.

It is starting to piss me off that we will have to ensure the encoding is set in all outgoing requests.

@utzer [Friendica] Here are my initial findings:

- social.yl.ms/objects/e18176ef-… doesn't show the encoding issue in the mention display name
- friendica.mrpetovan.com/displa… shows the encoding issue in the display name

However, I wasn't able to retrieve a source message for this post, so I don't know how it looked when it reached my node, but the mention shows OK:

@Michael Vogel @Hypolite Petovan maybe something todo with Diaspora... don't know.

I will see what happens in the future.

Here it happened again.
friendica.utzer.de/display/f4f…

Here is some test post which looks fine on both my servers and Mastodon.
social.yl.ms/display/e18176ef-…

@Hypolite Petovan and it happened again, would like to know if Rainer sees your post in the same way.

See his reply here: diasp.org/posts/e18176ef-2065-…