Thanks for reporting this! Just landed the same fix for the Story view as well. The root cause was servers not specifying charset in their HTTP headers, which caused our fetcher to assume ISO-8859-1 instead of UTF-8. Now deployed. And I just verified all the stories are now fixed.
