@andrew I agree, the tension is inevitable; think of it as the force that drives innovation.
Some of your points are about reputation… something the user doesn’t create, but rather it is bestowed by a community based on consistent behavior.
In many ways this is like the difference between my driving record and my name. I can change my name, but I can’t erase my driving record. So, the question for a reputation system isn’t about whether or not I can change my name. It’s about what are the appropriate and desired functions of community bestowed reputation? Should it be transferable to a new name?
I like to think of “Identity” as the set of identifiers we use to refer to people online. I wrote about that here, where I talk about four different kinds of identifiers used in online systems:authentication IDs, presentation IDs, reference IDs, and internal IDs. With that model, the question becomes what identifier does reputation adhere to? You could have a viable system with reputation adhered to the presentation ID, the reference ID, or to the internal ID. The latter would allow a user to use the same reputation with multiple handles (or names). Which is correct is a community defining choice.
So, I think you are grappling with the right issues. Every community has to set a framework for users to engage each other. As for whose responsibility it is: I suggest a two step best practice:
1. The system should do the right thing automatically, by default
2. Users should be able to override the default behavior without too much frustration
Your challenge is defining “the right thing” for the defaults. Do it well, and the system grows. Do it poorly and you alienate one group or another.
Jeff Jarvis, in What would Google Do talks about “Public by Default” and how powerful that is. I agree, while at the same time I think it is paramount to have deep support for privacy and for it to be easy to be private. I think Twitter is a good example of a simple and mostly acceptable way to do that. Tweets are public by default, but you can go private and you can block individuals, on top of the fundamental private/public mix of your “following” stream and search of the public stream.
Chris Anderson, who is about to release FREE talked at SXSW about building businesses that monetize just 5% of a large audience who participate in a free service. I think those same numbers apply here. If you build the community right, 95% of the folks are going to participate by the default rules that your community needs to work: public conversations, sustainable reputation, etc. Another 5% are going to be different. They’ll want to delete or opt-out or otherwise exert more control that normal. I think that’s ok. And it is probably sustainable. The community doesn’t need EVERYONE to contribute to the public discourse in an indelible permanent way. It just needs enough people to contribute consistently enough for people’s questions to be reliably answered. (And, no, I’m not suggesting you charge for that privilege, I was just highlighting that systems can be designed to support bi-modal populations.)
In any case, I like the way you guys have engaged on this question. I wish you luck figuring it out, and with the venture. =)
@johnpowell BTW, I think you could still sell your script idea. It’s just that Fluther could as well. It might be nice to limit the scope of the license in the TOS, but even as it is, their license to do anything with the content doesn’t prevent you from doing whatever you want to do. (Although you could get into a mess if you sell an exclusive right to someone and then Fluther does the same. If you think about the TwitPic of the plane crash in the Hudson, that scenario isn’t too far fetched.)
@ragingloli Actually, if you are using Fluther in Germany, Fluther is subject to German law. They may not yet be large enough for anyone to pay attention, but they are subject to the same laws, at least for their German users. Just ask eBay about international jurisdiction.