The Danger of POSSE
A recently published article on The Verge discusses POSSE and the Fediverse: “Publish (on your) Own Site, Syndicate Elsewhere.” This content strategy emphasizes the importance of owning the content you create by publishing it on your own platform, like a personal blog or website, and then syndicating or sharing that content on other platforms, such as social media or content aggregators.
The main idea behind POSSE is to ensure that creators maintain control over their content. By publishing first on their own platform, creators can establish a primary source for their work that remains under their control. They can then share or syndicate this content to other platforms to reach a wider audience, drive traffic back to their own site, and engage with communities on those platforms.
This strategy is particularly relevant in the digital age, where content creators often face the dilemma of reaching large audiences on popular platforms (like social media networks) while also wanting to maintain ownership and control over their work. POSSE offers a balanced approach, allowing creators to leverage larger platforms’ reach without sacrificing their own site’s autonomy.
I’m practicing POSSE myself; all my online setup is built around it. I depend on two publishing poles: Micro.blog and Ghost
-
Micro.blog is responsible for the cross-posting magic. ↩︎

I tried a POSSE approach for my digital identity but I don’t think I made it right. I decided that I would create everything in my micro.blog histed blog, then create an ActivityPub user and migrate my Mastodon accounts to that AT user. it was cool to have all the comments and replies from Mastodon show in my micro.blog timeline and in my site, but then I realized that I lacked a proper Mastodon account and user and many of its features when interacting with Mastodon users. So I’ve gone back to my traditional setup. I use Mastodon for tweet-like short content and my blog for short and long form posts.

@eumrz you can enable a Mastodon-compatible username in Micro.blog, did you know?

Yes, that's what I meant, sorry for my poor English. I enabled that Mastodon-compatible username in Micro.blog and migrated my two Mastodon accounts (and their followers) to that username. At first it seemed like a good idea (all my Mastodon followings appeared in my Micro.blog timeline and their responses showed in my blog too) but soon I realized that not having a proper Mastodon account is not convenient at all.