first

dev.sh

@@ -0,0 +1,7 @@
+docker run --rm \
+    -v $(pwd)/docs/slides:/reveal/docs/slides \
+    -v $(pwd)/scripts/test:/resources \
+    -v $(pwd)/images:/reveal/images \
+    -e TITLE='my Title' -e THEME_CSS='cloudogu-black.css' \
+    -p 8000:8000 -p 35729:35729 \
+    cloudogu/reveal.js:dev

docs/slides/00-title.md

@@ -0,0 +1,20 @@
+<!-- .slide: style=" text-align: center !important;"  -->
+
+<br/>
+
+<h2 class="title">
+    <span class="title-accent">//</span> 
+    Open Hardware
+</h2>
+<br/>
+
+**Joao Figueiredo**
+
+LCD Porto
+
+<BR />
+
+<div class="title-version">
+Abril 2025, Porto Innovation Hub
+<!--VERSION-->
+</div>

docs/slides/01-intro.md

@@ -0,0 +1,11 @@
+<!-- .slide: style=" text-align: center !important;"  -->
+
+## Me, me, me!
+
+# Joao figueiredo
+
+Father of three, cat porter, dog walker, ops tech manager and infinitely curious, mainly for programming, web technologies and electronics.
+
+### Coordenator @ LCD Porto
+
+Operational Technology Manager @ Mota-Engil

docs/slides/03-what-is.md

@@ -0,0 +1,44 @@
+### WTF is Open Hardware
+
+
+> Open-source hardware (OSH, OSHW) consists of physical artifacts of technology designed and offered by the open-design movement. Both free and open-source software (FOSS) and open-source hardware are created by this open-source culture movement and apply a like concept to a variety of components. It is sometimes, thus, referred to as free and open-source hardware (FOSH)
+
+Wikipedia
+
+--
+
+### WTF is Open Hardware
+
+> Open hardware (often called open-source hardware) is physical technology whose complete design files—such as schematics, PCB layouts, mechanical drawings, firmware, and bills of materials—are released to the public in a modifiable, accessible format under an open license. This lets *anyone* freely study, build, modify, distribute, and even sell the hardware (or derivatives) so long as they preserve the same openness in the resulting works.
+
+[ChatGPT o3](https://chatgpt.com/share/680a34fe-ddf8-800a-952d-bc4e23e981f4)
+
+--
+
+### WTF is Open Hardware / Examples
+
+# Arduino 
+
+<img width="30%" data-src="/images/03-what-is/arduino-uno-board-tutorial-beginners2-800x618.jpg">
+
+Launched in 2010 and still OSHWA-certified, every rev of the Uno ships with complete CAD schematics, PCB Gerbers, bill-of-materials and firmware under CC-BY-SA/GPL licences. Thousands of compatibles exist precisely because anyone can legally build, modify and sell their own versions.
+
+--
+
+### WTF is Open Hardware / Examples
+
+# BeagleBone Black – single-board Linux computer 
+
+<img width="30%" data-src="/images/03-what-is/DSC00505-scaled.webp">
+
+An ARM-based board aimed at industrial and maker use. Its reference design (Altium + KiCad files, PRU firmware, cape interface specs) is published by the BeagleBoard.org Foundation under CC-BY-SA, allowing third parties to clone or extend the hardware (e.g., industrial “Black Industrial” editions).
+
+--
+
+### WTF is Open Hardware / Examples
+
+# Cyton Biosensing Board
+
+<img width="30%" data-src="/images/03-what-is/openbci.png">
+
+Created after a 2013 Kickstarter, the Cyton board and its 3-D-printed Ultracortex headset target research‐grade brain-computer-interface work. Texas-Instruments ADS1299 analog front-end, KiCad files, enclosure STLs and all firmware are released under CERN-OHL v2 and GPL licences, enabling labs and hackerspaces to build or customize low-cost neuro-tech.

docs/slides/05-why.md

@@ -0,0 +1,150 @@
+## Open Hardware
+
+# Why?
+
+--
+
+### Why?
+
+# Because
+
+* John Deere
+* Apple
+* Tesla
+* HP 
+* ...
+
+--
+
+### Why?
+
+## John Deere
+
+* Digital keys (“Service ADVISOR,” encrypted ECU files) sold only to franchised dealers.
+* Contract language banning owners from “accessing source code.”
+
+
+
+--
+
+### Why?
+
+## John Deere / issues
+
+* Downtime: farmers can’t harvest until a dealer drives out.
+* Monopoly pricing: FTC says labor rates run 2–3 × higher than independent techs could charge.
+* Legal chill: Deere-farm-bureau MoU bars the farm lobby from pursuing right-to-repair bills.
+
+Note:
+
+* Farmer with lawn $600k ornament 
+* Ukranian hackerss
+* [Source](https://www.agriculturedive.com/news/deere-right-to-repair-ftc-investigation/730432/)
+
+--
+
+### Why?
+
+## Apple
+
+* Parts pairing”: replacement cameras, batteries, even screens must handshake with Apple’s servers or functions are degraded.
+* Activation Lock is now extended to individual parts.
+
+--
+
+### Why?
+
+## Apple / issues
+
+* Independent shops sidelined: Face ID, Touch ID, True Tone and other features break if Apple refuses calibration.
+* Higher e-waste: perfectly-good donor parts are unusable.
+
+## Nice side/effect
+
+* Regulatory friction: Oregon’s 2025 law outright bans parts-pairing—forcing Apple to dial it back.
+
+--
+
+### Why?
+
+## Tesla
+
+* Only Tesla will sell many critical parts; service manuals sit behind paywalls; software locks block salvaged modules.
+* Warranty language voids coverage after most third-party repairs.
+
+--
+
+### Why?
+
+## Tesla & issues
+
+* Supracompetitive pricing: class action alleges owners pay far above market for simple repairs.
+* Service deserts: where no Tesla center exists, cars can sit immobile for weeks.
+* Data monopoly: Tesla harvests telematics but withholds diagnostic data from independents and costomers. 
+
+Note:
+
+* Would like to dig deeper into Tesla's compliance with EU regulations 
+
+--
+
+### Why?
+
+## HP
+
+* “Dynamic Security” firmware silently disables printers if a cartridge lacks an HP-signed chip.
+
+
+--
+
+### Why?
+
+## HP / issues
+
+* Instant bricking: firmware pushes have frozen printers mid-emergency jobs (one plaintiff was a disaster-response charity).
+* Consumable monopoly: users must pay HP’s 60-80 % markup on toner/ink.
+* Legal exposure: HP settled a March 2025 class action but pays no damages, and the lockout code remains on by default. 
+
+Note:
+
+* Other printers brands, namey, OKI have similar baheviours 
+
+--
+
+### Why?
+
+# And many many more
+
+1. Repair monopoly → price & time penalties
+1. Regulatory & security opacity
+1. E-waste acceleration
+1. Chilling effect on competition and innovation
+
+Note:
+
+1. Repair monopoly → price & time penalties
+
+   When diagnostic software, cryptographic keys or parts supplies are closed, the manufacturer alone sets both the repair timetable and the price. Markets for independent service collapse.
+
+1. Regulatory & security opacity
+
+   Closed devices often hide firmware vulnerabilities and safety issues from third-party auditors, while still claiming “security” as the reason for secrecy.
+
+1. E-waste acceleration
+
+   Parts pairing and locked firmware make reuse and refurbishment uneconomical. Functional components head to recycling, and owners buy new hardware instead.
+
+1. Chilling effect on competition and innovation
+
+   Start-ups that could build accessories, do performance mods, or offer analytics can’t legally access the interfaces. That concentrates revenue with the OEM and slows downstream innovation.
+
+--
+
+### Why?
+
+It's not only about competitions between suppliers,<br>
+**it's mainly about equity in access to technology.**
+
+Note:
+
+If companies priotize for maximum proffit lower income persons will never have similar access.

docs/slides/06-mixed-realities.md

@@ -0,0 +1,154 @@
+### Open Hardware
+
+# Mixed realities 
+
+**When “your” hardware lives—and dies—in the vendor’s cloud**
+
+--
+
+### # Mixed realities 
+
+Modern IoT gear often won’t store data locally or accept direct connections.
+The cloud account *is* the product. That design brings two systemic risks:
+
+* Data hostage-taking
+* Single point of failure	
+
+
+Note:
+
+* Data hostage-taking
+   * Telemetry, user settings, even basic on-device functions sit behind the vendor’s login. If the account, API or certificate vanishes, owners lose historical data and live control
+
+* Single point of failure	
+   * When the provider turns the servers off (bankruptcy, acquisition, strategy shift), the device can’t boot, phone home for crypto keys, or accept commands—so otherwise-healthy hardware becomes e-waste overnight.
+
+--
+
+### Mixed realities 
+
+##  A big graveyard 
+
+* 2023 *Amazon Halo* fitness bands & bedside sleep tracker
+* 2024 *Google Nest* Secure home-alarm system
+* 2022 *Insteon smart-lighting hubs*
+* 2018 *Logitech Harmony Link* universal remote puck
+* 2016 *Revolv smart-home hub* (acquired by Google Nest)
+
+Note:
+
+* 2023 *Amazon Halo* fitness bands & bedside sleep tracker
+	* All bands and the Halo app stopped working.
+   * Health data deleted after deadline unless manually exported.
+   * Amazon suggested recycling the still-working hardware.	
+* 2024 *Google Nest* Secure home-alarm system
+   * No arming/disarming, no phone alerts, no lock bridge.
+   * Google offered an ADT kit or €200 voucher; data and automations vanished.	
+* 2022 *Insteon smart-lighting hubs*
+   * Cloud switch went dark without warning; apps & some wall keypads dead.
+   * Users had to reverse-engineer local control or replace entire setups.	
+* 2018 *Logitech Harmony Link* universal remote puck
+   * Logitech email: “device will no longer function.”
+   * Initial plan was no replacement; backlash forced the firm to swap in a newer model—proof the brick was purely a licensing choice.	
+* 2016 *Revolv smart-home hub* (acquired by Google Nest)
+   * $300 hub and app permanently bricked.
+   * Case became the textbook example of a company “reaching into your home and pulling the plug.”
+
+--
+
+### Mixed realities 
+
+## Moxie
+
+<img width="70%" data-src="/images/06-mixed-realities/sad_moxie.png">
+
+--
+
+### Mixed realities 
+
+## Moxie / 2020-2025
+
+<img width="10%"  data-src="/images/06-mixed-realities/sad_moxie.png"> 
+
+Moxie, an expressive table-top robot marketed as a social-skills “mentor” for children. Intro price: US $1,500, later cut to $800. All speech recognition, personality data and progress tracking live on Embodied’s servers.
+
+Nov 2024 – shutdown e-mail
+
+Early 2025 – service blackout	
+
+Note: 
+
+* 2020 – launch
+* Nov 2024 – shutdown e-mail
+   * funding round collapsed, the company will “wind down operations” and shut off the Moxie cloud “soon.” A link to a “farewell letter” helps parents explain to kids that their robot friend is “going away.” 
+* Early 2025 – service blackout	
+   * Cloud endpoints time out; Moxie units stall on startup or report server-error codes. Amazon and other retailers pull remaining stock.
+
+--
+
+### Mixed realities 
+
+## Moxie / Why it failed
+
+* Total cloud dependence
+* No escrow / open-sourcing plan 
+* High ongoing costs 
+
+Note:
+
+* Total cloud dependence – every wake-word, behavioral script and user log resided off-device.
+* No escrow / open-sourcing plan – when funding vanished there was no legal path to keep servers or firmware alive.
+* High ongoing costs – speech-to-text, emotion analysis and safety moderation are compute-heavy; with only ~15 k units sold (est.), subscription revenue never covered the bills.
+
+--
+
+### Mixed realities 
+
+## Moxie / Lessons highlighted
+
+* “Smart” toys must offer local-first operation or a published contingency (open-source firmware, community server code) to avoid instant obsolescence.
+* Regulators are beginning to act
+* Consumer awereness
+
+Note:
+
+* “Smart” toys must offer local-first operation or a published contingency
+   * (open-source firmware, community server code) to avoid instant obsolescence.
+* Regulators are beginning to act
+   * forthcoming EU Ecodesign and US state “Connected Devices” rules would obligate a guaranteed service period or mandatory refunds for cloud-tethered products. Moxie shows why such safeguards matter.
+* Consumer awereness
+   * Buyers should treat cloud-bound hardware like a subscription, not a durable good—unless the vendor can prove the device remains useful offline.
+
+--
+
+### Mixed realities 
+
+## Broader implications
+
+* Security & privacy
+* Cost shifting to consumers
+* Regulatory spotlight
+* Design takeaway
+
+Note:
+
+* Security & privacy
+   * Continuous cloud dependence gives the vendor perpetual access to raw sensor streams (sleep patterns, door-open events, health scans) with no on-prem option. A shutdown can wipe user archives or expose unmaintained endpoints to attack.
+
+* Cost shifting to consumers
+   * Owners pay twice: once for the device, again through mandatory subscriptions or forced upgrades when support ends.
+
+* Regulatory spotlight
+   * The EU’s proposed Right-to-Repair and Product Sustainability regulations would require a “minimum service period” and clearer data-export paths; several US states already obligate notice and refunds when a cloud shutdown bricks hardware.
+
+* Design takeaway
+   * Devices that can operate locally (local API, LAN fallback, open firmware) not only respect user autonomy but also outlive corporate pivots.
+   * Home asistant!!
+
+--
+
+### Mixed realities 
+
+* Open data
+* Open protocols
+* Open APIs

docs/slides/07-but.md

@@ -0,0 +1,64 @@
+# But
+
+> "Everything before the word ‘but’ is horseshit”
+> <br>
+> — Jon Snow, *Game of Thrones*
+
+--
+## But
+
+**Hardware is hard**, especially consumer hardware
+
+even to established companies
+
+--
+
+### But
+
+# most commertial Open Hardware projects 
+# Fail
+
+--
+
+### But
+
+Some reasons 
+
+1. High fixed costs but low, eroding margins
+1. Easy cloning
+1. Value-capture gap: few recurring-revenue hooks
+
+Note:
+
+1. High fixed costs but low, eroding margins
+    * Tooling, certification and inventory tie up large capital, yet the designs can be copied the moment they ship, crushing gross margin before volume rescues unit cost.
+    * Investors shun hardware because “it’s expensive, has lower margins than software, and production and iteration cycles take longer.” Inc.com  Open-hardware makers who price chiefly on “being cheaper” enter a “race to the bottom” that ignores real development costs. Aquiles Carattino Open Notes
+1. Easy cloning
+    * price competition and brand confusion     
+    * Open CAD files let factories or rivals release near-identical boards within weeks. The original vendor must drop prices or watch sales disappear, while still paying for R&D.
+    * Espruino’s creator has to mark up boards to fund software; $2 knock-offs pre-flashed with his firmware undercut him and still ask him for support. WIRED
+1. Value-capture gap: few recurring-revenue hooks
+    * Unlike OSS, support or cloud-service add-ons for physical devices are harder to bolt on and customers expect the files for free. Many firms never replace one-off sales with a service, subscription or consumable.
+    * Tile’s CEO notes that without “razor-blade” or network-effect revenue, hardware startups struggle to interest VCs. Inc.com
+
+--
+
+### But
+
+more reasons 
+
+1. Verification, compliance and liability are still your problem
+1. Support load scales faster than revenue
+1. Misaligned funding timelines
+
+Note:
+
+1. Verification, compliance and liability are still your problem
+    * Open IP does not waive EMC, safety, CE/FCC, or chip-level verification; those costs recur for every design spin and each derivative you release. Underestimating them kills cash flow.
+    * “Nothing is free—the true cost of RISC-V includes verifying any changes made to the design… effort that is incredibly easy to underestimate.” Semiconductor Engineering
+1. Support load scales faster than revenue
+    * Users of cheap clones (and of your own early prototypes) still email you when things break. The time spent on forums, docs and returns competes directly with engineering the next product.
+    * Clone users with “bad documentation and buggy firmware” generate the biggest support burden for the original vendor, per the Espruino case. WIRED
+1. Misaligned funding timelines
+    * Kickstarter cash or small grants cover first production run but not ongoing iterations, marketing or inventory buffers. When volume demand finally arrives, the firm often lacks working capital to order the next batch.
+    * Academic review of 37 open-hardware firms finds sustainability hinges on continuous cash flow; many stall after initial launch when orders outpace capital. ResearchGate

docs/slides/09-outro.md

@@ -0,0 +1,12 @@
+<!-- .slide: style=" text-align: center !important;"  -->
+
+# Obrigado!
+
+## Joao figueiredo
+
+### Coordenator @ LCD Porto
+
+joaofigueiredo@lcdporto.org
+
+
+Thanks to: **ChatGPY o3**

docs/slides/10-brighter.md

@@ -0,0 +1,97 @@
+## Open hardware
+
+# Brighter 
+
+--
+
+### Brighter 
+* Right-to-repair laws gaining force
+* Repairability & durability labels becoming standard
+* Modular, user-serviceable hardware is thriving
+* Big brands opening up self-service repair
+* Local-first smart-home standards
+* Broader sustainability framework in the EU
+
+Note:
+
+* Right-to-repair laws gaining force
+    * EU Directive on Promoting the Repair of Goods adopted 13 Jun 2024; obliges makers to offer spare parts and repair at “reasonable cost” for at least 10 years after purchase.
+European Commission
+    * California SB 244 (in force 1 Jul 2024) requires parts, tools and diagnostics for electronics and appliances—first US state to cover everything from phones to tractors.
+California Legislative Information
+
+* Repairability & durability labels becoming standard
+    * From 20 Jun 2025 every phone and tablet sold in the EU must carry A–G grades for battery life, durability and repairability, plus a pledge that key spares arrive in ≤10 days.
+
+
+* Modular, user-serviceable hardware is thriving
+    * Framework Laptop 16 ships with socketed CPU/GPU modules, replace-in-minutes keyboard and open parts store.
+    * Fairphone 5 promises 8 years of Android and 10 years of security 
+
+* Big brands opening up self-service repair
+    * Apple Self Service Repair expanded to 33 European countries in 2024 and now covers iPhone, Mac, and Studio Display diagnostics    
+
+* Local-first smart-home standards
+    * Matter 1.3 (Nov 2024) adds energy & water-management clusters while keeping the “works without the internet” rule; Home Assistant earned full Matter certification in Mar 2025. 
+
+* Broader sustainability framework in the EU
+    * The forthcoming Ecodesign for Sustainable Products Regulation (ESPR) will set durability, recyclability and firmware-support minima for nearly all consumer hardware.
+
+--    
+
+### Brighter 
+
+## EU Right-to-repair / timeline
+
+* 2021 - 1st wave "whitegoods" - washing-machines, dish-washers, fridges, displays, servers, vacuum-cleaners
+    * Spare-parts catalogue for 7–10 yrs
+    * 15-day delivery time
+    * Disassembly with basic tools
+* 2021-2027 - Batteries Regulation - All portable devices (phones, tablets, cameras, laptops, earbuds)
+    * Battery must be user-removable with commercially-available tools by Feb 2027
+    * Diagnostic software & instructions must be public
+
+--    
+
+### Brighter 
+
+## EU ight-to-repair / timeline
+
+* 2024 - Right-to-Repair Directive - whitegoods, portable devices
+    * After the 2-year legal-guarantee, the manufacturer must still offer repair “at a reasonable cost” unless impossible
+    * May not obstruct 3rd-party parts
+    * Must publish a European Repair Information Form and join the new EU repair-matching platform
+
+Note: 
+
+* 2024 - Right-to-Repair Directive
+    * Member-states must transpose by 31 Jul 2026; applies the same day
+
+--    
+
+### Brighter 
+
+## EU Right-to-repair / outline
+
+* Minimum repair window
+* No more “parts-pairing” road-blocks
+* European Repair Platform (2026)
+* Transparent labels drive demand-side pressure
+* Batteries come out again
+
+Note:    
+
+* Minimum repair window
+    * Between the 2-year Sales-of-Goods guarantee, the extended 12 months if a consumer chooses repair (Art. 12 R2R), and the Ecodesign spare-parts period, most white goods must now be fixable for 7–10 years, smartphones for 5 years (parts) and batteries for as long as the device is sold plus 5 years.
+
+* No more “parts-pairing” road-blocks
+    * Both the R2R Directive and the smartphone Ecodesign rules ban software practices that prevent using independent parts or disable features after repair.
+
+* European Repair Platform (2026)
+    * Think “EU‐wide Booking.com for fixes”: repairers and refurbishers list services; consumers compare price/time via the mandatory information form.
+
+* Transparent labels drive demand-side pressure
+    * From June 2025 every phone/tablet box in the EU carries the new multi-icon label, letting buyers rank devices on battery endurance and repairability score at a glance.
+
+* Batteries come out again
+    * By 2027 a dead phone battery will once more be a screwdriver job, not a €300 replacement or a new handset.

present.sh

@@ -0,0 +1,7 @@
+docker run --rm \
+    -v $(pwd)/docs/slides:/reveal/docs/slides \
+    -v $(pwd)/scripts/test:/resources \
+    -v $(pwd)/images:/reveal/images \
+    -e TITLE='my Title' -e THEME_CSS='cloudogu-black.css' \
+    -p 8080:8080 \
+    cloudogu/reveal.js

resources/slides.html

@@ -0,0 +1,6 @@
+<section data-markdown="docs/slides/00-title.md"				data-separator-vertical="^\r?\n\r?\n\r?\n"></section>
+<section data-markdown="docs/slides/01-intro.md"				data-separator-vertical="^\r?\n\r?\n\r?\n"></section>
+<section data-markdown="docs/slides/06-network-policies.md" 	data-separator-vertical="^\r?\n\r?\n\r?\n"></section>
+<section data-markdown="docs/slides/07-security-context.md" 	data-separator-vertical="^\r?\n\r?\n\r?\n"></section>
+<section data-markdown="docs/slides/08-pod-security-policy.md"	data-separator-vertical="^\r?\n\r?\n\r?\n"></section>
+<section data-markdown="docs/slides/09-outro.md" 				data-separator-vertical="^\r?\n\r?\n\r?\n"></section>

scripts/test/slides.html

@@ -0,0 +1,13 @@
+<section data-markdown="docs/slides/00-title.md"				data-separator-vertical="^\r?\n\r?\n\r?\n"></section>
+<section data-markdown="docs/slides/01-intro.md"				data-separator-vertical="^\r?\n\r?\n\r?\n"></section>
+<section data-markdown="docs/slides/03-what-is.md"              data-separator-vertical="--"></section>
+
+<section data-markdown="docs/slides/05-why.md"               	data-separator-vertical="--"></section>
+
+<section data-markdown="docs/slides/06-mixed-realities.md"              data-separator-vertical="--"></section>
+
+<section data-markdown="docs/slides/07-but.md"              data-separator-vertical="--"></section>
+
+<section data-markdown="docs/slides/10-brighter.md"              data-separator-vertical="--"></section>
+
+<section data-markdown="docs/slides/09-outro.md" 				data-separator-vertical="^\r?\n\r?\n\r?\n"></section>