Ok, this is a potential corner case but maybe still interesting.
Posts imported with rss-polling contain HTML code. If these posts are federated, most of the HTML code breaks and goes through as plain text.
In an ideal world, at least links would be translated. But if this is too much hassle, at the very least it would be good to scrap the HTML code, leaving the text.
A couple of screenshots to illustrate the problem:
Why are we federating posts imported via RSS? The use case is: we are a community of podcasts, we import new episodes via RSS for listeners to like and comment in one place, and we want to offer these podcasts a window to the Fediverse, where they might get more listeners, comments and likes – without adding more work on their busy plates.
Just for your context, when ActivityPub content is federated (from any platform) it is typically federated as HTML. We will alway federate Discourse posts as HTML by default.
What you probably want is a custom filter for ActivityPub content. We may add that at some point soonish, however this is a relatively specific use case, and it’s not at the top of the priority list.
@nightpool 님, 확인해 주셔서 감사합니다. 해당 계정을 팔로우하고 있기 때문에 Mastodon 타임라인에서 게시물을 볼 수 있지만, Discourse의 원본 게시물이 아닌 URL을 어떻게 얻어야 하는지 모르겠습니다. 원하시면 해당 액터를 팔로우하신 후, 테스트 목적으로 다른 게시물을 연동(federate)해 드리겠습니다.
