Mercurial > whatever / changeset

--- a/content/hp34970a_4.rst	Thu Nov 10 20:55:51 2022 +0100
+++ b/content/hp34970a_4.rst	Thu Nov 10 20:56:16 2022 +0100
@@ -131,9 +131,8 @@
 of the mbed platform, allowing to use threads instead of pure event
 driven code. So I tried to put the copy_to_lcd routine executions in a
 dedicated thread, and bingo, I've got now something that begins to
-work enough to make it usable:
+work enough to make it usable.
 
-.. peertube:: 2be141c0-64ca-446a-ac65-15014604fb37
 
 
 What's next

--- a/content/hp34970a_5.rst	Thu Nov 10 20:55:51 2022 +0100
+++ b/content/hp34970a_5.rst	Thu Nov 10 20:56:16 2022 +0100
@@ -128,7 +128,7 @@
 I also had to use my DSLogic logic analyzer to debug a few things and get to a
 point that make the front panel usable:
 
-.. peertube:: cc6f4327-703f-42f6-8157-03cd0a987387
+.. peertube:: 74b11332-ab1f-459b-8602-2f85c887e506
 
 In this version of the code are many remaining problems, the biggest one being
 the fact the display flickers a lot. In the code of the formware, I have a
@@ -167,7 +167,7 @@
 But in the end, I've now reach a point where the firmware begins to be really
 usable:
 
-.. peertube:: 172bf449-eba7-4429-8840-ab9b2d5398f8
+.. peertube:: 514b7c92-d3e5-49b5-9c2d-46317dd2a3e7
 
 
 

--- a/content/hp34970a_6.rst	Thu Nov 10 20:55:51 2022 +0100
+++ b/content/hp34970a_6.rst	Thu Nov 10 20:56:16 2022 +0100
@@ -145,4 +145,4 @@
    :alt: finished look of the device with the replacement front panel
    :class: image-process-large-photo
 
-.. peertube:: 14d0e7e2-74d5-44fe-90e9-d6b102ae01a1
+.. peertube:: 1b954399-4dd6-46ad-a263-ff8201b5455e

--- a/pelicanconf.py	Thu Nov 10 20:55:51 2022 +0100
+++ b/pelicanconf.py	Thu Nov 10 20:56:16 2022 +0100
@@ -119,4 +119,4 @@
                   },
   }
 
-PEERTUBE_URL = "https://peertube.social"
+PEERTUBE_URL = "https://diode.zone"