tantekwell, from having seen both rude/argumentative/trolling comments others' personal sites (e.g. Eric Meyer), and having had to filter / block comments from negative / trolling folks on content I've sharecropped various places (e.g. Google+), I'm not sure I would want a comment system on my own site that allowed comments from people I don't know.
tanteksomehow it's more ok that on my posts on Google+ there are sometimes semi-crazy type folks who take extra energy to deal with (and eventually turn positive, or have to block)
aaronpklately my sites have been getting a lot of spam comments (pretty neutral text comments with a link to their site) that I'd really don't even want to deal with
aaronpkalso ironic is the fact that I've started to replace my comment forms with facebook comment boxes for two reasons: combating spam, and getting the publication to facebook feeds built in
tantekso I think you may be solving the problem from the wrong end, starting *too* open and trying to limit it, rather than starting with commenting on your site as a privilege that is earned
aaronpkI think I would be comfortable with any of my facebook or twitter friends commenting on my site. That's a whitelist, but unfortunately the list is not my own.
tantekhere's another thought experiment - if you could give people the ability to make "editorial" changes on your primary content, how would you decide who to give those abilities to?
aaronpkCurrently my main site (http://aaronparecki.com) is editable to anybody I follow on Twitter. Since it's a wiki and keeps good changelogs, I trust my friends to not make destructive edits.
aaronpkOpenID would be one way if it weren't so confusing to set up and very underutilized, but there's still the UI problem for me to add people's domains.
tanteki.e. no reason for me to sign-in with Twitter. I could sign-in with tantek.com and via RelMeAuth it would end up using my Twitter to auth me as tantek.com, which you would then also be able to check to see if you're following me.
tantekthat would be a nice incremental step towards an OpenID-like experience without having to first code up a UI for whitelisting people's domains - you could do that later
tantekpeople are used to a normal/plain [ Sign in ] button requiring a site-specific login, email etc. and that if they don't think they already have an account there, they don't bother clicking it.
tantekwhereas with a [ Sign in with Twitter ] button, they are already given an expectation that if they have a Twitter, they might be able to do something
aaronpkyes I think so. it's unique enough to cause people to consider what it is before turning it away assuming as username/password login, but generic enough that it doesn't brand itself horribly (like RelMeAuth or iAuth would do)
tantekok finally wrote up a better first cut at a short paragraph (and a few more) to link to for a brief hopefully user-friendly explanation of web sign-in
tantek well, from having seen both rude/argumentative/trolling comments others' personal sites (e.g. Eric Meyer), and having had to filter / block comments from negative / trolling folks on content I've sharecropped various places (e.g. Google+), I'm not sure I would want a comment system on my own site that allowed comments from people I don't know.
aaronpk Currently my main site (http://aaronparecki.com) is editable to anybody I follow on Twitter. Since it's a wiki and keeps good changelogs, I trust my friends to not make destructive edits.