[Noisebridge-discuss] Proposal to open Noisebridge at sunrise

Thu Apr 30 21:11:27 UTC 2015

On 30 April 2015 at 13:53, Harry Moreno <morenoh149 at gmail.com> wrote:

> Here are my thoughts.
>
> From reading the user levels here
> https://github.com/hzeller/rfid-access-control/blob/master/software/earl/user.go
> my impression is that the users implementing the system want 'non-anonymous
> users' to be full Noisebridge Members.
>

Well, the 'member' category is just the kind of person who can give out new
key. This could be renamed, or we can actually assign a bitmap of
responsibilities to users.

non-annymous are tokens that don't expire after 30 days, while anonymous
do. This is necessary to make sure that it is possible to find lost tokens.
If someone has lost their token, we would have no idea which token to
disable when they are anonymous. This way, things are automatically taken
care of.

Also, people who are giving out tokens should be known by name, yes. In the
file called 'members' for lack of a better name.

> It's been repeated in the past that Membership has only one perk - Block
> rights for concensus.
>

Right.
Don't get hung up on the name of 'member' here. It is just a name that
stuck. We have members in the file that are not actually members, but have
been known to be responsible Noisebridgers so that they can be trusted to
give out new keys.

>
> I'd like to have early access to Noisebridge and not be a Member.
>

Well, then someone should you just put in the fulltime user category which
allows you to get in at 7am.

> I prefer to donate $ on my own terms and believe that the system as it
> currently stands makes the statement 'Membership has only one perk - Block
> rights for concensus.' a lie.
>
> Anyone object to allowing anonymous users early access to Noisebridge?
>

> And if I'm incorrect in anything I wrote please do correct me. :-)
>
> - Harry
>
> On Thu, Apr 30, 2015 at 1:46 PM, kjs <bfb at riseup.net> wrote:
>
>> In this case, I would like to improve the interface for adding
>> fulltimeusers. Am I correct that currently one must edit a text file on
>> Earl's raspPie to assign a key fulltimeuser permissions?
>>
>> Also,  is there somewhere between sunrise and 11:00 that y'all are
>> comfortable with? Sunrise+2hr? I feel most anon users are good users and
>> key expiry will filter a majority of the bad users.
>>
>> -Kevin
>>
>> On April 30, 2015 2:24:46 AM PDT, Mitch Altman <maltman23 at hotmail.com>
>> wrote:
>> >+1 to what Henner suggested:  'fulltimeusers' get extended from sunrise
>> >to start at sunrise.
>> >
>> >Best,
>> >Mitch.
>> >
>> >
>> >Date: Wed, 29 Apr 2015 22:13:35 -0700
>> >From: h.zeller at acm.org
>> >To: bfb at riseup.net
>> >CC: noisebridge-discuss at lists.noisebridge.net
>> >Subject: Re: [Noisebridge-discuss] Proposal to open Noisebridge at
>> >sunrise
>> >
>> >On 29 April 2015 at 20:17,  <bfb at riseup.net> wrote:
>> >Hi all,
>> >
>> >
>> >
>> >At the last several meetings there has been lively discussion to bump
>> >up our opening time from 11:00 to sunrise. Specifically, Earl, our
>> >gatekeeper, is configured for three user types.
>> >
>> >
>> >
>> >Earl currently opens when an RFID key is scanned for:
>> >
>> >
>> >
>> >anonymous users from 11:00 - 22:00
>> >
>> >deanonymized users from 7:00 - 23:59
>> >
>> >root users with 24 hour access
>> >
>> >the second group is actually 'fulltimeusers', which is like the other
>> >users as well and 'could' be anonymous, but in practice isn't (but
>> >should probably be a requirement).
>> >
>> >
>> >The proposal is to change this to:
>> >
>> >
>> >
>> >anonymous users from sunrise - 22:00
>> >
>> >deanonymized users form sunrise - 23:59
>> >
>> >root users with 24 hour access
>> >
>> >I would _not_ put anonymous users in the sunrise category. We give out
>> >tokens pretty freely these days, and I would like to continue this
>> >welcoming gesture. However, if this brings in the burden to really,
>> >really be sure that this is a person I can 100% trust, then giving out
>> >tokens will be slowed down; which is not what we want. Someone coming
>> >in in early hours should be explicitly put into that category.
>> >So I would like to have people who can access the space in the early
>> >hours to be known and explicitly put in the 'fulltimeuser' category.
>> >
>> >But I am (personally) ok with having 'fulltimeuser' extended in the
>> >morning to sunrise (and would slightly endorse it).
>> >-h
>> >
>> >
>> >To accomplish this we use the https://github.com/cpucycle/astrotime
>> >library. The code is in place, perhaps ready to deploy.
>> >
>> >
>> >
>> >How do others feel about this change? If you're curious, have a look at
>> >meeting discussions.
>> >
>> >
>> >
>> >https://www.noisebridge.net/Meeting_Notes_2015_04_07
>> >
>> >https://www.noisebridge.net/Meeting_Notes_2015_04_21
>> >
>> >https://www.noisebridge.net/Meeting_Notes_2015_04_28
>> >
>> >
>> >
>> >Some salient points for me include:
>> >
>> >
>> >
>> >Early birds have described friction with the 11:00 opening hour
>> >
>> >Noisebridge is lonely when empty
>> >
>> >Noisebridge prospers when used, not abused
>> >
>> >Early birds want to hack between sunrise and 11:00 at Noisebridge
>> >
>> >Updating RFID keys with contact information requires editing a text
>> >file (not currently supported via the touchpad interface)
>> >
>> >Decoupling Noisebridge from an arbitrary and obsolete governmental
>> >definition, the PDT/PST flux, is nice
>> >
>> >Sunrise is beautiful
>> >
>> >If the change is not working out, we can always roll back
>> >
>> >
>> >
>> >Thanks much for reading,
>> >
>> >Kevin
>> >
>> >
>> >
>> >_______________________________________________
>> >
>> >Noisebridge-discuss mailing list
>> >
>> >Noisebridge-discuss at lists.noisebridge.net
>> >
>> >https://www.noisebridge.net/mailman/listinfo/noisebridge-discuss
>> >
>> >
>> >
>> >
>> >_______________________________________________
>> >Noisebridge-discuss mailing list
>> >Noisebridge-discuss at lists.noisebridge.net
>> >https://www.noisebridge.net/mailman/listinfo/noisebridge-discuss
>> >
>>
>> _______________________________________________
>> Noisebridge-discuss mailing list
>> Noisebridge-discuss at lists.noisebridge.net
>> https://www.noisebridge.net/mailman/listinfo/noisebridge-discuss
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.noisebridge.net/pipermail/noisebridge-discuss/attachments/20150430/4fa35206/attachment-0003.html>