updates broken links to images

10 Notes/MixNets - Sphinx YouTube video.md

@@ -43,7 +43,7 @@ Existing Mix format
 	- compact
 	- Computationally cheap
 
-![[Pasted image 20260331141209.png]]
+![[MixNets - Sphinx YouTube video_0.png]]
 
 - r - maximum length of the path (common value 3, 5, 10)
 - s - size of the symmetric key in bytes - how much we choose for s depends on the level of security we want - commonly at that time 80-bit security - 2^80 operations for an attacker to brake the system. Today we prefer to use around 128 bits (16 bytes)
@@ -53,20 +53,20 @@ Some examples:
 
 RSA-like…
 
-![[Pasted image 20260331142627.png]]
+![[MixNets - Sphinx YouTube video_1.png]]
 
 EC:
 
-![[Pasted image 20260331142912.png]]
+![[MixNets - Sphinx YouTube video_2.png]]
 
 Around 100 bytes for 80-bit security.
 
 ### Sphinx message format
 
-![[Pasted image 20260331143337.png]]
+![[MixNets - Sphinx YouTube video_3.png]]
 
-![[Pasted image 20260331144536.png]]
+![[MixNets - Sphinx YouTube video_4.png]]
 
 Now, we could be tempted to use the same alpha for each hop (and different for different message/recipient), but then the message coming into the mix node and one coming out to the mix node could be correlated.
 
-![[Pasted image 20260331145433.png]]
+![[MixNets - Sphinx YouTube video_5.png]]

10 Notes/Privacy-preserving file sharing client in Rust.md

@@ -1 +0,0 @@
-https://hackmd.io/@codex-storage/H1kBvIgMbg

10 Notes/Running functional tests in status-go.md

@@ -80,7 +80,7 @@ docker compose -p "status-go-func-tests-$(git rev-parse --short HEAD)" -f tests-
 
 You will have the following containers running:
 
-![[Pasted image 20250911204521.png]]
+![[Running functional tests in status-go_0.png]]
 
 Now, with everything in place, we can run the tests:
 

10 Notes/Short Introduction to Obsidian.md

@@ -2,7 +2,7 @@ Here a short intro to [Obsidian](https://obsidian.md) and *Personal Knowledge Ma
 
 I currently, document some of the Codex/BitTorrent stuff in the vault you already can use to see how does it feel for you. The vault is available on GitHub: [https://github.com/codex-storage/bittorrent-codex-docs](https://github.com/codex-storage/bittorrent-codex-docs). You can just clone the rero, and open the cloned folder in Obsidian. That's it. This is you local copy - anything you do is only visible to you. GitHub is used for a more controlled syncing. Normally, when you work on your own content, you will put your vault on some shared network drive (end-to-end encrypted of course! :yum:  ), and then you can conveniently open it on any other device. Syncing is done by the network drive, Obsidian has nothing to do with it in this case. You content keeps the same structure (including folders) as you see it in your local (shared) folder - thus, everything is transparent and extremely portable. Myself, I have a paid subscription to Obsidian Sync service (not that I really need it, but I wanted to try it and to support the Obsidian team a bit). It costs me $96,00 per year:
 
-![[Pasted image 20250513024925.png]]
+![[Short Introduction to Obsidian_0.png]]
 
 Obsidian also provides publishing service, which I use for our Codex/BitTorrent documentation and which costs me around $10,- monthly: here you can see how it looks like: [https://publish.obsidian.md/bittorrent](https://publish.obsidian.md/bittorrent). You can also just as easily create an empty vault to play with the settings and plugin. The BitTorrent vault has some basic set of plugins included. For a more active collaborative vault, perhaps using Obsidian Sync and then try to [Collaborate on a shared vault](https://help.obsidian.md/sync/collaborate). It requires a paid subscription, but perhaps $96,- per user per year will not break the bank (limit is 20 users currently). Paid Sync service also includes versioning of the content.
 

10 Notes/testing codex-status-go integration.md

@@ -2,7 +2,7 @@
 related-to:
   - "[[status-go-codex integration - design notes]]"
 ---
-                                                                               In [[Running Unit Tests for status-go]] we provide general notes on running unit tests in the status-go project. And then we have a similar note about functional tests in [[Running functional tests in status-go]].
+In [[Running Unit Tests for status-go]] we provide general notes on running unit tests in the status-go project. And then we have a similar note about functional tests in [[Running functional tests in status-go]].
 
 Also, to learn the history archive creation/upload and download/processing flows (recorded AI conversation with some edits), please check: