Noisebridge - User contributions [en]

User talk:Maxisthespy

2026-03-24T02:25:03Z

ElanHR: Welcome!

'''Welcome to ''Noisebridge''!'''
We hope you will contribute much and well.
You will probably want to read the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents help pages].
Again, welcome and have fun! [[User:ElanHR|ElanHR]] ([[User talk:ElanHR|talk]]) 19:25, 23 March 2026 (PDT)

User:Maxisthespy

2026-03-24T02:25:03Z

ElanHR: Creating user page for new user.

Hi! Welcome to Myspace! " " < this is my space

^
This is mine too

The rest of it is for the people

User talk:Zackerthescar

2026-03-24T02:24:43Z

ElanHR: Welcome!

User:Zackerthescar

2026-03-24T02:24:43Z

ElanHR: Creating user page for new user.

https://zackerthescar.com im too lazy to cmd+c cmd+v

User talk:DerekRhodes

2026-03-24T02:24:13Z

ElanHR: Welcome!

User:DerekRhodes

2026-03-24T02:24:13Z

ElanHR: Creating user page for new user.

One who enjoys programming the computers.

User talk:Dc

2026-03-24T02:23:57Z

ElanHR: Welcome!

User:Dc

2026-03-24T02:23:57Z

ElanHR: Creating user page for new user.

I’m into unix. and minimalism also.

User talk:Davidporter-id-au

2026-03-24T02:23:34Z

ElanHR: Welcome!

User:Davidporter-id-au

2026-03-24T02:23:34Z

ElanHR: Creating user page for new user.

Ṱ̺̺̕o͞ ̷i̲̬͇̪͙n̝̗͕v̟̜̘̦͟o̶̙̰̠kè͚̮̺̪̹̱̤ ̖t̝͕̳̣̻̪͞h̼͓̲̦̳̘̲e͇̣̰̦̬͎ ̢̼̻̱̘h͚͎͙̜̣̲ͅi̦̲̣̰̤v̻͍e̺̭̳̪̰-m̢iͅn̖̺̞̲̯̰d̵̼̟͙̩̼̘̳ ̞̥̱̳̭r̛̗̘e͙p͠r̼̞̻̭̗e̺̠̣͟s̘͇̳͍̝͉e͉̥̯̞̲͚̬͜ǹ̬͎͎̟̖͇̤t͍̬̤͓̼̭͘ͅi̪̱n͠g̴͉ ͏͉ͅc̬̟h͡a̫̻̯͘o̫̟̖͍̙̝͉s̗̦̲.̨̹͈̣
̡͓̞ͅI̗̘̦͝n͇͇͙v̮̫ok̲̫̙͈i̖͙̭̹̠̞n̡̻̮̣̺g̲͈͙̭͙̬͎ ̰t͔̦h̞̲e̢̤ ͍̬̲͖f̴̘͕̣è͖ẹ̥̩l͖͔͚i͓͚̦͠n͖͍̗͓̳̮g͍ ̨o͚̪͡f̘̣̬ ̖̘͖̟͙̮c҉͔̫͖͓͇͖ͅh̵̤̣͚͔á̗̼͕ͅo̼̣̥s̱͈̺̖̦̻͢.̛̖̞̠̫̰
̗̺͖̹̯͓Ṯ̤͍̥͇͈h̲́e͏͓̼̗̙̼̣͔ ͇̜̱̠͓͍ͅN͕͠e̗̱z̘̝̜̺͙p̤̺̹͍̯͚e̠̻̠͜r̨̤͍̺̖͔̖̖d̠̟̭̬̝͟i̦͖̩͓͔̤a̠̗̬͉̙n͚͜ ̻̞̰͚ͅh̵͉i̳̞v̢͇ḙ͎͟-҉̭̩̼͔m̤̭̫i͕͇̝̦n̗͙ḍ̟ ̯̲͕͞ǫ̟̯̰̲͙̻̝f ̪̰̰̗̖̭̘͘c̦͍̲̞͍̩̙ḥ͚a̮͎̟̙͜ơ̩̹͎s̤.̝̝ ҉Z̡̖̜͖̰̣͉̜a͖̰͙̬͡l̲̫̳͍̩g̡̟̼̱͚̞̬ͅo̗͜.̟
̦H̬̤̗̤͝e͜ ̜̥̝̻͍̟́w̕h̖̯͓o̝͙̖͎̱̮ ҉̺̙̞̟͈W̷̼̭a̺̪͍į͈͕̭͙̯̜t̶̼̮s̘͙͖̕ ̠̫̠B̻͍͙͉̳ͅe̵h̵̬͇̫͙i̹͓̳̳̮͎̫̕n͟d̴̪̜̖ ̰͉̩͇͙̲͞ͅT͖̼͓̪͢h͏͓̮̻e̬̝̟ͅ ̤̹̝W͙̞̝͔͇͝ͅa͏͓͔̹̼̣l̴͔̰̤̟͔ḽ̫.͕
Z̮̞̠͙͔ͅḀ̗̞͈̻̗Ḷ͙͎̯̹̞͓G̻O̭̗̮

#

User talk:Renaud

2026-03-24T02:22:25Z

ElanHR: Welcome!

User:Renaud

2026-03-24T02:22:25Z

ElanHR: Creating user page for new user.

i like learning new things, my interest are mainly around: software infra/home labing, programing languages, software testing, os/hardware

Template:FrontPageHeader

2026-03-21T23:11:29Z

ElanHR: Changed the fundraising notice as the fundraiser drive has passed.

<div class="front-page-box front-page-box--single">
{{home}}

[[File:NB_Logo-Black_on_Red_272.png|left|50px|link=about]]<font size=4>'''Noisebridge''' is a fun space for sharing, creation, collaboration, research, development, mentoring, and of course, learning. Come visit, work, and use our equipment free (but please donate when you can!) It's part of the [[hackerspaces]] movement [https://hackerspaces.org/ extending around the world].</font></font>

<div style="background-color:#ddf8;border:3px #33c8;padding:5px;">

<font size=4> We run on donations! If you're able to, please consider supporting us by making a [[Donate or Pay Dues#Are donations to Noisebridge tax deductible?|tax deductible donation]]<sup>†</sup> at any of the following:</font>
* https://paypal.me/noisebridge
* https://donate.noisebridge.net/
* https://www.patreon.com/noisebridge

Most of all, thank you so much for being part of our community and making it something that people want to be a part of. Be excellent to each other and happy hacking! 🤟&🤘

<small>†: Donation receipt available on request</small>
</div>

Board/2026/Election

2026-03-17T07:50:22Z

ElanHR: Added Board Requirements

{{board}}

= Process =
The 2025 Board appoints a '''nominating committee''', which will collect nominations & confirm willingness to stand for election & serve, with each nominee.

A '''membership committee''' board is also materializing membership status from meeting & donation records.

The steps we need to complete:
* Announce (30+ days in advance)
* Nominations
** Acceptance of nominations ''(don't skip this step)''
* Election

=Goals=
* Elect a new board, as we aim to do annual, in accordance with our bylaws -- filed with the state and maintained.

=General Precedent=
* Announce (30+ days in advance)
* Nominations
** Acceptance of nominations ''(don't skip this step)''
* Election

=Caveats & Lessons=
We need people willing to share their real name--for the purposes of filing taxes, and signing agreements.

==Leverage & Success of the Board==
Board can do well by delegating & extending authority to the community through working groups & committees, e.g. the 2025 woodshop construction & city permitting working group.

==Board Requirements==
As the board is Noisebridge's legal interface to the outside world we require that board members:
* accept their nomination
* disclose their legal name to be reported to the state of California as well as other documents (e.g. taxes)
* provide a form of contact to be disclosed to other members of the board

User talk:Ciaraa

2026-02-24T05:48:27Z

ElanHR: Welcome!

User:Ciaraa

2026-02-24T05:48:27Z

ElanHR: Creating user page for new user.

Just a girl who does kubernetes and Linux. I post on my fedi often. https://pl.catboyindustries.co/doti

Next meeting

2026-02-12T00:20:58Z

ElanHR: Updated redirect

#redirect [[Meeting Notes 2026 02 17]]

<hr>
<div style="background-color:#ddd8;border:3px dashed #3338;padding:3px;">
<code><nowiki>{{next meeting}}</nowiki></code> to include link to this edit-able redirect page.

[[Special:PrefixIndex/Meeting_Notes_2026_]]:
{{Special:PrefixIndex/Meeting_Notes_2026_}}

[[Special:PrefixIndex/Meeting_Notes_2025_]]:
{{Special:PrefixIndex/Meeting_Notes_2025_}}

[[Special:PrefixIndex/Meeting_Notes_2024_]]:
{{Special:PrefixIndex/Meeting_Notes_2024_}}

{{:wikiwg/header}}

{{meetings}}
</div>

Last meeting

2026-02-12T00:20:39Z

ElanHR: Updated redirect

#redirect [[Meeting Notes 2026 02 10]]

<hr>
<div style="background-color:#ddd8;border:3px dashed #3338;padding:3px;">

<code><nowiki>{{last meeting}}</nowiki></code> to include link to this edit-able redirect page.

[[Special:PrefixIndex/Meeting_Notes_2026_]]:
{{Special:PrefixIndex/Meeting_Notes_2026_}}

[[Special:PrefixIndex/Meeting_Notes_2025_]]:
{{Special:PrefixIndex/Meeting_Notes_2025_}}

[[Special:PrefixIndex/Meeting_Notes_2024_]]:
{{Special:PrefixIndex/Meeting_Notes_2024_}}

{{:wikiwg/header}}

{{meetings}}
</div>

Meetups/Infra/2026-02-06-Roundtable

2026-02-10T21:06:54Z

ElanHR: Coped meeting notes from NB Infra Round Table etherpad

{{meetups/infra}}
= Meeting Announcement =
We'll be having a Digitial Infra Roundtable this Friday ~7:30pm to discuss near-term plans to improving various NB infra pain points. There will be pizza!

A loose agenda includes:
* Run through how current infra is structured / deployed
** primary repo: [https://github.com github.com/noisebridge/infrastructure]
** m3, m5, m6, m7 are live as of today
** Infra is (kind-of) configured via ansible.
** Elan (paraphrased): We should enable people to hack on stuff and auto-deploy after a (trusted) review (or two)
*** Some discussion on deploying on merge vs deploying triggered via comments and merged upon successful completion. No decision yet.

= Agenda check-in & priorities =
** let's talk about the pain points that brought us together. Wiki server hackability updates (& Cloudflare).

* agenda setting
* the intro

motivations:
* DNS
* Wiki
* Mailing lists
* Solicit ideas on how to improve our infra and get more people involved in contributing / curating cool NB services
** Redundant data backups. The infra is not valuable, but unique data is.
** Critical vs dev playgrounds.
** K8s: Argo, Rancher,
** Possible VM cloud service
** Data servers?

= Discussion =

* What is noisegarden?
** Bare metal kubernetes cluster
*** [[NoiseGarden]]

* What is Kubernetes / Docker / Containers?
** Kubernetes: Orchestrates a bunch of docker containers on the available hardware.
** Docker: Docker packages software into standardized units called containers that have everything the software needs to run including libraries, system tools, code, and runtime.
** Containers

* Noisebridge remote servers.
** Our infra is running in VMs remotely, not bare metal.

If I have a container with some application I'd like to run, how can I deploy it to the kubernetes cluster?

Topics to discuss:
** what services do people want
** internal domain names
** external names, or NAT routing.
** static ip ranges
** visiblity of services on laptop
** door fixing - visiblity of noisebridge
** docker container for print room, hand drawn images into 3d printable, toy
** ImageGen (live) brain dump of conversations
** prod vs dev distinction -- local

; Q: What services are lacking?
: '''Naomi:''' "I would like to be able to set up an internal hostname w/ static IP address for myself"
: '''Elan:''' Currently possible with a password
: '''Naomi:''' Be able to set up my own subdomain @ noisebridge.net (or whatever) with (maybe) NAT-routing of a port into an internal machine (audited by peers yes)
:* Static IP addresses?
:* More visibility into infra
:* Connecting on prem infra and remote infra.
: '''Erikk:'''
:* 2D -> 3D image service for the print room.
:* Brain dump conversations
:* Make some of the infra as non-essential more open - not require keys. Dev / sandbox area.
: '''Sophia:'''
:* transit alerts - when is next X showing up
:* DIY doorbell cam / press a button upstairs to open it from upstairs (Perry: +1!)
:* base model inference
:* Flaschentashen web interface
: '''Loren:'''
:* wanting to deploy small services on NoiseGarden (inventory / limited todos)
: '''Naomi:'''
:* Home assistant on raspberri pi (internal)
:* Streamlit dashboards w/ NAT-routed ports
: '''Derek:'''
:* locker management system w/ QR codes
: '''Daniel:'''
:* put hardware in local colo w/ donated hardware

How to modernize our noisebridge/infrastructure repo?
* '''Peter:''' What is the contract for hosted service?
** Security (security review process?)
** Externally accesible?
* '''Sophia:''' Does Docker solve this? Daniel: Unfortunately it is not a security layer
* '''Loren:''' We have limited network bandwidth to host externally visibility

Fine for internal-only things to be unsecured, but it's a nice excuse to learn how to use letsencrypt.
* can't do subdomains bc cookies are by-default shared

* '''Elan:''' Let's have 3 tiers re: trust:
** "Noisebridge services" - all noisebridgers depend on them. (Wiki, etc.)
** "Core services" - other services depond on them.
** "community services" - do whatever you want.

* '''Erikk:''' Is there a list of our hardware specs?
** Let's do this once a month ("office hours") (Naomi: "with pizza?")

* '''Erikk:'''
** Need backups, data (esp wiki data) is critical. Can't imagine losing that.
** VM rancher
** Proxmox hypervisor, with terraform provisioning.

* '''John:''' "The only way you know you have backups is if you can use them in anger"
* '''Loren:''' That's how we can populate a staging/test env.
* '''Elan:''' Would love if we can save this and serve a copy from the nb local network, if the public wiki is down.
* '''Naomi:''' I use the api to make a backup 1/hour.
** https://claude.ai/public/artifacts/76db8105-55f1-4c1c-b1af-33fc98047ff2

* '''Peter:''' autoschematic as a tool for testing deployments.

NoiseGarden

2026-02-07T08:16:59Z

ElanHR: /* State of Things */

NoiseGarden is a [https://en.wikipedia.org/wiki/Server_farm server farm] but small and unprofessional - hence a garden! 💻🪴

[[File:NoiseGarden Cluster.png|400px|thumb|right|NoiseGarden Cluster as of 2025-10-15]]

== State of Things ==

[[File:Nb_infra.png|800px|thumb|none|Noisebridge infrastructure in a nutshell (per Sophia)]]

== Design ==

== Components ==

=== Hardware ===
==== Networking ====

* 1x (finicky) [https://store.ui.com/us/en/products/er-4 '''EdgeRouter4''']: Has mysteriously gone offline and required a manual power cycle.
* 1x '''1Gib Managed Switch w/ 8x PoE ports''' each rated up to 30w. Since it is manage we can remotely power cycles the Pis by manually disabling/re-enabling power to specific ports.

==== Nodes ====
* 5x '''Raspberry Pi 5'''s (<code>berry{0...4}.garden</code>):
* 1x '''ThinkCenter''' (<code>sputnik.garden</code>):
* 1x '''RasPi CM5''' (<code>ducky.garden</code>): Primarily used to run bootstrapping cluster
* '''[[NoiseGarden/Barry|Barry]]''' (<code>barry.garden</code>): Used to bridge our cluster across the digital/biological divide allowing us access to the collective consciousness field
* 1x intel PC + old GPU(<code>ml2.garden</code>):
* ...many more?

=== Software Stack ===
==== Kubernetes ====

Working

==== Ceph ====

Working.

Details:
* 5 OSDs
* Currently 2 pools:
** 3x replication
** no-replication

==== Git / Forgejo ====

Working.

Two instances:
* <code>ducky.garden:3000</code> - used for bootstrapping k8s cluster (mirrored on <code>git.garden</code>
* <code>git.garden</code> - hosted on k8s, used for general git repos.

==== ArgoCD ====

Working: Currently using app-of-apps approach but would like to try converting these to ApplicationSets.

TODO:Add documentation

==== PiHole ====

Somewhat working.

==== netboot.xyz ====

Somewhat working

==== KeyCloak ====

TODO

==== MediaWiki ====

TODO

==== Package Mirrors ====

TODO

NoiseGarden

2026-02-07T08:16:46Z

ElanHR: Added a "State of Things" section

NoiseGarden is a [https://en.wikipedia.org/wiki/Server_farm server farm] but small and unprofessional - hence a garden! 💻🪴

[[File:NoiseGarden Cluster.png|400px|thumb|right|NoiseGarden Cluster as of 2025-10-15]]

== State of Things ==

[[File:Nb_infra.png|800px|thumb|none|Noisebridge infrastructure in a nutshell]]

== Design ==

== Components ==

=== Hardware ===
==== Networking ====

* 1x (finicky) [https://store.ui.com/us/en/products/er-4 '''EdgeRouter4''']: Has mysteriously gone offline and required a manual power cycle.
* 1x '''1Gib Managed Switch w/ 8x PoE ports''' each rated up to 30w. Since it is manage we can remotely power cycles the Pis by manually disabling/re-enabling power to specific ports.

==== Nodes ====
* 5x '''Raspberry Pi 5'''s (<code>berry{0...4}.garden</code>):
* 1x '''ThinkCenter''' (<code>sputnik.garden</code>):
* 1x '''RasPi CM5''' (<code>ducky.garden</code>): Primarily used to run bootstrapping cluster
* '''[[NoiseGarden/Barry|Barry]]''' (<code>barry.garden</code>): Used to bridge our cluster across the digital/biological divide allowing us access to the collective consciousness field
* 1x intel PC + old GPU(<code>ml2.garden</code>):
* ...many more?

=== Software Stack ===
==== Kubernetes ====

Working

==== Ceph ====

Working.

Details:
* 5 OSDs
* Currently 2 pools:
** 3x replication
** no-replication

==== Git / Forgejo ====

Working.

Two instances:
* <code>ducky.garden:3000</code> - used for bootstrapping k8s cluster (mirrored on <code>git.garden</code>
* <code>git.garden</code> - hosted on k8s, used for general git repos.

==== ArgoCD ====

Working: Currently using app-of-apps approach but would like to try converting these to ApplicationSets.

TODO:Add documentation

==== PiHole ====

Somewhat working.

==== netboot.xyz ====

Somewhat working

==== KeyCloak ====

TODO

==== MediaWiki ====

TODO

==== Package Mirrors ====

TODO

File:Nb infra.png

2026-02-07T05:37:23Z

ElanHR:

Discussion Meeting Notes Template

2026-01-28T04:16:13Z

ElanHR: reformats discussion items

<div style="background-color:#ddd8;border:3px dashed #3338;padding:3px;">
{{template/meeting}}




*Live notes
**https://pad.riseup.net/p/nbmeeting
*Virtual Meeting (jitsi mic/cam off by default)
**https://meet.jit.si/noisebridge — NOTE: Someone must log in with Google/Facebook/GitHub to start the meeting. Everyone else can join the meeting without logging into anything. ([https://jitsi.org/blog/authentication-on-meet-jit-si/ Blame Jitsi])
**Or, if it's ever revived: https://jitsi.noisebridge.io/hackitorium#config.startWithAudioMuted=true&config.startWithVideoMuted=true&userInfo.displayName=%22n00b%22
** Update last meeting: https://www.noisebridge.net/index.php?title=Last_meeting&redirect=no
** Update next meeting: https://www.noisebridge.net/index.php?title=Next_meeting&redirect=no

<code>Only after finishing notes, writing summary, uploading summary to discord/email. REMOVE ME (and above).</code></div>
---
</div>










{{meetings2026}}

These are the notes from the [https://www.noisebridge.net/wiki/Category:Meeting_Notes The XXXth Meeting of Noisebridge].

{|class="wikitable" style="text: left;"
! style="text-align:left;"| Date
| 2026 mm dd UPDATE DATE
|-
! Note-taker[s]
| PUT YOUR NAME HERE
|-
! Moderator[s]
| PUT THEIR NAME HERE
|}



{|class="wikitable"
| [[Meeting_Notes_2025 MONTH DAY|Previous Meeting]] {{last meeting}}
| [[Meeting_Notes_2025 MONTH DAY|Next Meeting]] {{next meeting}}
|}



* '''One or two bullet points of high-level meeting summary.'''

== Meeting Summary ==



* Announcements:
* Consensus Items:
* Discussion Items:

= Introductions =


= Short announcements and events =





= Excellence =
'''Our One Rule is to Be Excellent to Each Other.'''


What does that mean? Please see our page on excellence https://www.noisebridge.net/wiki/Excellence!

== Anti-Harassment Policy & Community Standards of Excellence ==
Noisebridge has an [[Anti-Harassment Policy]]!

Everyone is expected to follow the Anti-Harassment Policy, please familiarize yourself with it.)

For approachable & specific guidelines see: [[Community Standards]]



Please note: '''https://safespace.noisebridge.net/ is one way to quickly raise issues which will be seen by people in Discord.'''

== Brief Kudos ==


= Big C Consensus Items =


== [[ Consensus Items ]] ==


= Discussion Items =

== 1: [topic] ==
{{DiscussionItem|
| topic = <PUT_TOPIC_NAME_HERE>
| raised_by = <PUT_NOISEBRIDGER_ALIAS_HERE>
| seeking = decision/outcome/advice/[?]
}}

== 2: [topic] ==
{{DiscussionItem|
| topic = <PUT_TOPIC_NAME_HERE>
| raised_by = <PUT_NOISEBRIDGER_ALIAS_HERE>
| seeking = decision/outcome/advice/[?]
}}

== 3: [topic] ==
{{DiscussionItem|
| topic = <PUT_TOPIC_NAME_HERE>
| raised_by = <PUT_NOISEBRIDGER_ALIAS_HERE>
| seeking = decision/outcome/advice/[?]
}}

== [num]: [topic-short] ==
{{DiscussionItem|
| topic = <PUT_TOPIC_NAME_HERE>
| raised_by = <PUT_NOISEBRIDGER_ALIAS_HERE>
| seeking = decision/outcome/advice/[?]
}}

...Copy/Paste more discussion items as needed...

= Do-ocratic Task Board =
Participation also means doing stuff to contribute to the space. Propose new tasks or pick some tasks from [https://github.com/noisebridge/buildout-capp Github], from what needs to be done around you, or whatever, and see if someone will sign up to work on that task. Anyone can sign up and it's a great way to show you are contributing!

* What wiki pages need updating? What new wiki pages do we need? Discovered from the meeting.

= End of Meeting =





















[[Category:Meeting Notes]]

User talk:Dataduke

2026-01-23T23:55:37Z

ElanHR: Welcome!

User:Dataduke

2026-01-23T23:55:37Z

ElanHR: Creating user page for new user.

Benjamin has a long-standing background in software engineering. He studied Business Information Systems and went on to work as both a consultant and developer. In his spare time, he taught at five universities and founded several user groups in Germany, as well as run multiple conference series - serving in roles such as organization team lead, board chair, board member, content track lead, speaker, and workshop trainer.

He has delivered talks and keynotes in 19 countries and has been recognized by Oracle seven times as an ACE, Groundbreaker, and Developer Champion.

Beyond engineering, Benjamin built two consulting offices from the ground up, growing them to 18 employees, and founded a small startup that he later sold.

In 2023, he began traveling to San Francisco more frequently as client projects emerged, alongside a personal relationship. Since then, he has been an active member of the San Francisco Java Users Group team.

Next meeting

2026-01-15T08:30:01Z

ElanHR: Updated redirect and added 2026 items

#redirect [[Meeting Notes 2026 01 20]]

<hr>
<div style="background-color:#ddd8;border:3px dashed #3338;padding:3px;">
<code><nowiki>{{next meeting}}</nowiki></code> to include link to this edit-able redirect page.

[[Special:PrefixIndex/Meeting_Notes_2026_]]:
{{Special:PrefixIndex/Meeting_Notes_2026_}}

[[Special:PrefixIndex/Meeting_Notes_2025_]]:
{{Special:PrefixIndex/Meeting_Notes_2025_}}

[[Special:PrefixIndex/Meeting_Notes_2024_]]:
{{Special:PrefixIndex/Meeting_Notes_2024_}}

{{:wikiwg/header}}

{{meetings}}
</div>

Last meeting

2026-01-15T08:29:34Z

ElanHR: Updated redirect and added 2026 items

#redirect [[Meeting Notes 2026 01 13]]

<hr>
<div style="background-color:#ddd8;border:3px dashed #3338;padding:3px;">

<code><nowiki>{{last meeting}}</nowiki></code> to include link to this edit-able redirect page.

[[Special:PrefixIndex/Meeting_Notes_2026_]]:
{{Special:PrefixIndex/Meeting_Notes_2026_}}

[[Special:PrefixIndex/Meeting_Notes_2025_]]:
{{Special:PrefixIndex/Meeting_Notes_2025_}}

[[Special:PrefixIndex/Meeting_Notes_2024_]]:
{{Special:PrefixIndex/Meeting_Notes_2024_}}

{{:wikiwg/header}}

{{meetings}}
</div>

Discussion Meeting Notes Template

2026-01-15T08:14:44Z

ElanHR: Removes duplicate meeting Template

<div style="background-color:#ddd8;border:3px dashed #3338;padding:3px;">
{{template/meeting}}




*Live notes
**https://pad.riseup.net/p/nbmeeting
*Virtual Meeting (jitsi mic/cam off by default)
**https://meet.jit.si/noisebridge — NOTE: Someone must log in with Google/Facebook/GitHub to start the meeting. Everyone else can join the meeting without logging into anything. ([https://jitsi.org/blog/authentication-on-meet-jit-si/ Blame Jitsi])
**Or, if it's ever revived: https://jitsi.noisebridge.io/hackitorium#config.startWithAudioMuted=true&config.startWithVideoMuted=true&userInfo.displayName=%22n00b%22
** Update last meeting: https://www.noisebridge.net/index.php?title=Last_meeting&redirect=no
** Update next meeting: https://www.noisebridge.net/index.php?title=Next_meeting&redirect=no

<code>Only after finishing notes, writing summary, uploading summary to discord/email. REMOVE ME (and above).</code></div>
---
</div>










{{meetings2026}}

These are the notes from the [https://www.noisebridge.net/wiki/Category:Meeting_Notes The XXXth Meeting of Noisebridge].

{|class="wikitable" style="text: left;"
! style="text-align:left;"| Date
| 2026 mm dd UPDATE DATE
|-
! Note-taker[s]
| PUT YOUR NAME HERE
|-
! Moderator[s]
| PUT THEIR NAME HERE
|}



{|class="wikitable"
| [[Meeting_Notes_2025 MONTH DAY|Previous Meeting]] {{last meeting}}
| [[Meeting_Notes_2025 MONTH DAY|Next Meeting]] {{next meeting}}
|}



* '''One or two bullet points of high-level meeting summary.'''

== Meeting Summary ==



* Announcements:
* Consensus Items:
* Discussion Items:

= Introductions =


= Short announcements and events =





= Excellence =
'''Our One Rule is to Be Excellent to Each Other.'''


What does that mean? Please see our page on excellence https://www.noisebridge.net/wiki/Excellence!

== Anti-Harassment Policy & Community Standards of Excellence ==
Noisebridge has an [[Anti-Harassment Policy]]!

Everyone is expected to follow the Anti-Harassment Policy, please familiarize yourself with it.)

For approachable & specific guidelines see: [[Community Standards]]



Please note: '''https://safespace.noisebridge.net/ is one way to quickly raise issues which will be seen by people in Discord.'''

== Brief Kudos ==


= Zoning & Permitting Standing Item =


= Big C Consensus Items =


== [[ Consensus Items ]] ==


= Discussion Items =
== Template... [num]: [topic-short] ==
{{DiscussionItem|
| topic = <PUT_TOPIC_NAME_HERE>
| raised_by = <PUT_NOISEBRIDGER_ALIAS_HERE>
| seeking = decision/outcome/advice/[?]
}}

== (discussion item) 1: [topic] ==
{{DiscussionItem|
| topic = <PUT_TOPIC_NAME_HERE>
| raised_by = <PUT_NOISEBRIDGER_ALIAS_HERE>
| seeking = decision/outcome/advice/[?]
}}

== (discussion item) 2: [topic] ==
{{DiscussionItem|
| topic = <PUT_TOPIC_NAME_HERE>
| raised_by = <PUT_NOISEBRIDGER_ALIAS_HERE>
| seeking = decision/outcome/advice/[?]
}}

== (discussion item) 3: [topic] ==
{{DiscussionItem|
| topic = <PUT_TOPIC_NAME_HERE>
| raised_by = <PUT_NOISEBRIDGER_ALIAS_HERE>
| seeking = decision/outcome/advice/[?]
}}

...Copy/Paste more discussion items as needed...

= Do-ocratic Task Board =
Participation also means doing stuff to contribute to the space. Propose new tasks or pick some tasks from [https://github.com/noisebridge/buildout-capp Github], from what needs to be done around you, or whatever, and see if someone will sign up to work on that task. Anyone can sign up and it's a great way to show you are contributing!

* What wiki pages need updating? What new wiki pages do we need? Discovered from the meeting.

= End of Meeting =





















[[Category:Meeting Notes]]

Discussion Meeting Notes Template

2026-01-15T08:13:59Z

ElanHR: Updated instructions to match Meeting Notes Template

<div style="background-color:#ddd8;border:3px dashed #3338;padding:3px;">
{{template/meeting}}




*Live notes
**https://pad.riseup.net/p/nbmeeting
*Virtual Meeting (jitsi mic/cam off by default)
**https://meet.jit.si/noisebridge — NOTE: Someone must log in with Google/Facebook/GitHub to start the meeting. Everyone else can join the meeting without logging into anything. ([https://jitsi.org/blog/authentication-on-meet-jit-si/ Blame Jitsi])
**Or, if it's ever revived: https://jitsi.noisebridge.io/hackitorium#config.startWithAudioMuted=true&config.startWithVideoMuted=true&userInfo.displayName=%22n00b%22
** Update last meeting: https://www.noisebridge.net/index.php?title=Last_meeting&redirect=no
** Update next meeting: https://www.noisebridge.net/index.php?title=Next_meeting&redirect=no

<code>Only after finishing notes, writing summary, uploading summary to discord/email. REMOVE ME (and above).</code></div>
---

{{meetings2026}}

</div>










{{meetings2026}}

These are the notes from the [https://www.noisebridge.net/wiki/Category:Meeting_Notes The XXXth Meeting of Noisebridge].

{|class="wikitable" style="text: left;"
! style="text-align:left;"| Date
| 2026 mm dd UPDATE DATE
|-
! Note-taker[s]
| PUT YOUR NAME HERE
|-
! Moderator[s]
| PUT THEIR NAME HERE
|}



{|class="wikitable"
| [[Meeting_Notes_2025 MONTH DAY|Previous Meeting]] {{last meeting}}
| [[Meeting_Notes_2025 MONTH DAY|Next Meeting]] {{next meeting}}
|}



* '''One or two bullet points of high-level meeting summary.'''

== Meeting Summary ==



* Announcements:
* Consensus Items:
* Discussion Items:

= Introductions =


= Short announcements and events =





= Excellence =
'''Our One Rule is to Be Excellent to Each Other.'''


What does that mean? Please see our page on excellence https://www.noisebridge.net/wiki/Excellence!

== Anti-Harassment Policy & Community Standards of Excellence ==
Noisebridge has an [[Anti-Harassment Policy]]!

Everyone is expected to follow the Anti-Harassment Policy, please familiarize yourself with it.)

For approachable & specific guidelines see: [[Community Standards]]



Please note: '''https://safespace.noisebridge.net/ is one way to quickly raise issues which will be seen by people in Discord.'''

== Brief Kudos ==


= Zoning & Permitting Standing Item =


= Big C Consensus Items =


== [[ Consensus Items ]] ==


= Discussion Items =
== Template... [num]: [topic-short] ==
{{DiscussionItem|
| topic = <PUT_TOPIC_NAME_HERE>
| raised_by = <PUT_NOISEBRIDGER_ALIAS_HERE>
| seeking = decision/outcome/advice/[?]
}}

== (discussion item) 1: [topic] ==
{{DiscussionItem|
| topic = <PUT_TOPIC_NAME_HERE>
| raised_by = <PUT_NOISEBRIDGER_ALIAS_HERE>
| seeking = decision/outcome/advice/[?]
}}

== (discussion item) 2: [topic] ==
{{DiscussionItem|
| topic = <PUT_TOPIC_NAME_HERE>
| raised_by = <PUT_NOISEBRIDGER_ALIAS_HERE>
| seeking = decision/outcome/advice/[?]
}}

== (discussion item) 3: [topic] ==
{{DiscussionItem|
| topic = <PUT_TOPIC_NAME_HERE>
| raised_by = <PUT_NOISEBRIDGER_ALIAS_HERE>
| seeking = decision/outcome/advice/[?]
}}

...Copy/Paste more discussion items as needed...

= Do-ocratic Task Board =
Participation also means doing stuff to contribute to the space. Propose new tasks or pick some tasks from [https://github.com/noisebridge/buildout-capp Github], from what needs to be done around you, or whatever, and see if someone will sign up to work on that task. Anyone can sign up and it's a great way to show you are contributing!

* What wiki pages need updating? What new wiki pages do we need? Discovered from the meeting.

= End of Meeting =





















[[Category:Meeting Notes]]

Meeting Notes Template

2026-01-15T08:12:43Z

ElanHR: Fixes an non-terminated <div>

<div style="background-color:#ddd8;border:3px dashed #3338;padding:3px;">
{{template/meeting}}

* Click [https://www.noisebridge.net/index.php?title=Meeting_Notes_Template&action=edit Edit] in the MediaWiki top bar (or [https://www.noisebridge.net/index.php?title=Meeting_Notes_Template&action=edit&preview=no Edit without preview]) and copy all the source code into the new meeting notes page.
* Delete this paragraph from the actual notes. (Keep in template, & in live copy for next iteration)

*Live notes
**https://pad.riseup.net/p/nbmeeting
*Virtual Meeting (jitsi mic/cam off by default)
**https://meet.jit.si/noisebridge — NOTE: Someone must log in with Google/Facebook/GitHub to start the meeting. Everyone else can join the meeting without logging into anything. ([https://jitsi.org/blog/authentication-on-meet-jit-si/ Blame Jitsi])
**Or, if it's ever revived: https://jitsi.noisebridge.io/hackitorium#config.startWithAudioMuted=true&config.startWithVideoMuted=true&userInfo.displayName=%22n00b%22

---

</div>










{{meetings2026}}

These are the notes from the [https://www.noisebridge.net/wiki/Category:Meeting_Notes The XXXth Meeting of Noisebridge].

{|class="wikitable" style="text: left;"
! style="text-align:left;"| Date
| 2026 mm dd UPDATE DATE
|-
! Note-taker[s]
| PUT YOUR NAME HERE
|-
! Moderator[s]
| PUT THEIR NAME HERE
|}



{|class="wikitable"
| [[Meeting_Notes_2026 MONTH DAY|Previous Meeting]] {{last meeting}}
| [[Meeting_Notes_2026 MONTH DAY|Next Meeting]] {{next meeting}}
|}



== Meeting Summary ==



* Fundraising Update:
* Announcements:
* Finances:
* New members:
* New associates:
* Consensus Items:
* Discussion Items:

= Introductions =


= Short announcements and events =





= Excellence =
'''Our One Rule is to Be Excellent to Each Other.'''

What does that mean? Please see our page on [[Excellence]] !



== Anti-Harassment Policy & Community Standards of Excellence ==
Noisebridge has an [[Anti-Harassment Policy]]!

Everyone is expected to follow the Anti-Harassment Policy, please familiarize yourself with it.)

For approachable & specific guidelines see: [[Community Standards]]



Please note: '''https://safespace.noisebridge.net/ is one way to quickly raise issues which will be seen by people in Discord.'''

== Brief Kudos ==


= Zoning, Permitting, & Improvements -- Standing Item =


= [[Guild]]s & [[WG]]s =
''Reports from guilds & working groups. Updates! Events! Requests!''


= New Members/Associate Members =


= Financial Report (first Tuesday of month only) =
'''Anarchist societies under a capitalist state need money to survive and thrive, yo.'''

* Monthly revenue, expenses. Big projects. Big fundraising events. Reserves in bank.
* Any other details by those participating in handling our financials
* The latest financial reports from the treasurer are available at https://noisebridge.net/wiki/Finances

== Spending Needs ==




== Fundraising Update ==


= Big C Consensus Items =


== [[ Consensus Items ]] ==


= Discussion Items =
== Template... [num]: [topic-short] ==
{{DiscussionItem|
| topic = <PUT_TOPIC_NAME_HERE>
| raised_by = <PUT_NOISEBRIDGER_ALIAS_HERE>
| seeking = decision/outcome/advice/[?]
}}

== (discussion item) 1: [topic] ==
{{DiscussionItem|
| topic = <PUT_TOPIC_NAME_HERE>
| raised_by = <PUT_NOISEBRIDGER_ALIAS_HERE>
| seeking = decision/outcome/advice/[?]
}}

== (discussion item) 2: [topic] ==
{{DiscussionItem|
| topic = <PUT_TOPIC_NAME_HERE>
| raised_by = <PUT_NOISEBRIDGER_ALIAS_HERE>
| seeking = decision/outcome/advice/[?]
}}

== (discussion item) 3: [topic] ==
{{DiscussionItem|
| topic = <PUT_TOPIC_NAME_HERE>
| raised_by = <PUT_NOISEBRIDGER_ALIAS_HERE>
| seeking = decision/outcome/advice/[?]
}}

...Copy/Paste more discussion items as needed...

= Do-ocratic Task Board =
Participation also means doing stuff to contribute to the space. Propose new tasks or pick some tasks from [https://github.com/noisebridge/buildout-capp Github], from what needs to be done around you, or whatever, and see if someone will sign up to work on that task. Anyone can sign up and it's a great way to show you are contributing!

* What wiki pages need updating? What new wiki pages do we need? Discovered from the meeting.

= End of Meeting =





















[[Category:Meeting Notes]]

Discussion Meeting Notes Template

2026-01-15T08:06:16Z

ElanHR: Updated meeting template to reflect 2026 and to use new DiscussionItem template. Also moved instructions to use wikitext comments.

<div style="background-color:#ddd8;border:3px dashed #3338;padding:3px;">
{{template/meeting}}




*Live notes
**https://pad.riseup.net/p/nbmeeting
*Virtual Meeting (jitsi mic/cam off by default)
**https://meet.jit.si/noisebridge — NOTE: Someone must log in with Google/Facebook/GitHub to start the meeting. Everyone else can join the meeting without logging into anything. ([https://jitsi.org/blog/authentication-on-meet-jit-si/ Blame Jitsi])
**Or, if it's ever revived: https://jitsi.noisebridge.io/hackitorium#config.startWithAudioMuted=true&config.startWithVideoMuted=true&userInfo.displayName=%22n00b%22
** Update last meeting: https://www.noisebridge.net/index.php?title=Last_meeting&redirect=no
** Update next meeting: https://www.noisebridge.net/index.php?title=Next_meeting&redirect=no

<code>Only after finishing notes, writing summary, uploading summary to discord/email. REMOVE ME (and above).</code></div>
---

{{meetings2026}}

These are the notes from the [https://www.noisebridge.net/wiki/Category:Meeting_Notes The XXXth Meeting of Noisebridge].

-> Date / Note-taker / Moderator // Prev + Next links / Summary

UPDATE meeting number above where it says the XXXth meeting of Noisebridge (by checking previous meetings)

{|class="wikitable" style="text: left;"
! style="text-align:left;"| Date
| 2026 mm dd UPDATE DATE
|-
! Note-taker[s]
| PUT YOUR NAME HERE
|-
! Moderator[s]
| PUT THEIR NAME HERE
|}



{|class="wikitable"
| [[Meeting_Notes_2025 MONTH DAY|Previous Meeting]] {{last meeting}}
| [[Meeting_Notes_2025 MONTH DAY|Next Meeting]] {{next meeting}}
|}



* '''One or two bullet points of high-level meeting summary.'''

== Meeting Summary ==



* Announcements:
* Consensus Items:
* Discussion Items:

= Introductions =


= Short announcements and events =





= Excellence =
'''Our One Rule is to Be Excellent to Each Other.'''


What does that mean? Please see our page on excellence https://www.noisebridge.net/wiki/Excellence!

== Anti-Harassment Policy & Community Standards of Excellence ==
Noisebridge has an [[Anti-Harassment Policy]]!

Everyone is expected to follow the Anti-Harassment Policy, please familiarize yourself with it.)

For approachable & specific guidelines see: [[Community Standards]]



Please note: '''https://safespace.noisebridge.net/ is one way to quickly raise issues which will be seen by people in Discord.'''

== Brief Kudos ==


= Zoning & Permitting Standing Item =


= Big C Consensus Items =


== [[ Consensus Items ]] ==


= Discussion Items =
== Template... [num]: [topic-short] ==
{{DiscussionItem|
| topic = <PUT_TOPIC_NAME_HERE>
| raised_by = <PUT_NOISEBRIDGER_ALIAS_HERE>
| seeking = decision/outcome/advice/[?]
}}

== (discussion item) 1: [topic] ==
{{DiscussionItem|
| topic = <PUT_TOPIC_NAME_HERE>
| raised_by = <PUT_NOISEBRIDGER_ALIAS_HERE>
| seeking = decision/outcome/advice/[?]
}}

== (discussion item) 2: [topic] ==
{{DiscussionItem|
| topic = <PUT_TOPIC_NAME_HERE>
| raised_by = <PUT_NOISEBRIDGER_ALIAS_HERE>
| seeking = decision/outcome/advice/[?]
}}

== (discussion item) 3: [topic] ==
{{DiscussionItem|
| topic = <PUT_TOPIC_NAME_HERE>
| raised_by = <PUT_NOISEBRIDGER_ALIAS_HERE>
| seeking = decision/outcome/advice/[?]
}}

...Copy/Paste more discussion items as needed...

= Do-ocratic Task Board =
Participation also means doing stuff to contribute to the space. Propose new tasks or pick some tasks from [https://github.com/noisebridge/buildout-capp Github], from what needs to be done around you, or whatever, and see if someone will sign up to work on that task. Anyone can sign up and it's a great way to show you are contributing!

* What wiki pages need updating? What new wiki pages do we need? Discovered from the meeting.

= End of Meeting =





















[[Category:Meeting Notes]]

Meeting Notes Template

2026-01-15T08:02:19Z

ElanHR: Updated meeting template to reflect 2026 and to use new DiscussionItem template. Also moved instructions to use wikitext comments.

<div style="background-color:#ddd8;border:3px dashed #3338;padding:3px;">
{{template/meeting}}

* Click [https://www.noisebridge.net/index.php?title=Meeting_Notes_Template&action=edit Edit] in the MediaWiki top bar (or [https://www.noisebridge.net/index.php?title=Meeting_Notes_Template&action=edit&preview=no Edit without preview]) and copy all the source code into the new meeting notes page.
* Delete this paragraph from the actual notes. (Keep in template, & in live copy for next iteration)
---

*Live notes
**https://pad.riseup.net/p/nbmeeting
*Virtual Meeting (jitsi mic/cam off by default)
**https://meet.jit.si/noisebridge — NOTE: Someone must log in with Google/Facebook/GitHub to start the meeting. Everyone else can join the meeting without logging into anything. ([https://jitsi.org/blog/authentication-on-meet-jit-si/ Blame Jitsi])
**Or, if it's ever revived: https://jitsi.noisebridge.io/hackitorium#config.startWithAudioMuted=true&config.startWithVideoMuted=true&userInfo.displayName=%22n00b%22

---











{{meetings2026}}

These are the notes from the [https://www.noisebridge.net/wiki/Category:Meeting_Notes The XXXth Meeting of Noisebridge].

{|class="wikitable" style="text: left;"
! style="text-align:left;"| Date
| 2026 mm dd UPDATE DATE
|-
! Note-taker[s]
| PUT YOUR NAME HERE
|-
! Moderator[s]
| PUT THEIR NAME HERE
|}



{|class="wikitable"
| [[Meeting_Notes_2026 MONTH DAY|Previous Meeting]] {{last meeting}}
| [[Meeting_Notes_2026 MONTH DAY|Next Meeting]] {{next meeting}}
|}



== Meeting Summary ==



* Fundraising Update:
* Announcements:
* Finances:
* New members:
* New associates:
* Consensus Items:
* Discussion Items:

= Introductions =


= Short announcements and events =





= Excellence =
'''Our One Rule is to Be Excellent to Each Other.'''

What does that mean? Please see our page on [[Excellence]] !



== Anti-Harassment Policy & Community Standards of Excellence ==
Noisebridge has an [[Anti-Harassment Policy]]!

Everyone is expected to follow the Anti-Harassment Policy, please familiarize yourself with it.)

For approachable & specific guidelines see: [[Community Standards]]



Please note: '''https://safespace.noisebridge.net/ is one way to quickly raise issues which will be seen by people in Discord.'''

== Brief Kudos ==


= Zoning, Permitting, & Improvements -- Standing Item =


= [[Guild]]s & [[WG]]s =
''Reports from guilds & working groups. Updates! Events! Requests!''


= New Members/Associate Members =


= Financial Report (first Tuesday of month only) =
'''Anarchist societies under a capitalist state need money to survive and thrive, yo.'''

* Monthly revenue, expenses. Big projects. Big fundraising events. Reserves in bank.
* Any other details by those participating in handling our financials
* The latest financial reports from the treasurer are available at https://noisebridge.net/wiki/Finances

== Spending Needs ==




== Fundraising Update ==


= Big C Consensus Items =


== [[ Consensus Items ]] ==


= Discussion Items =
== Template... [num]: [topic-short] ==
{{DiscussionItem|
| topic = <PUT_TOPIC_NAME_HERE>
| raised_by = <PUT_NOISEBRIDGER_ALIAS_HERE>
| seeking = decision/outcome/advice/[?]
}}

== (discussion item) 1: [topic] ==
{{DiscussionItem|
| topic = <PUT_TOPIC_NAME_HERE>
| raised_by = <PUT_NOISEBRIDGER_ALIAS_HERE>
| seeking = decision/outcome/advice/[?]
}}

== (discussion item) 2: [topic] ==
{{DiscussionItem|
| topic = <PUT_TOPIC_NAME_HERE>
| raised_by = <PUT_NOISEBRIDGER_ALIAS_HERE>
| seeking = decision/outcome/advice/[?]
}}

== (discussion item) 3: [topic] ==
{{DiscussionItem|
| topic = <PUT_TOPIC_NAME_HERE>
| raised_by = <PUT_NOISEBRIDGER_ALIAS_HERE>
| seeking = decision/outcome/advice/[?]
}}

...Copy/Paste more discussion items as needed...

= Do-ocratic Task Board =
Participation also means doing stuff to contribute to the space. Propose new tasks or pick some tasks from [https://github.com/noisebridge/buildout-capp Github], from what needs to be done around you, or whatever, and see if someone will sign up to work on that task. Anyone can sign up and it's a great way to show you are contributing!

* What wiki pages need updating? What new wiki pages do we need? Discovered from the meeting.

= End of Meeting =





















[[Category:Meeting Notes]]

Meeting Notes Template

2026-01-15T07:39:50Z

ElanHR: Updated meeting template to reflect 2026 and to use new DiscussionItem template. Also moved instructions to use wikitext comments.

<div style="background-color:#ddd8;border:3px dashed #3338;padding:3px;">
{{template/meeting}}

* Click [https://www.noisebridge.net/index.php?title=Meeting_Notes_Template&action=edit Edit] in the MediaWiki top bar (or [https://www.noisebridge.net/index.php?title=Meeting_Notes_Template&action=edit&preview=no Edit without preview]) and copy all the source code into the new meeting notes page.
* Delete this paragraph from the actual notes. (Keep in template, & in live copy for next iteration)
---

*Live notes
**https://pad.riseup.net/p/nbmeeting
*Virtual Meeting (jitsi mic/cam off by default)
**https://meet.jit.si/noisebridge — NOTE: Someone must log in with Google/Facebook/GitHub to start the meeting. Everyone else can join the meeting without logging into anything. ([https://jitsi.org/blog/authentication-on-meet-jit-si/ Blame Jitsi])
**Or, if it's ever revived: https://jitsi.noisebridge.io/hackitorium#config.startWithAudioMuted=true&config.startWithVideoMuted=true&userInfo.displayName=%22n00b%22
** Update last meeting: https://www.noisebridge.net/index.php?title=Last_meeting&redirect=no
** Update next meeting: https://www.noisebridge.net/index.php?title=Next_meeting&redirect=no

---









{{meetings2026}}

These are the notes from the [https://www.noisebridge.net/wiki/Category:Meeting_Notes The XXXth Meeting of Noisebridge].

{|class="wikitable" style="text: left;"
! style="text-align:left;"| Date
| 2026 mm dd UPDATE DATE
|-
! Note-takers
| PUT YOUR NAME HERE
|-
! Moderators
| PUT THEIR NAME HERE
|}



{|class="wikitable"
| [[Meeting_Notes_2025 MONTH DAY|Previous Meeting]] {{last meeting}}
| [[Meeting_Notes_2025 MONTH DAY|Next Meeting]] {{next meeting}}
|}



== Meeting Summary ==



* Fundraising Update:
* Announcements:
* Finances:
* New members:
* New associates:
* Consensus Items:
* Discussion Items:

= Introductions =


= Short announcements and events =





= Excellence =
'''Our One Rule is to Be Excellent to Each Other.'''

What does that mean? Please see our page on [[Excellence]] !



== Anti-Harassment Policy & Community Standards of Excellence ==
Noisebridge has an [[Anti-Harassment Policy]]!

Everyone is expected to follow the Anti-Harassment Policy, please familiarize yourself with it.)

For approachable & specific guidelines see: [[Community Standards]]



Please note: '''https://safespace.noisebridge.net/ is one way to quickly raise issues which will be seen by people in Discord.'''

== Brief Kudos ==


= Zoning, Permitting, & Improvements -- Standing Item =


= [[Guild]]s & [[WG]]s =
''Reports from guilds & working groups. Updates! Events! Requests!''


= New Members/Associate Members =


= Financial Report (first Tuesday of month only) =
'''Anarchist societies under a capitalist state need money to survive and thrive, yo.'''

* Monthly revenue, expenses. Big projects. Big fundraising events. Reserves in bank.
* Any other details by those participating in handling our financials
* The latest financial reports from the treasurer are available at https://noisebridge.net/wiki/Finances

== Spending Needs ==




== Fundraising Update ==


= Big C Consensus Items =


== [[ Consensus Items ]] ==


= Discussion Items =
== Template... [num]: [topic-short] ==
{{DiscussionItem|
| topic = <PUT_TOPIC_NAME_HERE>
| raised_by = <PUT_NOISEBRIDGER_ALIAS_HERE>
| seeking = decision/outcome/advice/[?]
}}

== (discussion item) 1: [topic] ==
{{DiscussionItem|
| topic = <PUT_TOPIC_NAME_HERE>
| raised_by = <PUT_NOISEBRIDGER_ALIAS_HERE>
| seeking = decision/outcome/advice/[?]
}}

== (discussion item) 2: [topic] ==
{{DiscussionItem|
| topic = <PUT_TOPIC_NAME_HERE>
| raised_by = <PUT_NOISEBRIDGER_ALIAS_HERE>
| seeking = decision/outcome/advice/[?]
}}

== (discussion item) 3: [topic] ==
{{DiscussionItem|
| topic = <PUT_TOPIC_NAME_HERE>
| raised_by = <PUT_NOISEBRIDGER_ALIAS_HERE>
| seeking = decision/outcome/advice/[?]
}}

....Copy/Paste more discussion items as needed...

= Do-ocratic Task Board =
Participation also means doing stuff to contribute to the space. Propose new tasks or pick some tasks from [https://github.com/noisebridge/buildout-capp Github], from what needs to be done around you, or whatever, and see if someone will sign up to work on that task. Anyone can sign up and it's a great way to show you are contributing!

* What wiki pages need updating? What new wiki pages do we need? Discovered from the meeting.
= End of Meeting =





















[[Category:Meeting Notes]]

Template:2026

2026-01-15T06:54:33Z

ElanHR: Created Template:2026 using Template:2025 and find+replace

Include with: <code><nowiki>{{2026}}</nowiki></code>

==[[onlyinclude]]d==
<onlyinclude>[[Category:Y2026]]</onlyinclude>
<code><nowiki><onlyinclude>[[Category:Y2026]]</onlyinclude></nowiki></code>

==Purpose==
Alongside [[Wiki/Projects#Headerbox_template_links]], trying links for year categorization. More ways to browse, more links, easily
<noinclude>[[Category:Yearly]]</noinclude>

Template:Meetings2026

2026-01-15T06:52:19Z

ElanHR: Adding meeting template header based on Template:meetings2025 (and regex replacing 2025)

<onlyinclude>{{meetings}}
{{box3}} '''[[Meetings#2026]]''' | <small>[[Consensus]] ([[Consensus Item Drafts|D]]):</small> [[Current Consensus Items|Items]] · [[Consensus Items History|History]] | <small>[[Events]] ([[Hosting]]) — [[NB16]] | [[Maker Faire 2026]] | [[Open Sauce 2026]] </small>
|| <small>[[:Template:Meetings2026|V]] · [[:Template_Talk:Meetings2026|T]] · [[Special:EditPage/Template:Meetings2026|E]]</small>
{{boxend}}{{2026}} [[Category:Meetings/2026]]</onlyinclude>
<hr>
<div style="background-color: #dddd;">
{{linkshere}}
==Usage==
<code><nowiki>{{meetings2026}}</nowiki></code>
Generally as the first, and only header insert above the summary, [[TOC]], & meat of [[Meeting]] pages.
</div>

Meeting Notes 2026 01 13

2026-01-15T06:48:58Z

ElanHR: Adding meeting notes (using a new Discussion Item template * ooh la la *)

{{meetings2026}}

These are the notes from the [https://www.noisebridge.net/wiki/Category:Meeting_Notes The 848th Meeting of Noisebridge].

{|class="wikitable" style="text: left;"
! style="text-align:left;"| Date
| 2026 01 13
|-
! Note-takers
| We-z, Elan, Anh, Naomi
|-
! Moderators
| We-z
|}

{|class="wikitable"
| [[Meeting_Notes_2026 01 06|Previous Meeting]] {{last meeting}}
| [[Meeting_Notes_2026 01 20|Next Meeting]] {{next meeting}}
|}

* '''One or two bullet points of high-level meeting summary.'''

== Meeting Summary ==

Announcements:

* '''Global Game Jam (1/26 - 2/1)''' - talk to LX, we need volunteers!

* '''Wikipedia's 25th Birthday''' (Jan 24th SFPL main branch) [[https://en.wikipedia.org/wiki/Event:Wikipedia_25th_Birthday_Bay_Area Come hang out!]]

Discussion recap:
* Finalized decision on new member tier names! (supporting, access, and core)
* LLM usage in Noisebridge discussion
* Postmortem on last week's Elle discussion
* Proposal to improve interpersonal communications going forward. (Let's do more restorative communication!!)

= Introductions =

* '''WEZ:''' likes to learn, love love <3

* '''Anh:''' Graphic design and games

* '''Nthmost:''' turning a Rockband piano thingy into general controller

* '''Carl:''' Idk I hack on ....

* '''Jane:''' doing a lot of embroidery (hand)

* '''Zach:''' raises butterflies

* '''JD:''' teach lasers (in charge of NB ;)

* '''Elan:''' <3 wiki lover

* '''Jospeph/ Jojo:''' enjoys fashion

* '''Dean:''' Meshtastic

* '''Jawa:''' Fashion

* '''Daniel(Web):''' Jack of all trades master of none, 3d printers, is a chickenhawk.

* '''Zacchaeus:''' in search of Guix people

* '''Brad:''' into CAD / woodworking / sailing

* '''LX:''' global game jam

* '''Angelo:''' working on hardware, industrial man.

* '''Farley:''' Philosopher / ex web dev.

= Short announcements and events =

LX: '''Global Game Jam (1/26 - 2/1)''' would like volunteers to help out since it'll be big!

Elan: '''Wikipedia's 25th Birthday''' Jan 24th come hang out and celebrate Wikipedia in the SF main library (also posted in discord)
https://en.wikipedia.org/wiki/Event:Wikipedia_25th_Birthday_Bay_Area

Elan: This Saturday Eric's sister will be going through Eric's storage/workshop and see if there are any items that Noisebridge could use. I'd like to get something that is very Eric to put as a memorial next to the stairs.

= Excellence =
'''Our One Rule is to Be Excellent to Each Other.'''

'''Naomi:'''

* Positive part: showing up for the community, doing praxis!

* Negative: don't be mean, treat people how you would like to be treated

'''LX:''' Treat people how they want to be treated!

'''We-z:''' Kindness, empathy, emotional intelligence!

What does that mean? Please see our page on excellence https://www.noisebridge.net/wiki/Excellence!

== Anti-Harassment Policy & Community Standards of Excellence ==

Noisebridge has an [[Anti-Harassment Policy]] !

Everyone is expected to follow the Anti-Harassment Policy, please familiarize yourself with it.

More approachable & specific guidelines: [[Community Standards]].

https://safespace.noisebridge.net/ is one way to quickly raise issues which will be seen by people in Slack.

== Brief Kudos ==

* Naomi: Kudos to Daniel (web) for new signage

* LX: Also his new donation site!

= Zoning & Permitting Standing Item =

Matt had to submit a final letter that is bounding on final working/formatting for compliance.

Happy path = 1 week completion!!!

= Discussion Items =

== Discussion Item 1: Changing Names of Membership Tiers ==
{{DiscussionItem|
| topic = Changing Names of Membership Tiers
| raised_by = Daniel
| seeking = Final Decision
}}

Tell everyone coming in for the first time to become a supporting member!!! :D

Renaming of membership tiers to: supporting, access, and core.

...unrecorded discussions...

'''Lossy summary:''' There is discussion about the Discord poll not being unanimous around Core vs Steward but there is eventual agreement on "Core member"

== Discussion Item 2: LLMBridge ==

{{DiscussionItem|
| topic = LLMBridge
| raised_by = Elan
| seeking = Community Discussion/Decision (at some point, not this week)
}}

'''Context:''' https://www.noisebridge.net/wiki/LLMBridge

'''Elan:'''
I think it is good practice to have a policy/norm about LLM use on NB wiki and in interpersonal communication. I think there are weird issues about its usage that "I" put in the wiki article - e.g. if something is written slick, it's given authority by the reader.

I personally would like not to not see relationships at NB be mediated by LLMs

'''Michael:'''
One part of making someone a member of Sudo Room is excellence. If we use LLMs, we take away moral agency.

'''Naomi:'''
Is that what happened?

'''Elan:'''
I did not agree with how someone mediating used ChatGPT during the process and in general not disclosing LLM usage for Noisebridge interactions. It give me the ick.

'''JD:'''
Using LLMs how is it different from talking to your spouse or someone you trust for advice on a negotiation/mediation you're stumped on for reflective feedback?

'''Daniel(Web):''' '''...uncaptured discussion (sorry Daniel)...''' (extrapolated from context: we should treat Noisebridge wiki articles like one would Medium articles and attribute anything written to the original author)

'''Zackie:'''
Are you sending someone directly the output of the LLM or reading it and using your own words? I think there is a significant difference.

'''WE-Z:'''
I want to second what Daniel said earlier - i.e. treat it like Medium.com. I.e. attribute generated content solely to the person rather than the Noisebridge-voice. I think these should be e.g. Wheezy's ideas.

'''Daniel:'''
Most know the feeling of having your head wrapped around a problem - there is a feeling about figuring things out a problem and using LLM a tool. This is totally different than letting the LLM do the work for you.

'''LX:'''
Made a template for when people use LLM on the wiki disclosing use

'''Michael:'''
When people use LLM it should be up to personal use - the privacy issue is not a new issue. Data tracking issues is not new

'''Elan:'''
Agreed and makes sense. For me, it's disclosure. Disclosure solves all of the problems. Policy generating stuff, wiki articles, those things are less emotionally wrapped up. Using ungrounded input (for mediation) and treating the output as legit is not okay. The template that LX mentioned helps with these issues.

'''WEZ:'''
LLMs are excellent tools for processing personal emotions - they literally will echo what you say back tell you you're right. Personal LLMs are great.

== Discussion Item 3: Elle Decision Postmortem ==

{{DiscussionItem|
| topic = Elle Decision Postmortem
| raised_by = Elan
| seeking = Discussion
}}

'''Elan:'''
I want to voice that I think how the process to 86 Elle last week feels shitty.

'''Naomi:'''
I did not 86 her.

'''Elan:'''
What is the difference between permanent ATL and 86?

'''Zackie:'''

One difference is that you can still go to other hackerspaces - "something has to change" was the sentiment at that meeting.

'''Elan:'''
I was told part of the reason for not 86 was it would be difficult to document the reason. I feel like if behavior is unacceptable to Noisebridge we should make it an 86 and document it for future Noisebridgers.

'''WEZ:'''
Clearly this person is a manipulator - can we ask this person to stop being political and trying to power grab? If we are bothered by their behavior, can we come together and ask whether or not we should 86? It should be egalitarian and not dictatorial - it should include everyone. David for instance last week was caught off guard.

'''Naomi:'''
That is why I wrote the [[Anarchy Paralysis]] page.

'''JD:'''
I thought it was LLM! (*joking tone*)

'''Naomi:'''
It's not.

'''Elan:'''
One of the stated reasons for the ban is policy injection. ...something... I trust JD a lot with all things laser-related but he is not the king of the laser.

'''Naomi:'''
Why are we talking about guilds?

'''Elan:'''
Because one of the stated reasons for the decision was power grabbing behavior. People are being accused of aggregating power by practicing do-ocracy. This rational feels shitty and I did not like how it went down

'''WEZ:'''
I asked Elle to leave and did not want it to be super secretive which is Elle-like behavior. You (Elle) do this private political chat move that is shady. Noisebridge is a high trust community and we find out if you are trying to pull strings in the background. I was not going to be private about the ATL because I want to be transparent.

'''Elan:'''
I agree that we should be public. It seems we have applied a different set of standards here. Elle is being accused in one circumstances for declaring we should be public and then in another that she uses PMs and that is manipulative -- this feels like a double standard or at least inconstantly applied and that feels unexcellent. Similar things happened to other people doing good work. It sucks.

'''LX:'''
It was better that she was not 86'd - I think the consequences of 86 propose a direct safety risk rather than behavior disagreements. We can thank a person for their help and still get to a point where we ask them to leave without banning them from other hackerspaces. Naomi handled it better by not using a direct 86. I only had positive experiences with Elle. But I got a better understanding from other people and got that the discussion that were done were healthy. Elle was really nice with certain people and got into strong conflict with others. The process was fair and represents all the emotional labor done (mostly by Naomi). The most serious issue was injecting an ATL during mediation via Policy Injection and conflict escalation.

'''WEZ:'''
All these dark patterns that I were not appreciative of...it was a double edged sword. We have one rule which is to be excellent and not be manipulative. There are a lot of smart people here who are capable of manipulation. To Elan's point, we should have everyone's perspective involved for this.

'''Michael:'''
I've met Elle before and the interaction was good. Using private chats and channels itself is not problematic but we are a hackerspace so transparency is important. We have to consider if this person imposes a harm to NB.

'''Elan:'''
WEZ made precisely the same claim about transparency - ie that was claimed by Elle to be the norm when talking with Justin about talking in #bravespace. This is was called out as policy injection and it feels like its a repeated trend of a double standard.

I agree she has called people out stronger than need to be, and upset people in the process.

I was on vacation and two people messaged me about the mediation chat saying that people were pointing out that I would disagree and asked if I wanted to chime in - I declined. When I got back it felt weird that this all went down without an inciting incident after being put on notice by WEZ.

'''Naomi:'''
There was more info that was involved.

'''Elan:'''
It feels from the outside this was triggered by going through old discord logs.

'''Daniel:'''
Elle did not propose physical or property harm -- the harm was mostly sociological (that was my understanding).

'''Naomi:'''
The triggering event was not scraping logs - I reached out to Elle about 2-3 weeks ago - I put her on notice on purpose. She said we should have a private conversation -- which conflicts to what she said earlier about having a rule to not have private chats. She responds that things have been very stressful and came at me for 4 different things and had "please fire me" guilt energy. I was trying to have a decent convo but that triggered things for me.

'''LX:'''
As a friend of Elle, Cloud was asked to leave during mediation and that was a violation of our standards - you do not get to decide how things go, that's the mediator's job. Either we allow someone to improperly ATL Cloud and be at the space or we took the steps that we did.

'''WEZ:'''
Appreciate your insights - NB kind of runs on vibes. We can vibe out if an ATL is in good faith - we have this policy in place to help people feel safe. I did everything I could to help Elle feel safe even with the ATL. It sucks bc I also have friends that cannot handle the open transparency that we have. We are a leaderless cult. Some people can't handle NB because of their nature and tendencies.

'''Naomi:'''
That feels like a nature thing (i.e. some people can't handle NB) but I don't think it's a nature thing.

'''WEZ:'''
Yeah some people just really want to know who is in charge around here. I didn't mean to make it sound like a nature thing

'''Elan:'''
People don't always act excellent. People are imperfect - I'm sure if you look through my discord you could find examples of me being snippy.

'''Naomi:'''
I analyzed you as well for the record.

'''Elan:'''
Sure. That's a weird thing to do.

'''Elan:'''
Anyways - this is a mess. I'm just saying call people out and don't be mad when people call you out. Don't put off having uncomfortable conversations. We could have corrected this behavior and people don't have to be friends. The revealed preferencec of how we handle non-safety-related interpersonal issues is by kicking them out (which I would say is the wrong approach).

'''WEZ:'''
Mmm. We escalated someone who escalates.

'''Naomi:'''
Someone took a disagreement and re-framed it into a WIN-LOSE situation. Why do you think this situation became more than what it initially was?

'''Elan:''' ''thousand yard stare'' In a bygone era, Cloud took on Wyatt's cause as a way to fuel the vendetta with Elle (and others) and we have been rehashing incident ever since.

'''Naomi:'''
I don't think she was wrong in a lot of her intuitions but I didn't even use any of that. It was a lot of situations where things were framed as WIN-LOSE.

'''Michael:'''
Whoever blocked her Big M - is that confidential?

'''Everyone:'''
No, it was Mark.

'''LX:'''
Naomi is trying to put together a draft that better improves our process and conflict resolution toolkit. I offered to host a workshop for these things as well.

'''Carl:'''
If Elle returns in the future.. Is there an opportunity for her and what does that look like?

'''Naomi:'''
Right now there isn't a great path except for time. There are more than a dozen people who are not keen on seeing her. And we are bad at mediation. Maybe we should have a relationship with a 3rd party mediator. Mediation isn't cheap. Elle would probably have to be in mediation with a dozen people.

== Discussion Item 4: Restorative Communication ==

{{DiscussionItem|
| topic = Restorative Communication
| raised_by = Naomi
| seeking = Discussion
}}

'''Naomi:'''
[improv game: asks for a place, a relationship, and a situation to set up a hypothetical about RC]

'''Michael:'''
[interrupts Naomi in the middle of a hypothetical situation about RC] I just want to say I have to leave, I didn't come here for an extended thing about a situation i don't know about...

'''Naomi:'''
[looks flustered] Wow. Ok. Michael, when you stood up to interrupt me in the middle of my talking about RC, I felt frustrated. Next time, could you just stand up silently?

'''Michael:'''
Uh, yeah?

'''Naomi:'''
Thank you!

https://www.noisebridge.net/wiki/Restorative_Communication

'''Naomi:'''
Wow! That was way better than a hypothetical.

'''Naomi:'''
Vocalize dis-agreements according to the RC template:

* Look

* Feel

* Offer

* Ask

No sneak dissing! Vocalizing in front of others helps people people to these agreements.

'''JD:'''
What if not everyone uses it?

'''Naomi:'''
Yeah, there are multiple failure modes -- 1 is that people don't actually know what their feelings are. another is that you express your feelings and people take advantage of your vulnerability.

'''Naomi:'''
So that's why it's imperative to do this for the community all at once... you can't just do it one individual at at time.

'''Naomi:'''

Cultural interventions in order of how impactful i think they'd be:

* Modeling of RC behavior by people who are around a lot
* RC cards providing permanent, physical intervention in the space
* Strategic deployment in the meeting template
* Announcements for more RC workshops
* Putting more stuff on the wiki about the meta of RC
* Laminated page about RC placed in membership binder

'''LX:'''
We should run RC workshops.

= Do-ocratic Task Board =
Participation also means doing stuff to contribute to the space. Propose new tasks or pick some tasks from [https://github.com/noisebridge/buildout-capp Github], from what needs to be done around you, or whatever, and see if someone will sign up to work on that task. Anyone can sign up and it's a great way to show you are contributing!

= End of Meeting =

==Note taker posts the notes==

* Clean and tidy the meeting notes including removing all these really verbose instructions.
* Fill out the short summary at the top listing just announcements, consensus items, & discussion topics.
* Copy paste the notes to the next meeting page. (They will become Last meeting at midnight.) https://www.noisebridge.net/index.php?title=Last_meeting&redirect=no
* Email the meeting summary to Noisebridge Discuss and Noisebridge Announce lists.
* CC on the email treasurer@noisebridge.net and secretary@noisebridge.net if there are new members and philanthropists.
* Edit the Current Consensus Items if anything is proposed for consensus next week.
* Edit the Consensus Items History if anything was reached consensus or failed to reach consensus this week.

* What wiki pages need updating? What new wiki pages do we need? Discovered from the meeting.
==Fun things to do after==

* Do a 10 minute cleanup, bring dishes up stairs and wash them, clean the bathroom
* Have some beers on the patio
* Prepare the next weeks' meeting notes
* Lick the walls. Or just draw on them
* sing the [[Hackernationale]] (this almost never happens)

[[Category:Meeting Notes]]

Template:DiscussionItem

2026-01-15T06:04:55Z

ElanHR: Creating template for meeting discussion items (here's hoping it works)

{| class="wikitable" style="align:left margin:auto"
|-
| '''On topic:''' || {{{topic}}}
|-
| '''From/Raised by:''' || {{{raised_by}}}
|-
| '''Seeking:''' || {{{seeking}}}
|}

User:ElanHR/Essays/LLMBridge

2026-01-15T04:17:21Z

ElanHR: Added a foreword to not lead future readers down the garden path.

{{box2}}'''Foreword:''' This was originally published as a touch-in-cheek attempt to showcase some of the perils of using LLMs in interpersonal communications. The idea was to let people read this assuming that a human had put in thought into the words written/ideas expressed.

At the end it is revealed that the person reading this article has spent more time reading it than the "writer" did generating it. This is meant to induce the sense of betrayal that some Noisebridgers feel when consuming AI-generated/assisted/informed content that is not explicitly disclosed as such.

My intent is to push for a policy (or more accurately a norm) where folks disclose when/how AI is used. An ideal situation is the AI chat session (or the primary prompt) is provided so folks can consume the originating human intent (if they so desire).
{{boxend}}
{{essay}}
{{LLM}}

Let's get real: The whole “AI will save us” narrative is kinda getting out of hand. We’re all watching tech companies throw fancy algorithms into every part of life—policy-making, interpersonal communication, customer service, you name it. But before we jump on this shiny bandwagon, let’s talk about how this over-reliance on large language models (LLMs) is actually doing more harm than good, especially in the spaces we care about: communities, organizations, and interpersonal relationships.

If you care about privacy, transparency, or just not being treated like a cog in a corporate machine, stick with us because Noisebridge is about to break it down. The consequences of LLMs are real, and they’re messing with trust in some serious ways. So, let’s break it down, starting with the real problems: ''idea inflation'' and ''interpersonal denial-of-service''.

= Interpersonal Denial-of-Service: AI That Talks, But Doesn’t Listen =

Let’s talk about ''Interpersonal Denial-of-Service'' (or iDOS for short). It’s a term we’re coining here for when LLM-generated content doesn’t actually serve the people it’s supposed to, but instead ''overwhelms'' them with information. You know how, when you get an email, message, or policy update that’s ''way too long'' and you’re just like, “I don’t have the time for this”? Well, that's a classic symptom of AI-generated content.

While LLMs can ''generate'' content super quickly, they don’t ''understand'' how people process or engage with it. So what happens? You end up with a ton of information—long, verbose responses that take longer to read than it did to write. That’s exactly the opposite of ''serving'' people. It’s just a digital way of saying, “Here’s a wall of text. Good luck.”

This is where interpersonal trust starts to erode. Instead of getting straight to the point and respecting people's time, you’re bombarded with word soup. This isn't just inefficient, it’s frustrating. In a world where efficiency and meaningful communication matter, this AI-driven overload is a barrier, not a bridge.

In hackerspaces, where transparency and clarity are core values, this flood of content that takes longer to read than to generate is a huge turn-off. It’s like trying to have a meaningful conversation with someone who just talks in circles and doesn’t listen. Instead of fostering understanding, it fosters ''disengagement''.

= Idea Inflation: When Everything Sounds "Well-Thought-Out" But Isn’t Necessarily =

Alright, so here's the thing. When you ask a language model to draft a policy or response, it spits out something polished and slick. The formatting is on point, the tone is neutral, and it looks like it’s been carefully thought through by a team of experts. Sounds great, right? WRONG. That ''polished surface'' is actually the problem.

LLMs are ''great'' at sounding convincing—too convincing. The content they churn out looks like it's been pre-vetted, researched, and validated by some superhuman team of experts. But here’s the kicker: It hasn’t. It’s just stringing together sentences based on patterns in the data it’s been trained on, which means ''it’s as likely to be wrong or biased as it is to be right''. When you give a machine too much credit just because it ''sounds good'', you’re essentially inflating ideas—making them seem more authoritative than they actually are.

This is especially dangerous in organizational or public policy-making, where real people are impacted by decisions. Just because an LLM-generated statement looks professional, it doesn’t mean it’s been fact-checked, considered from all angles, or even accurate. But thanks to our biases, we tend to assume that polished = perfect. This idea inflation makes everything look more thought-out than it is, and it’s a quick way for organizations to lose trust.

In hackerspaces or any other community that values critical thinking and transparency, this is a huge red flag. It's one thing to ask AI for a draft—it's another to let it completely shape your policy without scrutiny.

= Privacy? Yeah, That’s Out the Window =

Privacy is ''everything''. And when you’re feeding sensitive information into an AI model, you need to know exactly where that data is going and who has access to it. Unfortunately, the companies behind these LLMs don’t exactly have a stellar track record when it comes to protecting user privacy. While some AI providers claim they anonymize data, the reality is that we have very little control over what happens to the information we share with them.

For hackerspaces, where privacy is key, the idea of passing off personal or organizational data to a third-party AI company (who might be data-mining or sharing your info with who-knows-who) is an absolute nightmare. It’s not just about keeping things private—it’s about the ''ethics'' of trusting a third party with potentially sensitive info.

We’ve seen how tech companies can mishandle our data, and in a world where data breaches are a dime a dozen, trusting AI with any personal info feels like playing Russian roulette with your privacy. Respecting user privacy is one of the highest standards of “being excellent to each other,” and giving that up for AI convenience isn’t the trade we want to make.

= The Accountability Black Hole: Who’s Really Behind That Message? =

One of the most annoying things about LLM-generated content is the ''accountability black hole''. Who’s really responsible for what’s being said? When organizations rely on LLMs to draft public statements, policies, or even internal communications, it gets messy fast. Is the organization responsible for this content, or is it the human who typed in the prompt? Or, is it the AI itself?

Let’s say an organization releases a statement generated by an LLM and it goes south. There’s no one to blame except for the faceless algorithm that produced the content. But it’s not just the AI’s fault—it’s the people who didn’t think about the consequences of using it in the first place. Without clear accountability, it’s hard to trust what’s being said, because no one can be held responsible when things go wrong.

It’s a classic case of ''hiding behind technology''—taking the easy way out by letting an AI do the talking while simultaneously dodging any blame if it backfires. Trust is built on transparency and clear accountability. And when both of those go out the window, so does the trust.

= Bias, Echo Chambers, and the Unverifiable “Truth” =

LLMs aren’t as neutral as they seem. Sure, they’re not human, but they ''are'' trained on human data, which means they ''inherit'' all the biases of the sources they were fed. That means if the AI is asked to craft a policy or position statement about a controversial issue, it can ''accidentally'' reinforce existing biases or only present one side of the story.

Think of it like this: you ask an LLM to summarize a political issue. What it produces might sound fair, but in reality, it could be one-sided, reflecting the biases baked into the model. When an organization relies on that content to set policy or make decisions, they’re just as guilty of feeding the bias machine as the model is. And that’s a huge problem when you’re trying to make fair, informed decisions that impact people.

We need to be aware of this and ask: ''Is the information we’re getting from these models truly balanced? Or are we just feeding into an algorithmic echo chamber?''

= The Bottom Line =

Look, we’re not anti-AI—LLMs can be powerful tools for drafting, brainstorming, and even assisting with tasks. But when it comes to interpersonal matters and organizational policy, using them without critical thought is a recipe for disaster. We’re talking about eroding public trust, undermining accountability, and putting privacy at serious risk. In communities like hackerspaces, where transparency, ethics, and mutual respect are the foundation of everything, these risks are ''not'' worth it.

So, before you rely on AI to set your organization’s policies or have an important conversation, ask yourself: ''Are we using this tool to serve people—or to serve convenience?'' Because when trust is lost, it’s hard to get back.

= References =

* Binns, R. (2018). 'The challenges of algorithmic transparency and accountability'. 'Journal of Ethics and Information Technology', 23(1), 1-18. [[https://doi.org/10.1007/s10676-018-9464-9 Link]]

* Noble, S. U. (2018). 'Algorithms of Oppression: How Search Engines Reinforce Racism'. NYU Press.

* O'Neil, C. (2016). 'Weapons of Math Destruction: How Big Data Increases Inequality and Threatens Democracy'. Crown Publishing Group.

* Lohan, J. (2020). 'The perils of AI in decision-making: Accountability, bias, and privacy'. 'IEEE Internet Computing', 24(5), 6-13. [[https://doi.org/10.1109/MIC.2020.2984677 Link]]

* Zengler, T. (2022). 'Why AI can't replace humans in sensitive organizational matters'. 'Harvard Business Review'. [[https://hbr Link]]

= TL;DR =
This took Elan less than 3 minutes to generate from conception to posting (including fixing the wikitext). None of this has been fact-checked/proofread. None of the ideas contained in can be attributed to a Noisebridgers aside from (possibly) those used in the original prompt.

== Generation ==
Model used: ChatGPT

Prompts:
```
Can you write a long article in wiki style describing how why LLM use for interpersonal matters and setting policy can lead to erosion of public trust in an organization. An incomplete list of ideas to expound on: * Lack of accountability. How can we tell what is being attributed to the person prompting vs what is said by the individual. * People put an overreliance on formatting so something that looks polished (as LLMs typically are) comes across as well thought out and often people assume things represent the organization and have been fact checked. * Over reliance on unverifiable inputs and sensitive to bias - i.e. only telling one side of an event and taking it as true * Interpersonal denial-of-service. Often LLM generated content can be longer to read than it is to generate. * Not privacy respecting. It could be considered unexcellent to share details with an AI company. Whenever possible please find sources to support your claims and create a citation section. Please write this for a hackerspace audience that strives to "be excellent to each other" and places a high premium on respecting privacy.
```

Refinement:

```
This is great, could you make it more edgy for a millennial+ gen Z audience and also lead with the ideas of "idea inflation" / interpersonal DOS?

```

LLMBridge

2026-01-15T03:57:08Z

ElanHR: ElanHR moved page LLMBridge to User:ElanHR/Essays/LLMBridge: Moving from main space to indicate that this is not Noisebridge consensus

#REDIRECT [[User:ElanHR/Essays/LLMBridge]]

User:ElanHR/Essays/LLMBridge

2026-01-15T03:57:08Z

ElanHR: ElanHR moved page LLMBridge to User:ElanHR/Essays/LLMBridge: Moving from main space to indicate that this is not Noisebridge consensus

{{essay}}
{{LLM}}

Let's get real: The whole “AI will save us” narrative is kinda getting out of hand. We’re all watching tech companies throw fancy algorithms into every part of life—policy-making, interpersonal communication, customer service, you name it. But before we jump on this shiny bandwagon, let’s talk about how this over-reliance on large language models (LLMs) is actually doing more harm than good, especially in the spaces we care about: communities, organizations, and interpersonal relationships.

If you care about privacy, transparency, or just not being treated like a cog in a corporate machine, stick with us because Noisebridge is about to break it down. The consequences of LLMs are real, and they’re messing with trust in some serious ways. So, let’s break it down, starting with the real problems: ''idea inflation'' and ''interpersonal denial-of-service''.

= Interpersonal Denial-of-Service: AI That Talks, But Doesn’t Listen =

Let’s talk about ''Interpersonal Denial-of-Service'' (or iDOS for short). It’s a term we’re coining here for when LLM-generated content doesn’t actually serve the people it’s supposed to, but instead ''overwhelms'' them with information. You know how, when you get an email, message, or policy update that’s ''way too long'' and you’re just like, “I don’t have the time for this”? Well, that's a classic symptom of AI-generated content.

While LLMs can ''generate'' content super quickly, they don’t ''understand'' how people process or engage with it. So what happens? You end up with a ton of information—long, verbose responses that take longer to read than it did to write. That’s exactly the opposite of ''serving'' people. It’s just a digital way of saying, “Here’s a wall of text. Good luck.”

This is where interpersonal trust starts to erode. Instead of getting straight to the point and respecting people's time, you’re bombarded with word soup. This isn't just inefficient, it’s frustrating. In a world where efficiency and meaningful communication matter, this AI-driven overload is a barrier, not a bridge.

In hackerspaces, where transparency and clarity are core values, this flood of content that takes longer to read than to generate is a huge turn-off. It’s like trying to have a meaningful conversation with someone who just talks in circles and doesn’t listen. Instead of fostering understanding, it fosters ''disengagement''.

= Idea Inflation: When Everything Sounds "Well-Thought-Out" But Isn’t Necessarily =

Alright, so here's the thing. When you ask a language model to draft a policy or response, it spits out something polished and slick. The formatting is on point, the tone is neutral, and it looks like it’s been carefully thought through by a team of experts. Sounds great, right? WRONG. That ''polished surface'' is actually the problem.

LLMs are ''great'' at sounding convincing—too convincing. The content they churn out looks like it's been pre-vetted, researched, and validated by some superhuman team of experts. But here’s the kicker: It hasn’t. It’s just stringing together sentences based on patterns in the data it’s been trained on, which means ''it’s as likely to be wrong or biased as it is to be right''. When you give a machine too much credit just because it ''sounds good'', you’re essentially inflating ideas—making them seem more authoritative than they actually are.

This is especially dangerous in organizational or public policy-making, where real people are impacted by decisions. Just because an LLM-generated statement looks professional, it doesn’t mean it’s been fact-checked, considered from all angles, or even accurate. But thanks to our biases, we tend to assume that polished = perfect. This idea inflation makes everything look more thought-out than it is, and it’s a quick way for organizations to lose trust.

In hackerspaces or any other community that values critical thinking and transparency, this is a huge red flag. It's one thing to ask AI for a draft—it's another to let it completely shape your policy without scrutiny.

= Privacy? Yeah, That’s Out the Window =

Privacy is ''everything''. And when you’re feeding sensitive information into an AI model, you need to know exactly where that data is going and who has access to it. Unfortunately, the companies behind these LLMs don’t exactly have a stellar track record when it comes to protecting user privacy. While some AI providers claim they anonymize data, the reality is that we have very little control over what happens to the information we share with them.

For hackerspaces, where privacy is key, the idea of passing off personal or organizational data to a third-party AI company (who might be data-mining or sharing your info with who-knows-who) is an absolute nightmare. It’s not just about keeping things private—it’s about the ''ethics'' of trusting a third party with potentially sensitive info.

We’ve seen how tech companies can mishandle our data, and in a world where data breaches are a dime a dozen, trusting AI with any personal info feels like playing Russian roulette with your privacy. Respecting user privacy is one of the highest standards of “being excellent to each other,” and giving that up for AI convenience isn’t the trade we want to make.

= The Accountability Black Hole: Who’s Really Behind That Message? =

One of the most annoying things about LLM-generated content is the ''accountability black hole''. Who’s really responsible for what’s being said? When organizations rely on LLMs to draft public statements, policies, or even internal communications, it gets messy fast. Is the organization responsible for this content, or is it the human who typed in the prompt? Or, is it the AI itself?

Let’s say an organization releases a statement generated by an LLM and it goes south. There’s no one to blame except for the faceless algorithm that produced the content. But it’s not just the AI’s fault—it’s the people who didn’t think about the consequences of using it in the first place. Without clear accountability, it’s hard to trust what’s being said, because no one can be held responsible when things go wrong.

It’s a classic case of ''hiding behind technology''—taking the easy way out by letting an AI do the talking while simultaneously dodging any blame if it backfires. Trust is built on transparency and clear accountability. And when both of those go out the window, so does the trust.

= Bias, Echo Chambers, and the Unverifiable “Truth” =

LLMs aren’t as neutral as they seem. Sure, they’re not human, but they ''are'' trained on human data, which means they ''inherit'' all the biases of the sources they were fed. That means if the AI is asked to craft a policy or position statement about a controversial issue, it can ''accidentally'' reinforce existing biases or only present one side of the story.

Think of it like this: you ask an LLM to summarize a political issue. What it produces might sound fair, but in reality, it could be one-sided, reflecting the biases baked into the model. When an organization relies on that content to set policy or make decisions, they’re just as guilty of feeding the bias machine as the model is. And that’s a huge problem when you’re trying to make fair, informed decisions that impact people.

We need to be aware of this and ask: ''Is the information we’re getting from these models truly balanced? Or are we just feeding into an algorithmic echo chamber?''

= The Bottom Line =

Look, we’re not anti-AI—LLMs can be powerful tools for drafting, brainstorming, and even assisting with tasks. But when it comes to interpersonal matters and organizational policy, using them without critical thought is a recipe for disaster. We’re talking about eroding public trust, undermining accountability, and putting privacy at serious risk. In communities like hackerspaces, where transparency, ethics, and mutual respect are the foundation of everything, these risks are ''not'' worth it.

So, before you rely on AI to set your organization’s policies or have an important conversation, ask yourself: ''Are we using this tool to serve people—or to serve convenience?'' Because when trust is lost, it’s hard to get back.

= References =

* Binns, R. (2018). 'The challenges of algorithmic transparency and accountability'. 'Journal of Ethics and Information Technology', 23(1), 1-18. [[https://doi.org/10.1007/s10676-018-9464-9 Link]]

* Noble, S. U. (2018). 'Algorithms of Oppression: How Search Engines Reinforce Racism'. NYU Press.

* O'Neil, C. (2016). 'Weapons of Math Destruction: How Big Data Increases Inequality and Threatens Democracy'. Crown Publishing Group.

* Lohan, J. (2020). 'The perils of AI in decision-making: Accountability, bias, and privacy'. 'IEEE Internet Computing', 24(5), 6-13. [[https://doi.org/10.1109/MIC.2020.2984677 Link]]

* Zengler, T. (2022). 'Why AI can't replace humans in sensitive organizational matters'. 'Harvard Business Review'. [[https://hbr Link]]

= TL;DR =
This took Elan less than 3 minutes to generate from conception to posting (including fixing the wikitext). None of this has been fact-checked/proofread. None of the ideas contained in can be attributed to a Noisebridgers aside from (possibly) those used in the original prompt.

== Generation ==
Model used: ChatGPT

Prompts:
```
Can you write a long article in wiki style describing how why LLM use for interpersonal matters and setting policy can lead to erosion of public trust in an organization. An incomplete list of ideas to expound on: * Lack of accountability. How can we tell what is being attributed to the person prompting vs what is said by the individual. * People put an overreliance on formatting so something that looks polished (as LLMs typically are) comes across as well thought out and often people assume things represent the organization and have been fact checked. * Over reliance on unverifiable inputs and sensitive to bias - i.e. only telling one side of an event and taking it as true * Interpersonal denial-of-service. Often LLM generated content can be longer to read than it is to generate. * Not privacy respecting. It could be considered unexcellent to share details with an AI company. Whenever possible please find sources to support your claims and create a citation section. Please write this for a hackerspace audience that strives to "be excellent to each other" and places a high premium on respecting privacy.
```

Refinement:

```
This is great, could you make it more edgy for a millennial+ gen Z audience and also lead with the ideas of "idea inflation" / interpersonal DOS?

```

User:ElanHR/Essays/LLMBridge

2026-01-13T20:29:19Z

ElanHR: /* TL;DR */

Let's get real: The whole “AI will save us” narrative is kinda getting out of hand. We’re all watching tech companies throw fancy algorithms into every part of life—policy-making, interpersonal communication, customer service, you name it. But before we jump on this shiny bandwagon, let’s talk about how this over-reliance on large language models (LLMs) is actually doing more harm than good, especially in the spaces we care about: communities, organizations, and interpersonal relationships.

If you care about privacy, transparency, or just not being treated like a cog in a corporate machine, stick with us because Noisebridge is about to break it down. The consequences of LLMs are real, and they’re messing with trust in some serious ways. So, let’s break it down, starting with the real problems: ''idea inflation'' and ''interpersonal denial-of-service''.

= Interpersonal Denial-of-Service: AI That Talks, But Doesn’t Listen =

Let’s talk about ''Interpersonal Denial-of-Service'' (or iDOS for short). It’s a term we’re coining here for when LLM-generated content doesn’t actually serve the people it’s supposed to, but instead ''overwhelms'' them with information. You know how, when you get an email, message, or policy update that’s ''way too long'' and you’re just like, “I don’t have the time for this”? Well, that's a classic symptom of AI-generated content.

While LLMs can ''generate'' content super quickly, they don’t ''understand'' how people process or engage with it. So what happens? You end up with a ton of information—long, verbose responses that take longer to read than it did to write. That’s exactly the opposite of ''serving'' people. It’s just a digital way of saying, “Here’s a wall of text. Good luck.”

This is where interpersonal trust starts to erode. Instead of getting straight to the point and respecting people's time, you’re bombarded with word soup. This isn't just inefficient, it’s frustrating. In a world where efficiency and meaningful communication matter, this AI-driven overload is a barrier, not a bridge.

In hackerspaces, where transparency and clarity are core values, this flood of content that takes longer to read than to generate is a huge turn-off. It’s like trying to have a meaningful conversation with someone who just talks in circles and doesn’t listen. Instead of fostering understanding, it fosters ''disengagement''.

= Idea Inflation: When Everything Sounds "Well-Thought-Out" But Isn’t Necessarily =

Alright, so here's the thing. When you ask a language model to draft a policy or response, it spits out something polished and slick. The formatting is on point, the tone is neutral, and it looks like it’s been carefully thought through by a team of experts. Sounds great, right? WRONG. That ''polished surface'' is actually the problem.

LLMs are ''great'' at sounding convincing—too convincing. The content they churn out looks like it's been pre-vetted, researched, and validated by some superhuman team of experts. But here’s the kicker: It hasn’t. It’s just stringing together sentences based on patterns in the data it’s been trained on, which means ''it’s as likely to be wrong or biased as it is to be right''. When you give a machine too much credit just because it ''sounds good'', you’re essentially inflating ideas—making them seem more authoritative than they actually are.

This is especially dangerous in organizational or public policy-making, where real people are impacted by decisions. Just because an LLM-generated statement looks professional, it doesn’t mean it’s been fact-checked, considered from all angles, or even accurate. But thanks to our biases, we tend to assume that polished = perfect. This idea inflation makes everything look more thought-out than it is, and it’s a quick way for organizations to lose trust.

In hackerspaces or any other community that values critical thinking and transparency, this is a huge red flag. It's one thing to ask AI for a draft—it's another to let it completely shape your policy without scrutiny.

= Privacy? Yeah, That’s Out the Window =

Privacy is ''everything''. And when you’re feeding sensitive information into an AI model, you need to know exactly where that data is going and who has access to it. Unfortunately, the companies behind these LLMs don’t exactly have a stellar track record when it comes to protecting user privacy. While some AI providers claim they anonymize data, the reality is that we have very little control over what happens to the information we share with them.

For hackerspaces, where privacy is key, the idea of passing off personal or organizational data to a third-party AI company (who might be data-mining or sharing your info with who-knows-who) is an absolute nightmare. It’s not just about keeping things private—it’s about the ''ethics'' of trusting a third party with potentially sensitive info.

We’ve seen how tech companies can mishandle our data, and in a world where data breaches are a dime a dozen, trusting AI with any personal info feels like playing Russian roulette with your privacy. Respecting user privacy is one of the highest standards of “being excellent to each other,” and giving that up for AI convenience isn’t the trade we want to make.

= The Accountability Black Hole: Who’s Really Behind That Message? =

One of the most annoying things about LLM-generated content is the ''accountability black hole''. Who’s really responsible for what’s being said? When organizations rely on LLMs to draft public statements, policies, or even internal communications, it gets messy fast. Is the organization responsible for this content, or is it the human who typed in the prompt? Or, is it the AI itself?

Let’s say an organization releases a statement generated by an LLM and it goes south. There’s no one to blame except for the faceless algorithm that produced the content. But it’s not just the AI’s fault—it’s the people who didn’t think about the consequences of using it in the first place. Without clear accountability, it’s hard to trust what’s being said, because no one can be held responsible when things go wrong.

It’s a classic case of ''hiding behind technology''—taking the easy way out by letting an AI do the talking while simultaneously dodging any blame if it backfires. Trust is built on transparency and clear accountability. And when both of those go out the window, so does the trust.

= Bias, Echo Chambers, and the Unverifiable “Truth” =

LLMs aren’t as neutral as they seem. Sure, they’re not human, but they ''are'' trained on human data, which means they ''inherit'' all the biases of the sources they were fed. That means if the AI is asked to craft a policy or position statement about a controversial issue, it can ''accidentally'' reinforce existing biases or only present one side of the story.

Think of it like this: you ask an LLM to summarize a political issue. What it produces might sound fair, but in reality, it could be one-sided, reflecting the biases baked into the model. When an organization relies on that content to set policy or make decisions, they’re just as guilty of feeding the bias machine as the model is. And that’s a huge problem when you’re trying to make fair, informed decisions that impact people.

We need to be aware of this and ask: ''Is the information we’re getting from these models truly balanced? Or are we just feeding into an algorithmic echo chamber?''

= The Bottom Line =

Look, we’re not anti-AI—LLMs can be powerful tools for drafting, brainstorming, and even assisting with tasks. But when it comes to interpersonal matters and organizational policy, using them without critical thought is a recipe for disaster. We’re talking about eroding public trust, undermining accountability, and putting privacy at serious risk. In communities like hackerspaces, where transparency, ethics, and mutual respect are the foundation of everything, these risks are ''not'' worth it.

So, before you rely on AI to set your organization’s policies or have an important conversation, ask yourself: ''Are we using this tool to serve people—or to serve convenience?'' Because when trust is lost, it’s hard to get back.

= References =

* Binns, R. (2018). 'The challenges of algorithmic transparency and accountability'. 'Journal of Ethics and Information Technology', 23(1), 1-18. [[https://doi.org/10.1007/s10676-018-9464-9 Link]]

* Noble, S. U. (2018). 'Algorithms of Oppression: How Search Engines Reinforce Racism'. NYU Press.

* O'Neil, C. (2016). 'Weapons of Math Destruction: How Big Data Increases Inequality and Threatens Democracy'. Crown Publishing Group.

* Lohan, J. (2020). 'The perils of AI in decision-making: Accountability, bias, and privacy'. 'IEEE Internet Computing', 24(5), 6-13. [[https://doi.org/10.1109/MIC.2020.2984677 Link]]

* Zengler, T. (2022). 'Why AI can't replace humans in sensitive organizational matters'. 'Harvard Business Review'. [[https://hbr Link]]

= TL;DR =
This took Elan less than 3 minutes to generate from conception to posting (including fixing the wikitext). None of this has been fact-checked/proofread. None of the ideas contained in can be attributed to a Noisebridgers aside from (possibly) those used in the original prompt.

== Generation ==
Model used: ChatGPT

Prompts:
```
Can you write a long article in wiki style describing how why LLM use for interpersonal matters and setting policy can lead to erosion of public trust in an organization. An incomplete list of ideas to expound on: * Lack of accountability. How can we tell what is being attributed to the person prompting vs what is said by the individual. * People put an overreliance on formatting so something that looks polished (as LLMs typically are) comes across as well thought out and often people assume things represent the organization and have been fact checked. * Over reliance on unverifiable inputs and sensitive to bias - i.e. only telling one side of an event and taking it as true * Interpersonal denial-of-service. Often LLM generated content can be longer to read than it is to generate. * Not privacy respecting. It could be considered unexcellent to share details with an AI company. Whenever possible please find sources to support your claims and create a citation section. Please write this for a hackerspace audience that strives to "be excellent to each other" and places a high premium on respecting privacy.
```

Refinement:

```
This is great, could you make it more edgy for a millennial+ gen Z audience and also lead with the ideas of "idea inflation" / interpersonal DOS?

```

User:ElanHR/Essays/LLMBridge

2026-01-13T19:02:00Z

ElanHR: /* TL;DR */

User:ElanHR/Essays/LLMBridge

2026-01-13T18:44:40Z

ElanHR: Fixed references

User:ElanHR/Essays/LLMBridge

2026-01-13T18:20:52Z

ElanHR: Do-ocratically created guides to excellence for LLM-use at Noisebridge

Let's get real: The whole “AI will save us” narrative is kinda getting out of hand. We’re all watching tech companies throw fancy algorithms into every part of life—policy-making, interpersonal communication, customer service, you name it. But before we jump on this shiny bandwagon, let’s talk about how this over-reliance on large language models (LLMs) is actually doing more harm than good, especially in the spaces we care about: communities, organizations, and interpersonal relationships.

If you care about privacy, transparency, or just not being treated like a cog in a corporate machine, stick with us because Noisebridge is about to break it down. The consequences of LLMs are real, and they’re messing with trust in some serious ways. So, let’s break it down, starting with the real problems: ''idea inflation'' and ''interpersonal denial-of-service''.

= Interpersonal Denial-of-Service: AI That Talks, But Doesn’t Listen =

Let’s talk about ''Interpersonal Denial-of-Service'' (or iDOS for short). It’s a term we’re coining here for when LLM-generated content doesn’t actually serve the people it’s supposed to, but instead ''overwhelms'' them with information. You know how, when you get an email, message, or policy update that’s ''way too long'' and you’re just like, “I don’t have the time for this”? Well, that's a classic symptom of AI-generated content.

While LLMs can ''generate'' content super quickly, they don’t ''understand'' how people process or engage with it. So what happens? You end up with a ton of information—long, verbose responses that take longer to read than it did to write. That’s exactly the opposite of ''serving'' people. It’s just a digital way of saying, “Here’s a wall of text. Good luck.”

This is where interpersonal trust starts to erode. Instead of getting straight to the point and respecting people's time, you’re bombarded with word soup. This isn't just inefficient, it’s frustrating. In a world where efficiency and meaningful communication matter, this AI-driven overload is a barrier, not a bridge.

In hackerspaces, where transparency and clarity are core values, this flood of content that takes longer to read than to generate is a huge turn-off. It’s like trying to have a meaningful conversation with someone who just talks in circles and doesn’t listen. Instead of fostering understanding, it fosters ''disengagement''.

= Idea Inflation: When Everything Sounds "Well-Thought-Out" But Isn’t Necessarily =

Alright, so here's the thing. When you ask a language model to draft a policy or response, it spits out something polished and slick. The formatting is on point, the tone is neutral, and it looks like it’s been carefully thought through by a team of experts. Sounds great, right? WRONG. That ''polished surface'' is actually the problem.

LLMs are ''great'' at sounding convincing—too convincing. The content they churn out looks like it's been pre-vetted, researched, and validated by some superhuman team of experts. But here’s the kicker: It hasn’t. It’s just stringing together sentences based on patterns in the data it’s been trained on, which means ''it’s as likely to be wrong or biased as it is to be right''. When you give a machine too much credit just because it ''sounds good'', you’re essentially inflating ideas—making them seem more authoritative than they actually are.

This is especially dangerous in organizational or public policy-making, where real people are impacted by decisions. Just because an LLM-generated statement looks professional, it doesn’t mean it’s been fact-checked, considered from all angles, or even accurate. But thanks to our biases, we tend to assume that polished = perfect. This idea inflation makes everything look more thought-out than it is, and it’s a quick way for organizations to lose trust.

In hackerspaces or any other community that values critical thinking and transparency, this is a huge red flag. It's one thing to ask AI for a draft—it's another to let it completely shape your policy without scrutiny.

= Privacy? Yeah, That’s Out the Window =

Privacy is ''everything''. And when you’re feeding sensitive information into an AI model, you need to know exactly where that data is going and who has access to it. Unfortunately, the companies behind these LLMs don’t exactly have a stellar track record when it comes to protecting user privacy. While some AI providers claim they anonymize data, the reality is that we have very little control over what happens to the information we share with them.

For hackerspaces, where privacy is key, the idea of passing off personal or organizational data to a third-party AI company (who might be data-mining or sharing your info with who-knows-who) is an absolute nightmare. It’s not just about keeping things private—it’s about the ''ethics'' of trusting a third party with potentially sensitive info.

We’ve seen how tech companies can mishandle our data, and in a world where data breaches are a dime a dozen, trusting AI with any personal info feels like playing Russian roulette with your privacy. Respecting user privacy is one of the highest standards of “being excellent to each other,” and giving that up for AI convenience isn’t the trade we want to make.

= The Accountability Black Hole: Who’s Really Behind That Message? =

One of the most annoying things about LLM-generated content is the ''accountability black hole''. Who’s really responsible for what’s being said? When organizations rely on LLMs to draft public statements, policies, or even internal communications, it gets messy fast. Is the organization responsible for this content, or is it the human who typed in the prompt? Or, is it the AI itself?

Let’s say an organization releases a statement generated by an LLM and it goes south. There’s no one to blame except for the faceless algorithm that produced the content. But it’s not just the AI’s fault—it’s the people who didn’t think about the consequences of using it in the first place. Without clear accountability, it’s hard to trust what’s being said, because no one can be held responsible when things go wrong.

It’s a classic case of ''hiding behind technology''—taking the easy way out by letting an AI do the talking while simultaneously dodging any blame if it backfires. Trust is built on transparency and clear accountability. And when both of those go out the window, so does the trust.

= Bias, Echo Chambers, and the Unverifiable “Truth” =

LLMs aren’t as neutral as they seem. Sure, they’re not human, but they ''are'' trained on human data, which means they ''inherit'' all the biases of the sources they were fed. That means if the AI is asked to craft a policy or position statement about a controversial issue, it can ''accidentally'' reinforce existing biases or only present one side of the story.

Think of it like this: you ask an LLM to summarize a political issue. What it produces might sound fair, but in reality, it could be one-sided, reflecting the biases baked into the model. When an organization relies on that content to set policy or make decisions, they’re just as guilty of feeding the bias machine as the model is. And that’s a huge problem when you’re trying to make fair, informed decisions that impact people.

We need to be aware of this and ask: ''Is the information we’re getting from these models truly balanced? Or are we just feeding into an algorithmic echo chamber?''

= The Bottom Line =

Look, we’re not anti-AI—LLMs can be powerful tools for drafting, brainstorming, and even assisting with tasks. But when it comes to interpersonal matters and organizational policy, using them without critical thought is a recipe for disaster. We’re talking about eroding public trust, undermining accountability, and putting privacy at serious risk. In communities like hackerspaces, where transparency, ethics, and mutual respect are the foundation of everything, these risks are ''not'' worth it.

So, before you rely on AI to set your organization’s policies or have an important conversation, ask yourself: ''Are we using this tool to serve people—or to serve convenience?'' Because when trust is lost, it’s hard to get back.

= References =

* Binns, R. (2018). 'The challenges of algorithmic transparency and accountability'. 'Journal of Ethics and Information Technology', 23(1), 1-18. [[https://doi.org/10.1007/s10676-018-9464-9 Link]]

* Noble, S. U. (2018). 'Algorithms of Oppression: How Search Engines Reinforce Racism'. NYU Press.

* O'Neil, C. (2016). 'Weapons of Math Destruction: How Big Data Increases Inequality and Threatens Democracy'. Crown Publishing Group.

* Lohan, J. (2020). 'The perils of AI in decision-making: Accountability, bias, and privacy'. 'IEEE Internet Computing', 24(5), 6-13. [[https://doi.org/10.1109/MIC.2020.2984677 Link]]

* Zengler, T. (2022). 'Why AI can't replace humans in sensitive organizational matters'. 'Harvard Business Review'. [[https://hbr Link]]

=
This took Elan less than 3 minutes to generate from conception to posting (including fixing the wikitext)

File:Eric.jpeg

2025-12-13T18:04:28Z

ElanHR:

User talk:Ratlord

2025-12-12T20:23:29Z

ElanHR: Welcome!

User:Ratlord

2025-12-12T20:23:29Z

ElanHR: Creating user page for new user.

Local maker/hacker/artist. I work on robots, sewing, embroidery & cross stitch, digital art, video games, and I’m learning to play the banjo.

Nb.wtf

2025-12-05T04:40:14Z

ElanHR: Added nb.wtf/16 ==> NB16 link

{{wiki}}

==Usage==
This page is the "database" for the Noisebridge link shortening/go link service at https://nb.wtf. To use it, add the URL in the right column, and the desired shortcode in the left column. For instance, if you put "about" in the left column, you can put [[About]] in the right column, and then nb.wtf/about will redirect to the wiki About page. Links to the Noisebridge site/wiki do not need to be full URLs, you can use normal wiki links.

===Short path /w/===
Additionally, URLs like <code><nowiki>http://nb.wtf/w/MyAwesomeHackerProject</nowiki></code> will redirect to <code><nowiki>https://noisebridge.net/wiki/MyAwesomeHackerProject</nowiki></code>. So you can put a /w/ between nb.wtf and the exact name of a page on the wiki, without having to add that page explicitly to this table.

===QR codes===
Finally, the nb.wtf service can generate QR codes that point to the target URL of shortcodes. So if you go to https://nb.wtf/about?qr you will get a QR code that points to [[About|About.]]

Any text in this page besides the first table encountered is ignored.
==Code & Operation==
The service should update (link should be live) within seconds of saving this page, assuming the NBWTF extension is installed and operating properly on this wiki. If it doesn't work automatically, you can [https://nb.wtf/api/v1/on_update ping the site directly] to force an update. If the site itself isn't working, you probably should ask [[User:Audiodude]]

For the code that makes this work, see https://github.com/audiodude/nb.wtf

===Links===

{| class="wikitable" style="margin:auto;"
|+ nb.wtf links
|-
! nb.wtf/ !! URL
|-
|nb
|[[Noisebridge]]
|-
|n
|[[Noisebridge]]
|-
|about
|[[About]]
|-
|report
|https://safespace.noisebridge.net/
|-
|donate
|[[Donate or Pay Dues]]
|-
|paypal
| https://www.paypal.com/donate/?cmd=_donations&business=treasurer%40noisebridge.net&lc=US&item_name=Noisebridge%20Donation&currency_code=USD
|-
|meeting
|[[Meeting]]
|-
|mtg
|[[Meetings]]
|-
|mtgv
|https://meet.jit.si/nbmeeting
|-
|mtgp
|https://pad.riseup.net/p/nbmeeting
|-
|events
|[[Events]]
|-
|host
|[[Hosting an Event]]
|-
|cal
|[[Events]]
|-
|calendar
|[[Events]]
|-
|cs
|[[Community Standards]]
|-
|logo
|[[Logo]]
|-
|notes
|https://pad.riseup.net/p/nbmeeting
|-
|joindiscord
|{{discord_link}}
|-
|discord!
|{{:Discord link}}
|-
|discord
|[[Discord]]
|-
|pyclass
|[[PyClass]]
|-
|consensus
|[[Consensus]]
|-
| 15 ||[[NB15Q]]
|-
| 16 ||[[NB16]]
|-
|auction15
|https://givebutter.com/c/OVhk3V/auction
|-
|sudo ||https://sudoroom.org/
|-
|spacebridge ||[[Spacebridge: The Next Generation]]
|-
|spacebridge-notes ||https://docs.google.com/document/d/1YasXd6d9ojCT7fCZXC0soYAJwO0hCMAUHZ4nushwC9M/edit?tab=t.0
|-
| ! || [[Nb.wtf]]
|-
|nb.wtf ||https://github.com/audiodude/nb.wtf/
|-
|atl
|[[AskToLeave]]
|-
|ats
|[[AskToStay]]
|-
|ghi
|https://github.com/noisebridge/infrastructure
|-
|gh
|https://github.com/noisebridge
|-
|tour-suggestions
|https://forms.gle/hQNKKCBQLj7Qir788
|-
|olympus
|[[Olympus]]
|-
|ft
|FlaschenTaschen
|-
|infra
|[[Meetups/Infra]]
|-
|infran
|https://pad.riseup.net/p/nb-meetup-infra
|-
|infrav
|https://meet.jit.si/nb-meetup-infra
|-
|mediabridge
|https://github.com/noisebridge/MediaBridge
|-
|5min
|[[5mof]]
|-
|5mof
|[[5mof]]
|-
|MF25
|[[Maker_Faire_2025/Met]]
|
|-
|MF25party
|https://luma.com/nbmrk6qb
|-
|bad-idea
|https://nb.wtf/bad-idea
|}

{| class="wikitable" style="margin:auto;"
| style="text-align:center" |{{#qrlite:|format=png|size=5|margin=0}}
|-
|{{fullurl:{{FULLPAGENAME}}}}
|}

Sewing

2025-11-25T21:23:12Z

ElanHR: /* Repair Instructions */

{{sewing}}
{{blackbox}}[[File:Sewingstation.jpg|200px|right]] You are in the Sewing Studio of Noisebridge [[upstairs]].

You see sewing machines, fabric, a large cutting table, sewing tools, and knitting machines.

'''EXITS:''' [[Upstairs]]
{{cursorboxend}}
{{headerbox}}
'''Noisebridge's sewing guild hosts sewing events and maintains three industrial sewing machines, a variety of domestic sewing machines, and knitting machines.'''

* '''RESOURCES:''' Sewing Machines, Knitting Machines, Rug-making Machine, [[Vinyl Cutter]] (downstairs near Print Shop)
* '''EVENTS:'''
* '''CHANNELS:''' #sewingstation on [[Slack]], [https://discord.gg/VzQPXCmW Sewing Channel on Discord]
* '''GET TRAINED:''' [[Sewing/Who_can_use_the_sewing_machines|Who can use the sewing machines]]
* '''MAINTAINERS:''' {{:Sewing/Maintainers}}</span>
{{recruiting}}
{{photography}}
{{boxend}}

[[File:Sewingstation.jpg|500px|link=sewing|right|thumb|The [[2169]] sewing station. The [[272]] version is upstairs.]]
[[Image:Starfive - q's noisebridge project.jpg|thumb|right|Craft hacking]]

=EVENTS=

* [[Sewing Project Night]]
* Open Project Night, an unstructured event in which participants brought their own projects for repair and alterations help, advice on techniques, materials, and machines, starting a new project with materials at the space, and just having fun sewing with fellow makers
* Sew With Knits, in which we went over how to operate the industrial serger, how to operate the domestic coverstitch, overview of domestic sewing machine stitch types appropriate for stretch knit material, and advice on participants' projects

==Past Events==
* In early 2019, we had a “Sewing Machine Fix-a-Thon” in which we serviced some of our sewing machines and determined what parts needed to be ordered.

=HOW TO BE EXCELLENT BY NOT BREAKING THE MACHINES=

We have home machines and industrial machines, and the home machines are all, to varying degrees, much more breakable. They're consumer products, often designed and built with a modern “what is this ‘repair’ of which you speak?” mindset, not built to withstand abuse or rough handling.

To that end, here are some strong guidelines for how to Be Excellent and use the home sewing machines in ways that don't break them:

# '''First, always be gentle.''' Treat the machine like a puppy. It will bite you, die, or incur a huge bill if you damage it.
# '''Do not pull fabric through the machine.''' Let the feed dogs do the work, or drop them if you want to free-sew or embroider. Pulling work through the machine is a good way to bend or break the needle, damage the bobbin and/or bobbin case and/or shuttle, pull the shuttle out of phase, or otherwise damage something. You're lucky if it's the needle or bobbin; those are replaceable. Anything else takes the machine out of commission.
#* If fabric isn't feeding properly, you may need to adjust the presser foot pressure. See point #4.
# '''Always turn the handwheel the correct direction''' On most of our machines, this is '''towards you'''. If you can't remember, press lightly on the pedal and you'll be able to feel which way the handwheel wants to turn. Turning the handwheel the wrong way won't necessarily break the machine, but it can mess up your stitch, break your thread, or cause a snarl that can break the needle.
# '''Change the machine's configuration as you need, but put it back when you're done.''' Every machine should have a standard presser foot and a “universal” needle (size 90/14) loaded when not in use. It should be on the default settings for presser foot pressure and tension. Anyone who needs something different should make whatever changes they need, '''and''' change them back before they put the machine away/leave.
# '''Put the machine away when you're done/before leaving.''' The cutting table is not a machine storage rack.
# '''Keep the machine's parts with the machine.''' Some machines have a storage compartment on the front of the bed (the bottom portion of the machine where the bobbin is). The domestic machines have a kit for holding bobbins, feet, needles, spool caps, screwdrivers, and anything else necessary to using the machine. The pedal should be kept with the machine at all times, and should have a paper tag tied to it identifying which machine it belongs to. (Such tags are kept in a drawer in the sewing area.)
# '''Use the correct needle, and change the needle when needed.''' Always check which needle is loaded into the machine before you start sewing—make sure it's right for the type (woven vs. knit vs. solid) of fabric, the tightness of weave/knit, and the weight of the fabric.
#* Non-woven materials such as leather or vinyl require special “leather” needles, made to pierce solid objects. Knitted fabrics, including T-shirt fabric, require “ball point” needles, which are less likely to pierce/cut a yarn. Tight weaves such as microsuede may require “microtex” or “sharp” needles that can find their way between the yarns. Denim and heavy canvas may require “denim” (a.k.a. “jeans”) needles. Most normal woven fabrics will work with a “universal” needle.
#* If you're using the right kind of needle but it isn't going through/is skipping stitches or is stitching irregularly or with difficulty, try a heavier diameter or (if woven) a denim needle. Most likely the needle is not able to cleanly penetrate the fabric. Continuing to sew in this state is a good way to permanently bend (i.e., ruin) or break the needle.
#* Needles wear out! They are a consumable. If you're pretty sure you have the right kind and diameter of needle, change it out for another like one. If that works better, safely dispose of the worn needle—don't put it back for some other sucker to try.
# '''Avoid computerized machines unless you ''really'' need them.''' Computerized machines are much more delicate than mechanical machines. The best reason to use a computerized machine is it's the one with embroidery features and you need that. Otherwise, take a mechanical one such as the Kenmore 385 if it's available—they hold up better.
# '''Use the correct type of bobbin for the machine you're using.''' Bobbins come in a variety of types, including Class 15, Class 15J, Class 66, and numerous oddballs. This page lists the correct type of bobbin for each machine, and the same information should soon be stickered onto all of our machines. Any machine, otherwise working, may fail to sew correctly (skipped stitches, shuttle snarls, etc.) with the wrong kind of bobbin in it.
# '''Do not use a damaged or broken bobbin.''' If it's cracked, chipped, or bent, don't use it. Transfer the thread (if any) to a new bobbin of the same type (or of the type for the machine you're going to use), then chuck the busted bobbin in the trash.

=RESOURCES=

==Sewing Machines==

===Industrial Sewing Machines===
* [[Juki DDL-227 Straight Stitch]]
* [[Singer 251-12 Straight Stitch]]
* [[Juki LU-563 Walking Foot]]
* [[Juki MO-2416 Serger]] (subclass FF6-500)
*Shoe Patcher, hand cranked (not yet up and running)

===Domestic Sewing Machines===
*[[Bernette 55]]
*[[Singer 4166]]
*[[Brother XR135]]
*[[White E-6354]]
*[[Singer Stylist 533]]
*[[Kenmore 385]]
*Singer SEQS-6700 Embroidery Machine
*Coverstitch

===Other Amenities===
* Large table with cutting mat surface (50 inches x ? inches )
* Irons and Ironing board
* Sewing/craft/fashion library
* Domestic knitting machines
* Buttons, buckles, zipper, grommets, etc
* 1 dress form
* Full length mirror

===Before donating a machine to Noisebridge===

Please reach out to a maintainer. We're looking to simplify our fleet. At the very least, this will mean getting rid of home machines that don't meet certain criteria (Class 15 bobbins, drop-in bobbin case, ''works'', etc.). We may go further than that and standardize on one model, but that's TBD.

The Community Thrift Store on Valencia would also probably love to have it.

=== Sewing Machine Usage Tips ===
* Please DO NOT unthread the sewing machines unless you must. (e.g. to remove a spool of thread, simply cut it close to the spool so that the next person can simply tie a knot with the next thread and pull it all the way through to the needle). This is most important for the serger.

* Domestic and industrial machines use different needles, bobbins, and feet, so check to make sure you are using the right kind. The industrial machines each have a kit hanging on the pegboard behind them. Domestic machine supplies are either in a kit on the table, or are located in labeled drawers on the white cabinet (PLEASE KEEP IT ORGANIZED).
** The closest place to get domestic machine parts and supplies is Fabric Outlet on Mission between 17th & 18th st. Industrial machine parts are only available by mail order (if you know anyone local please let us know)
** Needles may differ between machines and come in sizes (10, 11, 12, 14, 16, etc.). The higher numbers are heavier gauge needles suitable for thicker fabrics.
** Needles also come in different types, including (this is an abridged list; look to other sites for more complete lists):
***Jersey: Has a ball point, for knitted fabrics (including T-shirt fabric).
***“Universal”: Moderately sharp, for most woven fabrics. Denim needles are the same but more rigid, for tighter weaves of thick yarns (like denim or canvas).
***Microtex needles are the sharpest, for tight weaves of thin yarns, like microsuede or nylon.
***Leather needles have a tiny blade at the tip, for cutting holes in leather and vinyl. Don't use a leather needle for woven or knitted fabrics: The blade will cut the threads rather than squeezing between them, leaving holes that may start rips.
**Needles for the industrial straight stitch and walking foot machines must be inserted with the scarf facing right. Please check the respective manuals.

* If you've never operated a sewing machine before please attend a Sewing 101, which happens every 2nd friday, before you use our machines on your own. The class fills up and has a waitlist, so we ask that you only come if you've secured a spot on Meetup. Sewing machines are delicate creatures and we want to minimize the amount of breakage.
**Read the manual! You'll probably learn something even if you've been sewing for a long time.
**Printed manuals for each industrial machine are in the gray binder on the bookshelf. We don't have manuals printed for all the domestics, but a Google search should bring them up.

*Use scraps for testing to determine thread tension and sewing speed.

===Recommended reading===

[http://www.threadsmagazine.com/item/3751/machine-needle-know-how About sewing machine needles]

[http://www.threadsmagazine.com/item/6847/perfect-machine-tension-every-time Understanding thread tension]

[http://leatherworker.net/forum/index.php?showtopic=25126&st=0 Sew heavy material]

[http://www.wipo.int/pctdb/en/wo.jsp?WO=2002000984&IA=US2001041173&DISPLAY=STATUS What is a thread wiper?]

[http://www.citysewing.com/diference-between-clutch-motor-servo-motor/ Difference between clutch and servo motors]

==Winding a Bobbin==

=== Juki DDL-227 & Juki LU-563 ===
*To wind a bobbin, place the empty bobbin on the horizontal spindle to the right of the machine body (near the hand wheel). Run a second thread through the upper holder, down to the tensioner at the back of the right side of the machine, in line with the spindle. Thread the end through one of the holes in the bobbin side, from the inside to the outside. Press the lever to push the spindle down in contact with the sewing machine belt. While holding the thread end so it doesn't just whip out of the bobbin, press the pedal to run a couple of inches (if there were fabric in the machine). Soon enough you can let go of the thread end as it will have been caught by windings on top of it. If you are doing a lot of sewing, you can start a new bobbin before the current one is empty, and let it wind up as you sew. When the bobbin is full, the lever will automatically snap out away from the belt and stop winding thread.

=== Most home sewing machines ===
The bobbin winder is usually on the top of the machine near the right corner (right being the side with the handwheel). It should look like a short spindle that can't be removed and sticks up about half an inch (the thickness of a bobbin) from a flat round surface.

Place a bobbin on the spindle, then:

* On some machines, the handwheel can be pulled out to switch from sewing to bobbin-winding. (Push it back in when you're done winding bobbins.)
* On the big Singer machine, the handwheel has a part that flips up to engage the bobbin-winder.
* On the Brother machines, the bobbin spindle can be slid between the left (sewing) and right (winding). In the latter position, a brake slightly intersects the bobbin and will stop it from getting over-wound.

Once the machine is in winding mode and is powered on, press the pedal slightly and make sure thread is going onto the bobbin properly. Once it's winding properly, floor the pedal until the bobbin is fully wound (some machines will stop the bobbin automatically; others may require you to pay attention).

Remember to switch the machine back to sewing mode when you're done winding bobbins!!!

== Repairing a Sewing Machine ==
Before declaring a machine broken, try the steps on [[Sewing/Troubleshooting]] first.

If a sewing machine is actually broken and non functional, as opposed to just you can't figure out how to make it work, please call Billy from Apparel City at 415-816-8645 (mobile) and schedule an appointment for him to come fix it.
* He usually charges around $80 per hour, plus parts.
* Email the [https://www.noisebridge.net/mailman/listinfo/sewing/|sewing list] and people will chip in to cover this. If you can't manage this process, email the sewing list and find someone else who can. Also, please put a note on the machine so people know what is going on with it.

= Sewing Machines =

== 130-Stitch Computerized Sewing and Quilting (Brother XR1355) ==
'''Works''' as of 2021-12-28

This machine is on the home sewing machine table (Table 3).

=== Overview ===
* This machine does 130 different stitches including lots of cool decorative flowers and patterns.
* Bobbin: Clear plastic, class 15 ([https://www.joann.com/brother-sa156-clear-plastic-class-15-bobbin/16386419.html Brother SA156]). Please use bobbins in Table 3 toolbox.

=== Manual for Brother XR1355 ===

* PDF - http://download.brother.com/welcome/doch001142/xr1355ug02en.pdf
*Spanish copy located on bookshelf in grey binder.

== Singer Simple 3229 sewing machine ==
'''Works''' as of 7-17-2021

*Manual: [https://manual.singer.com/Manuals/RetrievePDF/195 pdf]
*Bobbin: [https://www.singeronline.com/si15clbo.html Class 15]. Use bobbins in the toolbox on Table 3.

=Specialty Machines=

== Brother Coverstitch Serger ==
'''Works''' as of 2022-02-15
This machine is on Table 4. This machine is useful to alter and finish clothes (hems).

=== Overview ===
*intro ([https://www.youtube.com/watch?v=fwYR3pUFJJw])
*narrow cover stitches (no tri-cover stitch as the third needle was broken in the head of the machine.
*should work for a variety of fabrics

=== Manual ===
([https://support.brother.com/g/b/manualtop.aspx?c=us&lang=en&prod=hf_2340cveus])

=== Repair Instructions ===

{{#ev:youtube|IG23Sy5pS0g||center|A huge thanks Farley and Ken for putting together this video!|frame||true|middle|width=50%}}

== Leather Stitching Machine ==
https://www.youtube.com/watch?v=zawvl5ZZIdI

== Knitting Machine ==
We have a [[Industrial Knitting Machine|Raynen CHJX-1-52 52-inch flat knitting machine]].

== '''[https://www.youtube.com/watch?v=RYQY5-UepEk Watch Video Tour March 2023]''' ==

= Manual Snap Setting Tools =
We have hand presses but no dies for them.

There are a few misc. hand-setting tools in the grommets box

= Scissors =

The sewing station includes a variety of scissors, including straight scissors/shears, a pair of pinking shears, and a couple other specialty scissors.

'''DO NOT USE FABRIC SCISSORS FOR ANYTHING THAT ISN'T FABRIC.''' Paper and other non-fabric things will rapidly dull blades to the point where we need to sharpen them again to use them on fabric.

There are some “paper only” (i.e., pre-ruined) scissors on the tools wall since we know people will look in the sewing section for scissors. There are also some “fabric only” (i.e., not yet ruined) scissors that should only ever be used for fabric.

Also related: There is a sharpening stone on the tools wall in the sewing station.

= Thread snips =

Thread snips are the small scissor-like tools used for cutting the thread sticking out of a work so you can remove the work from the machine.

Thread snips shouldn't be used to cut fabric—use the fabric shears (scissors) or rotary cutters for that. Neither should they be used on non-fabric things like paper or tape.

There are three pairs of thread snips hanging from the tools wall in the sewing section.

= Rotary cutters =

These look similar to pizza cutters but are '''NOT FOR FOOD USE''' (both because it trashes the blade and because the blades are not food-safe: new blades are coated in machine oil).

All of our rotary cutters are 45mm, except for one, which is 60mm but has no blade. It's unclear whether we'll keep that one, since we would need to keep 60mm blades in stock and that would mean figuring out where to keep them and what to use them for.

== How to use ==

Each rotary cutter has a cutting (blade extended) position and a safe (blade retracted) position. The Olfa ergonomic cutters will also spring back to retracted automatically, and can't be extended unless the safety button is pushed to the unlocked side.

Rotary cutters should be used on a cutting mat such as the one on the main sewing station table. Usually you want a straight cut, so you should use an acrylic ruler to guide the blade.

Rotary cutters are EXTREMELY sharp, so be careful. Please keep the cutter blade-side-up so it's less likely to come into accidental contact with the table or anything on it—if you can see the blade, you can avoid contact with it.

=== Safety tips ===

*Follow an acrylic ruler.
*Keep your body (including fingers) out of the path of the blade.
*Only use a sharp blade. Don't use a rotary cutter with a dull or trashed blade. Change out the blade if you have to.
*Don't force it to cut if it's not cutting.

== Maintenance ==

Rotary cutters are mostly pretty foolproof. As long as you don't cut yourself, your ruler, wood, another rotary cutter, a 1973 Oldsmobile, or anything else that isn't fabric, the blade should enjoy a good, long life.

But, every blade wears down eventually. Blade sharpeners exist, but we don't currently have one, and a sharpener can't save a chipped or bent blade.

If a blade can't be sharpened, there are new 45mm blades in the storage drawers along the wall.

=== Changing the blade ===

Different rotary cutters have different parts, but they all have these four, in this order:

*Hub/screw
*Rotary cutter body
*Blade
*Nut

You should try to keep all of the parts (including those not listed—some cutters do have some bonus parts) in the correct order. If you get the order wrong, the blade might not spin freely or it might be too far from the cutter body. If that's the case, no biggie, just disassemble and try again.

No tools are needed.

#Remove the nut by hand, keeping your thumb on the hub/screw on the other side.
#Gently turn the cutter over and let the blade fall out onto your fingers, and any other parts onto the table.
#Sharpen or replace the blade.
#Put the blade onto the screw.
#Put the screw (with blade) into the cutter, and put all of the other parts, ending with the nut, onto the other side.

= Parts Needed =

Some of the parts (especially pedals and/or cords) for the sewing machines have, shall we say, installed a walking foot. Here's what we're currently missing:

=HISTORY=
*2008: Noisebridge began having sewing machines at [[83c]].
*2009: Rachel [[Industrial_Sewing_Machine_Donations|purchased industrial sewing machines]] from the sewing shop that formerly occupied Noisebridge's 2169 space with member donations and held its first [[Sewing Workshop]] at [[2169]].
*2015: Grand reopening event of the rebooted Sewing Station.
*2019: Sewing station moved over near the fire escape. Also, we did a Sewing Machine Fix-a-Thon and started holding training classes.

==Grand Reopening Poster ==

[[File:Sewing-Area-Poster.jpg|none|300px]]

== Machines not currently available (location unknown or else) ==

====Brother XR1355====
Status: Location unknown as of 2023-04-20
130-Stitch Computerized Sewing and Quilting (Brother XR1355) Works as of 2021-12-28
This machine is on the home sewing machine table (Table 3).
Overview This machine does 130 different stitches including lots of cool decorative flowers and patterns. Bobbin: Clear plastic, class 15 (Brother SA156). Please use bobbins in Table 3 toolbox.

====Singer Ultralock 14U64A serger====
Status: Broken as of 2023/02. Ready for discard
Type: Domestic serger
Year: probably 1990s
Notes:dropped when being carried by handle. On/off switch broken, possible replacement part found, just needs to be wired on. side plastic casing broken, could possibly be repaired with plastic molding material. Part not necessary to functioning, but nice to have to protect machine from dust
This is a four-thread overlock machine. It's evidently meant for knitted fabrics, as a silkscreened note on the upper-left of the front of the machine notes that it requires a Singer 2045 needle, which is a ball point.
The thread guides above the machine are on a pole that telescopes out. Make sure to raise it before using the machine; it works better that way.
*Manual: http://www.singerco.com/uploads/download/974c69637ba13cd29bf98419910a853043dc9e83.pdf
*Parts list: http://parts.singerco.com/CPpartCharts/14U00/14U64A.pdf

====Brother Exedra E-40====
We've gotten rid of this machine (when we moved the sewing station over to the fire escape) but we still have the digitized manual: https://www.noisebridge.net/wiki/File:Brother_E-40_Operation_Panel_Instruction_Manual.pdf

====Kenmore Overlock 3/4D====
Manual: In Manuals Collection, also https://www.noisebridge.net/wiki/File:Overlock_34d_38516631.compressed.pdf

====Brother SE400 Embroidery Machine====
'''currently missing''' as of 2021-07-14
This machine is awesome, and can do many different stitches as well as CNC embroidery.
It's usually stored on the wall of the sewing area. It looks like a home sewing machine but is as expensive as an industrial one and is many people's favorite machine.
* [[Embroidery Machine]]
* Bobbin: Class 15 ([https://www.joann.com/brother-sa156-clear-plastic-class-15-bobbin/16386419.html Brother SA156])
* Manual: https://download.brother.com/welcome/doch000184/885v31_v32_v33_om04en.pdf

====Pfaff Creative 1471 sewing machine====
'''Location unknown''' as of 2021-7-14
This machine has a bobbin case, so it requires a little bit more knowledge to change out the bobbin than newer machines that have a top drop-in bobbin.
*Bobbin: Special metal bobbins. There's a parts drawer specifically for Pfaff bobbins.
*Manual: http://www.pfaff.com/SiteMedia/PFAFF/Products/Machines/Support-manuals/creative1471-manual-EN.pdf

====Singer CG-590-C====
Manual: In Manuals Collection

====White YM-43-8====
Manual: Unknown

====Singer 621-B====
Manual: Unknown

====Singer Heavy Duty 4423 sewing machine====
'''Broken''' as of 2019-11-04: Shuttle pops up out of bobbin race, resulting in failure to make stitches and internal pressure upon the bobbin race door.
Has a top drop-in bobbin. Likely to become our workhorse, as the Heavy Duty is a sturdy mechanical machine.
Has a one-step buttonhole feature with a plastic buttonhole foot. Tricky to use but handy if you know how.
A knob on the top of the machine, near the slot where the take-up lever pops up, enables adjusting the presser foot pressure. Like top thread tension, this should generally not be messed with and should be put back after a job that does require adjusting it, but changing the presser foot pressure makes sense in certain circumstances:
*For thick works such as three or more layers of denim (e.g., when hemming denim garments), reduce the presser foot pressure in order to be able to drive over the inseam and outseam.
*For light works made of thin or sheer fabrics, or slippery fabrics, you may need to increase the pressure to ensure the feed dogs can properly feed (all layers of) the work.
'''Always put the presser foot pressure back how it was when you're done!!!''' Setting up future machine-users for difficulty/failure is un-excellent.
*Bobbin: Class 15
*Quick-start guide: http://www.singerco.com/uploads/download/HD%20Series_ANT_Generic_QSG_F_0222_lo-res.pdf
*Manual: http://www.singerco.com/uploads/download/a719909a6ca001462cb1c2536a04506fa9ff327c.pdf

====Singer 57817====
'''Works''' as of 2020-01-06. Missing the reverse button, though.
This machine can only do straight and zigzag stitches. No overcast or anything else.
*Bobbin: [https://www.sewingpartsonline.com/singer-57817-sewing-machine-parts.aspx?sort.ss_cat_sort=desc&keywords=bobbin&index=1 Class 66]
*Manual: https://www.noisebridge.net/wiki/File:Singer_57817.pdf

====Brother XL-2300i====
Currently on the top of one of the sewing area shelves.
Overview
* Bobbin: Class 15 ([https://www.joann.com/brother-sa156-clear-plastic-class-15-bobbin/16386419.html Brother SA156])
Manual + quick set-up guide
* https://support.brother.com/g/b/manualtop.aspx?c=us&lang=en&prod=hf_xl2600i2610eus

====Automatic Snap Setting Machines====
In November 2020 we received a generous donation of two Automatic Snap Machines worth over $4000 from Craig Spring http://www.brotus.com !

One pair (one female, one male) of fully automatic, electric powered, 20 line, snap setting machines. These are older model machines manufactured by the Ho Hung Ming company in Taiwan (https://www.hohm.com).

They have a US location at: Ho Hung Ming USA Enterprise, 13525 Alma Ave, Gardena, CA 90249, Phone: 3103274847.

One of the advantages of these older machines is that they are simple mechanical machines built to last. Like an old car, they are easier to repair than newer ones. In 22 years, he never needed to repair these machines. They still run like a beast.

As there exists no manual for these machines, Craig and DK gave a servicing and use demonstration on Nov 15, 2020 via Jitsi and X uploaded it to https://www.youtube.com/watch?v=dc2ozToy38Q

Photos are at https://discuss.noisebridge.info/t/automatic-snap-setting-machines-donation-instructions/2132

[[Category:Pages with a Noisebridge Tiny URL]]
{{guilds}}

Sewing

2025-11-25T07:06:24Z

ElanHR: /* Repair Instructions */

{{sewing}}
{{blackbox}}[[File:Sewingstation.jpg|200px|right]] You are in the Sewing Studio of Noisebridge [[upstairs]].

You see sewing machines, fabric, a large cutting table, sewing tools, and knitting machines.

'''EXITS:''' [[Upstairs]]
{{cursorboxend}}
{{headerbox}}
'''Noisebridge's sewing guild hosts sewing events and maintains three industrial sewing machines, a variety of domestic sewing machines, and knitting machines.'''

* '''RESOURCES:''' Sewing Machines, Knitting Machines, Rug-making Machine, [[Vinyl Cutter]] (downstairs near Print Shop)
* '''EVENTS:'''
* '''CHANNELS:''' #sewingstation on [[Slack]], [https://discord.gg/VzQPXCmW Sewing Channel on Discord]
* '''GET TRAINED:''' [[Sewing/Who_can_use_the_sewing_machines|Who can use the sewing machines]]
* '''MAINTAINERS:''' {{:Sewing/Maintainers}}</span>
{{recruiting}}
{{photography}}
{{boxend}}

[[File:Sewingstation.jpg|500px|link=sewing|right|thumb|The [[2169]] sewing station. The [[272]] version is upstairs.]]
[[Image:Starfive - q's noisebridge project.jpg|thumb|right|Craft hacking]]

=EVENTS=

* [[Sewing Project Night]]
* Open Project Night, an unstructured event in which participants brought their own projects for repair and alterations help, advice on techniques, materials, and machines, starting a new project with materials at the space, and just having fun sewing with fellow makers
* Sew With Knits, in which we went over how to operate the industrial serger, how to operate the domestic coverstitch, overview of domestic sewing machine stitch types appropriate for stretch knit material, and advice on participants' projects

==Past Events==
* In early 2019, we had a “Sewing Machine Fix-a-Thon” in which we serviced some of our sewing machines and determined what parts needed to be ordered.

=HOW TO BE EXCELLENT BY NOT BREAKING THE MACHINES=

We have home machines and industrial machines, and the home machines are all, to varying degrees, much more breakable. They're consumer products, often designed and built with a modern “what is this ‘repair’ of which you speak?” mindset, not built to withstand abuse or rough handling.

To that end, here are some strong guidelines for how to Be Excellent and use the home sewing machines in ways that don't break them:

# '''First, always be gentle.''' Treat the machine like a puppy. It will bite you, die, or incur a huge bill if you damage it.
# '''Do not pull fabric through the machine.''' Let the feed dogs do the work, or drop them if you want to free-sew or embroider. Pulling work through the machine is a good way to bend or break the needle, damage the bobbin and/or bobbin case and/or shuttle, pull the shuttle out of phase, or otherwise damage something. You're lucky if it's the needle or bobbin; those are replaceable. Anything else takes the machine out of commission.
#* If fabric isn't feeding properly, you may need to adjust the presser foot pressure. See point #4.
# '''Always turn the handwheel the correct direction''' On most of our machines, this is '''towards you'''. If you can't remember, press lightly on the pedal and you'll be able to feel which way the handwheel wants to turn. Turning the handwheel the wrong way won't necessarily break the machine, but it can mess up your stitch, break your thread, or cause a snarl that can break the needle.
# '''Change the machine's configuration as you need, but put it back when you're done.''' Every machine should have a standard presser foot and a “universal” needle (size 90/14) loaded when not in use. It should be on the default settings for presser foot pressure and tension. Anyone who needs something different should make whatever changes they need, '''and''' change them back before they put the machine away/leave.
# '''Put the machine away when you're done/before leaving.''' The cutting table is not a machine storage rack.
# '''Keep the machine's parts with the machine.''' Some machines have a storage compartment on the front of the bed (the bottom portion of the machine where the bobbin is). The domestic machines have a kit for holding bobbins, feet, needles, spool caps, screwdrivers, and anything else necessary to using the machine. The pedal should be kept with the machine at all times, and should have a paper tag tied to it identifying which machine it belongs to. (Such tags are kept in a drawer in the sewing area.)
# '''Use the correct needle, and change the needle when needed.''' Always check which needle is loaded into the machine before you start sewing—make sure it's right for the type (woven vs. knit vs. solid) of fabric, the tightness of weave/knit, and the weight of the fabric.
#* Non-woven materials such as leather or vinyl require special “leather” needles, made to pierce solid objects. Knitted fabrics, including T-shirt fabric, require “ball point” needles, which are less likely to pierce/cut a yarn. Tight weaves such as microsuede may require “microtex” or “sharp” needles that can find their way between the yarns. Denim and heavy canvas may require “denim” (a.k.a. “jeans”) needles. Most normal woven fabrics will work with a “universal” needle.
#* If you're using the right kind of needle but it isn't going through/is skipping stitches or is stitching irregularly or with difficulty, try a heavier diameter or (if woven) a denim needle. Most likely the needle is not able to cleanly penetrate the fabric. Continuing to sew in this state is a good way to permanently bend (i.e., ruin) or break the needle.
#* Needles wear out! They are a consumable. If you're pretty sure you have the right kind and diameter of needle, change it out for another like one. If that works better, safely dispose of the worn needle—don't put it back for some other sucker to try.
# '''Avoid computerized machines unless you ''really'' need them.''' Computerized machines are much more delicate than mechanical machines. The best reason to use a computerized machine is it's the one with embroidery features and you need that. Otherwise, take a mechanical one such as the Kenmore 385 if it's available—they hold up better.
# '''Use the correct type of bobbin for the machine you're using.''' Bobbins come in a variety of types, including Class 15, Class 15J, Class 66, and numerous oddballs. This page lists the correct type of bobbin for each machine, and the same information should soon be stickered onto all of our machines. Any machine, otherwise working, may fail to sew correctly (skipped stitches, shuttle snarls, etc.) with the wrong kind of bobbin in it.
# '''Do not use a damaged or broken bobbin.''' If it's cracked, chipped, or bent, don't use it. Transfer the thread (if any) to a new bobbin of the same type (or of the type for the machine you're going to use), then chuck the busted bobbin in the trash.

=RESOURCES=

==Sewing Machines==

===Industrial Sewing Machines===
* [[Juki DDL-227 Straight Stitch]]
* [[Singer 251-12 Straight Stitch]]
* [[Juki LU-563 Walking Foot]]
* [[Juki MO-2416 Serger]] (subclass FF6-500)
*Shoe Patcher, hand cranked (not yet up and running)

===Domestic Sewing Machines===
*[[Bernette 55]]
*[[Singer 4166]]
*[[Brother XR135]]
*[[White E-6354]]
*[[Singer Stylist 533]]
*[[Kenmore 385]]
*Singer SEQS-6700 Embroidery Machine
*Coverstitch

===Other Amenities===
* Large table with cutting mat surface (50 inches x ? inches )
* Irons and Ironing board
* Sewing/craft/fashion library
* Domestic knitting machines
* Buttons, buckles, zipper, grommets, etc
* 1 dress form
* Full length mirror

===Before donating a machine to Noisebridge===

Please reach out to a maintainer. We're looking to simplify our fleet. At the very least, this will mean getting rid of home machines that don't meet certain criteria (Class 15 bobbins, drop-in bobbin case, ''works'', etc.). We may go further than that and standardize on one model, but that's TBD.

The Community Thrift Store on Valencia would also probably love to have it.

=== Sewing Machine Usage Tips ===
* Please DO NOT unthread the sewing machines unless you must. (e.g. to remove a spool of thread, simply cut it close to the spool so that the next person can simply tie a knot with the next thread and pull it all the way through to the needle). This is most important for the serger.

* Domestic and industrial machines use different needles, bobbins, and feet, so check to make sure you are using the right kind. The industrial machines each have a kit hanging on the pegboard behind them. Domestic machine supplies are either in a kit on the table, or are located in labeled drawers on the white cabinet (PLEASE KEEP IT ORGANIZED).
** The closest place to get domestic machine parts and supplies is Fabric Outlet on Mission between 17th & 18th st. Industrial machine parts are only available by mail order (if you know anyone local please let us know)
** Needles may differ between machines and come in sizes (10, 11, 12, 14, 16, etc.). The higher numbers are heavier gauge needles suitable for thicker fabrics.
** Needles also come in different types, including (this is an abridged list; look to other sites for more complete lists):
***Jersey: Has a ball point, for knitted fabrics (including T-shirt fabric).
***“Universal”: Moderately sharp, for most woven fabrics. Denim needles are the same but more rigid, for tighter weaves of thick yarns (like denim or canvas).
***Microtex needles are the sharpest, for tight weaves of thin yarns, like microsuede or nylon.
***Leather needles have a tiny blade at the tip, for cutting holes in leather and vinyl. Don't use a leather needle for woven or knitted fabrics: The blade will cut the threads rather than squeezing between them, leaving holes that may start rips.
**Needles for the industrial straight stitch and walking foot machines must be inserted with the scarf facing right. Please check the respective manuals.

* If you've never operated a sewing machine before please attend a Sewing 101, which happens every 2nd friday, before you use our machines on your own. The class fills up and has a waitlist, so we ask that you only come if you've secured a spot on Meetup. Sewing machines are delicate creatures and we want to minimize the amount of breakage.
**Read the manual! You'll probably learn something even if you've been sewing for a long time.
**Printed manuals for each industrial machine are in the gray binder on the bookshelf. We don't have manuals printed for all the domestics, but a Google search should bring them up.

*Use scraps for testing to determine thread tension and sewing speed.

===Recommended reading===

[http://www.threadsmagazine.com/item/3751/machine-needle-know-how About sewing machine needles]

[http://www.threadsmagazine.com/item/6847/perfect-machine-tension-every-time Understanding thread tension]

[http://leatherworker.net/forum/index.php?showtopic=25126&st=0 Sew heavy material]

[http://www.wipo.int/pctdb/en/wo.jsp?WO=2002000984&IA=US2001041173&DISPLAY=STATUS What is a thread wiper?]

[http://www.citysewing.com/diference-between-clutch-motor-servo-motor/ Difference between clutch and servo motors]

==Winding a Bobbin==

=== Juki DDL-227 & Juki LU-563 ===
*To wind a bobbin, place the empty bobbin on the horizontal spindle to the right of the machine body (near the hand wheel). Run a second thread through the upper holder, down to the tensioner at the back of the right side of the machine, in line with the spindle. Thread the end through one of the holes in the bobbin side, from the inside to the outside. Press the lever to push the spindle down in contact with the sewing machine belt. While holding the thread end so it doesn't just whip out of the bobbin, press the pedal to run a couple of inches (if there were fabric in the machine). Soon enough you can let go of the thread end as it will have been caught by windings on top of it. If you are doing a lot of sewing, you can start a new bobbin before the current one is empty, and let it wind up as you sew. When the bobbin is full, the lever will automatically snap out away from the belt and stop winding thread.

=== Most home sewing machines ===
The bobbin winder is usually on the top of the machine near the right corner (right being the side with the handwheel). It should look like a short spindle that can't be removed and sticks up about half an inch (the thickness of a bobbin) from a flat round surface.

Place a bobbin on the spindle, then:

* On some machines, the handwheel can be pulled out to switch from sewing to bobbin-winding. (Push it back in when you're done winding bobbins.)
* On the big Singer machine, the handwheel has a part that flips up to engage the bobbin-winder.
* On the Brother machines, the bobbin spindle can be slid between the left (sewing) and right (winding). In the latter position, a brake slightly intersects the bobbin and will stop it from getting over-wound.

Once the machine is in winding mode and is powered on, press the pedal slightly and make sure thread is going onto the bobbin properly. Once it's winding properly, floor the pedal until the bobbin is fully wound (some machines will stop the bobbin automatically; others may require you to pay attention).

Remember to switch the machine back to sewing mode when you're done winding bobbins!!!

== Repairing a Sewing Machine ==
Before declaring a machine broken, try the steps on [[Sewing/Troubleshooting]] first.

If a sewing machine is actually broken and non functional, as opposed to just you can't figure out how to make it work, please call Billy from Apparel City at 415-816-8645 (mobile) and schedule an appointment for him to come fix it.
* He usually charges around $80 per hour, plus parts.
* Email the [https://www.noisebridge.net/mailman/listinfo/sewing/|sewing list] and people will chip in to cover this. If you can't manage this process, email the sewing list and find someone else who can. Also, please put a note on the machine so people know what is going on with it.

= Sewing Machines =

== 130-Stitch Computerized Sewing and Quilting (Brother XR1355) ==
'''Works''' as of 2021-12-28

This machine is on the home sewing machine table (Table 3).

=== Overview ===
* This machine does 130 different stitches including lots of cool decorative flowers and patterns.
* Bobbin: Clear plastic, class 15 ([https://www.joann.com/brother-sa156-clear-plastic-class-15-bobbin/16386419.html Brother SA156]). Please use bobbins in Table 3 toolbox.

=== Manual for Brother XR1355 ===

* PDF - http://download.brother.com/welcome/doch001142/xr1355ug02en.pdf
*Spanish copy located on bookshelf in grey binder.

== Singer Simple 3229 sewing machine ==
'''Works''' as of 7-17-2021

*Manual: [https://manual.singer.com/Manuals/RetrievePDF/195 pdf]
*Bobbin: [https://www.singeronline.com/si15clbo.html Class 15]. Use bobbins in the toolbox on Table 3.

=Specialty Machines=

== Brother Coverstitch Serger ==
'''Works''' as of 2022-02-15
This machine is on Table 4. This machine is useful to alter and finish clothes (hems).

=== Overview ===
*intro ([https://www.youtube.com/watch?v=fwYR3pUFJJw])
*narrow cover stitches (no tri-cover stitch as the third needle was broken in the head of the machine.
*should work for a variety of fabrics

=== Manual ===
([https://support.brother.com/g/b/manualtop.aspx?c=us&lang=en&prod=hf_2340cveus])

=== Repair Instructions ===

{{#ev:youtube|IG23Sy5pS0g||center|A quick thanks Farley and Ken!|frame||true|middle|width=50%}}

== Leather Stitching Machine ==
https://www.youtube.com/watch?v=zawvl5ZZIdI

== Knitting Machine ==
We have a [[Industrial Knitting Machine|Raynen CHJX-1-52 52-inch flat knitting machine]].

== '''[https://www.youtube.com/watch?v=RYQY5-UepEk Watch Video Tour March 2023]''' ==

= Manual Snap Setting Tools =
We have hand presses but no dies for them.

There are a few misc. hand-setting tools in the grommets box

= Scissors =

The sewing station includes a variety of scissors, including straight scissors/shears, a pair of pinking shears, and a couple other specialty scissors.

'''DO NOT USE FABRIC SCISSORS FOR ANYTHING THAT ISN'T FABRIC.''' Paper and other non-fabric things will rapidly dull blades to the point where we need to sharpen them again to use them on fabric.

There are some “paper only” (i.e., pre-ruined) scissors on the tools wall since we know people will look in the sewing section for scissors. There are also some “fabric only” (i.e., not yet ruined) scissors that should only ever be used for fabric.

Also related: There is a sharpening stone on the tools wall in the sewing station.

= Thread snips =

Thread snips are the small scissor-like tools used for cutting the thread sticking out of a work so you can remove the work from the machine.

Thread snips shouldn't be used to cut fabric—use the fabric shears (scissors) or rotary cutters for that. Neither should they be used on non-fabric things like paper or tape.

There are three pairs of thread snips hanging from the tools wall in the sewing section.

= Rotary cutters =

These look similar to pizza cutters but are '''NOT FOR FOOD USE''' (both because it trashes the blade and because the blades are not food-safe: new blades are coated in machine oil).

All of our rotary cutters are 45mm, except for one, which is 60mm but has no blade. It's unclear whether we'll keep that one, since we would need to keep 60mm blades in stock and that would mean figuring out where to keep them and what to use them for.

== How to use ==

Each rotary cutter has a cutting (blade extended) position and a safe (blade retracted) position. The Olfa ergonomic cutters will also spring back to retracted automatically, and can't be extended unless the safety button is pushed to the unlocked side.

Rotary cutters should be used on a cutting mat such as the one on the main sewing station table. Usually you want a straight cut, so you should use an acrylic ruler to guide the blade.

Rotary cutters are EXTREMELY sharp, so be careful. Please keep the cutter blade-side-up so it's less likely to come into accidental contact with the table or anything on it—if you can see the blade, you can avoid contact with it.

=== Safety tips ===

*Follow an acrylic ruler.
*Keep your body (including fingers) out of the path of the blade.
*Only use a sharp blade. Don't use a rotary cutter with a dull or trashed blade. Change out the blade if you have to.
*Don't force it to cut if it's not cutting.

== Maintenance ==

Rotary cutters are mostly pretty foolproof. As long as you don't cut yourself, your ruler, wood, another rotary cutter, a 1973 Oldsmobile, or anything else that isn't fabric, the blade should enjoy a good, long life.

But, every blade wears down eventually. Blade sharpeners exist, but we don't currently have one, and a sharpener can't save a chipped or bent blade.

If a blade can't be sharpened, there are new 45mm blades in the storage drawers along the wall.

=== Changing the blade ===

Different rotary cutters have different parts, but they all have these four, in this order:

*Hub/screw
*Rotary cutter body
*Blade
*Nut

You should try to keep all of the parts (including those not listed—some cutters do have some bonus parts) in the correct order. If you get the order wrong, the blade might not spin freely or it might be too far from the cutter body. If that's the case, no biggie, just disassemble and try again.

No tools are needed.

#Remove the nut by hand, keeping your thumb on the hub/screw on the other side.
#Gently turn the cutter over and let the blade fall out onto your fingers, and any other parts onto the table.
#Sharpen or replace the blade.
#Put the blade onto the screw.
#Put the screw (with blade) into the cutter, and put all of the other parts, ending with the nut, onto the other side.

= Parts Needed =

Some of the parts (especially pedals and/or cords) for the sewing machines have, shall we say, installed a walking foot. Here's what we're currently missing:

=HISTORY=
*2008: Noisebridge began having sewing machines at [[83c]].
*2009: Rachel [[Industrial_Sewing_Machine_Donations|purchased industrial sewing machines]] from the sewing shop that formerly occupied Noisebridge's 2169 space with member donations and held its first [[Sewing Workshop]] at [[2169]].
*2015: Grand reopening event of the rebooted Sewing Station.
*2019: Sewing station moved over near the fire escape. Also, we did a Sewing Machine Fix-a-Thon and started holding training classes.

==Grand Reopening Poster ==

[[File:Sewing-Area-Poster.jpg|none|300px]]

== Machines not currently available (location unknown or else) ==

====Brother XR1355====
Status: Location unknown as of 2023-04-20
130-Stitch Computerized Sewing and Quilting (Brother XR1355) Works as of 2021-12-28
This machine is on the home sewing machine table (Table 3).
Overview This machine does 130 different stitches including lots of cool decorative flowers and patterns. Bobbin: Clear plastic, class 15 (Brother SA156). Please use bobbins in Table 3 toolbox.

====Singer Ultralock 14U64A serger====
Status: Broken as of 2023/02. Ready for discard
Type: Domestic serger
Year: probably 1990s
Notes:dropped when being carried by handle. On/off switch broken, possible replacement part found, just needs to be wired on. side plastic casing broken, could possibly be repaired with plastic molding material. Part not necessary to functioning, but nice to have to protect machine from dust
This is a four-thread overlock machine. It's evidently meant for knitted fabrics, as a silkscreened note on the upper-left of the front of the machine notes that it requires a Singer 2045 needle, which is a ball point.
The thread guides above the machine are on a pole that telescopes out. Make sure to raise it before using the machine; it works better that way.
*Manual: http://www.singerco.com/uploads/download/974c69637ba13cd29bf98419910a853043dc9e83.pdf
*Parts list: http://parts.singerco.com/CPpartCharts/14U00/14U64A.pdf

====Brother Exedra E-40====
We've gotten rid of this machine (when we moved the sewing station over to the fire escape) but we still have the digitized manual: https://www.noisebridge.net/wiki/File:Brother_E-40_Operation_Panel_Instruction_Manual.pdf

====Kenmore Overlock 3/4D====
Manual: In Manuals Collection, also https://www.noisebridge.net/wiki/File:Overlock_34d_38516631.compressed.pdf

====Brother SE400 Embroidery Machine====
'''currently missing''' as of 2021-07-14
This machine is awesome, and can do many different stitches as well as CNC embroidery.
It's usually stored on the wall of the sewing area. It looks like a home sewing machine but is as expensive as an industrial one and is many people's favorite machine.
* [[Embroidery Machine]]
* Bobbin: Class 15 ([https://www.joann.com/brother-sa156-clear-plastic-class-15-bobbin/16386419.html Brother SA156])
* Manual: https://download.brother.com/welcome/doch000184/885v31_v32_v33_om04en.pdf

====Pfaff Creative 1471 sewing machine====
'''Location unknown''' as of 2021-7-14
This machine has a bobbin case, so it requires a little bit more knowledge to change out the bobbin than newer machines that have a top drop-in bobbin.
*Bobbin: Special metal bobbins. There's a parts drawer specifically for Pfaff bobbins.
*Manual: http://www.pfaff.com/SiteMedia/PFAFF/Products/Machines/Support-manuals/creative1471-manual-EN.pdf

====Singer CG-590-C====
Manual: In Manuals Collection

====White YM-43-8====
Manual: Unknown

====Singer 621-B====
Manual: Unknown

====Singer Heavy Duty 4423 sewing machine====
'''Broken''' as of 2019-11-04: Shuttle pops up out of bobbin race, resulting in failure to make stitches and internal pressure upon the bobbin race door.
Has a top drop-in bobbin. Likely to become our workhorse, as the Heavy Duty is a sturdy mechanical machine.
Has a one-step buttonhole feature with a plastic buttonhole foot. Tricky to use but handy if you know how.
A knob on the top of the machine, near the slot where the take-up lever pops up, enables adjusting the presser foot pressure. Like top thread tension, this should generally not be messed with and should be put back after a job that does require adjusting it, but changing the presser foot pressure makes sense in certain circumstances:
*For thick works such as three or more layers of denim (e.g., when hemming denim garments), reduce the presser foot pressure in order to be able to drive over the inseam and outseam.
*For light works made of thin or sheer fabrics, or slippery fabrics, you may need to increase the pressure to ensure the feed dogs can properly feed (all layers of) the work.
'''Always put the presser foot pressure back how it was when you're done!!!''' Setting up future machine-users for difficulty/failure is un-excellent.
*Bobbin: Class 15
*Quick-start guide: http://www.singerco.com/uploads/download/HD%20Series_ANT_Generic_QSG_F_0222_lo-res.pdf
*Manual: http://www.singerco.com/uploads/download/a719909a6ca001462cb1c2536a04506fa9ff327c.pdf

====Singer 57817====
'''Works''' as of 2020-01-06. Missing the reverse button, though.
This machine can only do straight and zigzag stitches. No overcast or anything else.
*Bobbin: [https://www.sewingpartsonline.com/singer-57817-sewing-machine-parts.aspx?sort.ss_cat_sort=desc&keywords=bobbin&index=1 Class 66]
*Manual: https://www.noisebridge.net/wiki/File:Singer_57817.pdf

====Brother XL-2300i====
Currently on the top of one of the sewing area shelves.
Overview
* Bobbin: Class 15 ([https://www.joann.com/brother-sa156-clear-plastic-class-15-bobbin/16386419.html Brother SA156])
Manual + quick set-up guide
* https://support.brother.com/g/b/manualtop.aspx?c=us&lang=en&prod=hf_xl2600i2610eus

====Automatic Snap Setting Machines====
In November 2020 we received a generous donation of two Automatic Snap Machines worth over $4000 from Craig Spring http://www.brotus.com !

One pair (one female, one male) of fully automatic, electric powered, 20 line, snap setting machines. These are older model machines manufactured by the Ho Hung Ming company in Taiwan (https://www.hohm.com).

They have a US location at: Ho Hung Ming USA Enterprise, 13525 Alma Ave, Gardena, CA 90249, Phone: 3103274847.

One of the advantages of these older machines is that they are simple mechanical machines built to last. Like an old car, they are easier to repair than newer ones. In 22 years, he never needed to repair these machines. They still run like a beast.

As there exists no manual for these machines, Craig and DK gave a servicing and use demonstration on Nov 15, 2020 via Jitsi and X uploaded it to https://www.youtube.com/watch?v=dc2ozToy38Q

Photos are at https://discuss.noisebridge.info/t/automatic-snap-setting-machines-donation-instructions/2132

[[Category:Pages with a Noisebridge Tiny URL]]
{{guilds}}