[hackerspaces] Makerspaces
Russell Fair
rfair404 at gmail.com
Sun Jun 26 23:18:54 CEST 2016
I would be very interested in some notes from ISTE re: makerspaces. Please
& thank you!
On Sun, Jun 26, 2016 at 8:05 AM, Kyle Muir <kyle at fuzeinteractive.io> wrote:
> I am headed to ISTE in Denver today. There are a number of lectures and
> workshops on this topic I plan to attend.
>
> Will anyone else be attending or like notes to be shared?
>
> Kyle
>
> On Sunday, June 26, 2016, <discuss-request at lists.hackerspaces.org> wrote:
>
>> Send Discuss mailing list submissions to
>> discuss at lists.hackerspaces.org
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>> http://lists.hackerspaces.org/mailman/listinfo/discuss
>> or, via email, send a message with subject or body 'help' to
>> discuss-request at lists.hackerspaces.org
>>
>> You can reach the person managing the list at
>> discuss-owner at lists.hackerspaces.org
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of Discuss digest..."
>>
>>
>> Today's Topics:
>>
>> 1. US hackerspace and makerspaces - safety practices in risky
>> neighborhoods (Shirley Hicks)
>> 2. Re: US hackerspace and makerspaces - safety practices in
>> risky neighborhoods (Arclight)
>>
>>
>> ----------------------------------------------------------------------
>>
>> Message: 1
>> Date: Sat, 25 Jun 2016 09:43:52 -0500
>> From: Shirley Hicks <shirley at velochicdesign.com>
>> To: Hackerspaces General Discussion List
>> <discuss at lists.hackerspaces.org>
>> Subject: [hackerspaces] US hackerspace and makerspaces - safety
>> practices in risky neighborhoods
>> Message-ID: <95B80BEB-9706-4F26-B4F0-B7C0C8056CE2 at velochicdesign.com>
>> Content-Type: text/plain; charset=utf-8
>>
>> Hey everyone,
>>
>> For a whole bunch of reasons, we’re having to push through and complete
>> safety and security protocols for our makerspace.
>> The thing we need to address is very US-centric, that of having taken a
>> low(er) rent space in a neighborhood with crime problems and needing to
>> beef up security and safety practices as a result.
>>
>> We have a good crew in charge of this at our makerspace, but we now need
>> to get a formal process in place for our membership so that we capture
>> _all_ incidents. (we’re working with our city police and administration to
>> improve safety in the area).
>>
>> Am wondering if you would be willing to share your practices at your
>> makerspace. Also, if you have linked material or docs, would you be willing
>> to share that as well?
>>
>> Thanks in advance,
>>
>> Shirley Hicks
>> Red Mountain Makers
>> Birmingham, AL
>>
>> ------------------------------
>>
>> Message: 2
>> Date: Sat, 25 Jun 2016 23:14:11 -0700
>> From: Arclight <arclight at gmail.com>
>> To: Hackerspaces General Discussion List
>> <discuss at lists.hackerspaces.org>
>> Subject: Re: [hackerspaces] US hackerspace and makerspaces - safety
>> practices in risky neighborhoods
>> Message-ID:
>> <
>> CABh0E1ZTSddHVTE1Q6voSZ618dw8H13YndgQ3y0QN2spXtzehw at mail.gmail.com>
>> Content-Type: text/plain; charset=UTF-8
>>
>> I don't think this is a strictly US problem. Other folks from Europe
>> and Latin America have told me stories about the dodgy spaces they
>> rent due to affordability.
>>
>> In any case, we don't have a "safety manual," but we do have a few
>> core principals. Our place is located in an industrial area 2 blocks
>> from a methadone clinic and a downtown with a large homeless
>> population. It's not gangland or especially dangerous, but common
>> sense must be observed.
>>
>> 1. Lock it or lose it! Don't store anything outside that you don't
>> want stolen. It could be fine for weeks, but it's bad practice,
>> serves as an attractor to scumbags, and often ends in lots of crying.
>> This applies to materials, bikes, large tools, etc.
>>
>> 2. The space gets locked when not open, 100% of the time, no
>> exceptions. Make the workflow of your access system encourage this
>> practice by making "door stays unlocked' an explicit mode that is not
>> the default after the first person comes in, and setting a nightly
>> timeout to relock everything if forgotten.
>>
>> 3. Use cameras and alarm functionality the right way. I'll say it
>> now: Cameras do very little to prevent crime. We have a visible
>> camera right over the dumpster, and it has never stopped the taggers
>> or the phantom pooper. And unless you have a very high quality (i.e.
>> 1MP or above with good low-light and appropriate optics), you'll just
>> have a bunch of blurry pictures of people stealing your stuff.
>>
>> And if you have a monitored alarm, you're also not using it right if
>> you have repeated false alarms.
>>
>> The right way: Use cameras as a way of verifying who is at the door,
>> or verifying what is going on in real-time should your alarm go off.
>> Cops will be more likely to respond if you have a video-verified alarm
>> than the typical "something may or may not have happened" telemetry.
>>
>> Regarding the alarm system itself, we have a self-monitored system,
>> and have made it very easy for people to arm it and lock up when
>> leaving. (You just enter '1's until it starts the 30 second
>> countdown, or chirps an error if you left a door open).
>>
>> We also make it easy to disarm - something like "the act of badging in
>> also disarms the alarm" is a good way to prevent falses and make the
>> 5+ people callout list that gets SMS'd in the event of an alarm
>> immediately jump up and check the cameras.
>>
>> Yes, you can go into endless "what if the attackers jammed cell
>> service, cut the wires, and took advantage of the fact that MD5 is an
>> outdated hashing algorithm" scenarios. The truth is, you're trying to
>> protect your assets from a bunch of thieves parking a moving truck in
>> your loading dock and stripping the place while everyone is at DEFCON,
>> or the odd "smash and grab" druggie from the alley.
>>
>> 4. Make it look like there is nothing to steal. No laptops, camera
>> bags, etc should be sitting on your car seat. Don't make it look
>> from the outside like it's a weed grow, a computer shop or anything
>> with cash or retail goods. Be forgettable.
>>
>> 5. If you see people that don't belong to your group milling around,
>> engage them. When we do this, we either end up inviting them in or
>> they quickly find out this isn't the place to go to "just use the
>> bathroom" for 2 hours...
>>
>> 6. The best defense is having people there a lot and at unpredictable
>> times. In most hacker spaces, there is not "safe" time a person could
>> break in and be assured of it being unoccupied. This ain't Starbucks.
>> You can also maintain a presence if you have an active chat room/IRC
>> channel and a webcam. You can even set up the webcam to be disabled
>> if the space is unoccupied/alarm is armed. That is a personal choice.
>> Some folks actually like turning on a webcam and being logged in to
>> chat if they are working alone - it's like having someone keeping an
>> eye on you if you get hurt/etc.
>>
>> 7. The last thing: If you need someone to leave, ask them to leave
>> clearly and unambiguously. No passive-aggressive games. If they are
>> aggressive, crazy and/or otherwise won't leave, call the police. All
>> of the local businesses here have the direct number to the PD taped to
>> the counter for a reason. Some spaces have a "No cops, EVAH!" policy.
>> The bottom line is that they are a resource you occasionally need,
>> warts and all.
>>
>> Cheers,
>>
>> Arclight
>>
>>
>> We've have neighbors get broken into, but our space has never been
>> targeted.
>>
>> On Sat, Jun 25, 2016 at 7:43 AM, Shirley Hicks
>> <shirley at velochicdesign.com> wrote:
>> > Hey everyone,
>> >
>> > For a whole bunch of reasons, we’re having to push through and complete
>> safety and security protocols for our makerspace.
>> > The thing we need to address is very US-centric, that of having taken a
>> low(er) rent space in a neighborhood with crime problems and needing to
>> beef up security and safety practices as a result.
>> >
>> > We have a good crew in charge of this at our makerspace, but we now
>> need to get a formal process in place for our membership so that we capture
>> _all_ incidents. (we’re working with our city police and administration to
>> improve safety in the area).
>> >
>> > Am wondering if you would be willing to share your practices at your
>> makerspace. Also, if you have linked material or docs, would you be willing
>> to share that as well?
>> >
>> > Thanks in advance,
>> >
>> > Shirley Hicks
>> > Red Mountain Makers
>> > Birmingham, AL
>> > _______________________________________________
>> > Discuss mailing list
>> > Discuss at lists.hackerspaces.org
>> > http://lists.hackerspaces.org/mailman/listinfo/discuss
>>
>>
>> ------------------------------
>>
>> Subject: Digest Footer
>>
>> _______________________________________________
>> Discuss mailing list
>> Discuss at lists.hackerspaces.org
>> http://lists.hackerspaces.org/mailman/listinfo/discuss
>>
>>
>> ------------------------------
>>
>> End of Discuss Digest, Vol 94, Issue 4
>> **************************************
>>
>
>
> --
>
> -
> - Kyle
>
> 775.848.1006
> - www.linkedin.com/in/kylegmuir/
> *CONFIDENTIALITY ---* This email is directed only to the person or entity
> to whom it is addressed, and the contents hereof and any attachments hereto
> are intended to be strictly confidential and may otherwise be subject to
> the attorney-client privilege and/or the work-product doctrine, and should
> not, therefore, be in any way copied, distributed, or disclosed to other
> parties. If you have received this message by error, please reply by email
> to inform us and delete any copies from your hard drive. Thank you.
>
>
>
> _______________________________________________
> Discuss mailing list
> Discuss at lists.hackerspaces.org
> http://lists.hackerspaces.org/mailman/listinfo/discuss
>
>
--
Thanks,
Russell Fair
770.401.9039
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hackerspaces.org/pipermail/discuss/attachments/20160626/66e57d78/attachment-0001.html>
More information about the Discuss
mailing list