@leonp check out my site, starrwulfe.xyz for an example of BridgyFed Site-As-Mastodon instance integration.
I can walk you through it; took only 15 minutes and is one extra step needed if you’ve already done the “regular” Bridgy set up for syndication.
@leonp in my case I effectively get two ActivityPub accounts when counting micro.blog as well…and you can still have the “traditional” post to third party Mastodon site, meaning 3 ways to blog into the Fediverse.
My main reasoning for site as account is
– being able to centralize all conversation around content from the site.
– no limits to how long my post will be; if I post as a note, I can go as long as I like.
– no worries about site load, caching, etc since it’s effectively a one user instance and “heavy” media is on CDN.
– it’s cool to have my site be the “@“ name when giving out my Mastodon address. 😝
The drawbacks:
– no DMs. Maybe @snarfed is working on a way to handle that, but my method is to use my micro.blog handle for that since @manton came up with a good solution for it (you did know micro.blog handles are also AP enabled, right?)
– federation is “wobbly”; some instances won’t see your posts until one of their users threads caches it in; I wind up boosting my own posts from other instances to get around it. It’s not a problem as much as it used to be since there’s a lot of us using BridgyFed now.
@leonp that’s what I like about indieweb— one size doesn’t fit all, and you can do it however you like!
I say set it up the way you like and you can change and adjust it on the fly