The vending machine now provides some more feedback after money is put in.
Source code associated with my contribution is here. I haven't documented
the other components of the vending machine.
Based on the implementation details, it appears to me that
the bill acceptor is in fact plugged into one board (Arduino Leonardo)
that is connected by serial to another board (Raspberry Pi). Why is
the former board used at all? That is, why is the bill acceptor not
plugged directly into the latter board?
I've set up a jitsi terminal on the wall in Sudoroom!
It's a big TV made by Hitachi, and it has a feature where it can go into "power
saving" mode when the HDMI signal is lost. That means the screen can power
down when DPMS puts the monitor to "sleep". It has a webcam that's clearly
labeled, and on a hinge so it can easily be aimed down at the floor if people
are shy, and it has a Jabra USB speaker/microphone thing which should hopefully
provide good speakerphone functionality. I have the computer setup to start
firefox, and i have firefox set to open the jitsi page, where permissions are
already enabled for webcam/audio. The only remaining need is to automatically
wake the monitor from sleep (using "DISPLAY=:0 xset force dpms on") whenever
there is anyone else detected in the jitsi "room"
This feature is important so that people can see (on the screen) whenever
someone is in the screen/camera/microphone with them. For now the monitor is
either left on a lot, or blanks out due to a timeout.
I've determined that the most direct ways to make the monitor turn on when
anyone joins the jitsi channel are:
1. make an XMPP client in python or something, which connects to the server and
finds out how many people are in the room (and whether there's anyone other
than the telescreen in there) and sets the monitor on/off state accordingly
2. make a browser extension to find the element containing the number of
"Meeting participants" and copy the number to the window title, where it can be
observed from the shell with a command like wmctrl -l
<div class="jss52">Meeting participants (2)</div>
unfortunately the div class is not always jss52 but the innertext is always
Meeting Participans(#) so it should be able to be found.
The idea is that with this setup, people can go on jitsi and talk to whomever
is in sudoroom, as well as each other.
presently i'm using this link but that can change if we find something better:
note: the telescreen in sudoroom is not signed in right now, not sure why but
i'll fix it asap
I was wondering if anyone might be interested in having a 3D resin printing
setup at sudo room?
I'm thinking one of those ~$200 resin printers, a little wash basin and a
UV exposure box. We can probably make the wash basin and UV box ourselves
and maybe some of us can contribute a few bucks and split the cost of the
I know resin tends to stink and release questionable VOCs into the air,
I have acquired a tabletop ductless fume hood. It functions by sucking the
fumes through a carbon filter. I'd be happy to keep it at sudo room for the
resin printing setup.
It probably needs a new carbon filter but I got some carbon filter material
and plan to simply re-stuff the existing filter cartridge.
The hood is 35.5" wide with a 24" tall work area. It looks like this but
without the bottom tray:
I'm thinking we can put it on the white southernmost table behind the laser
Maybe a front-opening printer like this one would be appropriate?
If this happens I'd like to keep access to the printer and a small supply
box locked off unless folks have been checked out on usage of the printer
since it's easy to permanently destroy these by not cleaning off the resin
and letting the sun's UV harden it.
Folks from CCL might also be interested since resin is generally
autoclavable and more chemical resistant than what can be done with the
Anyone interested enough to help buy such a thing?
Hey, that's my first email to the group👋 I sent the same msg below to `
info(a)sudoroom.org` and got some answers from Jake and Andrew, who told me
to post here. So here it goes:
Hey, this is Juliana, a bit about myself, I'm originally from Brazil, have
been living in Oakland for 10 yrs, and in the last 3 ones I got more
involved in the tech world. In 2019 I joined a software eng bootcamp and
since 2020 I've been working as a software engineer. I never imagined I was
going to work in tech one day, much less be a software engineer. Having a
non-tech background and being a person from several underrepresented groups
in tech make it hard to imagine that's even a possibility.
Anyways, it's because of that that I've been trying to volunteer more and
more to help the community to conquer what I got, and that's where Sudo
Rooms gets in. I've heard about Sudo Room maybe 3 years ago but never had
the opportunity to be part of an event (cause pandemic..). I would love to
help organize some kind of event with women/nb only and have a "coding
night", where we can help each other in coding projects or even help ppl to
learn how to code. I see you folks have a JS night, so it would prob be
I emphasize the women/nb only because this is a real barrier in tech, I
studied in a women/nb only bootcamp and that totally made a difference.
Even when men are allies and empathize with beginners, It's all about
seeing that other non-men can do that and feel empowered by that.
About my skills, I'm still Level I but have been working with Ruby on
Rails, Python, SQL, React, Typescript. I'm full stack although I prefer
backend :) So far I've volunteered/attended events from Techtonica, Women
who Code, Wnb.rb, Ruby for Good, Lesbians who Tech, PyLadies, etc.
My linkedin https://www.linkedin.com/in/julianaalmeida78/
My twitter @JFArebelyell
Let me know if this is something Sudo Room would be interested in hosting!
is there some patient human (or equivalent) here that can teach me how to
use the laser cutter? I know almost nothing about such machines beyond a
solid theoretical understanding of how it works. I'm looking for a class or
elmer to teach me how one really uses such machines.
Carl and I spoke at the last Noisebridge five minutes of fame - (the april
Pt 1: https://youtu.be/fGNGWw4Q9Ek
Pt 2: https://www.youtube.com/watch?v=3TeRN5PwKuQ
I mean, obviously I talked about the light projector project I've been
working on, that I've received so much help on. But then I showed how I was
experimenting in the Omni Commons ballroom, and I emphasized how SudoRoom
has this very unique environment in the SF Bay Area -- a place where
artists can jam alongside hardcore hardware hackers, and we have a lot of
beautiful space to experiment.
I couldn't make it to tonight's Hardware Hack night, but I think I'll do a
blog post about my project so far (the bike party) and my next steps, which
involve making a series of mobile apps to help do skew and distort. There
is of course math involved, so there can be small math worksheets!
Yeah, I agree that with the values and purpose/intent it’s more important to be specific.
Especially because I think the stated intent (based on sudoroom’s wiki: social change, community engagement, etc.) is actually quite a bit more ambitious relative to, say, Noisebridge, whose vision statement is (paraphrasing) “provide infrastructure and opportunities for people interested in <various art/technology topics>”.
What does openness and “hack the planet” mean to you? Why are those things important as values? Are those things also our intent, or is there a separate mission/purpose?
> On Apr 11, 2022, at 13:26, Andrew R Gross <arg5029(a)gmail.com> wrote:
> These are great. Personally, I don’t feel the need to overthink things or reinvent the wheel, so I’d be pretty happy to adopt the community standards pretty much unchanged. I’m happy to help people edit it as they see fit, but I think it’s overall definitely good enough.
> I think the statements of values are similarly pretty good, although I’d like to edit them to be a bit more specific. For instance, I think articulating what openness means, and what what it means to hack the planet, and why, and in the pursuit of what outcome. But again, I’d say they’re good enough that I’d support them as is if others wanted to take the path of least resistance.
> On Sun, Apr 10, 2022 at 9:33 AM Eric O'Connor <eric(a)oco.nnor.org> wrote:
>> Here’s some resources from Sudoroom’s wiki and other hacker/maker space pages that could be useful reference material.
>> I like how Noisebridge has a specific guidelines on community norms.
>> How is sudoroom’s purpose different from these other communities?
>> Part of it might just be a geographical niche, but there are probably intentional cultural differences as well? What are those?
>>> From the Wiki :
>>> We're into technology and where it intersects with social justice, sustainability, education and solidarity.
>>> We strive to be an open, transparent, horizontal and welcoming community where all are supported and free to learn, create, gather, collaborate, work, play and more! .
>>> We've got tons of tools for you to use from a 3D printer to public computer terminals, Math projects, a big huge library and all kinds of gadgets!
>>> We are exclusively volunteer-run and supported through donations!! Learn more about membership.
>>> Our slogan is: HACK THE PLANET!
>>> On Apr 9, 2022, at 22:51, Andrew R Gross via sudo-discuss <sudo-discuss(a)sudoroom.org> wrote:
>>> Should we establish a statement of purpose and a code of conduct?
>>> I think Sudoroom should adopt a code of conduct, because currently our only behavioral rules are the Omni Commons Safer Space policy: https://omnicommons.org/wiki/Safer_Space_Policy
>>> These rules are vital, but are limited to a broad set of wildy unacceptable behavior anywhere. They don't outline minor and hackerspace specific guidelines on ideal and discouraged behavior.
>>> PB asked if we have any statement defining our most basic principle or goal, and while it sounds like there is a lot of diverse informal wisdom, there isn't a clear singular statement of intent. So I'd like to propose we agree on one of those as well.
>>> I think a starting point for a code of conduct would be something like "Try to enhance the experience of others in Sudoroom and avoid impeding it", and then we could go into a few more specific examples like cleaning up, asking people if they'd like companionship or space when working in the space at the same time, etc.
>>> I don't have any clear suggestions for what our statement of purpose would be, but I like the values of justice and openness.
>>> Andrew R Gross, (he/him)
>>> 412.657.5332 - shrad.org
>>> sudo-discuss mailing list -- sudo-discuss(a)sudoroom.org
>>> To unsubscribe send an email to sudo-discuss-leave(a)sudoroom.org
>>> More options at https://sudoroom.org/lists/postorius/lists/sudo-discuss.sudoroom.org/
> Andrew R Gross, (he/him)
> 412.657.5332 - shrad.org
In light of new members / groups having arrived 10 months on into intensive
building improvements and infrastructure maintenance that myself, Sarah,
and Safer DIY began last summer - and in the spirit of ‘step up, step back’
that I generally think is a healthy collective practice to horizontalize
labor and responsibility - I thought this would be an opportune time to
consciously transition these responsibilities to a new member(s).
For those with interests in continuing any building improvements /
effecting property maintenance - which was originally begun to pass omni’s
fire inspection, then in a valiant effort to aid in Omni’s narrowing refi
prospects - I would like to pass on the following contact information for
Omni’s most recent carpenter, electrician, plumber, HVAC, Roofer, etc:
Matt Costa, carpenter:
+1 (718) 290-5758
Clif Walker, electrician:
+1 (510) 435-0796
Tony Fazule, plumber:
+1 (510) 534-5480
+1 (415) 254-782
DTC Lighting & Grip:
+1 (510) 595-0770
Mike Tenuto, Roofer:
+1 (510) 575-2800
* TL;DR: As some are aware, Mike currently owes omni a ~$8.9K refund and
has also guaranteed the roof for 7y; and (because I have been asked more
than once) fwiw he is not my referral, he was a referral from within omni
and not someone I previously worked with. His payment on the refund to omni
is pretty late; a claim with the surety company may need to be filed and
I’m sure there are deadlines.. for more detail, please reach out to others
on this list.
Also - based on my experience working on omni with the help of other
building professionals since 2014, I thought it might be helpful to
reiterate what I have found to be the following best practices for omninoms
in order to maintain healthy, positive working relationships with such
- Arrange in advance for a consistent, single point of contact at omni,
with at most one backup contact. Whenever possible, avoid changing this up;
ideally there should be at least a 4mo commitment from some omninom to
being a designated point of contact.
- Avoid adding these folks to any text groups or email lists (can quickly
equate to overwhelm for non-omninoms).
- While compensation terms can differ obviously, in general be prepared to
pay the full balance on the last day / completion of work (don’t assume
net-15/30 type terms), and it is best to clarify with each contractor
before work starts as to whether whether a deposit is required for a given
scope of work (for materials? Etc), and whether cash vs check vs
PayPal/venmo etc is expected as the medium.
- Particularly on-site, professional boundaries should be consciously
maintained in that it may not be obvious to others using the building that
these folks are not fellow volunteers. Contractors may not have an
awareness of various activities or groups using the building at a given
time as they focus on their work, nor be completely read into the full
details of omnis politics / mission / structure etc etc so this should not
be assumed. Seeking to strike up an extended convo or offering to help etc
may distract more than aid, in spite of good intentions. Yelling at a
contractor because you’re trying to work on your own stuff and it’s loud
etc, or critiquing their work as they are doing it, is to be avoided.
Unless there is an imminent hazard, omninoms should be instructed to have
an inconvenienced human yell at the point of contact for the contractor,
and not the contractor.
- If it changes, be sure to inform contractors of the lockbox code / key /
card so they can freely access the building. In general, a contractor
waiting or working = same cost to omni. Most use the lockbox I installed
- If things seem to go south with a contractor for whatever reason,
remember that locating a talented, affordable, dependable, nice etc
tradesperson for Omni’s not-insignificant task list of ‘small’ jobs for is
not always easily achieved. It is worth keeping in mind for example, that
the present electrician will have a relatively deep knowledge of Omni’s
electrical to start with and therefore, be more likely to fix a problem in
less time (cheaper) than a different electrician. Same with plumber, etc
etc. So, imo it is best to over-budget any time needed to locate and
establish a relationship with a suitable replacement should that ever be
required. Finally, while I don’t expect this will realistically last within
Omni’s institutional memory very long I would like to remind folks that I
generally continue rely on those contractors I brought in to omni, in order
to preserve affordable housing and myriad community spaces elsewhere.. so
if things ever go south with any contractor I would really appreciate being
notified as a courtesy.