We have a couple of people, including myself, who are now syndicating their external blogs into the Christarchy! site, in a similar fashion to how Facebook allows you to import a blog feed as notes. Our syndication has many more features, though, and one of them could cause some confusion.
You will notice, when you set up your syndication, that under the author settings tab you can set it to create a new user for authors who are not already users. Apparently this still works even though I’ve theoretically disabled users’ ability to add new users to the site through their blogs. There doesn’t appear to be any way for me to keep this from happening, so I’m going to have to request that if you syndicate a blog into the site you set it so that all its posts, regardless of the original author, are credited to your username. If, as you have the option to do, you set it so the activity stream notification (e.g. “orpheus42 wrote a new blog post on Absolution Revolution: lorem ipsum etc. etc.”) links to the original post, instead of the Christarchy! blog to which you are importing the feed, then you will have nothing to worry about if your original blog has multiple authors because the author information will be available on the original site.
This should only affect users who import posts from blogs that have multiple authors. If you cannot figure out how to make this change to your settings let me know and I will walk you through it. If time goes on and this is not fixed, I’ll have go into your blog dashboard and do it myself.
Speaking of users, I think the spam prevention measures I have in place (captcha, email notification, etc.) do a pretty good job of keeping illegitimate users out, but I’ve still had to delete a couple of questionable users and “splogs” (spam blogs). I will be deleting any user who does not have all the profile fields required at registration filled out, as I can only assume these are not legitimate users. One shouldn’t be able to sign up without filling them out, so there must be some registration bug (probably similar to the above) I have not yet found. As always, if you see a problem or someone spams you please contact me.