Lindsey
Well-known member
I know how a conventional wiki is intended to work. I just think in this context open edits are not the best approach. Just because it's called a wiki doesn't mean it has to conform to conventional wiki rules regarding content additions.
One example of where this could become a problem is people who disagree on repair methods. It happens on here all the time and often there is never a resolution where all people agree on a common method. Who's method gets to be the one posted if both people are deleting each others advice? Do both get posted?
I realize I'm bringing up a lot of negatives but it's inevitable that some of this stuff will come up eventually. On the whole I think it's awesome. The more information we have out there the better. I think pinrepair.com going down is going to inspire a lot of people to put together repair guides. That is a good thing.
I just registered and removed content with no email confirmation. Not that it really matters. Email confirmation doesn't ensure good information.
I'm hopeful about the good but realistic about the bad. Pinwiki.com could be taken down at any time but I get your point about the content. We could just copy it somewhere else in a matter of minutes. In that sense it's a better system.
Agreed.
At the end of the day I'm just giving my $.02. My only real point is that moderating the content prior to publishing feels like a lot less work than dealing with open edits. Sure, the work involved in moderating open edits is theoretically shared among everyone but that's not necessarily a good thing and I'm sure there will be no problem finding moderators for each section. This will have no effect on the "free" nature of the content because the license will still apply. The bulk of the content will be pretty straight forward. It's when you get into the finer details and more advanced stuff that there can be conflicting opinions which could cause issues.
EDIT: There is email confirmation but I was able to make edits before confirming. That might be a bug worth looking at.
One example of where this could become a problem is people who disagree on repair methods. It happens on here all the time and often there is never a resolution where all people agree on a common method. Who's method gets to be the one posted if both people are deleting each others advice? Do both get posted?
I realize I'm bringing up a lot of negatives but it's inevitable that some of this stuff will come up eventually. On the whole I think it's awesome. The more information we have out there the better. I think pinrepair.com going down is going to inspire a lot of people to put together repair guides. That is a good thing.
Pinwiki doesn't allow edits until someone is registered. And registration requires email confirmation.
I just registered and removed content with no email confirmation. Not that it really matters. Email confirmation doesn't ensure good information.
Everyone is worried about the bad when it comes to a Wiki. Well, we've also seen what happen with a single maintainer.
I'm hopeful about the good but realistic about the bad. Pinwiki.com could be taken down at any time but I get your point about the content. We could just copy it somewhere else in a matter of minutes. In that sense it's a better system.
Neither method is perfect.
Agreed.
At the end of the day I'm just giving my $.02. My only real point is that moderating the content prior to publishing feels like a lot less work than dealing with open edits. Sure, the work involved in moderating open edits is theoretically shared among everyone but that's not necessarily a good thing and I'm sure there will be no problem finding moderators for each section. This will have no effect on the "free" nature of the content because the license will still apply. The bulk of the content will be pretty straight forward. It's when you get into the finer details and more advanced stuff that there can be conflicting opinions which could cause issues.
EDIT: There is email confirmation but I was able to make edits before confirming. That might be a bug worth looking at.
Last edited: