Gregory's Server@Mastodon Migration wrote:
I suppose this is what most Mastodon users expect, but I think it's backwards. Formatting for the Fediverse does not mean (and should not mean) formatting to match the artificial limitations imposed by Mastodon.
The Fediverse has supported blog-style posts, with text formatting, inline images, and no character limit, since before Mastodon was invented. WordPress + ActivityPub means that Mastodon users will be seeing increasing numbers of such posts. And yes, this means they will need to click the link and go read the original post -- or switch from Mastodon to a different Fediverse platform that supports blog-style formatting.
What should NOT happen is that a WordPress blog must become "not a WordPress blog" in order to be accepted in the Fediverse.
> "...From experience, the posts generated for Mastodon need to be formatted with the idea that it is being sent to the Fediverse. Images are avoided because only want the primary image to show up, need to repeat the title or it doesn't show up. Limit character formatting etc. Really using it as a Fediverse long form posting tool, not a Wordpress blog..."
I suppose this is what most Mastodon users expect, but I think it's backwards. Formatting for the Fediverse does not mean (and should not mean) formatting to match the artificial limitations imposed by Mastodon.
The Fediverse has supported blog-style posts, with text formatting, inline images, and no character limit, since before Mastodon was invented. WordPress + ActivityPub means that Mastodon users will be seeing increasing numbers of such posts. And yes, this means they will need to click the link and go read the original post -- or switch from Mastodon to a different Fediverse platform that supports blog-style formatting.
What should NOT happen is that a WordPress blog must become "not a WordPress blog" in order to be accepted in the Fediverse.