But open sourcing alone does create a hierarchy with the programmers having the final say. And I think would scare off the less technical folk. Certainly most of my non-online friends would be pretty unfamiliar how it all worked and not necessarily interested in learning about it. They’d care about writing and chatting far more than how it all happened. I enjoy technical discussions that I understand 10% of, but I’m pretty sure I’m an outlier. Offline, I’m the indecipherable tech geek because I simply know what github is. Or the idea of version control itself. And most find it pretty boring/mystifying at the end of the day. They’d rather talk about music or sexism or urban walks or other such things.
I think the basic questions need to come first: What is our community? How do we want to organize? What atmosphere do we want to foster? Do we want a single community or multiple? Once a group grows too far past Dunbar’s Number, cohesiveness becomes difficult.
And a big one: what does @manton want? He is the owner of the software and servers after all.
Also, isn’t everything built on open standards under the hood? How hard would it be to set up a “Nano.blog” which accepted the json/rss feeds and created a timeline of its own? I think that was part of Manton’s idea: if a group didn’t like his place, they could start up their own. But again, I’m trying to recall CoreInt episodes from long ago.