<HTML>
<style> BODY { font-family:Arial, Helvetica, sans-serif;font-size:12px; }</style>I'd rather stay open to pranks and malice than implement something counter to our values. It's not like a plane will explode if we don't IR scan everyone who edits our wiki. But as you said, we have a right to insist that a person reserving "significant resources" leave some contact info. All that remains is to define "significant resources" and "contact information". <br>
--D<br>
<br>
<br>
<span style="font-weight: bold;">On Sun 24/01/10 8:48 AM , "jim" jim@well.com sent:<br>
</span><blockquote style="border-left: 2px solid rgb(245, 245, 245); margin-left: 5px; margin-right: 0px; padding-left: 5px; padding-right: 0px;"><br>
<br>
i think your note below is right on. to claim <br>
resources, all that's needed for sure is some <br>
means of communication with the prospective claimer. <br>
i don't see a need for validating the actual <br>
identity of the claimer. <br>
<br>
i like the idea that claims on resources would <br>
involve a member (not to say non-members should <br>
not be able to use resources ad hoc, and "resources" <br>
to me means things that are significant, such as <br>
classroom space, electrical power costs, quality <br>
of air, use of community effort...). <br>
<br>
<br>
<br>
On Sat, 2010-01-23 at 23:00 -0800, Ian Atha wrote:<br>
<span style="color: rgb(102, 102, 102);">> We could have an optional organiser field for each event created.</span><br>
<span style="color: rgb(102, 102, 102);">> During a meeting two weeks ago, someone mentioned that "it's nice to</span><br>
<span style="color: rgb(102, 102, 102);">> have events sponsored by a member". Anything other than that is</span><br>
<span style="color: rgb(102, 102, 102);">> impossible, or we would be fooling ourselves, given our current</span><br>
<span style="color: rgb(102, 102, 102);">> infrastructure.</span><br>
<span style="color: rgb(102, 102, 102);">> </span><br>
<span style="color: rgb(102, 102, 102);">> That's to say, I have no clue who "Ever Falling" is, if they are a</span><br>
<span style="color: rgb(102, 102, 102);">> member, or if they are to be trusted. I have no way of actually</span><br>
<span style="color: rgb(102, 102, 102);">> associating that guy who introduced himself as "Leif" to me with</span><br>
<span style="color: rgb(102, 102, 102);">> "<a href="javascript:top.opencompose('leif@synthesize.us','','','')">leif@synthesize.us</a>", other than good faith. I have no problem</span><br>
<span style="color: rgb(102, 102, 102);">> extending that good faith to people editing the wiki putting a "name"</span><br>
<span style="color: rgb(102, 102, 102);">> (or a moniker, or whatever).</span><br>
<span style="color: rgb(102, 102, 102);">> </span><br>
<span style="color: rgb(102, 102, 102);">> If someone really wants authentication and authorization for reserving</span><br>
<span style="color: rgb(102, 102, 102);">> resources, I would really like to hear a full-fledged proposal. How do</span><br>
<span style="color: rgb(102, 102, 102);">> we associate monikers with faces? How do we associate monikers with</span><br>
<span style="color: rgb(102, 102, 102);">> usernames? Who validates that? Who says "thatha" is a trusted person,</span><br>
<span style="color: rgb(102, 102, 102);">> but not "anonymous_user_1234"?</span><br>
<span style="color: rgb(102, 102, 102);">> </span><br>
<span style="color: rgb(102, 102, 102);">> On Sat, Jan 23, 2010 at 20:59, jim <<a href="javascript:top.opencompose('jim@well.com','','','')">jim@well.com</a>> wrote:</span><br>
<span style="color: rgb(102, 102, 102);">> ></span><br>
<span style="color: rgb(102, 102, 102);">> > makes sense.</span><br>
<span style="color: rgb(102, 102, 102);">> > i wasn't worried about spam-like robots, mainly</span><br>
<span style="color: rgb(102, 102, 102);">> > some way to manage contention for resources, also</span><br>
<span style="color: rgb(102, 102, 102);">> > to minimize pranks and malice.</span><br>
<span style="color: rgb(102, 102, 102);">> > non-logged in edits seem fine, but people so</span><br>
<span style="color: rgb(102, 102, 102);">> > doing and who want to claim a resource should</span><br>
<span style="color: rgb(102, 102, 102);">> > identify themselves somehow or another, it seems</span><br>
<span style="color: rgb(102, 102, 102);">> > to me.</span><br>
<span style="color: rgb(102, 102, 102);">> ></span><br>
<span style="color: rgb(102, 102, 102);">> ></span><br>
<span style="color: rgb(102, 102, 102);">> ></span><br>
<span style="color: rgb(102, 102, 102);">> > On Sat, 2010-01-23 at 18:35 -0800, Leif Ryge wrote:</span><br>
<span style="color: rgb(102, 102, 102);">> >> So-called "anonymous" edits on mediawiki are really a misnomer - it is more accurate to describe them as non-logged-in edits, since they are actually attributed to an IP address which is potentially much less anonymous than logging in with a pseudonym.</span><br>
<span style="color: rgb(102, 102, 102);">> >></span><br>
<span style="color: rgb(102, 102, 102);">> >> The reason to allow them is convenience and the increased participationn that results from that. People are much more likely to edit the wiki if there are no barriers to doing so, and the small hassle of picking a name and password is a significant barrier. On the other hand, requiring login to edit achieves absolutely nothing, unless you also restrict account creation (which would obviously be a much bigger barrier and reduce the use(fulness) of the wiki). I'm an admin on a couple of wikis which do require a login to edit, and let me tell you: spam robots figured out how to create mediawiki accounts a *long* time ago.</span><br>
<span style="color: rgb(102, 102, 102);">> >></span><br>
<span style="color: rgb(102, 102, 102);">> >> So, I think we should continue to allow non-logged-in edits on the wiki, and by extension the calendar, so that forgetting one's password (or not wanting to create yet another) is no excuse for not putting something on it.</span><br>
<span style="color: rgb(102, 102, 102);">> >></span><br>
<span style="color: rgb(102, 102, 102);">> >> ~leif</span><br>
<span style="color: rgb(102, 102, 102);">> >></span><br>
<span style="color: rgb(102, 102, 102);">> >> p.s.: notes from Ian and me meeting today are at <a target="_blank" href="parse.php?redirect=https://www.noisebridge.net/wiki/NoiseCal"><span style="color: red;">https://www.noisebridge.net/wiki/NoiseCal</span></a></span><br>
<span style="color: rgb(102, 102, 102);">> >></span><br>
<span style="color: rgb(102, 102, 102);">> >> ----- Original message -----</span><br>
<span style="color: rgb(102, 102, 102);">> >> ></span><br>
<span style="color: rgb(102, 102, 102);">> >> > oh, i don't get why anonymous edits:</span><br>
<span style="color: rgb(102, 102, 102);">> >> > anonymity seems antithetical to accountabilty, and</span><br>
<span style="color: rgb(102, 102, 102);">> >> > it seems to me things that our community depends on</span><br>
<span style="color: rgb(102, 102, 102);">> >> > ought to have some accountability track: who's claiming</span><br>
<span style="color: rgb(102, 102, 102);">> >> > what resources and why. requiring a name also reduces</span><br>
<span style="color: rgb(102, 102, 102);">> >> > the vulnerability to malice and pranks.</span><br>
<span style="color: rgb(102, 102, 102);">> >> ></span><br>
<span style="color: rgb(102, 102, 102);">> >> ></span><br>
<span style="color: rgb(102, 102, 102);">> >> ></span><br>
<span style="color: rgb(102, 102, 102);">> >> ></span><br>
<span style="color: rgb(102, 102, 102);">> >> > On Sat, 2010-01-23 at 13:36 -0800, Ian Atha wrote:</span><br>
<span style="color: rgb(102, 102, 102);">> >> > > Hey folks,</span><br>
<span style="color: rgb(102, 102, 102);">> >> > ></span><br>
<span style="color: rgb(102, 102, 102);">> >> > > Leif and I are meeting up at 2169 today circa 3pm to brainstorm about</span><br>
<span style="color: rgb(102, 102, 102);">> >> > > the implementation of the One True Noisebridge Calendar. If you have</span><br>
<span style="color: rgb(102, 102, 102);">> >> > > anything you'd like us to consider now's the time to speak!</span><br>
<span style="color: rgb(102, 102, 102);">> >> > ></span><br>
<span style="color: rgb(102, 102, 102);">> >> > > For your reference, voilá Kelly's specs:</span><br>
<span style="color: rgb(102, 102, 102);">> >> > ></span><br>
<span style="color: rgb(102, 102, 102);">> >> > > - Publicly editable, anonymously editable</span><br>
<span style="color: rgb(102, 102, 102);">> >> > > - Publicly linkable</span><br>
<span style="color: rgb(102, 102, 102);">> >> > > - Has the usual variety of calendar layouts (day, week, month, list)</span><br>
<span style="color: rgb(102, 102, 102);">> >> > > - The usual calendar capabilities (description field, repeating events)</span><br>
<span style="color: rgb(102, 102, 102);">> >> > > - iCal feed, RSS feed</span><br>
<span style="color: rgb(102, 102, 102);">> >> > > - Some sort of feed which can auto-update the wiki homepage</span><br>
<span style="color: rgb(102, 102, 102);">> >> > > - Probably free</span><br>
<span style="color: rgb(102, 102, 102);">> >> > > - Hosted locally(ish)</span><br>
<span style="color: rgb(102, 102, 102);">> >> > ></span><br>
<span style="color: rgb(102, 102, 102);">> >> > > And bonus options:</span><br>
<span style="color: rgb(102, 102, 102);">> >> > > - Can use wiki logins or some other kind of identification in addition</span><br>
<span style="color: rgb(102, 102, 102);">> >> > > to anonymous</span><br>
<span style="color: rgb(102, 102, 102);">> >> > > - Events have a field for which room/area of NB</span><br>
<span style="color: rgb(102, 102, 102);">> >> > > - Calendars show which room/area of NB</span><br>
<span style="color: rgb(102, 102, 102);">> >> > > - open source or some other moral superiority</span><br>
<span style="color: rgb(102, 102, 102);">> >> > > - easy publishing to email (for nb-announce, for instance)</span><br>
<span style="color: rgb(102, 102, 102);">> >> > > - misc bells and whistles</span><br>
<span style="color: rgb(102, 102, 102);">> >> > ></span><br>
<span style="color: rgb(102, 102, 102);">> >> > > I'd heart you so much more if we keep this thread relevant!</span><br>
<span style="color: rgb(102, 102, 102);">> >> > ></span><br>
<span style="color: rgb(102, 102, 102);">> >> > ></span><br>
<span style="color: rgb(102, 102, 102);">> >> > > -ian.</span><br>
<span style="color: rgb(102, 102, 102);">> >> > > _______________________________________________</span><br>
<span style="color: rgb(102, 102, 102);">> >> > > Noisebridge-discuss mailing list</span><br>
<span style="color: rgb(102, 102, 102);">> >> > > <a href="javascript:top.opencompose('Noisebridge-discuss@lists.noisebridge.net','','','')">Noisebridge-discuss@lists.noisebridge.net</a></span><br>
<span style="color: rgb(102, 102, 102);">> >> > > <a target="_blank" href="parse.php?redirect=https://www.noisebridge.net/mailman/listinfo/noisebridge-discuss"><span style="color: red;">https://www.noisebridge.net/mailman/listinfo/noisebridge-discuss</span></a></span><br>
<span style="color: rgb(102, 102, 102);">> >> ></span><br>
<span style="color: rgb(102, 102, 102);">> >> > _______________________________________________</span><br>
<span style="color: rgb(102, 102, 102);">> >> > Noisebridge-discuss mailing list</span><br>
<span style="color: rgb(102, 102, 102);">> >> > <a href="javascript:top.opencompose('Noisebridge-discuss@lists.noisebridge.net','','','')">Noisebridge-discuss@lists.noisebridge.net</a></span><br>
<span style="color: rgb(102, 102, 102);">> >> > <a target="_blank" href="parse.php?redirect=https://www.noisebridge.net/mailman/listinfo/noisebridge-discuss"><span style="color: red;">https://www.noisebridge.net/mailman/listinfo/noisebridge-discuss</span></a></span><br>
<span style="color: rgb(102, 102, 102);">> >></span><br>
<span style="color: rgb(102, 102, 102);">> >> _______________________________________________</span><br>
<span style="color: rgb(102, 102, 102);">> >> Noisebridge-discuss mailing list</span><br>
<span style="color: rgb(102, 102, 102);">> >> <a href="javascript:top.opencompose('Noisebridge-discuss@lists.noisebridge.net','','','')">Noisebridge-discuss@lists.noisebridge.net</a></span><br>
<span style="color: rgb(102, 102, 102);">> >> <a target="_blank" href="parse.php?redirect=https://www.noisebridge.net/mailman/listinfo/noisebridge-discuss"><span style="color: red;">https://www.noisebridge.net/mailman/listinfo/noisebridge-discuss</span></a></span><br>
<span style="color: rgb(102, 102, 102);">> ></span><br>
<span style="color: rgb(102, 102, 102);">> > _______________________________________________</span><br>
<span style="color: rgb(102, 102, 102);">> > Noisebridge-discuss mailing list</span><br>
<span style="color: rgb(102, 102, 102);">> > <a href="javascript:top.opencompose('Noisebridge-discuss@lists.noisebridge.net','','','')">Noisebridge-discuss@lists.noisebridge.net</a></span><br>
<span style="color: rgb(102, 102, 102);">> > <a target="_blank" href="parse.php?redirect=https://www.noisebridge.net/mailman/listinfo/noisebridge-discuss"><span style="color: red;">https://www.noisebridge.net/mailman/listinfo/noisebridge-discuss</span></a></span><br>
<span style="color: rgb(102, 102, 102);">> ></span><br>
<span style="color: rgb(102, 102, 102);">> </span><br>
<br>
_______________________________________________<br>
Noisebridge-discuss mailing list<br>
<a href="javascript:top.opencompose('Noisebridge-discuss@lists.noisebridge.net','','','')">Noisebridge-discuss@lists.noisebridge.net</a><br>
<a target="_blank" href="parse.php?redirect=https://www.noisebridge.net/mailman/listinfo/noisebridge-discuss"><span style="color: red;">https://www.noisebridge.net/mailman/listinfo/noisebridge-discuss</span></a><br>
<br>
<br>
</blockquote></HTML>