Hackerspace News

News

Aug 29 2026 : Yoga for Hackers

🇺🇸 · NYC Resistor · Classes

Hack your body. We'll cover fundamental yoga postures, with an emphasis on alignment, breathing practices and strength. All are welcome! Note: class begins at noon, please try to come a few minutes early to set up! Description : Perfect for those of us who spend too much time at our computers or hunched over a project. No prior experience with yoga required. Please wear comfortable clothes for stretching and bring a yoga mat (or borrow one from a friend)! Instructor : Hal has been practicing yoga since they were a teenager. Their first yoga teacher used to come around the room and cheerfully say the class would be in the pose for a week to 10 days. Hal has a similar sense of humor and thinks a yoga class is best when students feel both deeply supported and challenged. Hal is a software dev who appreciates a good bug and is a 200-hr certified yoga teacher. More info : No masks required As with all NYC Resistor events, this class is 18+ and governed by our Code of Conduct. The Code of Conduct, as well as accessibility information, can be found at www.nycresistor.com/participate/ . Please note that refunds must be requested 24 hours in advance. If you have any questions, please email classes@nycresistor.com. More info and RSVP

classesclass

Patching il proprio cervello: Manuale di sopravvivenza per botanici autodidatti

🇮🇹 · /root · Lamberto Tedaldi

E se vi dicessi che il sistema operativo più antico, complesso e decisamente meno documentato del pianeta non gira su kernel Linux, ma è scritto nel DNA di ogni foglia che vedete mentre andate a comprare il pane? Spesso passiamo le ore a cercare di capire perché una dipendenza si rompe o perché un container Docker non vuole cooperare, ma raramente ci fermiamo a guardare il mondo ‘analogico’ con lo stesso occhio critico. Recentemente è circolata una lettura interessante che parla di botanica, e no, non è la solita fuffa da giardinaggio per pensionati. È un invito a fare reverse engineering della natura. Il problema principale per chi vuole approcciarsi alla botanica è il setup iniziale. Il lessico è un incubo di termini latini che sembrano usciti da un manuale di incantesimi di Harry Potter. Ma qui sta il trick: la tassonomia è, in fondo, un sistema di classificazione gerarchica. Se masticate le strutture dati, avete già metà del lavoro fatto. Il latino non è lì per fare i fighi (anche se Linneo, il padre del sistema, era decisamente un tipo del suo tempo), ma serve come un protocollo universale. È il nostro DNS: un nome univoco che evita conflitti di namespace. Se dico «cedro», potrei riferirmi a otto piante diverse; se uso il nome scientifico, non c’è ambiguità. La vera magia però sta nella sistematica. Una volta che capite le «sinapomorfie» — ovvero quei tratti condivisi che definiscono un gruppo evolutivo — potete iniziare a identificare specie che non avete mai visto prima. È come riconoscere un pattern in un log di sistema: vedi certe caratteristiche e sai immediatamente a quale famiglia appartiene il problema. Per chi vuole approfondire senza spendere un patrimonio in libri accademici (perché sappiamo tutti che i prezzi dei textbook sono un crimine contro l’umanità), la buona notizia è che la cultura della condivetà è viva. Anche se non parliamo di repository GitHub, l’idea che la conoscenza debba essere accessibile è la stessa. Strumenti come Sci-Hub o LibGen sono quelli che permettono a chiunque, indipendentemente dal budget, di fare un deep dive serio. Quindi, la prossima volta che siete in un parco e vedete una pianta strana, non limitatevi a scattare una foto per l’AI. Provate a capire la sua genealogia. È un debugging della realtà che, credetemi, è molto più gratificante di risolvere un ticket su Jira. Source: Crime Pays but Botany Doesn't

webnewsbotanyknowledge sharingNaturereverse engineering

Cloudflare OS: un nuovo sistema operativo o solo l’ennesimo modo per farci vivere nel loro giardino?

🇮🇹 · /root · Lamberto Tedaldi

Immaginate di svegliarvi una mattina e scoprire che il vostro intero ecosistema aziendale non è più solo un insieme di server, database e script sparsi qua e là, ma un unico, grande, coerente organismo digitale. Sembra la trama di un episodio di Black Mirror, vero? Eppure, Cloudflare ha deciso di lanciare la sua bomba: Cloudflare OS. Per chi non mastica il marketing delle Big Tech, non si tratta di un vero e proprio sistema operativo da installare su un vecchio ThinkPad che trovi in soffitta. No, è una piattaforma open-source pensata per far girare agenti, app e automazioni, con l’idea di creare uno strato che ‘conosce’ come funziona la tua azienda e gestisce l’accesso ai sistemi interni in modo sicuro. L’idea di base è piuttosto potente: invece di avere mille microservizi che non si parlano e VPN che sembrano reliquie dell’era analogica, avresti una piattaforma che orchestra tutto. La parte figa? È open-source. Questo significa che, almeno sulla carta, possiamo sbirciare sotto il cofano, capire come gestiscono la logica e, soprattutto, non siamo solo spettatori passivi di una scatola nera proprietaria. Certo, c’è un piccolo ‘ma’ che non possiamo ignorare. Sebbene il codice sia aperto, l’infrastruttura che fa girare tutto questo è, beh, Cloudflare. È quel classico dilemma del mondo moderno: ti do gli strumenti per costruire il tuo castello, ma le fondamenta, le mura e la guardia alla porta sono tutte gestite da me. Se decidi di costruire tutto il tuo workflow aziendale su questo framework, potresti ritrovarti con le mani legate se un giorno decidessi di cambiare fornitore. È un po’ come il supereroe che ha poteri incredibili, ma solo finché resta all’interno della città protetta dal suo stesso muro. In Italia, poi, siamo abituati a gestire infrastrutture un po’ più… diciamo, ‘artigianali’. Spesso ci troviamo a combattere con configurazioni legacy che sembrano sopravvissute alla caduta dell’Impero Romano. Un approccio del genere potrebbe essere una manna dal cielo per standardizzare i processi, a patto di non trovarsi a dover pagare un abbonamento astronomico per ogni singolo automazione che decidiamo di far girare. In sintesi: Cloudflare OS è un progetto da tenere d’occhio con estremo interesse. Se riusciranno a mantenere la promessa di un ecosistema realmente flessibile e non solo un’estensione del loro controllo sul traffico web, potrebbe essere una svolta per il modo in cui concepiamo il lavoro digitale. Se invece diventerà solo un modo più elegante per renderci dipendenti dal loro stack, beh… avremo visto abbastanza film di fantascienza per capire come va a finire. Source: Cloudflare OS: an open platform for agents, apps, and work

webnewscloud computingcloudflaredevopsopen source

La porta sul retro è sempre stata aperta (e pure con l’aria condizionata)

🇮🇹 · /root · Lamberto Tedaldi

Scommetto che pensavate che il vostro perimetro di sicurezza fosse solido come le mura di Hogwarts, e invece siamo tutti in un episodio di Mr. Robot senza nemmeno averlo scelto. Recentemente è emerso che i Baseboard Management Controllers (BMC) di alcuni dei più grandi produttori di hardware al mondo sono un vero e un disastro di sicurezza. Per chi non ha passato le ultime notti a compilare kernel custom, il BMC è quel piccolo computer dentro il server che serve ai sysadmin per gestire tutto da remoto: accendere, spegnere, monitorare le temperature… un vero comodino digitale. Il problema è che questo componente, che dovrebbe essere il guardiano del castello, si è rivelato avere una serratura che si apre con uno stuzzicadenti. Il succo della questione è che questi controller sono pieni di bug che permettono di inserire delle backdoor. Non stiamo parlando di un semplice script che ti manda una notifica su Telegram, ma di un accesso profondo, a livello hardware, che bypassa quasi ogni controllo software che avete implementato con tanto amore. Se un attaccante riesce a colpire il BMC, il vostro sistema operativo, i vostri firewall e le vostre policy di sicurezza diventano praticamente dei soprammobili inutili. È la solita storia: i giganti del settore lanciano hardware su scala industriale, corrono per battere la concorrenza e si dimenticano che il firmware non è solo un dettaglio tecnico, ma la base su cui poggia tutto il resto. È quel classico approccio ‘release now, patch later’ che però, quando si parla di infrastrutture critiche, non è affatto divertente. E non fatevi illusioni: anche se la notizia arriva da fonti internazionali e riguarda i colossi del mercato globale, l’impatto sui datacenter e sulle infrastrutture che gestiamo anche qui in Italia è enorme. Se il cuore dell’internet globale è vulnerabile, anche la nostra piccola porzione di rete è a rischio. La cosa che fa più rabbia è la mancanza di trasparenza e la difficoltà di gestire queste patch. Non è come aggiornare un container Docker su Kubernetes; qui si parla di firmware, di roba che se sbagli il flash rischi di trasformare un server da diecimila euro in un fermacarte molto costoso. Insomma, un promemoria brutale: non fidatevi mai ciecamente dell’hardware che comprate solo perché ha un brand famoso sulla scatola. La sicurezza inizia molto prima del primo comando sudo. Source: Thousands of servers can be backdoored by exploiting buggy motherboard controllers

webnewsBMCcybersecurityhardwareinfosec

Shaping the Nigeria AI Trust: Key Conversations from London, Lagos and Abuja

🇳🇬 · CcHUB (Co-creation Hub Nigeria) · CcHUB Communications

Photo Caption: Government leaders, researchers, legal experts, and AI practitioners came together across three convenings to help shape the mandate, governance, and long-term direction of the Nigeria AI Trust. As artificial intelligence continues to evolve, conversations about its future are becoming increasingly important. One such conversation is the Nigeria AI Trust, a new independent body being established under a presidential directive. Following the founding convening held in June at Warwick Business School, The Shard, London, two Nigerian convenings were held in Lagos on 29 July and Abuja on 4 August. Together, these convenings built on the discussions from London and brought together senior thinkers, global voices, researchers, and AI experts to co-design the Trust’s mandate and form strategic alliances that will support its founding and long-term success. The convenings were structured around four foundational questions and provocateurs on theory of change, legal longevity, financial independence, and selection legitimacy, with a cross-cutting framing guiding the discussions. At the Abuja convening, the Honourable Minister of the Federal Ministry of Communications, Innovation, and Digital Economy, Dr. Bosun Tijani, delivered the welcome remarks and ministerial opening, framing the presidential mandate, the strategic rationale for constituting the trust at this time, and what the ministry requires from the convened group. In Lagos, the welcome remarks were delivered by Dr. Olubunmi Ajala on behalf of the minister. During both convenings, Ojoma Ochai, Managing Director of CcHUB, presented the intelligence brief and framed the working session. CcHUB, Africa’s leading innovation and creative ecosystem enabler, is anchoring this work as the research and design lead, with support from the MacArthur Foundation. We extend our sincere appreciation to UNDP Nigeria for hosting the Abuja convening and to our distinguished speakers, Dr. Bosun Tijani, Dr. Olubunmi Ajala, Ojoma Ochai, Dr. William Tsuma, Barr. Gbenga Oyebode MFR, Mr. Oyedapo Oyekunle Olorunyomi OON, Dr. Osasuyi Dirisu and Prof. Olayinka David-West , for sharing their expertise and contributing to these important conversations. We also thank our moderators, Aanu Oyeniran for the Lagos convening and Vahyala Kwaga for the Abuja convening, as well as Eweka Yvonne for coordinating the program. The Nigeria AI Trust convenings reflect a shared commitment to bringing together diverse expertise to shape the Trust’s mandate and build strategic alliances that will support its founding and long-term success. The post Shaping the Nigeria AI Trust: Key Conversations from London, Lagos and Abuja appeared first on Co-creation HUB Africa (CcHUB) .

AI Trust

Pareto, Mario Kart e l’arte di non scegliere la build di m***a

🇮🇹 · /root · Lamberto Tedaldi

Smettetela di pensare che la vittoria in Mario Kart sia solo questione di riflessi e di quanto sapete evitare le buche di Donkey Kong. Se siete qui, sapete bene che sotto il cofano di ogni gioco (e di ogni sistema complesso) c’è un mare di variabili che possono farvi svoltare o condannarvi al fandom di serie TV che non finiscono mai. Recentemente Antoine Mayerowitz ha tirato fuori una riflessione che, al di là di quanto possa sembra di leggere un paper di microeconomia, è pura poesia per chiunque ami ottimizzare le proprie performance. Il punto? Usare il concetto di ‘Frontiera di Pareto’ per smettere di sprecare tempo su build che sono matematicamente inferiori ad altre. Il concetto è semplice, quasi brutale. Immaginate di dover scegliere il vostro setup: pilota, telaio, gomme e aliante. Avete migliaia di combinazioni. Potreste pensare: «Vado su Bowser, è il più veloce, fine della storia». Ma la velocità non è tutto. Se avete una velocità pazzesca ma un’accelerazione che sembra quella di un bradipo sotto sedativi, al primo colpo ricevuto tornerete alla linea di partenza nel 2029. Qui entra in gioco Pareto. L’idea è identificare le opzioni ‘efficienti’. Se un personaggio come Koopa ha meno velocità e meno accelerazione rispetto a Cat Peach, Koopa è ‘dominato’. È un’opzione inutile, un errore di sistema, un bug nel vostro piano di vittoria. Non ha senso tenerlo nel roster se esiste un’alternativa che eccelle in entrambi i parametri. La ‘Frontiera di Pareto’ è l’insieme di tutte quelle combinazioni che non possono essere migliorate in un parametro senza peggiorarne un altro. È il limite oltre il quale non puoi andare senza fare dei trade-off. Questa cosa non serve solo a vincere i trofei virtuali. È la stessa logica che usiamo quando cerchiamo un LLM che non ci prosciughi il budget in API ma che non risponda con la latenza di un modem 56k, o quando cerchiamo il setup hardware perfetto tra potenza di calcolo e calore generato. Siamo costantemente in bilico tra variabili contrastanti. Certo, non è una bacchetta magica. La frontiera ti dice quali sono le scelte sensate, ma non ti dice quale sia la ‘tua’ scelta ideale. Quella dipende dalla tua ‘utility function’, ovvero da quanto peso dai alla velocità rispetto alla manovrabilità. Però, almeno, grazie a Pareto puoi eliminare tutto il rumore di fondo e non perdere tempo con le build che sono oggettivamente delle boiate. In un mondo pieno di marketing che vi promette il ‘migliore in assoluto’ (spoiler: non esiste), imparare a identificare la frontiera è l’unico modo per navigare nel caos senza farsi fregare dai compromessi inutili. Insomma, meno fuffa, più ottimizzazione. Source: Mario Meets Pareto

webnewsData ScienceGamingMario Kartoptimization

Demis Hassabis: il CEO che voleva solo fare lo scienziato (e noi lo capiamo)

🇮🇹 · /root · Lamberto Tedaldi

Spostare il proprio focus dalla gestione di un impero tecnologico alla pura ricerca scientifica è un lusso che pochissimi possono permettersi, ma Demis Hassabis sembra averlo fatto con una determinazione degna di un protagonista di un film di Christopher Nolan. Secondo quanto trapelato da recenti indiscrezioni, l’ex CEO di Google DeepMind non stava solo cercando di gestire la pressione del potere, ma stava attivamente tramando per abbandonare la poltrona da amministratore delegato e tornare a fare quello che sa fare davvero: lo scienziato. Immaginate la scena: invece di guardare fogli di calcolo, metriche di crescita e dashboard piene di KPI che non dicono nulla di utile, Hassabis sognava di tornare tra i dataset, i modelli e la bellezza pura della scoperta. Per noi che passiamo le serate a debuggare script o a cercare di far girare un modello LLM locale su hardware che urla pietà, questa notizia suona quasi come un manifesto. C’è qualcosa di profondamente onesto nel desiderio di scappare dal ‘corporate-speak’ e dalle decisioni strategiche prese in board room per tornare alla materia prima, quella che non ha bisogno di slide di PowerPoint per giustificare la propria esistenza. Certo, per noi che viviamo in Italia, le dinamiche interne di un colosso come Google sembrano sempre un po’ un dramma lontano, una specie di soap opera per tech-entusiasti che non influisce direttamente sulla nostra capacità di compilare codice o di montare un nuovo cluster Raspberry Pi. Eppure, il tema è universale. Quante volte, mentre siamo sommersi da task burocratici o da aggiornamenti software che rompono tutto senza motivo, non abbiamo desiderato resettare tutto e tornare alle basi? Il punto è che la gestione dell’hype attorno all’IA sta diventando una macchina da guerra di marketing e business, dove spesso la ricerca vera e propria finisce in secondo piano rispetto alla necessità di dominare il mercato. Se Hassabis ha davvero cercato di fuggire per un anno per ritrovare la sua bussola scientifica, forse ha capito che il vero valore non sta nel decidere quanto fatturato far generare a un chatbot, ma nel capire come quel chatbot sia costruito. In un mondo che corre verso l’automazione selvaggia, forse l’unico modo per non perdere la bussola è proprio quello che ha tentato di fare lui: staccare la spina dal management e rimettersi al banco di lavoro. Meno meeting, più esperimenti. Chi altro si sente così? Source: Demis Hassabis Had Reportedly Been Plotting to Leave His DeepMind CEO Job for a Year

webnewsArtificial IntelligenceDeepMindgooglescience

La guerra dei benchmark: chi è il vero Re dell’AI?

🇮🇹 · /root · Lamberto Tedaldi

Misurare l’intelligenza è un’impresa quasi impossibile, eppure ci stiamo comportando come se esistesse un termometro universale per i Large Language Models. Benvenuti nell’era dei benchmark, dove un millisecondo di latenza o un token in meno può spostare le sorti di un intero ecosistema. Recentemente, la competizione tra i giganti dell’AI è uscita dai laboratori per finire dritta in una sorta di ‘Grande Guerra dei Dati’. Non si tratta più solo di sapere chi risponde meglio a una domanda di filosofia o chi scrive il codice Python più pulito. La sfida si è spostata su un terreno molto più tecnico e, per certi versi, spietato: l’efficienza pura. Se guardiamo i dati più recenti, la vera partita si gioca su tre fronti: costo, velocità e precisione. Le metriche stanno diventando sempre più stratificate. Non basta più dire ‘il modello X è intelligente’. Ora dobbiamo chiederci: quanto mi costa ogni mille token? Quanto tempo impiega a generare la risposta? E quanto è affidabile il dato che mi sta fornendo senza allucinazioni? Entra in gioco l’indice di efficienza. Stiamo assistendo a una corsa frenetica dove i provider cercano di massimizzare il rapporto tra performance e latenza. Vediamo provider che si sfidano sul ‘Time to First Token’ (quanto velocemente inizia a scrivere) e sull’uso strategico del caching per abbattere i costi. È una guerra di logistica invisibile che avviene sotto il cofano dei nostri prompt. Ma c’è un lato meno brillante. Questa ossessione per le metriche sta creando un circolo vizioso: i modelli vengono addestrati per eccellere proprio in quei test che li misurano, un fenomeno che rende i benchmark sempre meno rappresentativi della ‘vita vera’. Inoltre, la frammentazione è totale. Ogni azienda ha il suo modo di misurare la ‘qualità’, rendendo quasi impossibile un confronto onesto e trasparente tra un modello proprietario e uno open-source. In definitiva, mentre noi cerchiamo la risposta perfetta al nostro prompt, sotto la superficie si sta costruendo una struttura di misurazione sempre più complessa e frammentata. La vera sfida non sarà solo creare il modello più intelligente, ma trovare un linguaggio comune per capire quanto sia, effettivamente, intelligente. Source: Qwen3.8 Max now ranked as the best overall model by agentic index

webnewsaiArtificial IntelligenceBenchmarksLLM

Addio Git, benvenuto DeltaDB: il version control che ti spia (ma con stile)

🇮🇹 · /root · Lamberto Tedaldi

Dimenticate il conforto del vostro commit atomico, quello pulito, ben documentato e che finalmente dà un senso al vostro lavoro. Sembra che il concetto di «commit» stia per diventare un fossile del passato, una reliquia di un’epoca in cui gli umani scrivevano codice senza avere un agente AI che sussurrava suggerimenti in tempo reale. Il team di Zed ha appena rilasciato in early access DeltaDB, e non è il solito database con un nome altisonante per fare hype. È un version control system che punta a registrare tutto quello che succede *tra* un commit e l’altro. Sì, avete letto bene. L’idea è quella di catturare ogni singola operazione, ogni modifica, ogni frazione di secondo di evoluzione del codice, collegandola direttamente alla conversazione che l’ha generata. In pratica, se state usando un agente AI per scrivere una funzione, DeltaDB non si limita a salvare il risultato finale. Ti permette di fare il «rewind» a qualsiasi modifica intermedia e, cosa ancora più folle, ti permette di saltare direttamente dalla riga di codice al log della chat che l’ha prodotta. Immaginate di scovare un bug e poter dire: «Fammi vedere cosa stava dicendo l’agente quando ha deciso che questo puntatore era sicuro». È una feature che farebbe impazzire ogni debugger, ma che solleva anche qualche dubbio su quanto spazio (e sanità mentale) occuperà questo flusso di dati infinito. La parte che definire «figa» è d’obbligo: la virtualizzazione del worktree. Creare nuovi branch è quasi istantaneo e praticamente gratuito in termini di risorse, perché puoi creare branch partendo da qualsiasi punto della storia, persino a metà di un’esecuzione. E per i team che lavorano in modo asincrono, la promessa è di poter condividere il «thread» della conversazione invece del solito, noioso Pull Request. Un collega può entrare nel flusso mentre il lavoro è ancora in corso, commentare e interagire con l’agente che sta scrivendo il codice. Certo, c’è una piccola nota di cautela per chi, come me, ama la separazione netta tra il «fare» e il «documentare». Questo approccio trasforma il processo di sviluppo in un flusso continuo e indissolubile, dove la distinzione tra idea, conversazione e implementazione svanisce. Se da un lato è una bomba per la tracciabilità, dall’altro ci si ritrova in un ecosistema dove ogni pensiero digitale lascia una traccia indelebile. Per ora è tutto in early access, quindi restiamo con un piede in una parte del futuro e l’altro ancorato al nostro amato, vecchio e solido Git. Speriamo solo che il prossimo update non decida di tracciare anche i nostri sospiri di frustrazione quando il test fallisce. Source: Zed DeltaDB

webnewsAI CodingDeltaDBsoftware engineeringVersion Control

DeepMind si scombina: Demis scende dal trono (o quasi) e Jeff Dean prende la porta

🇮🇹 · /root · Lamberto Tedaldi

Se pensavate che il mondo dell’intelligenza artificiale fosse ormai una tranquilla passeggiata nel parco tra algoritmi ottimizzati e cluster di GPU, preparatevi a un reboot improvviso. Le ultime notizie che arrivano dal quartier generale di Alphabet hanno scosso un po’ la community di Hacker News, e non per un nuovo modello che batte il benchmark di turno, ma per un classico ‘cambio di assetto’ ai vertici. Sundar Pichai, il CEO che gestisce Google con la precisione di un database relazionale, ha annunciato che Demis Hassabis sta lasciando la carica di CEO di DeepMind per assumere quella di President. Non è che stia andando in pensione a giocare a scacchi in un resort sulle Alpi, sia chiaro, ma la sua figura si sposta su un piano più… diciamo, strategico e meno operativo. Ma la vera bomba, quella che fa sussultare anche i server più tranquilli, è la notizia della partenza di Jeff Dean. Per chi mastica codice e infrastrutture da una vita, il nome di Dean non è solo un nome: è un’istituzione. Parliamo dell’uomo che ha contribuito a gettare le fondamenta su cui poggia gran parte dell’ecosistema moderno di machine learning. Vedere uno dei pilastri di Google che decide di spostarsi altrove è come vedere un pezzo fondamentale di una libreria open source sparire dal repository principale proprio mentre tutto il mondo sta cercando di buildare il prossimo grande modello linguistico. Certo, leggendo tra le righe del comunicato aziendale — quel linguaggio patinato e privo di anima che sembra scritto da un algoritmo di marketing — tutto sembra un naturale ‘prossimo capitolo’. Ma noi sappiamo che quando i big cambiano poltrona, di solito c’è sotto una ristrutturazione pesante per centralizzare ancora di più il potere decisionale. È il solito schema: meno focus sulla ricerca pura e più attenzione al far quadrare i bilanci e l’integrazione con i prodotti consumer. Per noi che viviamo di sperimentazioni, di script scritti in emergenza e di quella sana diffidenza verso i giardini recintati delle Big Tech, questo movimento solleva interrogativi. La direzione sta diventando troppo orientata al prodotto e troppo poco alla ricerca esplorativa? Quando i pionieri lasciano il posto alla governance, il rischio di trovarsi con sistemi sempre più chiusi, meno trasparenti e più orientati al profitto immediato è sempre dietro l’angolo. In Italia, dove spesso subiamo le decisioni prese nei meeting di Mountain View come se fossero leggi divine, questa notizia ci riguarda eccome. Non è solo questione di nomi su un organigramma, ma di quale direzione prenderà l’architettura del mondo digitale in cui siamo immersi. Restiamo sintonizzati per vedere se questo ‘momentum’ di cui parla Pichai porterà innovazione reale o solo un altro strato di astrazione sopra le solite API proprietarie. Source: Changes at Google DeepMind: Demis Hassabis from CEO to Chair, Jeff Dean departs

webnewsArtificial IntelligenceDeepMindgoogleJeff Dean

Other

The 49th 3D Print & Pizza Meetup @ Pixelbar Rotterdam

🇳🇱 · Pixelbar

Are you interested in 3D printing? Whether you have yet to buy your first 3D printer or already have an entire print farm, the 3D Print & Pizza Meetup is the perfect opportunity to meet like-minded individuals and share your passion. Everyone with an interest in 3D printing is welcome! What to expect Show and Tell : Have you printed something cool? Feel free to bring it along to show it off or maybe ask for feedback. Troubleshooting : Having problems with your 3D printer? Bring it along, and maybe others can help you solve the issue. Bringing something is not mandatory, but it often starts a good conversation. Presentations and Workshops : Want to give a presentation or organize a workshop? The meetup offers a platform for everyone to share knowledge. Discuss with the venue in advance if you need any extra equipment. Location 3D Print and Pizza Rotterdam is hosted at Hackerspace Pixelbar. We are at Schiemond 20, 3024 EE Rotterdam. This is inside “De Kroon”, follow the signs for K14. If you’re coming with public transportation: you can go to Tram stop Schiemond or Metro Station Delfshaven and then walk towards the harbor. To access the space you need to go up a set stairs, we sadly don’t have an elevator. If you are bringing a large object we have a seperate entrance, ping one of the Pixelbar members. INFO Print & Pizza meetup 🗓 Thursday 3 September 2026 🕛 18:00 till 23:00 💸 Free entrance, pizza and 2 drinks for €15 📍 Schiemond 20, 3024 EE, Rotterdam, inside “De Kroon” at K14.1.01 You can RSVP on one of the following platforms: Discord , Meetup (RSVP is not required, but recommended)

HAC-32-DEV

🇳🇱 · Hackalot · Okabe

Nieuwe pagina aangemaakt met '{{Project |name=HAC-32-DEV |contact=Okarin |info=A adapter for ESP32 Dev boards |status=in progress }} = Dev Board = It's a adapter from the ESP32-D1_mini == Pinout == == Files ==' Nieuwe pagina {{Project |name=HAC-32-DEV |contact=Okarin |info=A adapter for ESP32 Dev boards |status=in progress }} = Dev Board = It's a adapter from the ESP32-D1_mini == Pinout == == Files ==

Shirtpers

🇳🇱 · Bitlair · Polyfloyd

← Oudere versie Versie van 6 aug 2026 20:15 Regel 2: Regel 2: |Use=Iedereen |Use=Iedereen |Location=Flexlab |Location=Flexlab |Warnings=Bestand:Waarschuwing heet oppervlak.svg }} }} Pers voor het bedrukken van t-shirts met folie. Pers voor het bedrukken van t-shirts met folie.

TV

🇳🇱 · Bitlair · Polyfloyd

← Oudere versie Versie van 6 aug 2026 20:10 Regel 1: Regel 1: {{Tool {{Tool |Name=TV |description=Samsung 65" |description=Samsung 65" |Use=Iedereen |Use=Iedereen |Location=Flexlab |Location=Flexlab |Name=TV }} }} Deze TV in het [[Flexlab]] kan gebruikt worden voor bijvoorbeeld presentaties of instructies bij workshops. Deze TV in het [[Flexlab]] kan gebruikt worden voor bijvoorbeeld presentaties of instructies bij workshops. Regel 10: Regel 10: Na gebruik aub de kabel weer oprollen en de afstandsbediening terugplaatsen in de houder. Na gebruik aub de kabel weer oprollen en de afstandsbediening terugplaatsen in de houder. == Extra's == * [[File:TV Afstandsbediening Houder.stl]]

Projects/$andere ruimte

🇳🇱 · Bitlair · Polyfloyd

← Oudere versie Versie van 6 aug 2026 18:03 Regel 1: Regel 1: {{Project {{Project | name = De andere ruimte | info = Can not be blank |start=2017-04-16 |start=2017-04-16 |contact=AK, Polyfloyd |contact=AK, Polyfloyd |info=Can not be blank |status=Abandoned |status=Abandoned |Picture=Space2_20161003_193904.jpg |name=De andere ruimte }} }} Dit was de projectpagina voor de aan de hoofdruimte grenzende pagina van [[Space2.0]]. Dit was de projectpagina voor de aan de hoofdruimte grenzende pagina van [[Space2.0]].

Projects/Flipdot 20x16

🇳🇱 · Bitlair · Polyfloyd

← Oudere versie Versie van 6 aug 2026 17:53 Regel 1: Regel 1: {{Project {{Project | name =20x16 pixel flipdot display | info =20x16 pixel flipdot display we got at eth0:2019 |start=2019-10-20 |start=2019-10-20 |contact=Eightdot, Polyfloyd |contact=Eightdot, Polyfloyd |info=20x16 pixel flipdot display we got at eth0:2019 |status=Beta |status=Beta |Picture=Flipdot 20x16.jpg |name=20x16 pixel flipdot display }} }} Part Info: Part Info:

Events/2016-08-14 Metameet 0x8

🇳🇱 · Bitlair · Polyfloyd

← Oudere versie Versie van 6 aug 2026 17:43 Regel 4: Regel 4: |start=2016/08/14 08:30:00 PM |start=2016/08/14 08:30:00 PM |end=2016/08/14 08:45:00 PM |end=2016/08/14 08:45:00 PM |location= Bitlair |location= Space1.0 }} }} == Wie notuleert? == == Wie notuleert? ==

Events/2016-06-19 Metameet 0x5

🇳🇱 · Bitlair · Polyfloyd

← Oudere versie Versie van 6 aug 2026 17:42 Regel 4: Regel 4: |start=2016/06/19 20:15:00 |start=2016/06/19 20:15:00 |end=2016/06/19 20:30:00 |end=2016/06/19 20:30:00 |location= Bitlair |location= Space1.0 }} }} Wie notuleert? Wie notuleert?

Events/2016-04-24 MetaMeet 0x1

🇳🇱 · Bitlair · Polyfloyd

← Oudere versie Versie van 6 aug 2026 17:41 Regel 4: Regel 4: |start=2016/04/24 08:00:00 PM |start=2016/04/24 08:00:00 PM |end=2016/04/24 08:30:00 PM |end=2016/04/24 08:30:00 PM |location= Bitlair |location= Space1.0 }} }} Wie notuleert? Wie notuleert?

Events/2015-03-28 Open dag Hackerspaces

🇳🇱 · Bitlair · Polyfloyd

← Oudere versie Versie van 6 aug 2026 17:40 Regel 4: Regel 4: |start=2015/03/28 02:00:00 PM |start=2015/03/28 02:00:00 PM |end=2015/03/28 10:00:00 PM |end=2015/03/28 10:00:00 PM |location= Bitlair |location= Space1.0 }} }}

Events/2014-01-05 Nieuwjaarsborrel

🇳🇱 · Bitlair · Polyfloyd

← Oudere versie Versie van 6 aug 2026 17:40 Regel 4: Regel 4: |start=2014/01/05 04:00:00 PM |start=2014/01/05 04:00:00 PM |end=2014/01/05 11:59:59 PM |end=2014/01/05 11:59:59 PM |location= Bitlair |location= Space1.0 }} }} We would like to invite you for a Newyears Drink @ Bitlair We would like to invite you for a Newyears Drink @ Bitlair

Events/2013-10-12 The one ring workshop

🇳🇱 · Bitlair · Polyfloyd

← Oudere versie Versie van 6 aug 2026 17:38 Regel 4: Regel 4: |start=2013/10/12 10:00:00 AM |start=2013/10/12 10:00:00 AM |end=2013/11/12 5:00:00 PM |end=2013/11/12 5:00:00 PM |location= Bitlair |location= Space1.0 }} }}

Events/2013-04-29 Koninginnenacht kampvuur

🇳🇱 · Bitlair · Polyfloyd

← Oudere versie Versie van 6 aug 2026 17:37 Regel 4: Regel 4: |start=2013/04/29 07:00:00 PM |start=2013/04/29 07:00:00 PM |end=2013/04/30 06:00:00 AM |end=2013/04/30 06:00:00 AM |location= Bitlair |location= Space1.0 }} }} We krijgen een nieuwe koning, dat is vast reden om bier te drinken en dingen in de fik te zetten. We krijgen een nieuwe koning, dat is vast reden om bier te drinken en dingen in de fik te zetten.

Events/2013-04-14 BBQ

🇳🇱 · Bitlair · Polyfloyd

← Oudere versie Versie van 6 aug 2026 17:37 Regel 3: Regel 3: |start=2013/04/14 17:00:00 |start=2013/04/14 17:00:00 |end=2013/04/14 21:00:00 |end=2013/04/14 21:00:00 |location= Bitlair |location= Space1.0 }} }} BBQ BBQ BBQ BBQ BBQ BBQ

Events/2019-08-10 Gamenight

🇳🇱 · Bitlair · Polyfloyd

Tekst vervangen - "Computerweg 20a, Amersfoort" door "Space3.0" ← Oudere versie Versie van 6 aug 2026 17:36 Regel 4: Regel 4: |start=2019/08/10 15:00:00 |start=2019/08/10 15:00:00 |end=2019/08/10 23:59:59 |end=2019/08/10 23:59:59 |location= Computerweg 20a, Amersfoort |location= Space3.0 }} }} Hello allemaal, Hello allemaal,

Events/2019-04-07 Metameet 0x28

🇳🇱 · Bitlair · Polyfloyd

Tekst vervangen - "Computerweg 20a, Amersfoort" door "Space3.0" ← Oudere versie Versie van 6 aug 2026 17:36 Regel 4: Regel 4: |start=2019/04/07 20:00:00 |start=2019/04/07 20:00:00 |end=2019/04/07 20:30:00 |end=2019/04/07 20:30:00 |location= Computerweg 20a, Amersfoort |location= Space3.0 }} }} Notulen: [https://member.bitlair.nl/Pages/2019-04-07_Metameet_0x28] Notulen: [https://member.bitlair.nl/Pages/2019-04-07_Metameet_0x28]

Events/2018-01-14 Metameet 0x1C

🇳🇱 · Bitlair · Polyfloyd

Tekst vervangen - "Computerweg 20a, Amersfoort" door "Space3.0" ← Oudere versie Versie van 6 aug 2026 17:36 Regel 4: Regel 4: |start=2018/01/14 20:00:00 |start=2018/01/14 20:00:00 |end=2018/01/14 20:30:00 |end=2018/01/14 20:30:00 |location= Computerweg 20a, Amersfoort |location= Space3.0 }} }} Notulen: [https://member.bitlair.nl/Pages/2018-01-14_Metameet_0x1C] Notulen: [https://member.bitlair.nl/Pages/2018-01-14_Metameet_0x1C]

User:Nthmost/MeetingNotes Previews/Meeting Notes 2026 08 04

🇺🇸 · Noisebridge · Nthmost

Auto-posted meeting notes for 2026_08_04 (meetingnotes) New page * For the full meeting facilitation guide (roles, agenda, post-meeting tasks), see [[Meeting_Notes_Reference|Meeting Instructions Reference]]. {{meetings2026}} These are the notes from the [https://www.noisebridge.net/wiki/Category:Meeting_Notes The 875th Meeting of Noisebridge]. {|class="wikitable" style="text: left;" ! style="text-align:left;"| Date | 2026-08-04 |- ! Note-taker[s] | Chaz, mister_name, Derek |- ! Moderator[s] | Heather |} {|class="wikitable" | [[Meeting_Notes_2026_07_28|Previous Meeting]] | [[Meeting_Notes_2026_08_11|Next Meeting]] |} == Meeting Summary == * New Core members: * New Access members: = Introductions = * Name / Pronouns / Fact that doesn't seem like it should be a fact. * Heather - she/her - anything that has to do with quantum mechanics * Johnathon - he/him - Tomatoes * Derek - he/him - Magnetic fields are an illusion * mister_name - he/him - Takes magnetic fields on faith * Sif - he/him - Magnetics are fun, Octopus have 3 hearts * Ciara - she/her - Squirrels are on all continnents except antartica * Chaz - He/Any - 2 is prime. * Sam - - Possums have 13 nipples, thats too many. * Daniel - he/him - All fruits are also vegetables * Rai - he/him - the domain space type out * Elan - - recently learned the http status 'I am a teapot' is not actual http error code, but is reserved because of outstanding use. * Marci - she/him - no fact [=( - Chaz] * Zacchae - - really happy that someone before him, do not know, or can't think of an interesting * Loren - he/him - was going to be here in person but showed up online * Corey - he/him - can't think of a fact that is not a fact and that's a fact. * LX - - helps with logistics around the space, gamebridge * blitzkrieg - he/him - = Short announcements and events = * Elan: Magwest is happening in San Jose!!! * discount code for `NOISEBRIDGE`, groups badges get a discount. * Elan - MAG West is happening [soon(tm)], use code NOISEBRIDGE for $10 off. * Chaz - You can also buy badges as a group for a further discount. = Excellence = '''Our One Rule is to Be Excellent to Each Other.''' What does that mean? Please see our page on [[Excellence]] ! [Group of quotes from Danial, Ciara, Elan, mister_name, others] it's excellent to put things back it's excellent to be humble it's excellent to clean up messes Pita with Hummus is excellent == 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 == '''Elan:''' [?] for cleaning the bathroom. Kudos to Loren and Elan for setting up a service Kudos to Loren for setting up meeting at sudoroom '''Loren:''' Kudos to Dave, mister_name, Loren, others for helping with Trash and sweeping/cleaning last night '''Derek:''' Zacchae for providing cake [which We-Z paid for]. = [[Guild]]s & [[WG]]s = Music representative; working on getting notes from Lucifer. printing guild had it's first meeting, ideated about strategies to reduce entropy = New Members/Access Members = [Heather explains what Access Members and Core Members are] [Jonathan is returing to for Access Membership, sponsored by Jet. Access approved.] = Financial Report = '''Anarchist societies under a capitalist state need money to survive and thrive, yo.''' '''Zacchae:''' Sent reimbursements to Josh and mister_name, sum of ~$300. It is the firt week of the month, reminder that we burn through ~15k a month. With 90k a moth, that's 6 months of runway. More supporting members would be great, $150 is the recommendation, adjust down (and up!) based on your capability. '''Sam:''' How much are we currently making from donations? '''Zacchae:''' monthly income from stripe about $2k; '''LX:''' Requesting reimbursement for TV and Tent, ~$200 '''Zacchae:''' Approved, not yet processed. '''Loren:''' Last month's numbers as a baseline? [Loren pulls up old records] '''Loren:''' In May, we had a deficit of $3k. '''Zacchae:''' Reimbursements and other financial info, https://noisebridge.net/wiki/treasury/2026 Best to @zacchae on Zulip to get their attention * 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 _may_ be available at https://noisebridge.net/wiki/Finances == Spending Needs == == Fundraising Update == [Elevator grant process stalled out because grant writer left after some conflict.] = Consensus Items = = Discussion Items = == 3: Environment Chamber == {{DiscussionItem| | topic = Environment Chamber | raised_by = Jonathan | seeking = connection }} '''Jonathan:''' I want to find someone who knows something about the Environmental Chamber '''Josh:''' I know that the it's junk, everytime we get close to get rid of it, noone is going to use it for production work. I had a use for it 3 days ago, josh will take it. '''Jonathan:''' What would b the process to get conconcesses '''Kevin:''' Does it have any value as scrap '''Josh:''' it's a wash '''Danirel:''' No response on facebook, hard to sell : Context for this? '''Josh:''' Context is in this notes, a years worth. It's not worth anything because it's hard to connect to modern interfaces. Etc. It's not usable in modern env '''Josh:''' Will take it. little c; Josh will take it == 2: Rodents == {{DiscussionItem| | topic = Rodents | raised_by = Elan | seeking = decision/outcome/advice/[?] }} '''Elan:''' NB has pests since Early Jult, growing more bold over time. They are not afraid of people, which is concerning. We should look into relocating them. Blitzkrieg suggested a bucket trap (plan can be found in #faclities). [Many missed things] '''Sam:''' Rats alive? Dead? '''Elan:''' Alive preferably. Kavya: we can't have cats. Is it ok to bring cats? '''General Response:''' Cats can't live here. '''Derek:''' I may be illegal to relocate rodents, check the laws. '''Elan:''' I won't do that, then. Also, a request for funding for bucket traps. '''Zacchae:''' I was here until 5 AM, so many rats in the last hour, more than five scurrying around. They would just walk up to me. Also, there are mouse jungle gyms in the walls (entry points can be found in the tops of either stairwell). Be clean about food. '''Josh:''' Cool with a cat. No one is allergic to snakes! Jonathon: 5 gallon rat traps? '''Elan:''' I believe so '''Sam:''' Have you seen Ratatouillie? We could have rat-controlled NBers. [A bunch of jokes about rats] '''Loren:''' It would be good to be better about food. '''Ciara:''' cute signs! '''Heather:''' Signage about cleaning waste '''Corey:''' When I eat food at NoiseBridge, I put waste directly in the compost. '''Heather:''' I think the concern is primarily about food left in open spaces. Crumbs on tables/floors. '''Elan:''' I don't think they are getting into the compost. '''Derek:''' But the rats are smelling it and are attracted to it. '''Blitzkrieg:''' Rats are an invasive species, we need traps. We have too much readily accessible open food out. No amount of signage and asking people nicely will fix this. We need to dispose of dead rats. '''Kavya:''' If active infestation means lease violation, shouldn't landlord take care of it? '''Zacchae:''' We don't want the landlord to get involved. '''Loren:''' the lease basically says that we control what happens inside the walls, landlord controls what happens outside the walls. '''Josh:''' Mouse apocolypse controlled with better food discipline and not traps in 2024. == 1: Guild Trash Management == {{DiscussionItem| | topic = Guild Trash Management | raised_by = Derek | seeking = outcome }} '''Derek:''' Good idea if each guild took care of their trash, on their own, do what they think is right. '''Kavya:''' No elected leaders or members ofa guild, just people who use the room, mostly. Open to suggestions for how to deal. Something happened to the sewing room trash can. '''Heather:''' I feel like it's ok to ignore sewing and printing room in general trash '''Loren:''' Hoping there's group support for this. Derek has ben the main dealer-with of trash for 5-8 months. I was frustrated with all the pickup we had to do yesterday. Some cans were not rebagged. We need a better trash system. '''Elan:''' People should check if trash needs to be taken out in spaces they use. It's excellent (and member-like). '''Loren:''' We need to standardize/catalog trash can sizes, as well as trash can locations. '''Blitzkrieg:''' Part of the problem is that the 'big' bins are full. One week of sawdust fills the compost. We should probably have larger bins. '''Loren:''' Sawdust and printing scraps should not be handled with general trash. '''Corey:''' There is a service that collects wood waste and turns it into particle board. (human made?) == 2: Corey disengaging from mister_name and ceasing communication with him == {{DiscussionItem| | topic = Corey disengaging from mister_name and ceasing communication with him | raised_by = mister_name | seeking = outcome }} mister_name: Over the weekend, Corey said some things to me that I found highly distressful, and I asked them to disengage. They did not disengage, I'm now formally requesting it at a meeting. I will respond to Hivemapper topics. '''Corey:''' I do not wish to respond to Mister Name; was talking to everyone about using the CNC; it was not my intention to distress anyone. mister_name: That is understood, you are not acknowledging that I felt distressed. '''Corey:''' I did acknowledge that...[many people spoke]. == 3: Hivemapper Camera handling == {{DiscussionItem| | topic = Hivemapper Camera handling | raised_by = mister_name | seeking = decision }} '''Loren:''' there may be deep agreement from both sides. In interest of noisebridge in voices. '''Heather:''' Setting context, noisebridge recently got a donation of 140 units with computer module 4 with camera hardware. There is discussion about how to repurpose. There is a note that some have gone missing, Some may be recovered. What do? '''Derek:''' Good idea if each guild took care of their trash, on their own, do what they think is right. Mister_name: a founding engineer of hivemaper donated a 140-150 DOA cameras, the ... The cameras have been moved to a locker. '''Web Daniel:''' Took the biggest chunk, does have some specific noisebridge projects, will bring back the ones. mister_name: These pieces are worth $100 minimum a piece, people didn't consider that in taking them. It is worth asking people to voluntarily return them. Perform some service or put them to use for noisebridge '''Blitzkrieg:''' I think that selling up to 100 of them are fine for fundraising. '''Chaz:''' not fully up to date, I think there was not a do not hack, it's hard to tell people to bring them back. Mister_name: It's worth asking. '''Web Daniel:''' People should do projects. It would be a shame if they were just sold. Mister_name: People should make proposals to receive units. '''Corey:''' Yeah, so I just to state for the rescord that halt in distribution was the right thing to do to prevent the drainage. The value is greater of education than selling them. I feel like the notion of dismantle and selling is un???? I don't believe that serves noisebridge. Thre are opportunities other than selling them. The philiosophy ... teaching dissassembly is a lesson. They are almost a univserally a problem of the power boards, we could have .... ???????/ I want to make sure the we,.. before we go any further, desperate to stop dismantling; there's no rush to dissassemble, we have time to take stock and come up with more ideas about to use them. We can get substantailly more money and educational value by perhaps running a class that use them. The people who donated them wanted the people of noisebridge to use [them in a noise bridgey way] Mister_name: We have no idea what people are planning to do with the modules already take. We should form a group that handles distribution/use of the units. '''Kavya:''' How confident are you that we could sell them at the suggested prices? Mister_name: No current confirmation. the boards in the camera are currently highly in demand. The prices presented in the doc are a range seen on a handful of websites, so they're likely to sell in that range '''Elan:''' I think there was already a discussion project propsal on the discord. If we can sell them at a reasonable cost then we can buy them at a reasonable cost. Maybe selling them is not so bad, as if there a class in the works, then they could be bought for the class. '''Blitzkrieg:''' I'm not opposed to hosting a class. I'm not opposed to selling them at the current value; I don't know how many we need at the space. I woud suggest that we have an open period of no more than two weeks for review. People may take responsibility for the units. '''Corey:''' All I wanted to do was stop wholesale distribution. There will be units broken during use. We should always kep a buffer for replacement when needed. The fault that the majority of units are facing are power board related, from sudden surges. We shouldn't assume why people took units. We didn't properly handle reception of this, discussion was only had on the electronics channel. I want to make sure people have a chance to get to use these. Mister_name: The units have been at NB for a week, Derek and I explained to many people (including Corey) that they should not be taken until we had a plan for them. A panel would be a great. '''Corey:''' I think word of mouth was not a proper communication method. I apologize for calling people impulsive, I didn't want to see this units get misused. '''Chaz:''' Let's table the hindsight suggestions. '''Loren:''' I want to offer a question, I'm confused to what the concern is. There is concerns that these are useful as they are. Feels like potential is that there much more than that, we want to use them interally, maybe know that we're on terms of aggreement, I'm curious what the productive agreement is? '''Corey:''' Yeah just a direct response: I just need to articulate that the poroopsoal process is a great first step, and that is my direct response, keeping them intact to me is an opportunity . When people fail to repair them, that will be a candidate to step up to use the compute module alone. (or sell them) '''Heather:''' Sounds like project proposals would be good '''Chaz:''' Next week would be a good idea. Any takers on who wnat to be on that pane? Next week to give people a time to think. '''Heather:''' Let's use this as general concensus to not do anything with the hivemapper units until next meeting '''Kevin:''' Let's not tear down any more units, we can experiement on the existing parts. '''Kavya:''' Is there protocol for selling? '''Kevin:''' Check the discord for presentinxt week. '''Heather:''' If anyone has disassembled units, don't sell them. = 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 = [[Category:Meeting Notes]]

MediaWiki:Common.css

🇳🇱 · MakerSpaceLeiden · MarkKlaauw

← Oudere versie Versie van 6 aug 2026 17:36 (3 tussenliggende versies door dezelfde gebruiker niet weergegeven) Regel 125: Regel 125: #siteNotice a:not(.new):visited { #siteNotice a:not(.new):visited { color: #36C; color: #36C; } } @media screen { #content a.new, #siteNotice a.new { color: #d03; } } } }

Makerspace Leiden

🇳🇱 · MakerSpaceLeiden · MarkKlaauw

Lege pagina aangemaakt Nieuwe pagina

Hoofdpagina

🇳🇱 · MakerSpaceLeiden · MarkKlaauw

Doorverwijzingsdoel gewijzigd van MakerSpace Leiden:Makerspace Leiden naar MakerSpace Leiden ← Oudere versie Versie van 6 aug 2026 08:40 Regel 1: Regel 1: #DOORVERWIJZING [[MakerSpace Leiden:Makerspace Leiden]] #DOORVERWIJZING [[MakerSpace Leiden]]

Intranet

🇳🇱 · MakerSpaceLeiden · MarkKlaauw

← Oudere versie Versie van 6 aug 2026 08:08 (Een tussenliggende versie door dezelfde gebruiker niet weergegeven) Regel 1: Regel 1: The Makerspace Intranet is the portal for participants . It provides access to your account, agenda , and SpaceTegoed balance in one place . Makerspace Intranet is het portaal voor de deelnemers . Je vindt hier je account, agenda en SpaceTegoed op één plek . Go to [https://mijn.makerspaceleiden.nl Makerspace Intranet] [https://mijn.makerspaceleiden.nl Makerspace Intranet]

Intranet

🇳🇱 · MakerSpaceLeiden · MarkKlaauw

← Oudere versie Versie van 6 aug 2026 07:08 (2 tussenliggende versies door dezelfde gebruiker niet weergegeven) Regel 1: Regel 1: The Makerspace Intranet is the portal for participants. It provides access to your account, agenda, and SpaceTegoed balance in one place. Go to [https://mijn.makerspaceleiden.nl Makerspace Intranet]

2026-08 VarnaLab за всички, всички за VarnaLab

🇧🇬 · VarnaLab · kaloyan (kaloyan@undisclosed.example.com)

2026-08 VarnaLab за всички, всички за VarnaLab * Да обсъдим има ли как фирми да плащат co-working и да издаваме фактура (а не да е договор за дарение), ако ще плащаме данъци - просто ще ги калкулираме в цената, в другите coworking-и е 150-200 евро на месец [Калоян] - 10% от общата печалба на фирмата може да отива за дарения и те ще им бъдат признати. Към момента, можем да предложим само договор за дерение, а след проучване как стоят нещата с инспекторати, проверки, изисквания и дали на тях ще…

Elektra-Beckum HC 260 Abricht- und Dickenhobel

🇩🇪 · Leinelab · joern.e@undisclosed.example.com (joern.e)

Elektra-Beckum HC 260 Abricht- und Dickenhobel Die HC 260 ist eine kombinierte Abricht- und Dickenhobelmaschine. Mit ein wenig Umbauarbeit lässt sich zwischen diesen beiden Modi wechseln. Da die beiden Arbeitsschritte „Abrichten“ (engl. jointing

Its-g5

🇳🇱 · Revelation space · Bertrik Sikken

Introduction ← Oudere versie Versie van 6 aug 2026 15:29 Regel 19: Regel 19: * Source code for an ITS-G5 receiver https://github.com/pit711/v2x2map * Source code for an ITS-G5 receiver https://github.com/pit711/v2x2map * Simplest source code for Arduino-based sniffer: https://git.devlol.org/jstsmthrgk/simple-its-g5-receiver-firmware * Simplest source code for Arduino-based sniffer: https://git.devlol.org/jstsmthrgk/simple-its-g5-receiver-firmware * Transmitting ITS-G5 signals? https://codeberg.org/opentrafficmap/its-g5-receiver-firmware_txenabled/src/branch/main/main/tx_custom.c Would be nice to have on your bicycle! :D In the Netherlands, SPAT/MAPem messages from traffic lights are not transferred over wifi-p, but over UDAP. In the Netherlands, SPAT/MAPem messages from traffic lights are not transferred over wifi-p, but over UDAP.

HAC-32-DEV

🇳🇱 · Hackalot · Okabe

← Oudere versie Versie van 6 aug 2026 21:20 (2 tussenliggende versies door dezelfde gebruiker niet weergegeven) Regel 1: Regel 1: {{Project {{Project |name=HAC-32-DEV |name=HAC-32-DEV |start=2026 |contact=Okarin |contact=Okarin |URL=https://hackalot.nl/HAC-32-DEV |info=A adapter for ESP32 Dev boards |info=A adapter for ESP32 Dev boards |status=in progress |status=in progress |Picture=Hac-32-dev.jpg }} }}

Logo

🇳🇱 · Hackalot · Okean

← Oudere versie Versie van 6 aug 2026 18:14 Regel 16: Regel 16: <gallery> <gallery> Bestand:Hackalot_logo.svg|Logo color svg Bestand:Logo color.pdf|Logo color pdf Bestand:Logo color.pdf|Logo color pdf Bestand:logo-path.svg| logo als pad, ook geschikt voor de vinylsnijder Bestand:logo-path.svg| logo als pad, ook geschikt voor de vinylsnijder

TV

🇳🇱 · Bitlair · Polyfloyd

Extra's ← Oudere versie Versie van 6 aug 2026 20:11 Regel 13: Regel 13: == Extra's == == Extra's == * [[File:TV Afstandsbediening Houder.stl]] * [[File:TV Afstandsbediening Houder.stl]] * [[File:HDMI Kabel Houder.stl]]

BambuLab

🇳🇱 · Bitlair · ChillThijs

← Oudere versie Versie van 6 aug 2026 19:26 Regel 6: Regel 6: |Location=Flexlab |Location=Flexlab |Warnings=Bestand:Waarschuwing heet oppervlak.svg, Bestand:Waarschuwing pletgevaar voor handen.svg |Warnings=Bestand:Waarschuwing heet oppervlak.svg, Bestand:Waarschuwing pletgevaar voor handen.svg |Name=BambuLab 3D-Printers }} }} De BambuLab printers zijn de 3e generatie aan 3D-printers waar Bitlair over beschikt. Deze printers volgen de [[Gereedschap/Ultimaker|Ultimakers]] en [[Gereedschap/Ender_3_Pro|Ender 3 Pro]] op. De BambuLab printers zijn de 3e generatie aan 3D-printers waar Bitlair over beschikt. Deze printers volgen de [[Gereedschap/Ultimaker|Ultimakers]] en [[Gereedschap/Ender_3_Pro|Ender 3 Pro]] op. Regel 100: Regel 99: |- |- | 2026-01 || z-as schroeven en rods gesmeerd || [[User:ChillThijs]] | 2026-01 || z-as schroeven en rods gesmeerd || [[User:ChillThijs]] |- | 2026-06 || z-as schroeven en rods gesmeerd || [[User:ChillThijs]] |} |}

Bestand:Flipdot 20x16.jpg

🇳🇱 · Bitlair · Polyfloyd

Polyfloyd heeft Bestand:Flipdot 20x16.jpg geüpload Nieuwe pagina

Events/2016-07-31 Metameet 0x7

🇳🇱 · Bitlair · Polyfloyd

← Oudere versie Versie van 6 aug 2026 17:42 Regel 4: Regel 4: |start=2016/07/31 20:00:00 |start=2016/07/31 20:00:00 |end=2016/07/31 20:30:00 |end=2016/07/31 20:30:00 |location= Bitlair |location= Space1.0 }} }} == Wie notuleert == == Wie notuleert ==

Events/2016-05-22 Metameet 0x3

🇳🇱 · Bitlair · Polyfloyd

← Oudere versie Versie van 6 aug 2026 17:42 Regel 4: Regel 4: |start=2016/05/22 08:00:00 PM |start=2016/05/22 08:00:00 PM |end=2016/05/22 08:00:00 PM |end=2016/05/22 08:00:00 PM |location= Bitlair |location= Space1.0 }} }} Metameet. Metameet.

Events/2016-01-09 Movienight

🇳🇱 · Bitlair · Polyfloyd

← Oudere versie Versie van 6 aug 2026 17:41 Regel 4: Regel 4: |start=2016/01/09 08:00:00 PM |start=2016/01/09 08:00:00 PM |end=2016/01/09 02:00:00 AM |end=2016/01/09 02:00:00 AM |location= Bitlair |location= Space1.0 }} }} Movienight january 2016 Movienight january 2016

Events/2014-12-24 Bitkerst 2014

🇳🇱 · Bitlair · Polyfloyd

← Oudere versie Versie van 6 aug 2026 17:40 Regel 3: Regel 3: |start=2014-12-24T19:00:00.000Z |start=2014-12-24T19:00:00.000Z |end=2014-12-25T00:00:00.000Z |end=2014-12-25T00:00:00.000Z |location= Bitlair |location= Space1.0 |status=Confirmed |status=Confirmed |contact=Stijn |contact=Stijn

Events/2013-10-30 Discussion

🇳🇱 · Bitlair · Polyfloyd

← Oudere versie Versie van 6 aug 2026 17:39 Regel 4: Regel 4: |start=2013/10/30 08:00:00 PM |start=2013/10/30 08:00:00 PM |end=2013/10/30 10:00:00 PM |end=2013/10/30 10:00:00 PM |location= Bitlair |location= Space1.0 |info= |info= }} }}

Events/2013-05-19 OHM Hackathon

🇳🇱 · Bitlair · Polyfloyd

← Oudere versie Versie van 6 aug 2026 17:38 Regel 4: Regel 4: |start=2013/05/19 14:00:00 |start=2013/05/19 14:00:00 |end=2013/05/19 19:00:00 |end=2013/05/19 19:00:00 |location= Bitlair |location= Space1.0 }} }} Some teams are coming together at bitlair to hack on various parts necessary for OHM2013. Some teams are coming together at bitlair to hack on various parts necessary for OHM2013.

Events/2013-04-28 BBQ

🇳🇱 · Bitlair · Polyfloyd

← Oudere versie Versie van 6 aug 2026 17:37 Regel 4: Regel 4: |start=2013/04/28 05:00:00 PM |start=2013/04/28 05:00:00 PM |end=2013/04/28 11:00:00 PM |end=2013/04/28 11:00:00 PM |location= Bitlair |location= Space1.0 }} }} BBQ BBQ BBQ BBQ BBQ BBQ

Events/2012-12-31 29C3 afterparty plus New Years

🇳🇱 · Bitlair · Polyfloyd

← Oudere versie Versie van 6 aug 2026 17:37 Regel 3: Regel 3: |start=2012/12/31 07:00:00 PM |start=2012/12/31 07:00:00 PM |end=2013/01/01 06:00:00 AM |end=2013/01/01 06:00:00 AM |location= Bitlair |location= Space1.0 }} }} New years party! 29C3 Afterparty in Amersfoort! New years party! 29C3 Afterparty in Amersfoort!

Events/2017-04-29 WebHacking Workshop

🇳🇱 · Bitlair · Polyfloyd

Tekst vervangen - "Ariane 24, Amersfoort" door "Space2.0" ← Oudere versie Versie van 6 aug 2026 17:36 Regel 4: Regel 4: |start=2017-04-29T14:30:00.000Z |start=2017-04-29T14:30:00.000Z |end=2017-04-29T18:00:00.000Z |end=2017-04-29T18:00:00.000Z |location= Ariane 24, Amersfoort |location= Space2.0 |status=Confirmed |status=Confirmed |contact=WilcoBaanHofman |contact=WilcoBaanHofman

Events/2019-01-20 Metameet 0x26

🇳🇱 · Bitlair · Polyfloyd

Tekst vervangen - "Computerweg 20a, Amersfoort" door "Space3.0" ← Oudere versie Versie van 6 aug 2026 17:36 Regel 4: Regel 4: |start=2019/01/20 20:00:00 |start=2019/01/20 20:00:00 |end=2019/01/20 20:30:00 |end=2019/01/20 20:30:00 |location= Computerweg 20a, Amersfoort |location= Space3.0 }} }} Notulen: [https://member.bitlair.nl/Pages/2019-01-20_Metameet_0x26] Notulen: [https://member.bitlair.nl/Pages/2019-01-20_Metameet_0x26]

Events/2018-05-06 Metameet 0x20

🇳🇱 · Bitlair · Polyfloyd

Tekst vervangen - "Computerweg 20a, Amersfoort" door "Space3.0" ← Oudere versie Versie van 6 aug 2026 17:36 Regel 4: Regel 4: |start=2018/05/06 20:00:00 |start=2018/05/06 20:00:00 |end=2018/05/06 20:30:00 |end=2018/05/06 20:30:00 |location= Computerweg 20a, Amersfoort |location= Space3.0 }} }} Notulen: [https://member.bitlair.nl/Pages/2018-05-06_Metameet_0x20] Notulen: [https://member.bitlair.nl/Pages/2018-05-06_Metameet_0x20]

Lasersaur Laser Cutter

🇳🇱 · MakerSpaceLeiden · LucasV

← Oudere versie Versie van 6 aug 2026 19:01 Regel 6: Regel 6: Also Known As: Laser Cutter, Laser Engraver, Laser Snijder Also Known As: Laser Cutter, Laser Engraver, Laser Snijder {{NeedsWorkOlga|Ventilatie / afzuiging werkt nu anders.}} <tabs> <tabs>

MediaWiki:Mainpage

🇳🇱 · MakerSpaceLeiden · MarkKlaauw

Nieuwe pagina aangemaakt met 'MakerSpace Leiden' Nieuwe pagina MakerSpace Leiden

Makerspace Leiden

🇳🇱 · MakerSpaceLeiden · MarkKlaauw

MarkKlaauw heeft de pagina Makerspace Leiden hernoemd tot MakerSpace Leiden zonder een doorverwijzing achter te laten Nieuwe pagina [[Category:Organization]] __TOC__<big>'''Hallo en welkom op de wiki van MakerSpace Leiden!'''</big> Deze wiki wordt door de deelnemers van de MakerSpace onderhouden. Schroom niet om zelf wat toe te voegen, de wiki is een gedeelde bron waar ook jij aan mee kunt helpen. * Ook deelnemer worden? Kijk dan op de [https://wiki.makerspaceleiden.nl/mediawiki/index.php/Participate#Ik_overweeg_deelnemer_te_worden. deze pagina]. * Ben je nieuw lid en wil je aan de slag op de Space? De pagina [[Getting started in the Makerspace]] geeft je de juiste intro. * Wil je wat toevoegen aan de wiki? Lees dan de onderste helft van de pagina [[Getting started in the Makerspace#Introductie_wiki|Getting started in the Makerspace]] ==[[File:031-ink.png|middle|48px|link=]] Wat is de MakerSpace Leiden?== De MakerSpace Leiden is een gezamenlijke werkplaats. Mensen worden deelnemer voor een vast bedrag per maand en krijgen vervolgens toegang tot de Space, een stem in de deelnemersraad en een plek in de deelnemerskast om hun projecten op te slaan.<br /> Communicatie gaat via de [[Mailing List|Mailing list]], en je deelnemer administratie kun je zelf regelen via [https://mijn.makerspaceleiden.nl/ mijn.makerspaceleiden.nl] .<br /> Er wordt elke maand een deelnemersraad gehouden. Hier worden plannen voor de space, organisatorische zaken en gebeurtenissen van belang besproken. Het is niet verplicht om aanwezig te zijn, maar is wel aan te raden omdat je op de hoogte blijft van de ontwikkelingen en kunt meebeslissen. De grote ideeën achter de MakerSpace zijn: * Vrijheid om projecten op te zetten en eraan te werken. * Een gedeelde verantwoordelijkheid voor de Space en haar deelnemers. * Open uitwisseling van ideeën, plannen en hulp. * Een vriendelijke, ondersteunende sfeer. Met dit fundament wordt de MakerSpace een plek waar mensen graag aan hun creaties willen werken en de Space zelf willen helpen groeien. ==Gereedschap en Machines== We hebben vrij veel gereedschap gedocumenteerd. Hieronder staan alfabetisch wat categorieën. {| |- |[[File:003-3d printer.png|left|64px|link=:Categorie:CNC machines]] | [[:Categorie:CNC machines|CNC-apparaten]]: 3D printers, lasercutters, de vinylsnijder, routers and de 3D-scanner. |- |[[File:018-electronics.png|left|64px|link=[:Categorie:Electronics tools]] | [[:Categorie:Electronics tools|Electronica-gerelateerd]] gereedschap. |- |[[File:078-woodworking.png|left|64px|link=:Categorie:Wood working tools]] | [[:Categorie:Wood working tools|Houtbewerkingsmachines]] en -gereedschappen. |- |[[File:073-welding.png|left|64px|link=:Categorie:Welding tools]] | [[:Categorie:Welding tools|Lasapparaten]]. |- |[[File:Measuring-tape_icon.png|left|64px|link=:Categorie: Measuring tools|meet instrumenten]] | [[:Categorie:Measuring tools|Meetinstrumenten]]. |- |[[File:006-screw.png|left|64px|link=:Categorie:Metal working tools]] | [[:Categorie:Metal working tools|Metaalbewerkingsgereedschap]] en machines. |- |[[File:066-toolbox.png|left|64px|link=:Categorie:Compressed air tools]] | [[:Category:Compressed air tools|Perslucht gereedschap]]. |- |[[File:Vacuum_cleaner_icon.png|left|64px|link=:Categorie:Cleaning_tools]] | En natuurlijk [[:Categorie:Cleaning_tools|Schoonmaakspullen]]. |- |} De totale lijst van machines en gereedschappen staat [[:Category:Tools|hier]]. ==[[File:exclam.png|middle|48px|link=]] Veiligheid en geluidsproductie [[File:exclam.png|middle|48px|link=]]== Veiligheid op de Space is een vereiste. Dit zijn onze [[SAFETY|regels en instructies]]. We verwachten dat je ze goed kent. {| |- |[[File:022-first aid kit.png|left|64px|link=]] | Veiligheid voor mensen en machines * Dit gereedschap heeft [[:Category:Tools that require Permission or Instruction prior to use|speciale]] toestemming en instructie nodig voordat je ermee aan de slag mag. * Dit gereedschap heeft een [[:Category:SafetySheet|veiligheidsblad]]. Neem de lijst door, zodat je een overzicht hebt. * Als je iets onveiligs ziet gebeuren, spreek dan je medemakers erop aan, want je medemakers zijn zich hier vaak ook niet van bewust.<br> We zijn hier samen verantwoordelijk voor, en hoe meer mensen dit doen, hoe beter dit werkt. |} {| |- |[[File:audio-speaker.png|left|64px|link=]] | We hebben buren, dus houd daar rekening mee. Hun achtertuin grenst aan de grote werkplaats. * Machines in [[:Categorie:NoiseCat1|geluidscategorie 1]] mogen alleen tussen 07:00 en 19:00 uur worden gebruikt. Doe zelf ook oorkappen op. * Machines en gereedschap in [[:Categorie:NoiseCat2|geluidscategorie 2]] mogen ook in de avond worden gebruikt, maar wordt afgeraden.<br> Als je zelf oordoppen in wilt doen, maak je per definitie teveel herrie voor de buren. |} {| |- |[[File:051-face mask.png|left|64px|link=]] | Let ook op stofproductie en regels omtrent gasflessen. * Machines in [[:Category:DustControl1|stofklasse 1]] moeten altijd aangesloten worden op een afzuiger voordat je ze aanzet. Ophopend stof vormt een brandgevaar en kan zelfs [https://en.wikipedia.org/wiki/Dust_explosion ontploffen]. * Bij machines in [[:Category:DustControl2|klasse 2]] is dit ook verplicht en in [[:Category:DustControl3|klasse 3]] is het aangeraden. Makers met gevoelige longen zullen je dankbaar zijn. * Sommige apparaten zijn aangesloten op een [[:Category:Gasflesgebruik|gasfles]]. Vergeet niet het kraantje dicht te doen na gebruik en let op de [[Gas Bottle Pressure Vessel Limit|gasfleslimiet]]. De gemeente treedt zeer agressief op bij het overtreden van deze limiet! |} Als laatst: Meld kapot gereedschap, onveilige situaties of zaken die niet in de haak zijn, via de maillijst of rechtstreeks aan het [https://makerspaceleiden.nl/contact/ bestuur]. Dit is niet alleen verplicht, maar helpt ons met zijn allen een veilige cultuur te creeeren en te onderhouden. ==[[File:064-Thermal.png|middle|48px|link=]] Procedures en Principes== Wat algemene gebruiken om de Space aangenaam te houden: * 'Be excellent & try to not to be on fire.' * Laat de ruimte schoner / netter achter dan hoe je het aantrof. * Al ons gereedschap heeft z'n plek. Vergeet het niet terug te leggen na gebruik. * Is iets een bende? Laat je er dan vooral over horen! Wil je alsnog aan de slag, ruim dan alles op. Bijvoorbeeld bij de kolomboor eigen spanen en ook die van de vorige; een schoon resultaat is wat telt. Meld & fix. * Is een voorraad leeg? Licht dan de [[Mailing List|Mailing list]] in of vul het zelf aan. Bij dat laatste mag je declareren via ons [https://mijn.makerspaceleiden.nl/pettycash/show SpaceTegoed ]. * Let erop dat sommig gereedschap [[:Categorie:On loan tools|in bruikleen]] is. Dan zijn er nog wat procedures voor het runnen van de space: * De Space [[Opening the space|openen]] * De Space [[Closing the space|sluiten]] * De Space [[Cleaning_the_Space|schoonmaken]] Verdere protocollen staan [[:Category:Procedures|hier]]. ==[[File:008-pigment.png|middle|48px|link=]] Overige Informatie== * [https://flat-icons.com/ Flaticons] is de ontwerper van de icoontjes, via [https://www.flaticon.com/packs/diy-10 FlatIcon.com]. * [[Woordenlijst]]; een poging om het jargon een beetje inzichtelijk te maken. * [[Oude_Plattegronden|Plattegrond]] van de Space. * [[:Speciaal:AllePaginas| Alle]] pagina's op een rij. * [[Leveranciers| Leveranciers, webwinkels etc]]. Handig als je materialen zoekt voor je project. * [[Wish list| Wish list]]. * [[in memoriam Willem| In Memoriam]].

Hoofdpagina

🇳🇱 · MakerSpaceLeiden · MarkKlaauw

MarkKlaauw heeft pagina Hoofdpagina hernoemd tot MakerSpace Leiden:Makerspace Leiden Nieuwe pagina

MediaWiki:Common.css

🇳🇱 · MakerSpaceLeiden · MarkKlaauw

← Oudere versie Versie van 6 aug 2026 08:05 (14 tussenliggende versies door dezelfde gebruiker niet weergegeven) Regel 89: Regel 89: --bs-font-sans-serif: sans-serif !important; --bs-font-sans-serif: sans-serif !important; --bs-body-font-family: var(--bs-font-sans-serif); --bs-body-font-family: var(--bs-font-sans-serif); --bs-body-font-size: 1rem !important; --bs-link-color-rgb: 51, 102, 204; } } Regel 104: Regel 105: @media screen and (min-width: 768px) { @media screen and (min-width: 768px) { :root { :root { --bs-body-font-size: 0. 85rem ; --bs-body-font-size: 0. 9rem !important ; } } } } Regel 118: Regel 119: .btn { .btn { font-size: 0.85rem; font-size: 0.85rem; } @media screen { a:not(.new) { color: #36C; } a:not(.new):visited { color: #36C; } } } Regel 133: Regel 144: #mw-main-container aside { #mw-main-container aside { position: absolute; position: absolute; right: 0 ; right: 10% ; width: 12%; width: 12%; } @media screen and (min-width: 768px) { #mw-main-container aside { right: 0; } } }

Intranet

🇳🇱 · MakerSpaceLeiden · MarkKlaauw

Lege pagina aangemaakt Nieuwe pagina

Konvent/06.08.2026

🇩🇪 · Attraktor · DCtoDaylight

Created page with " Noch vorläufig!!! Aus dem letzten Konvent kopiert! = Protokoll zum Konvent vom 06.08.2026 = == Top 1: Begrüßung und Feststellung auf Beschlussfähigkeit == Der Konvent wird um 19:33 Uhr von Art eröffnet. Es sind 11 Mitglieder anwesend, damit ist der Konvent beschlussfähig. Die Protokollführung erfolgt durch Peer (kratenko) – und Eric. == Top 2: Vorstellung und Verabschiedung der Tagesordnung (inkl. Zeitrahmen) == Die Konvent ist bis 21:30 Uhr terminiert. ==..." New page Noch vorläufig!!! Aus dem letzten Konvent kopiert! = Protokoll zum Konvent vom 06.08.2026 = == Top 1: Begrüßung und Feststellung auf Beschlussfähigkeit == Der Konvent wird um 19:33 Uhr von Art eröffnet. Es sind 11 Mitglieder anwesend, damit ist der Konvent beschlussfähig. Die Protokollführung erfolgt durch Peer (kratenko) – und Eric. == Top 2: Vorstellung und Verabschiedung der Tagesordnung (inkl. Zeitrahmen) == Die Konvent ist bis 21:30 Uhr terminiert. == Top 3: Verlesung und Genehmigung des Protokolls des vorangegangenen Konventes == Verlesung und Genehmigung des Protokolls des vorangegangenen Konventes entfällt mit Verweis auf das Protokoll im Wiki. Der Konvent hat durch Zuruf entschieden, das Protokoll nicht zu verlesen, == Top 4: Termine und Berichte == === Termine === * 13.-14.06.2026 „Parkour für eine bessere Welt“ der jungen altonale erneut auf der Christianswiese durchführen. ** Wann: 13. & 14. Juni 2026, jeweils von 13 – 17 Uhr (Sa. Aufbau 11-13 Uhr)(Freiwillige: Axel, Alex, Andreas, Jan R, Fatima, Marlon, ( Andrea (unsicher) ) )Material wird am Do. 11.06. bereitgelegt, Transport: ** Wer? Treffen im Attraktor um 10 Uhr; Getränke (Apfelschorle): Sven, Andrea wg Regenschutz ansprechen, ** Bericht: war erfolgreich, es wurde mit mehreren Dutzend Kindern gearbeitet. Es gab keine Probleme. Plan für nächstes mal: wieder machen. * 16.06. Einweisung Formatkreissäge ** Bericht: Wurde durchgeführt, aber es haben wohl zwei unentschuldigt gefehlt, was unschön ist. Nächst Einweisung nicht vor August (Höhrensagen). * 02.07. Geburtstagsfeier Attraktor wird volljährig, Angebot: Kuchen (Andrea, Fatima, Axel), Daniel bietet Grillen an; ** Bericht: Gab Kuchen, wurde durchgeführt, hat Spaß gemacht. Manche haben es leider nicht mitbekommen. Benachrichtigung gabs über Matrix, das erreicht wohl nicht alle. * nächster Konvent am 06.08.2026 ** Der im Kalender eingetragene Termin ist in vier Wochen (nicht in fünf). ** Kein Anwesender weiß, ob das Absicht ist oder nicht. ** Der Konvent hat durch Zuruf sich auf den Termin 6.8. geeinigt und damit den in vier Wochen bestätigt. * Bastelsamstag: 11.07.2026 ** Es wird gesucht, ob ein Mitglied am Bastelsamstag sicher anwesend ist. ** Es findet sich Sven, der 17h mit Schlüssel hier ist zum Aufschließen, und Axel der für Führungen anwesend sein wird (bis 19h min). ** 17h-19h wird als Termin eingetragen. * Internationaler Linkshändertag: 13.08.2026 Antrag von Fatima: Der Konvent möge beschließen, dass Donnerstag den 13.8.2026 ein Workshop zum Internationalen Linkshändertag stattfindet. Für Organisation und Durchführung brauche ich Unterstützung, gerne auch aus allen Werkstätten. Begründung: Viele oder alle kennen den Spruch: "Das mache ich mit links" - Ich mache es tatsächlich täglich mit links. Anlässlich des Linkhändertages würde ich gerne eine Veranstaltung organisieren und hoffe dabei auf eure Unterstützung . Ich weiß nicht wie viele Mitglieder im Verein Linkshänder sind aber ich hoffe ich bin nicht die Einzige. Ich möchte euch zeigen wie wir in einer Welt für Rechtshänder das meiste trotzdem händeln können, auch ohne spezielle "Linkshändergeräte" Ich stelle mir u.a. Stationen vor, an denen Rechtshänder versuchen können einiges tatsächlich mit links zu machen. Außerdem möchte ich Linkshänder ermutigen etwas auszuprobieren, auch wenn die Anleitungen für Rechtshänder sind. ** Es scheint keine Linkshänderscheren im Verein zu geben, wir sollten welche anschaffen für den Verein; in der Vergangenheit mussten wohl für Aktionen Linkshänderscheren geliehen werden. ** Der Tag soll wohl Stationen haben, wo Geräte für Linkshänder aufgebaut sind, damit Rechtshänder merken, wie problematisch ist. ** Fatima, Olof ** Abstimmung Antrag: 10 Dafür, 0 Dagegen, 1 Enthaltung * 15.-16.08.2026 Sa. So. makerfaire Hannover ** Keiner anwesend, der Federführend ist. Vorschlag: Diskussion im Anschluss, wenn jemand verfügbar ist. ** Wollen wir da basteln? Wir haben wohl viel Platz? Haben wir genügend Leute? ** Klärung über Matrixgruppe und nachher im Treffen. ** Muss jetzt zeitnah geklärt werden, für Ankündigungen. ** Zur Teilnahme sind alle herzlich aufgerufen. * 10. Oktober 2026 – 25. Oktober 2026 code week 2026 (Auftaktveranstalung in der Zentralbibliothek, 2 Lötworkshops)(Freiwillige: Axel, Andreas, ) ** ist wohl alles besprochen. Es stehen erst zwei auf der Liste, eigentlich brauchen wir 6-8, aber das scheint zu Laufen. ** Es gibt immer beliebig viele dort, die löten wollen. ** Das ist auch eine zusätzliche Einnahmequelle für den Verein. ** Wir brauchen daher quasi beliebig viele Löthelfer ** Gerne auch nichtlötende Mitglieder bis dahin noch ins Löten führen. Am besten noch heute! * 9.-11.10.2026 Polaris (Messe Hamburg) ** ist eine anime/cosplay convention ** wir würden einen Makerspace für Cosplayer anbieten. 3D Druck, löt, Nähen ** Wir bräuchten dafür aber genügend Leute. Tickets gibt es dann kostenlos, aber auch nur, wenn dann wirklich da ist. 3 Leute rund um die Uhr. ** Vermutlich nicht genügend Leute mit festem Comittment. Großes Zeitinvestment. ** wenn kein Stand, dann hält Olof trotzdem die Attraktorfahne hoch (Flyer). ** Wir wären auch zu spät für dieses Jahr. Thema ist wohl durch. ** Vielleicht nächstes mal? * 18.11.2026 - 21.11.2026 -. Play Festival ( <nowiki>https://www.playfestival.de/</nowiki> ) ** Ist in Hamburg ** "Da muss ich (Olof) sich kümmern. Ist Scheiße ist aber so." ** Olof hat da Zugang zur Orga. ** Thema ist dieses mal: Sound. Könnte man was zu anbieten ** Spontan der Plan, im Anschluss dazu zusammenzusitzen. * 27.-30.12. 40c3 auf dem Gelände der Messe! nicht cch, sondern Messehallen ** Leere Hallen, wir werden Informationen sicher noch bekommen ** Wer was machen will, macht! Aber bringt euch bitte rechtzeitig ein! ** Wir sind traditionell mit mehreren Assemblies dort. === Berichte zu vergangenen Terminen === * s.O. === Projektstatus === Projekte, welche über keine persönliche Vertretung auf dem jeweiligen Konvent verfügen werden nicht behandelt und demgemäß in der Tagesordnung übersprungen. ([[Konvent/05.06.2025]]) * Elektroinstallation: Was fehlt noch? wenig Zeit, wenig Mithilfe, Dokumentation geschrieben, ist rechtlich alles abgesichert; Verteilung hinten, Installation Holze steht aus; nächste 6-8 Wochen wird wenig passieren; Liste der noch abzuarbeitenden Arbeiten wird erstellt, Jan R schubbst. ** In letzter Zeitr wenig Fortschritt ** Metallwerkstatt gehen die Steckdosen ** Holzwerkstatt hat Strom für Frese, Notaus sind da, aber ohne Funktion ** 09.07.2026 Liste der ausstehenden Arbeiten steht noch aus. * Mail Verteiler wird eingerichtet (Konvent/20.06.2024) - nemo (kein update) ** kein Update * Einen Tag im Monat zum allgemeinen Aufräumen nutzen (Konvent/25.07.2024) ** kein spürbarer Fortschritt in Organisation ** Klemmbrett mit Aufgaben liegt auf den Mitgliederkisten ** Müll schein rausgebracht zu werden ** Es wird eine Verbesserung der Situation wahrgenommen. Wenn auch nicht messbar. ** Lob für Zustand von Metall- und Holzwerkstatt wird ausgesprochen * Keramikwerkstatt-Fenster installieren (Konvent/25.07.2024) - Maya, Joachim ** kein update * Fahrradwerkstatt - Daniel F (fyi: 24.04.2025: Eric, Axel, Olof und Daniel F. hatten vor da mitzumachen) Wird versucht zu kontaktieren und aktuellen Stand dazu herauszufinden. will zeitnah vorbeikommen. Suche nach Personen den Fahrradmaterialbestand durchzugehen und auszusortieren ** ist noch aktuell, wird drum gekümmert * Neuer Gefrierschrank - Daniel B. ** Beide Geräte sind finanziert und da. Umbau ist in arbeit. * Inbetriebnahme Keramikwerkstatt - Maya, Sven ** Inbetriebnahme Toepferscheibe: Besorgen von Auffangbecken (120€) ** Einbau Steckdosen (Dominic? Blockiert durch Elektroinstallation) ** Tonabscheider nimmt Form an; Abdeckung für Abflussbecken in Arbeit ( soll in attracess aufgenommen werden); ** Waschbecken Abdeckung - in arbeit === Vorträge, Workshops o. ähnl. === * Olof arbeitet an einem Insel-Workshop für Papierinseln ** Vorhaben scheitert wohl. Vielleicht in Hanover * Daniel F will 3D-Druck machen - Noch kein Termin. Ab Juli Terminfindung moeglich (kein update, nicht anwesend) * Andreas E will Workshop über Sensorik machen (kein update, nicht anwesend) * Sven kommt noch mal auf nemo zu wegen Workshop Einführung 3D Design m. onshape - April, Mai (kein Update, nicht anwesend) * Erste Hilfe via Michael - später Sommer; Michael schickt da noch mal eine Themenabfrage was so an Themen relevant ist fuer uns; Michael würde gerne Themeninput haben; Absprachen für Material u. Themen laufen (z.B. Beatmungspuppe, etc. ); Kostenbeitrag f. Verbandsmaterial, Terminidee (Wochenende , Fenster 10-18:00 Uhr + Mittagspause) ** kein update * Idee für Veranstaltungsreihe DI.Day (digital independence day) jeden ersten Sonntag 1x im Monat; siehe di.day/de ; z.B. linux installieren (17.05. linux installations-party i.d.Nähe) ** finden viele gut, aber keiner macht was ** Alternativvorschlag: beim CCC-HH aufspringen, die brauchen Leute, die mitmachen * evtl. Einführender Elektronikkurs (Peter macht sich Gedanken dazu) ** Siehe Projektstatus ** kein Update * sobald Kücheninsel fertig ist, will Daniel einen Pizza-Kurs machen (Ab September) ** kein Update * Wiederholen bereits gehaltener Workshops? ** kein Update * Verteilung laut Nemo: Ab jetzt jeden Monat einen! * Dinge entfernen: ** Der Laser ist weg ** Die Fräse (welche) soll aus der Metallwerkstatt. Wollen die Abnehmer das denn haben? Klärung sollte erfolgen, Ergebnis unklar. Wenn der andere Verein dass nicht will, gibt es wohl Abnehmer, die bezahlen wollen. ** Eric fragt bei Nemo nach == Top 5: Anträge und Verschiedenes == * Linkshänderscheren: Der Konvent entscheidet durch Abstimmung, über die allgemeine Idee, Linkshänderscheren zu beschaffen: 12 dafür, Dagegen: 0, Enthaltungen: 0 – Details werde noch geklärt. === Erklärung zur Funktion der Konvenanträge === (dieser gesamte Punkt ist unverändert aus dem Vorprotokoll übernommen, da er für die Zukunft wohl noch Relevanz hat) * Anträge und die Abstimmungsergebnisse dienen als Empfehlung an den Vorstand * Es sollte klar zwischen Anträgen und anderen allgemeinen Konsensentscheidungen stattfinden * In der MV sollten nur Anträge landen, für die der Vorstand die Zustimmung der MV braucht * Hier werden Dinge die kategorisiert * Freiwild * Verkaeufe * Spenden * Muell Bilder gemacht Am naechsten Konvent gesichtet, ein Aufraeumtermin final festgelegt und die Liste zur Sichtung Online (Signal + Matrix) geposted (https://trilium.apps.attraktor.org/share/AttraktorSpaceDinge) vorlaeufiger Entsorgungstermin (25.04.2026) 2. Entscheiden, was aktiv genutzt wird und bleiben soll (Termin 2 beim nächsten Konvent) 3. Benötigte Gegenstände platzsparender organisieren (z.B. Foto-Ausrüstung kompakter im Regal verstauen, ähnliche Dinge zusammenlegen) 4. Nicht mehr benötigte Gegenstände zum Spenden, Verkaufen oder Entsorgen vorbereiten - Wichtig:** Um zu verhindern, dass gute Absichten im Alltag untergehen, schlage ich vor, dass wir **direkt am Aufräum-Tag** auch die nächsten Schritte umsetzen: - Spendenfähige Gegenstände werden noch am selben Tag zu einer Annahmestelle gebracht - Verkäufliches wird sofort fotografiert und online gestellt (oder ein fester Verkaufstermin in der Folgewoche vereinbart) - Entsorgung wird direkt organisiert * Mein Angebot:** Ich kann gerne mit meinem Transporter kommen und Fahrten zum Recyclinghof oder zu Annahmestellen übernehmen.) einstimmig angenommen Grüner Punkt: Teil 1 :Reste davon : Wechsel zu Brauner Punkt Teil 2: Frei für alle, Rest wird entsorgt Teil 3: Frei für alle sonst entsorgt Teil 4: Frei für alles ausser wenn vorhanden POE Switch Teil 5: Verbleibt im Attraktor Teil 6: Verbleibt im Attrator (bei anderen Reinigunsgmittel) Teil 7: Freie Verfügiung sonst Müll Teil 8: Fatima ihrs jetzt Teil 9: In Klärung mit Frank Brauner Punkt: Teil 1: An Tobi(tja) vergeben Teil 2: Sind in Kleinanzeigen inseriert 30.05 Stichtag Teil 3: Frei verfügbar sonst Müll 25.04. Stichtag Teil 4: Müll bis auf den Motor (Eric 25.04.) Teil 5: Aufheben bis 30.05. Teil 6.: Müll Teil 7: Müll Teil 8: 2 Vergeben an Ludwig Rest Müll Teil 9: Müll , Umbaumaterial zurück an Dominic Teil 10: Müll Teil 11: gamnmelisgte Palette weg, Rest bleibt Gelber Punkt: Teil 1 : Verbleiben im Space , Abgabe mit sozialer Komponente bleibt Teil 2: Vorschlag/Plan/Projekt bis 28.05. Konvent20 zur weiteren Verwendung, bei ausbleiben Spende (einstimmig beschlossen auf Konvent19); Mehrheit ist dafür den abzugeben; Antrag: Dirk nimmt den Laser (wird spätestens bis zum 18.06.2026 abgeholt) 10 dafür, keine Enthaltungen, keine Gegenstimmen Teil 3 : Für Projekt (Joachim, Michael, ) Team muss bis 28.05. stehen (Beschlossen) Team: Joachim, Andrea (bis auf die Adapterplatte können die Monitorfüße entsorgt werden) Teil 4: Verbleibt: wird auf Konvent20 verlegt, Angebote (Vereine, Privatmenschen werden angenommen) CNC Fräse Haus3 hat Intresse daran bekundet. Teil 5: Klärung Lucas, Axel möcht ihn haben Teil 6: Müll bis 25.04. Teil 7: Wird für Spende abgegeben (Kleinanzeigen ? Daniel ?): Teil 8: Werden verkauft (Lötworkshops etc.) Teil 9: Verbleibt in Attraktor (Projekte) Bei allen Entscheidungen die es benötigen wurde abgestimmt und jeweils die gemeinsame Entscheidung dokumentiert === Antrag: (Name) === - Begründung: === Verschiedenes === Das ist ein Beispielantrag. Der Konvent möge beschließen ... . Begründung: ... == Ende == Der Konvent endet um xx:xx Uhr.

Geräte im LeineLab

🇩🇪 · Leinelab · joern.e@undisclosed.example.com (joern.e)

Geräte im LeineLab Im und um das LeineLab stehen Geräte, die entweder im direkten Besitz des LeineLab sind oder entsprechend zur Mitnutzung freigegeben sind. Für einige ist der Werkstattzugang nötig. Darüber hinaus gibt es noch diverse Handwerkzeuge, die nicht hier aufgelistet sind.

Bestand:Hac-32-dev.jpg

🇳🇱 · Hackalot · Okabe

Okabe heeft Bestand:Hac-32-dev.jpg geüpload A picture of the hackalot HAC-32-DEV devboard. to adapt esp32 d1 mini's to breadboard Nieuwe pagina == Beschrijving == A picture of the hackalot HAC-32-DEV devboard. to adapt esp32 d1 mini's to breadboard == Licentie == {{CC-by-sa-2.5}}

Cooking up community and creativity

🇺🇸 · AS220 Labs · David Dvorchak

Cooking Crew member Fenelys (front) plates sticky chicken under the supervision of Chef Bean (rear) Running a restaurant isn’t easy. AS220 has offered a variety of food options since the ‘90s, from a cafe counter to a sit-down eatery. In alignment with the values of our youth program, our kitchen also offered entry-level jobs and training to young people. Even in the best of times, it was hard to make the numbers work – but the pandemic and changes to downtown office occupancy and foot traffic were the last straws. After a period of dormancy, we’re now remixing and rethinking what our kitchen can be. The kitchen at AS220 has been cooking at full throttle since July, not as a commercial business, but as an educational space. The Cooking Crew, a group of young people taking part in AS220’s Summer Jobs program, are being introduced to the culinary arts under the watchful eye of Chef Adena "Bean" Marcelino, who has years of professional experience with running restaurants and catering operations. Bean's goal is to teach her students hands-on skills in the kitchen that will serve them for the rest of their lives. "When they go into adulthood, they’ll have a base of knowledge of how to cook affordably, easily, and in a way that they'll actually enjoy the food that they eat." When I stopped by to see what was being whipped up, it was a whirlwind of activity: puff pastries, whipped cream, and sweet potato filling, all made from scratch, for sweet potato hand pies. I had already missed a busy morning session. “They made a sticky chicken sauce from scratch, they learned how to fry chicken wings, how to glaze a sticky chicken sauce, and how to bake chicken to make sticky chicken wings. They also made fried rice using that sauce.” Cooking Crew member Sa’qure enjoys the fruits of her labor If that sounds like a high-pressure production schedule, Cooking Crew member Fenelys says it’s anything but. “I enjoy how creative we can get. Everybody can be themselves in the kitchen, and if somebody messes up, that’s OK. You can just redo it. It’s a work in progress.” Food made with love and care nourishes the soul as well as the body, as AS220 Artistic Director Anjel Newmann explains. “We wanted young people to experience the kitchen as more than a place to prepare meals. We wanted it to become a space where they could express creativity, learn practical skills, collaborate with one another, and care for their community.” Cooking Crew member Fenelys adds the finishing touches to a sweet potato hand pie While downtown offices and workers may not be at pre-COVID numbers, our neighborhood has become home to numerous schools and after-school programs and the hundreds of students who attend them. Despite this, the landscape is not designed to accommodate these young people once the bell rings. Newmann hopes to change that. “My hope is that AS220’s kitchen becomes the foundation for a youth-centered café that is designed for and operated by young people, and rooted in creativity, hospitality, and community. A place where students can stop after school to grab an affordable meal or drink, charge their phones, work on homework, read a book, meet friends, or simply spend time in a space where they feel welcomed and valued. This summer’s Cooking Crew is the first step toward that larger vision.” Cooking Crew member Nariah is pleased with her homemade sweet potato hand pie

Leer tools

🇳🇱 · Bitlair · Polyfloyd

← Oudere versie Versie van 6 aug 2026 19:55 (2 tussenliggende versies door dezelfde gebruiker niet weergegeven) Regel 7: Regel 7: }} }} Gereedschap voor het bewerken van leer. Gereedschap voor het bewerken van leer. Je vindt het naast de naaimachines, in de metaalkast [[ Bestand:List of tools.jpg| links|geen|alt= List of tools ]] Je vindt het naast de naaimachines, in de metaalkast [[ Bestand:Outside.jpg| links|geen|alt= Outside of case ]] <gallery> Bestand:List of tools.jpg|List of tools Bestand:Outside.jpg|Outside of case </gallery>

Space2.0

🇳🇱 · Bitlair · Polyfloyd

Foto's ← Oudere versie Versie van 6 aug 2026 18:04 Regel 47: Regel 47: File:Space2_20170920_162648.jpg File:Space2_20170920_162648.jpg File:ArianeMax.png|[[User:Maeddoc]] aan het klussen File:ArianeMax.png|[[User:Maeddoc]] aan het klussen File:Space2_20161003_193904.jpg|[[Projects/$andere ruimte]] </gallery> </gallery> == Zie ook == == Zie ook == * [[Lijst van Spaces]] * [[Lijst van Spaces]]

Space2.0

🇳🇱 · Bitlair · Polyfloyd

← Oudere versie Versie van 6 aug 2026 17:56 Regel 2: Regel 2: |info=Ariane 24, Amersfoort |info=Ariane 24, Amersfoort |start=2016-10-11 |start=2016-10-11 |contact=Hobbybob, AK, Vuurtorenjeroen, mro, eightdot, Maeddoc |contact=Hobbybob, AK, Vuurtorenjeroen, mro, eightdot, Maeddoc , Polyfloyd |status=Abandoned |status=Abandoned |Picture=MadRGB-4.jpg |Picture=MadRGB-4.jpg

Events/2024-04-28 Huurders space 4 meeting

🇳🇱 · Bitlair · Polyfloyd

← Oudere versie Versie van 6 aug 2026 17:43 Regel 3: Regel 3: |start=2024/04/29 19:30:00 |start=2024/04/29 19:30:00 |end=2024/04/29 22:00:00 |end=2024/04/29 22:00:00 |location= Bitlair |location= Space4.0 }} }} Meeting met alle huurders van space 4 om te bespreken wat er gedaan moet worden. Hoofdruimte is niet beschikbaar. Meeting met alle huurders van space 4 om te bespreken wat er gedaan moet worden. Hoofdruimte is niet beschikbaar.

Events/2016-07-03 Metameet 0x6

🇳🇱 · Bitlair · Polyfloyd

← Oudere versie Versie van 6 aug 2026 17:42 Regel 4: Regel 4: |start=2016/07/03 20:00:00 |start=2016/07/03 20:00:00 |end=2016/07/03 20:10:00 |end=2016/07/03 20:10:00 |location= Bitlair |location= Space1.0 }} }}

Events/2016-05-08 MetaMeet 0x2

🇳🇱 · Bitlair · Polyfloyd

← Oudere versie Versie van 6 aug 2026 17:41 Regel 4: Regel 4: |start=2016/05/05 08:00:00 PM |start=2016/05/05 08:00:00 PM |end=2016/05/05 08:30:00 PM |end=2016/05/05 08:30:00 PM |location= Bitlair |location= Space1.0 }} }} Wie notuleert? Wie notuleert?

Events/2015-11-14 Movienight

🇳🇱 · Bitlair · Polyfloyd

← Oudere versie Versie van 6 aug 2026 17:40 Regel 4: Regel 4: |start=2015/11/14 08:00:00 PM |start=2015/11/14 08:00:00 PM |end=2015/11/15 02:00:00 AM |end=2015/11/15 02:00:00 AM |location= Bitlair |location= Space1.0 }} }} Movienight november 2015 Movienight november 2015

Events/2014-05-10 LAOS meeting

🇳🇱 · Bitlair · Polyfloyd

← Oudere versie Versie van 6 aug 2026 17:40 Regel 4: Regel 4: |start=2014/05/10 02:00:00 PM |start=2014/05/10 02:00:00 PM |end=2014/05/10 08:00:00 PM |end=2014/05/10 08:00:00 PM |location= Bitlair |location= Space1.0 |info=http://redmine.laoslaser.org/boards/1/topics/619 |info=http://redmine.laoslaser.org/boards/1/topics/619 }} }} Check here for details: http://redmine.laoslaser.org/boards/1/topics/619 Check here for details: http://redmine.laoslaser.org/boards/1/topics/619

Events/2013-06-09 BBQ

🇳🇱 · Bitlair · Polyfloyd

← Oudere versie Versie van 6 aug 2026 17:39 Regel 4: Regel 4: |start=2013/06/09 04:00:00 PM |start=2013/06/09 04:00:00 PM |end=2013/06/09 10:00:00 PM |end=2013/06/09 10:00:00 PM |location= Bitlair |location= Space1.0 }} }} Bring your own Meat BBQ!! Bring your own Meat BBQ!!

Events/2013-05-01 Noiseless vault vergadering

🇳🇱 · Bitlair · Polyfloyd

← Oudere versie Versie van 6 aug 2026 17:38 Regel 4: Regel 4: |start=2013/05/01 08:00:00 PM |start=2013/05/01 08:00:00 PM |end=2013/05/01 10:00:00 PM |end=2013/05/01 10:00:00 PM |location= Bitlair |location= Space1.0 }} }}

Events/2013-04-24 LOC-Meeting

🇳🇱 · Bitlair · Polyfloyd

← Oudere versie Versie van 6 aug 2026 17:37 Regel 3: Regel 3: |start=2013-04-24T20:00:00.000Z |start=2013-04-24T20:00:00.000Z |end=2013-04-24T22:00:00.000Z |end=2013-04-24T22:00:00.000Z |location= Bitlair |location= Space1.0 |status=Confirmed |status=Confirmed |date=2013/04/24 |date=2013/04/24 }} }} Meeting van OHM2013 LOC Meeting van OHM2013 LOC

Events/2019-09-29 Metameet 0x2B

🇳🇱 · Bitlair · Polyfloyd

Tekst vervangen - "Computerweg 20a, Amersfoort" door "Space3.0" ← Oudere versie Versie van 6 aug 2026 17:36 Regel 4: Regel 4: |start=2019/09/29 20:00:00 |start=2019/09/29 20:00:00 |end=2019/09/29 20:30:00 |end=2019/09/29 20:30:00 |location= Computerweg 20a, Amersfoort |location= Space3.0 }} }} Notulen: [https://member.bitlair.nl/Pages/2019-09-29_Metameet_0x2B] Notulen: [https://member.bitlair.nl/Pages/2019-09-29_Metameet_0x2B]

Events/2018-06-03 Metameet 0x21

🇳🇱 · Bitlair · Polyfloyd

Tekst vervangen - "Computerweg 20a, Amersfoort" door "Space3.0" ← Oudere versie Versie van 6 aug 2026 17:36 Regel 4: Regel 4: |start=2018/06/03 20:00:00 |start=2018/06/03 20:00:00 |end=2018/06/03 20:30:00 |end=2018/06/03 20:30:00 |location= Computerweg 20a, Amersfoort |location= Space3.0 }} }} Notulen: [https://member.bitlair.nl/Pages/2018-06-03_Metameet_0x21] Notulen: [https://member.bitlair.nl/Pages/2018-06-03_Metameet_0x21]

Events/2019-11-03 Metameet 0x2C

🇳🇱 · Bitlair · Polyfloyd

Tekst vervangen - "Computerweg 20a, Amersfoort" door "Space3.0" ← Oudere versie Versie van 6 aug 2026 17:36 Regel 4: Regel 4: |start=2019/11/03 20:00:00 |start=2019/11/03 20:00:00 |end=2019/11/03 20:30:00 |end=2019/11/03 20:30:00 |location= Computerweg 20a, Amersfoort |location= Space3.0 }} }} Notulen: [https://member.bitlair.nl/Pages/2019-11-03_Metameet_0x2C] Notulen: [https://member.bitlair.nl/Pages/2019-11-03_Metameet_0x2C]

Events/2018-11-25 Metameet 0x25

🇳🇱 · Bitlair · Polyfloyd

Tekst vervangen - "Computerweg 20a, Amersfoort" door "Space3.0" ← Oudere versie Versie van 6 aug 2026 17:36 Regel 4: Regel 4: |start=2018/11/25 20:00:00 |start=2018/11/25 20:00:00 |end=2018/11/25 20:30:00 |end=2018/11/25 20:30:00 |location= Computerweg 20a, Amersfoort |location= Space3.0 }} }} Notulen: [https://member.bitlair.nl/Pages/2018-11-25_Metameet_0x25] Notulen: [https://member.bitlair.nl/Pages/2018-11-25_Metameet_0x25]

Klipper op Ultimaker Project

🇳🇱 · MakerSpaceLeiden · LucasV

Hoe ← Oudere versie Versie van 6 aug 2026 18:59 Regel 27: Regel 27: * SSH toegang to Pi regelen (Public key(s) in .ssh / Pi op MakerSpace netwerk of even met kabeltje naar laptop). - DONE * SSH toegang to Pi regelen (Public key(s) in .ssh / Pi op MakerSpace netwerk of even met kabeltje naar laptop). - DONE * Klipper firmware in UM flashen - DONE * Klipper firmware in UM flashen - DONE * configuratiefile op Raspi (Op basis van standaard config UM, de UM van de MakerSpace configureren) - In progress * configuratiefile op Raspi (Op basis van standaard config UM, de UM van de MakerSpace configureren) - DONE * configuratie testen en zo nodig aanpassen en hertesten en aanpassen etc. - In progress * configuratie testen en zo nodig aanpassen en hertesten en aanpassen etc. - In progress * Uitzoeken hoe snel de extruder maximaal kan extruden en wat dus de maximale snelheden worden - "left as an excersise to the reader" - 120mm/s met PLA gaat goed. * Uitzoeken hoe snel de extruder maximaal kan extruden en wat dus de maximale snelheden worden - "left as an excersise to the reader" - 120mm/s met PLA gaat goed. * Slicer instellen (Prusaslicer, Slic3r, of Orcaslicer oid), net ónder de maximale snelheden. (Waarschijnlijk verschillen die per filament... Dus alleen even voor PLA en PETG en aan de veilige kant gaan zitten zodat het tenminste werkt) -- in progress * Slicer instellen (Prusaslicer, Slic3r, of Orcaslicer oid), net ónder de maximale snelheden. (Waarschijnlijk verschillen die per filament... Dus alleen even voor PLA en PETG en aan de veilige kant gaan zitten zodat het tenminste werkt) -- in progress * Test printjes, ten behoeve van Presure Advance en Input Shaping (PA moet eigenlijk voor elk filament, maar iig voor die ene waarmee we input shaping instellen) -- In progress * Test printjes, ten behoeve van Presure Advance en Input Shaping (PA moet eigenlijk voor elk filament, maar iig voor die ene waarmee we input shaping instellen) -- In progress * [[Ultimaker_2_Klipper_3D_Printer|Wikipage]] (Met wat uitleg over het gebruik en een bestandje met de slicer instellingen) -- started/placeholder * [[Ultimaker_2_Klipper_3D_Printer|Wikipage]] (Met wat uitleg over het gebruik en een bestandje met de slicer instellingen) -- DONE = Wat niet = = Wat niet =

Makerspace Leiden

🇳🇱 · MakerSpaceLeiden · MarkKlaauw

Verwijst door naar MakerSpace Leiden ← Oudere versie Versie van 6 aug 2026 08:46 Regel 1: Regel 1: #DOORVERWIJZING [[MakerSpace Leiden]]

MakerSpace Leiden:Makerspace Leiden

🇳🇱 · MakerSpaceLeiden · MarkKlaauw

MarkKlaauw heeft de pagina MakerSpace Leiden:Makerspace Leiden verwijderd De inhoud was: " Category:Organization __TOC__<big>'''Hallo en welkom op de wiki van MakerSpace Leiden!'''</big> Deze wiki wordt door de deelnemers van de MakerSpace onderhouden. Schroom niet om zelf wat toe te voegen, de wiki is een gedeelde bron waar ook jij aan mee kunt helpen. * Ook deelnemer worden? Kijk dan op de [https://wiki.makerspaceleiden.nl/mediawiki/index.php/Participate#Ik_overweeg_deelnemer_te_worden. deze pagina]. * Ben je nieuw lid en wil je aan de slag op de Space? De…"

MediaWiki:Common.css

🇳🇱 · MakerSpaceLeiden · MarkKlaauw

← Oudere versie Versie van 6 aug 2026 08:20 (2 tussenliggende versies door dezelfde gebruiker niet weergegeven) Regel 122: Regel 122: @media screen { @media screen { a:not(.new) { #content a:not(.new) :visited, #siteNotice a:not(.new):visited { color: #36C; color: #36C; } } } a:not( . new):visited { @media screen { color : #36C ; . mw-body-content { line-height : 1.625 ; } } } }

MediaWiki:Sidebar

🇳🇱 · MakerSpaceLeiden · MarkKlaauw

← Oudere versie Versie van 6 aug 2026 07:09 Regel 4: Regel 4: ** Participate|Participate ** Participate|Participate ** Category:Procedures|How we operate ** Category:Procedures|How we operate ** https://mijn.makerspaceleiden.nl |Intranet ** Intranet |Intranet ** Contact|Contact ** Contact|Contact

MediaWiki:Common.css

🇳🇱 · MakerSpaceLeiden · MarkKlaauw

← Oudere versie Versie van 6 aug 2026 06:56 (11 tussenliggende versies door dezelfde gebruiker niet weergegeven) Regel 87: Regel 87: :root { :root { -- medik : #D62410 !important; -- bs-font-sans-serif : sans-serif !important; --bs-body-font-family: var(--bs-font-sans-serif); } body { font-family: var(--bs-body-font-family) !important; } body, .mw-body, .mw-parser-output { font-family: var(--bs-body-font-family) !important; } } Regel 109: Regel 121: .mw-wiki-logo { .mw-wiki-logo { height: 1. 8em !important; height: 1. 7em !important; } } Regel 123: Regel 135: position: absolute; position: absolute; right: 0; right: 0; width: 15 %; width: 12 %; } }

Category:Konvent

🇩🇪 · Attraktor · DCtoDaylight

Added Konvent 09.07.2026 ← Older revision Revision as of 18:51, 6 August 2026 Line 18: Line 18: === 2026 === === 2026 === * [[Konvent/09.07.2026|09.07.2026]] * [[Konvent/04.06.2026|04.06.2026]] (für Mai; versch. f. Fernsehdreh) * [[Konvent/04.06.2026|04.06.2026]] (für Mai; versch. f. Fernsehdreh) * [[Konvent/23.04.2026|23.04.2026]] * [[Konvent/23.04.2026|23.04.2026]]

Equipment - +multimetry

🇨🇿 · Brmlab · fyzikar (fyzikar@undisclosed.example.com)

1786050860 current Line 20: Line 20:   |{{:equipment:osciloscope.jpg?100}} |[[:equipment:osciloscope|Osciloscope Tektronix TDS 2002]] |  |   |{{:equipment:osciloscope.jpg?100}} |[[:equipment:osciloscope|Osciloscope Tektronix TDS 2002]] |  |   |  |Laboratorní váha torzní |přesnost 0.1 mg, max. zátěž 50 mg |   |  |Laboratorní váha torzní |přesnost 0.1 mg, max. zátěž 50 mg |   +   + ==== Multimeters ====   +   + Just click to see the detail (and specific model). Spare batteries are always provided.\\   + {{:equipment:img_20260807_003847.jpg?direct&100|}}   + {{:equipment:img_20260807_003851.jpg?direct&100|}}   + {{:equipment:img_20260807_003927.jpg?direct&100|}}   + {{:equipment:img_20260807_003931.jpg?direct&100|}}   + {{:equipment:img_20260807_003934.jpg?direct&100|}}       ==== Grafické karty / Graphics Cards ====   ==== Grafické karty / Graphics Cards ====

Usuário:Gwiethaus/KiCad/Reparando Cabeçalho de Arquivo

🇧🇷 · Garoa Hacker Clube · Gwiethaus

Reparando Cabeçalho de Arquivo do Kicad de Versões Diferentes ← Edição anterior Edição das 17h02min de 6 de agosto de 2026 (2 revisões intermediárias pelo mesmo usuário não estão sendo mostradas) Linha 1: Linha 1: Última Atualização: '''2026- 06 - 26 ''' Última Atualização: '''2026- 08 - 06 ''' =Reparando Cabeçalho de Arquivo do Kicad de Versões Diferentes= =Reparando Cabeçalho de Arquivo do Kicad de Versões Diferentes= <br> <div style="text-align: justify;"> Quando baixamos alguns fontes do Kicad projetos esquemáticos ou de PCB vindo de alguns sites podemos nos deparar com alguns erros seja devido ao erro na geração dos arquivos de projeto e esquemático ou devido a própria versão muito diferente do Kicad para ma mais atual. Resolvi investigar os problemas que estavam ocorrendo do não reconhecimento do arquivo e encontrei uma forma de rapidamente corrigir esse erro de versão no KiCad da versão 9.0 para 10.x que era a última versão que eu estava utilizando. Quando baixamos alguns fontes do Kicad projetos esquemáticos ou de PCB vindo de alguns sites podemos nos deparar com alguns erros seja devido ao erro na geração dos arquivos de projeto e esquemático ou devido a própria versão muito diferente do Kicad para ma mais atual. Resolvi investigar os problemas que estavam ocorrendo do não reconhecimento do arquivo e encontrei uma forma de rapidamente corrigir esse erro de versão no KiCad da versão 9.0 para 10.x que era a última versão que eu estava utilizando. Linha 57: Linha 61: .... .... </pre> </pre> Perceba que alem do '''comment''' duplicados o bloco "'''title_block'''" não estava presente. </div>