diff --git a/en/blog/2022-10-31-Storia-Antica-del-DSpacc.md b/en/blog/2022-10-31-Storia-Antica-del-DSpacc.md
new file mode 100644
index 0000000..4798865
--- /dev/null
+++ b/en/blog/2022-10-31-Storia-Antica-del-DSpacc.md
@@ -0,0 +1,101 @@
++++
+Title = "🎮 Ancient history of DSpacc"
+Description = "The first game console of my life went to war, then gathered dust, and to this day it's not very well; but I gave it a purpose."
+Aliases = [
+  "/Posts/2022-10-31-Storia-Antica-del-DSpacc.html",
+]
+Categories = [ "Gaming", "Technology" ]
+Date = 2022-10-31
++++
+
+{{< noticeAutomaticTranslation it >}}
+
+
+
+Almost two months ago, the **DSpacc** came to mind somewhat by chance; first as a concept, talking about it with people online, and then directly as the little object that I proudly own.
+
+This thing of mine has seen **dust**, **glory**, **war**, and **despair**. This is exactly what I should have talked about today, what I did recently to remove some dust and thus bring my device back to glory.
+As I was writing, however, I realized how the context would have been confused if I hadn't given the right space to the story; but alas, the story itself is long, and worthy of a detailed article, so here we are.
+
+## The beginnings
+
+It all started when, at the age of about 6, I received this **Nintendo DS Lite** as a gift for my birthday... no, I'm not rambling, I'm getting there now. For a good 3 years it was my only gaming console - and, for at least 1-2 of those years, my only gaming device, before I got the Galaxy Player or the _scassone tablet_.
+For me it was an absolutely indispensable battle object, necessary always and everywhere like my smartphone today, and perhaps for this reason it had a particularly intense life in its first years. I didn't have a lot of games, because I only had 2 GB of memory in the flashcart and no physical games (apart from an obscure one, which I didn't buy until later), but I had some of the top ones. In short, with Pokémon, all the main Mario games, and even stuff like Cooking Mama (which was very popular at the time), the enjoyment was always present.
+
+[![Nintendo DS Lite (right side)]({{< assetsRoot >}}/Media/Misc/Nintendo_DS_Lite_(right_side)/4.jpg)](https://commons.wikimedia.org/wiki/File:Nintendo_DS_Lite_ (right_side).jpg)
+_A DS Lite.. not mine, for obvious reasons soon - <small>Havok at en.wikipedia, CC BY 2.5 <https://creativecommons.org/licenses/by/2.5>, via Wikimedia Commons</small> _
+
+## The day of the smash
+
+Despite a couple of flashcart mishaps - the first one mysteriously stopped working one day, the second was starting to show serious signs of failure after about 2 years - **the little console fought** and kept me entertained.
+One bad day at the beginning of July however, in the early afternoon, returning from the sea, my desire to play went **_crack_**, together with the plastic of the zipper when I opened the shell. Oh yes, exactly this is a "DSpacc": a **split DS**. The name might not mean much, I'm aware of that, because not only did I coin it, but also very recently.
+
+At the moment it seemed absurd to me that simply by opening the console, it could have broken; and it still seems absurd to me today, even though I have discovered that it is a very widespread problem: just type "nintendo ds broken" on any image search engine to notice how not only are the images showing the broken hinge the majority, but also how those depicting DS and DS Lite are the majority. It seems that, starting from the DSi, Nintendo has in fact redesigned the clamshell mechanism, which until then had proven unsuitable, and has further perfected it with the 3DS; evidently, the original _did cahà_.
+
+### The consequences of damage
+
+Despair was about to set in, even though at the time the console continued to work perfectly, because a piece of the plastic on the right of the hinge had simply broken, which has the sole task of ensuring **structural integrity**. Despair really started to set in the moment I saw the colors on the screen start to shift as I moved the clamshell: there you have it, **the cable** of the display **started to suffer damage**.
+A little later, I think the same afternoon, I went with my father to a shop on the other side of town, to see how much **a repair** would cost. I don't remember the price now, but I decided that **it wasn't worth it**, and that it would be better to buy a nice 3DS, given the interesting games that had been released or were about to be released for the new family of consoles.
+
+I don't remember if I continued to use the DS Lite in the following days, because many of the titles I wanted to play required the upper screen, and I didn't like gaming with _diminished_ colors (today it doesn't bother me too much, however). In any case, by the end of that week, after several searches in local shops in search of the cheapest price, [I got my o3DS XL](https://mastodon.uno/@octo/109262437212406002).. and that it's a whole different story.
+
+## The Age of Dust
+
+From this moment, of course, the old new **DSpacc fell into the background**. Maybe I still took it sometimes, at least for games like Animal Crossing that only require the bottom panel, because (according to the _Diary_ app, certainly more precise than my memory) in the first 2 weeks of the 3DS I didn't have anything to play with other than the system applications . Then, however, on the one hand I was slowly able to populate the new console with software, on the other hand the DS Lite **continued to break** - sooner rather than later, in fact, the upper display started to stop working completely, showing only a white screen with a black spot (?) - **dust** started attacking the DSpacc. As if that wasn't enough, the flashcart one day _said bye-bye_! 🙄
+Even after years, despite my new console, every now and then I still had to **pick up the old one again**... I'm not sure why, given that I couldn't do anything special with it anymore, as I don't have games on a dedicated card. that I could use without the top screen. Even years later, perhaps because over time I started collecting some original DS cartridges and felt like starting them, **sometimes I turned **the DS Lite** back on for a few minutes.
+
+Everything was great, until, at a certain point, **I even played **the _SLOT-1_** (the one for the DS cards) on the poor console! I remember that he showed some difficulty reading even original slips, but my other memories on the subject are very cloudy. I remember that when I looked inside the slot I saw some **bent pins**, and that I tried to insert something to straighten them, but in vain. I don't think that by doing this I damaged others, but already at least 3 years ago (compared to the present) I remember that in the slot some pins were **broken, missing**... so, either when I stuck stuff in the port I weakened or even disconnected other pins without realizing it, or it is the occasional putting and removing of cartridges, in the hope that some would be read, which has broken the already weakened contacts (and it would be serious, because it would demonstrate the poor quality of the slot).
+
+After this new unexpected event, I could certainly still, via _Download DS_, use the console for technically limited, volatile software, without the possibility of saving any configuration (or progress, in games), but **let's not beat around the bush**: what do you do? useful and continuous like this? Practically nothing, and **the console had** therefore become **a paperweight**... until, some time later, at a fair I accidentally found and **bought a Pokémon Ruby cartridge**. Even though it didn't even have a box, I had to have it: **finally I could play** something complete on my poor little console!
+
+## Edit arranged
+
+However, **that broken panel was starting to take its toll**, _literally_. The split hinge unbalanced the weight of the entire device, and the top part of the shell remained hanging only thanks to the _assorted cables_.
+I had already discovered the concept of **GBA Macro** a while ago. For non-experts, it involves giving a second life to a DS that has lost its upper screen, to play titles (emulated, or not like the GBA ones, for which the console offers hardware backward compatibility) from previous consoles that their nature possessed only one screen.
+Online I was already seeing people creating their own personalized ones with uniquely hand-coloured bodies, or by adding LED tubes that create a neon effect, placed in place of the zipper. All fantastic stuff, but if I didn't have the desire (and the way, at least at the time it couldn't be found on Amazon.it) to buy a new display to properly repair the console, could I ever start spending on details which, however beautiful, are objectively superfluous?
+
+I take a pair of scissors, and **cut away** the cables so the top half of the case remains attached to the main one. And this is it? Can we play again? Well, _not exactly_.
+To be honest, making a good Game Boy Macro requires some hardware work _a little more elaborate_ than violently ripping away the broken screen, and for this reason my story has been **a little troubled**. First of all, a **particular operation** is practically mandatory, if you don't want to lose the **DS features**: open the device and - in addition to _properly_ disconnecting the display, speakers, microphone, and antenna cables, _without cutting them_ - solder a small **resistor** on 2 testpoints of the motherboard. Normally, the console fails POST and shuts down if it doesn't detect the top screen (namely, if it doesn't detect the power draw it would expect from the top screen's backlight); soldering a resistor of a value between about 300 and 1000 Ohm in the right places serves precisely to make the system believe that nothing is out of place.
+
+However, I had done **my searches** on the Web, thus discovering that the POST is not performed to start a cartridge from the _SLOT-2_ (the GBA one), if **automatic start is set in the system settings ** of a game card if present. Well before committing my _violent act_ therefore, because afterwards I would no longer be able to access the system menu, I set the automatic startup, and made sure that the bottom screen was selected as the panel used in Game Boy Advance mode.
+Once _the crime_ is done, I see that the console works exactly the way _strangers on the Internet_ had said: **it's practically a GBA**, as if it had never been a DS... except that it doesn't have speakers, because I have them cut away. 😅
+
+## A new plan
+
+A little later, however, I started **wanting things** like _Download DS_ mode.. or backlight adjustment. I decided to buy a kit of screwdriver bits online, which among many also included the damned bit for tri-wing screws, those screws loved by Nintendo exactly as much as they are hated by us idiots who buy their products.
+With my new **very dangerous weapon** (this is not my opinion, but that of those who insist on using shitty screws for the objects they produce) I can finally open my DSpacc, in order to **solder the resistor** .. resistor **which I don't have**! But **I have a piece of gum**.
+Other kind souls on the Internet, in fact, illustrate how the conductive rubbers used for the buttons of the remote controls (and of the DS itself) often have the right resistance value needed in this case. As luck would have it, an old broken remote control I had on hand had suitable rubber pads: by cutting one, and holding it down with my finger on the infamous test points, **the console turned on** as before I cut the panel off.
+Here **the hard thing** was managing to **fix** that _little thing_ to the motherboard, so that it made the right pressure, and therefore the right electrical contact, on the points where in theory soldering should be made - _for the reason that the very word "welding" suggests_. A few centimeters of **electrical tape** later, which I had to apply and reapply until I could secure it with the right tension, and it seemed that I was done; but _fate decided to mock me_.
+
+![Photo of the testpoint area, with a mixture of insulating tape and adhesive applied over it.]({{< assetsRoot >}}/Media/Misc/GBA-Macro-Button-Resistor.avif)
+
+### Yet another trouble
+
+Given that the _great quality_ device - but not only it, now also _"smart"phones_ for 15 years now - does not turn on without a battery connected (only with the external power cable, so to speak), and that it is only the plastic body that keeps the cell stuck and aligned, now that the console was disassembled I had to **hold the battery with my hands** close to the spring contacts, in those moments of a few seconds in which I simply wanted to **verify that the console worked**.
+Well, due to these maneuvers (and I only understood this later), perhaps due to my mishandling of the battery or who knows what, all of a sudden **the DS no longer turned on**! The POST didn't fail like before, eh, but it just **showed no signs of life**. _Despair_ rose quickly, I had no idea what had happened and where to put my hands. It was only thanks to _Ashfly_, who was helping me in chat with my mess, I came to the conclusion that the fuse dedicated to the battery connection had just blown.
+
+Don't feel bad about me, but not having the resistor that I knew exactly I needed, could I ever have the fuse that I could never imagine would blow? I therefore had to make a beautiful bridge with tin... Come on, there's no point making too many fuss about it, it will never happen that I connect **by mistake**, in the battery compartment, a more powerful energy source than that that the console circuitry can handle; the charging port fuse is separate, so it's out of the question that a faulty power supply could discharge _literal lightning_ into the console's CPU.
+
+![Photo of the tin bridge made (with difficulty) over the battery fuse, with the position of the area marked on the entire board.]({{< assetsRoot >}}/Media/Misc/DSpacc-Fuse-Bridge.png )
+
+### Issue resolved
+
+I would have liked to reconnect the speaker (the place is located in the lower part of the console) but, on the one hand, having cut the wire and my absolute incompetence in soldering some time (_the photo of the jumper speaks for itself_) - even if , to date, I know how to solder at least one wire on a large testpoint - and on the other hand the frenzy of closing everything in fear that my insulating tape disaster could move, **I preferred to close everything** and pretend nothing happened . At least, I still have the 3.5 jack port to listen to audio in headphones.
+
+Subsequently (well **13 months later**... I thought all this time that the console was beautiful to look at as it was?!?) I **refinished** the body** a little, mainly using sandpaper to completely flatten the other protrusion that normally serves the clamshell mechanism, bringing it to the state it **still is in**.
+
+![Old photo showing the DSpacc and a piece of sandpaper on my desk, while working.]({{< assetsRoot >}}/Media/Misc/GBA-Macro-Sandpaper-Job-Detail.avif)
+
+## The sequel
+
+**Playing** Pokémon Ruby on my new GBA Macro, much more compact and lighter than the DS in original form, **took** a whole new flavor**. I played for dozens of hours, but every now and then it occurred to me that I wanted to have fun with other things on the elegant console.
+Totally excluding DS flashcarts, because the slot is, as I said, **dead**, I looked at GBA ones. On Amazon.it, the only online store where I could and can buy, it seems to me that I **found** already at the time a _scassona_ for no more than **twenty euros**, but I don't know why **I just looked* * - and I have done this more than once - without ever touching (buying).
+
+So another good year has passed, and I'm just **a few weeks ago**. A bit randomly, I remember my DSpacc and, since I'm sorry about its being out of use, I try to do **some slightly crazy stuff**, which I talked about in [this entry from 2022-09-18 of the MicroBlog](./MicroBlog/2022-09-18- Quando-Metto-Mano-Io-Spacc.html).
+At this point, however, I am now entering the story of the **contemporary age of the DSpacc**, which has far **too many implications** to talk about. In the **next detailed article** on the topic there will be plenty of time to talk about how, finally, I dusted off this **valiant** gaming device in style, which still remains valid despite the bad luck.
+
+**Thanks for reading!** If you found the story intriguing, then keep your eyes peeled for the sequel! 😄
+
+---
+
+_Pss... The story regarding the Macro modification itself deserves a small dossier on its own, in my opinion. Thanks to the existence of old written messages I can compose it.. should I?_
diff --git a/en/blog/2022-12-13-Blogging-Rapido-con-Standard-Notes.md b/en/blog/2022-12-13-Blogging-Rapido-con-Standard-Notes.md
index 36cd168..ed2cf50 100644
--- a/en/blog/2022-12-13-Blogging-Rapido-con-Standard-Notes.md
+++ b/en/blog/2022-12-13-Blogging-Rapido-con-Standard-Notes.md
@@ -1,11 +1,11 @@
 +++
-Title= "⚡️ Quick blogging with Standard Notes"
-Date= 2022-12-13
-Downsync= "/it/blog/Blogging-Rapido-con-Standard-Notes.html"
-Aliases= [ "/Posts/2022-12-13-Blogging-Rapido-con-Standard-Notes.html" ]
-Description= "As I wanted to write and publish more, I found my workflow was slowing me down, and in looking for faster ways to blog, I looked back to Listed."
-Lastmod= 2022-12-16
-Categories= [ "Technology" ]
+Title = "⚡️ Quick Blogging with Standard Notes"
+Date = 2022-12-13
+Downsync = "/it/blog/Blogging-Rapido-con-Standard-Notes.html"
+Aliases = [ "/Posts/2022-12-13-Blogging-Rapido-con-Standard-Notes.html" ]
+Description = "Wanting to write and publish more, I find that my workflow was slowing me down, and in looking for faster ways to blog, I look back to Listed."
+Lastmod = 2022-12-16
+Categories = [ "Technology" ]
 +++
 
 {{< noticeAutomaticTranslation it >}}
@@ -14,103 +14,88 @@ Categories= [ "Technology" ]
 
 <!-- Autogenerated by ListedDownsync.js. Do not edit (unless also set "% Downsync = False") - it would be overwritten. -->
 
-<p>I'd say I've been using <strong><a href="https://standardnotes.com" rel="noopener nofollow" target="_blank">Standard Notes</a></strong> for a long time as < strong>personal notes</strong>app.<br>
-Years ago I chose it for its being <strong>free and open-source</strong>, but at the same time very <strong>clean, well-kept, and functional</strong>. It was a perfect fit at a time when I was looking for something that supported data encryption that works, without affecting usability.</p>
+I've been using **[Standard Notes](https://standardnotes.com)** as my personal **notes app** for a long time now.  
+Years ago I chose it for its being **free and open-source**, but at the same time very **clean, tidy, and functional**. It was a perfect fit at a time when I was looking for something that supported data encryption that works, without affecting usability.
 
-<p><img src="{{< assetsRoot >}}/Media/Misc/Standard-Notes-Tablet.webp" alt="Old Standard Notes Android app on my tablet."></p>
+![Old Standard Notes Android app on my tablet.]({{< assetsRoot >}}/Media/Misc/Standard-Notes-Tablet.webp)
 
-<p>Without dwelling on why I liked continuing to use it, then I stopped, and then I started again until now, we need to delve deeper into one of its <strong>integrated functions</strong> in particular: <strong> <a href="https://listed.to">Listed</a></strong>.<br>
-It is a <strong>blogging</strong> platform designed by the same developers as Standard Notes, and available for self-hosting or <strong>free</strong> use on the official instance. Although I have never really used it before, I found the concept and its application interesting from the beginning.</p>
+Without going into detail about why I liked continuing to use it, then I stopped, and then I started again until now, we need to delve deeper into one of its **integrated functions** in particular: **[Listed](https:/ /listed.to)**.  
+It is a **blogging** platform designed by the same developers as Standard Notes, and available for self-hosting or **free** use on the official instance. Although I have never really used it before, I found the concept and its application **interesting** from the beginning.
 
-<h2>A quick need</h2>
+## A quick need
 
-<p>A few days ago, however, I started playing around with <a href="https://listed.to/@ChatGPT_Experiences">ChatGPT</a>. This is a totally different question, yes, but it's relevant because I asked myself a question: all these conversations I'm having with artificial intelligence, where can I put them to keep them integral, organised, findable and accessible to anyone, and <strong>easy to load</strong> for me?</p>
+A few days ago, however, I started playing around with [ChatGPT](https://listed.to/@ChatGPT_Experiences). This is a totally different question, yes, but it's relevant because I asked myself a question: all these conversations I'm having with artificial intelligence, where can I put them to keep them integral, organised, **findable** and accessible to anyone, and for me **easy to load**?
 
-<p>The choice was about to<strong>use <a href="https://gitlab.com/octtspacc/staticoso" rel="noopener nofollow" target="_blank">staticoso</a></ strong>, <strong>my generator</strong> of static sites that I already use for <a href="https://sitoctt.octt.eu.org" rel="noopener nofollow" target="_blank"> sitoctt</a>, but then <strong>I thought better of it</strong>.</p>
+The choice was about to **use [staticoso](https://gitlab.com/octtspacc/staticoso)**, **my static site generator** that I already use for the [sitoctt](https: //sitoctt.octt.eu.org), but then **I thought better of it**.
 
-<p>I thought that, in fact, I want to actually make my collection of experiences findable on the Web. The <strong>problem</strong> here, however, which I have been able to bitterly observe in all these months, is how my site example is, how to say... <strong>Search engines don't give a damn</strong>. 😭<br>
-Besides this being a separate topic, it should be noted that the blame for the horrendous fate of my site does not depend on its code; It's the fault of the domain and/or the host. So, no, I will never abandon my static one: just changing the generator (and consequently the templates) with a more serious one wouldn't solve any problem.</p>
+I thought that, in fact, I want to actually make my collection of experiences findable on the Web. The **problem** here, however, which I have been able to bitterly observe in all these months, is how my site, for example, is, so to speak. .. **Search engines don't give a shit**. 😭  
+Besides this being a separate topic, it should be noted that the blame for the horrendous fate of my site does not depend on its code; It's the fault of the domain and/or the host. So, no, I will never abandon my static one: just changing the generator (and consequently the templates) with a more serious one wouldn't solve any problem.
 
-<p>In short, I had to completely <strong>trash</strong> the idea of<strong>hosting on GitHub and GitLab</strong>, and think about something else.</p>
+In short, I had to totally **trash** the idea of**hosting on GitHub and GitLab**, and think about something else.
 
-<ul>
-Google <li><strong>Blogger</strong>? The editorial experience leaves something to be desired on mobile.</li>
-<li><strong>WordPress</strong>? It would be OK, but we know what could happen in many years to data inserted into a complex system; and WordPress is very complex. I struggled to find a <a href="https://github.com/lonekorean/wordpress-export-to-markdown" rel="noopener nofollow" target="_blank">little program that converts your backup</a> XML in Markdown file... which will most likely break in a few years, being unofficial, as apparently the WordPress team has a habit of changing the structure of that XML from time to time; other conversion solutions that I had found a moment earlier were a few years old and didn't work, so to speak.</li>
-<li>Maybe <strong><a href="https://writefreely.org" rel="noopener nofollow" target="_blank">WriteFreely</a></strong>? I already have an account on the <a href="https://noblogo.org" rel="noopener nofollow" target="_blank">Devol instance</a>, but the blog limit for each account is 5 and I didn't want to potentially waste one.</li>
-<li><strong><a href="https://joinplu.me" rel="noopener nofollow" target="_blank">Plume</a></strong>, maybe? This other blogging platform seemed nice, hosted by many and compatible with ActivityPub (not a necessity for me, but still a nice bonus), but it doesn't allow you to set custom CSS; serious shortcoming for this use case of mine, since there is no other way to layout everything in the specific way I need to represent a chat without boilerplate for each paragraph of HTML.</li>
-</ul>
+* **Blogger** from Google? The editorial experience leaves something to be desired on mobile.
+* **WordPress**? It would be OK, but we know what could happen in many years to data inserted into a complex system; and WordPress is very complex. I struggled to find a [little program that converts its backup](https://github.com/lonekorean/wordpress-export-to-markdown) XML into Markdown files... which will most likely break in a few years, being unofficial, as apparently the WordPress team has a habit of changing the structure of that XML from time to time; other conversion solutions that I had found a moment before were a few years old and didn't work, so to speak.
+* Maybe **[WriteFreely](https://writefreely.org)**? I already have an account on the [Devol instance](https://noblogo.org), but the blog limit for each account is 5 and I didn't want to potentially waste one.
+* **[Plume](https://joinplu.me)**, maybe? This other blogging platform seemed nice, hosted by many and compatible with ActivityPub (not a necessity for me, but still a nice bonus), but it doesn't allow you to set custom CSS; serious shortcoming for this use case of mine, since there is no other way to layout everything in the specific way I need to represent a chat without boilerplate for each paragraph of HTML.
 
-<h2>The choice of Listed</h2>
+## The choice of Listed
 
-<p>My ideas were finished and, since I was in a hurry to put on this site and start uploading the experiences I had with ChatGPT, considering how <em>my goodness</em> it was <strong>convenient</strong> to copy and paste things <strong>directly into Standard Notes</strong>, this was a good time to try <strong>Listed</strong>.</p>
+My ideas were finished and, since I was in a hurry to put up this site and start uploading the experiences I had with ChatGPT, considering how _oh my goodness_ it was **convenient** to copy and paste things **directly into Standard Notes**, this was the **good time to** try **Listed**.
 
-<p>To be honest, I'm a little worried about the prospect that the weekly backup file of notes could become tens of MB large, but the die has now been cast.<br>
-I could create a second account to use only for ChatGPT notes, exporting them from the primary one and importing them there, and then deleting them from the first account to lighten the collection, but there are problems. Maybe I can transfer the username, but the links to the individual posts will be broken, because they include automatic IDs, and therefore a redirect to the home page for those who follow an old one. Also, old guestbook messages aren't copied over, and I don't think email subscriptions are transferred either.</p>
+To be honest, I'm a little worried about the prospect that the weekly backup file of notes could become tens of MB large, but the die has now been cast.  
+I could create a second account to be used only for ChatGPT notes, exporting them from the primary one and importing them there, and then deleting them from the first account to lighten the collection, but there are problems. Maybe I can transfer the username, but the links to the individual posts will be broken, because they include automatic IDs, and therefore a redirect to the home page for those who follow an old one. Also, old guestbook messages aren't copied over, and I don't think email subscriptions are transferred either.
 
+## The thought of "what a drag"
 
+All in all though, for this limited purpose I **appreciated** how **efficient** it is to have **Standard Notes** as the **final** part of** my **workflow**. It seems to me to greatly reduce the "I'm annoyed" effect.
 
-<h2>The thought of "what a drag"</h2>
+Therefore, considering the pleasure of the discovery, I **reflected** for a moment on how the **_"what a pain" factor_** is one of the things that **holds me back from updating** the ctt site more frequently.
 
-<p>All in all however, for this limited purpose <strong>I appreciated</strong> how <strong>efficient</strong> it is to have <strong>Standard Notes</strong> as the <strong>final</strong> part of the</strong> > my <strong>workflow</strong>. It seems to me to greatly reduce the <em>"I'm annoyed" effect</em>.</p>
+Let's leave aside the thematic pages, which are _beasts apart_; let's leave aside the long posts, which require strong inspiration and enough writing time; but what the hell, at least **something** for the MicroBlog, which is all the rage, **I would** like to create it **more often**! But **I just don't feel like it**, for some reason, considering all the trouble I have to go through.  
+To tell the truth, I had already immediately got into the habit of starting to write a post in Standard Notes, so as to be able to manage everything more flexibly, perhaps quickly switching from one device to another. However, if I had to start writing something not long and elaborate, to be published as soon as possible, I just didn't feel like taking action.
 
-<p>Considering the pleasure of the discovery, I <strong>reflected</strong> for a moment on how the <strong><em>"what a pain" factor</em></strong> is one of the things that < strong>keeps me from updating</strong>the ctt site more frequently.</p>
+"_But why don't I switch to **Listed at least for** my **microblog**?_", I therefore think. Well, there's a reason why I even got to the point of making my own static site generator: I need it!... _And even if I didn't need it anymore and could therefore stop using it, I honestly wouldn't even want to think about doing something about it like that, after all the work!_ 😖
 
-<p>Let's leave aside the thematic pages, which are <em>beasts apart</em>; let's leave aside the long posts, which require strong inspiration and enough writing time; but what the hell, at least <strong>something</strong> for the MicroBlog, which is all the rage, I would <strong>like</strong> to create it <strong>more often</strong>! But <strong>I just don't feel like it</strong>, for some reason, considering all the process I have to do.<br>
-To tell the truth, I had already immediately got into the habit of starting to write a post in Standard Notes, so as to be able to manage everything more flexibly, perhaps quickly switching from one device to another. However, if I had to start writing something not long and elaborate, to be published as soon as possible, I just didn't feel like taking action.</p>
+## Limitations of Listed
 
-<p>"<em>But why don't I switch to <strong>Listed at least for</strong> my <strong>microblog</strong>?</em>", I therefore think. Well, there's a reason why I even got to the point of making my own static site generator: I need it!...<em>And even if I no longer needed it and could therefore stop using it, I honestly wouldn't even want to think about it. do something like this, after all the work!</em> 😖</p>
+However, to put it nicely, **Listed is pretty bare**: it barely allows you to insert custom **CSS**, and format posts in **Markdown** and a limited **subset** of **HTML* *. I propose my analyzes of the latter below:
 
-<h2>Limitations of Listed</h2>
+* All **elements** that are **inline in nature are** automatically **placed in a** `<p>` block (for example, you cannot have `<body><span>Erre< /span></body>`, it will always be `<body><p><span>Erre</span></p></body>`);
+* Any element **attribute** other than `id`, `class`, or `style`, (and `href` or `src`, as well as I believe stuff like `title`, `width`, or ` height`, in appropriate cases) **is thrown** away: so forget, for example, deviating from the default configuration of the platform regarding the behavior of the links (the `rel` is not touched);
+* **Certain elements** just don't work: those with non-standard tags (custom in short, like `<pincopallino>`) **are eliminated**, as are `<script>`, `<link>`, and others apparently stuff like `<video>` too - but `<iframe>`, so to speak, works, and luckily so does my beloved `<details>`.
 
-<p>However, to put it well, <strong>Listed is quite bare-bones</strong>: it barely allows you to insert custom <strong>CSS</strong>, and to format posts in <strong>Markdown</strong> and a narrow <strong>subset</strong> of <strong>HTML</strong>. I propose my analyzes of the latter below:</p>
+It is very clear that absolutely **it cannot replace** 100% **any section of the sitectt**, not even that of the MicroBlog, and even if it could it would create fragmentation: the main site would no longer contain all the posts in a centralized way , and anyone interested should therefore follow 2 different sites.
 
-<ul>
-<li>All <strong>elements</strong> that are <strong>inline in nature are</strong> automatically <strong>inserted into a block</strong> <code class="prettyprint"><p> </code> (for example, you cannot have <code class="prettyprint"><body><span>Err</span></body></code>, it will always be <code class="prettyprint"> <body><p><span>Err</span></p></body></code>);</li>
-<li>Any element <strong>attribute</strong> that is not <code class="prettyprint">id</code>, <code class="prettyprint">class</code>, or <code class= "prettyprint">style</code>, (and <code class="prettyprint">href</code> or <code class="prettyprint">src</code>, as well as I believe stuff like <code class=" prettyprint">title</code>, <code class="prettyprint">width</code>, or <code class="prettyprint">height</code>, in appropriate cases) <strong>is thrown away</strong > go: so forget, for example, deviating from the default configuration of the platform regarding the behavior of the links (the <code class="prettyprint">rel</code> is not touched);</li>
-<li><strong>Certain elements</strong> just don't work: those with non-standard tags (custom in short, like <code class="prettyprint"><pincopallino></code>) <strong>are eliminated</strong> strong>, as well as <code class="prettyprint"><script></code>, <code class="prettyprint"><link></code>, and apparently stuff like <code class="prettyprint" too ><video></code> - but <code class="prettyprint"><iframe></code>, so to speak, works, and luckily so does my beloved <code class="prettyprint"><details>< /code>.</li>
-</ul>
+## The blogoctt with Standard Notes
 
-<p>It is very clear that <strong>it cannot replace</strong> 100% absolutely <strong>any section of the ctt site</strong>, not even that of the MicroBlog, and even if it could it would create fragmentation: the main site does not it would contain all the posts in a centralized way, and anyone interested would therefore have to follow 2 different sites.</p>
+I was _almost_ about to give up, but luckily I had a flash of genius: _But I can **write on Standard Notes**, and have the **notes that** automatically **synchronize** as files **on the site* *? ...No, there's no way. No, wait, who said that? I say there is a way._
 
-<h2>The blogoctt with Standard Notes</h2>
+Now, Standard Notes, as I said, uses a client-side data encryption system, so to access the notes from your account **a minimum **specialized** software** should be used.  
+There is _sn-cli_, the official command line client, which could be useful for creating scripts... but [it seems to have been abandoned](https://github.com/jonhadfield/sn-cli/issues/ 33): nothing to do.
 
-<p>I was <em>almost</em> about to give up, but luckily I have a flash of genius: <em>But I can <strong>write on Standard Notes</strong>, and have the <strong>notes that Do they automatically <strong>synchronize</strong> as files <strong>on the site</strong>? ...No, there's no way. No, wait, who said that? I say there is a way.</em></p>
+### "My way" solution
 
-<p>Now, Standard Notes, as I said, uses a client-side data encryption system, so to access the notes from your account <strong>you should use</strong> a specific <strong>software</strong> minimum <strong>specialised</strong>.<br>
-There is <em>sn-cli</em>, the official command line client, which could be useful for creating scripts... but <a href="https://github.com/jonhadfield/sn- cli/issues/33" rel="noopener nofollow" target="_blank">it seems to have been abandoned</a>: nothing to be done.</p>
+So, here too I speak, and I say: _Who said that I have to do things properly and use the "real" APIs?_  
+I say that, given that for some reason the **HTML** of a blog **on Listed** (specifically, the page [/all](https://listed.to/@u8/all), the only one that seems to me to really include everything, and not just the last on Listed **from Standard Notes** and have a **program that does** the dirty work - but in this case really simple, since it only has to download and parse 1 file - the job of **scraping**.
 
-<h3>Solution "my way"</h3>
+_And script fu scripto._ I leave it here: [gitlab.com/octtspacc/sitoctt/Scripts/ListedDownsync.js](https://gitlab.com/octtspacc/sitoctt/-/blob/main/Scripts/ListedDownsync.js) ; Be careful though, there is _nothing nice to read_, also because I haven't yet implemented everything that should serve me in the long term, but **for those who want to use it** it's there.  
+It is technically **independent of the ctt site** and static, as it **saves** simple **Markdown files** on disk (even if the syntax of the metadata lines written in them is mine; so, in case , some text strings in the program should be changed to support the more classic YAML metadata format).
 
-<p>So, here too I speak, and I say: <em>Who said that I have to do things properly and use "real" APIs?</em><br>
-I say that, since for some reason the <strong>HTML</strong> of a blog <strong>on Listed</strong> (specifically, the page <a href="https://listed.to/ @u8/all">/all</a>, the only one that seems to me to really include everything, and not just the last X posts) <strong>include as</strong> string <strong>JSON</strong> i data of <strong>all the posts</strong>, then I can simply <strong>publish</strong> to Listed <strong>by Standard Notes</strong> and have a <strong>program that does</strong> the dirt - but in this case really simple, since it only has to download and parse 1 file - <strong>scraping</strong> work.</p>
+I don't want to say that I really thought of everything, but I came close.  
+No, I still can't decide - due to my _paturnias_ - which standard to use to indicate special blocks (of metadata, or of HTML not to be interpreted by Listed's SSG).  
+No, I haven't yet created the script to start as a **cronjob** on the server, which every now and then should **download the data from** the **Listed** blog and **update** the files in** the Git repository** if there are updates.  
+However, I thought about the really mandatory things, such as the possibility for the synchronization program not to overwrite a file already in the repo if this specifies the thing in the metadata. Suppose some mess happens, and I have to modify the post data for the ctt site without touching the note data on Standard Notes: by setting this flag, the synchronization script will not replace it the next time it runs.
 
-<p><em>And script fu scripto.</em> I leave it here: <a href="https://gitlab.com/octtspacc/sitoctt/-/blob/main/Scripts/ListedDownsync.js" rel= "noopener nofollow" target="_blank">gitlab.com/octtspacc/sitoctt/Scripts/ListedDownsync.js</a>; Be careful though, there is <em>nothing nice to read</em>, also because I haven't yet implemented everything that should serve me in the long term, but <strong>for those who want to use it</strong> it's there. <br>
-It is technically <strong>site-independent</strong> and static, as it <strong>saves</strong> simple <strong>Markdown files</strong> to disk (even if the syntax of the metadata lines written in them it is mine; therefore, in this case, some text strings in the program should be changed to support the more classic YAML metadata format).</p>
+## Conclusions
 
-<p>I don't want to say that I really thought of everything, but I came close.<br>
-No, I still can't decide - due to my <em>paturnia</em> - which standard to use to indicate special blocks (of metadata, or of HTML not to be interpreted by Listed's SSG).<br>
-No, I haven't yet created the script to start as a <strong>cronjob</strong> on the server, which every now and then should <strong>download the data from</strong>the <strong>Listed</strong> blog and < strong>update</strong> the files in the<strong>Git repository</strong> if there are updates.<br>
-However, I thought about the really mandatory things, such as the possibility for the synchronization program not to overwrite a file already in the repo if this specifies the thing in the metadata. Suppose some mess happens, and I have to modify the post data for the ctt site without touching the note data on Standard Notes: by setting this flag, the synchronization script will not replace it the next time it runs.</p>
+How to conclude, then.  
+Today **I've already written too much** (it turned out to be a blog article and not a microblog!), and I'll end it here. But I sincerely hope that all this new efficiency and convenience, having additional **technology that works for me**, and does not force me to work for it _(in theory, anyway the problems must come out, otherwise I am not me!)_, can **make me write more** and **with more pleasure**. Whether on the **[sitoctt](https://sitoctt.octt.eu.org)**, or on the stone slabs.
 
-<h2>Conclusions</h2>
+Ah, yes, this here was the **first post** on [my **Listed** blog](https://listed.to/@u8), it's right to point it out for those reading from the site... but I hope that at least the Listed version of the blog can be indexed well and **discovered by more people**, while we're at it.  
+It is precisely in the hope of achieving this objective that I am accepting some **compromises** when I write here, such as doing without macros (which I can use with statiso, while here they would produce broken texts and broken links), to ensure that the articles are actually also available on the Listed pages.
 
-<p>How to conclude, then.<br>
-Today <strong>I have already written too much</strong> (it turned out to be a blog article and not a microblog!), and I'll end it here. But I sincerely hope that all this new efficiency and convenience, having additional <strong>technology that works for me</strong>, and does not force me to work for it <em>(in theory, anyway, the problems must come out , otherwise I'm not me!)</em>, may it <strong>make me write more</strong> and <strong>with more pleasure</strong>. Whether on the <strong><a href="https://sitoctt.octt.eu.org" rel="noopener nofollow" target="_blank">sitoctt</a></strong>, or on the stone slabs .</p>
+## {{% i18n notes-refs %}}
 
-<p>Ah, yes, this here was the <strong>first post</strong> on <a href="https://listed.to/@u8">my <strong>Listed blog</strong>< /a>, it's right to point this out for those reading from the ctt site... but I hope that at least the Listed version of the blog can be indexed well and <strong>discovered by more people</strong>, while we're at it.<br >
-It is precisely in the hope of achieving this objective that I am accepting some <strong>compromises</strong> when I write here, such as doing without macros (which I can use with statiso, while here they would produce holes in text and broken links), to so that the articles can also be effectively consulted from the Listed pages.</p>
-
-
-
-
-
-<h2>{{% i18n notes-refs %}}</h2>
-
-<ul>
-<li><strong>Updates</strong> to the post:
-
-<ul>
-<li><strong>2022-12-16</strong>: I added a cover photo for the article, and clarified the final detail I had forgotten.</li>
-<li><strong>2022-12-14</strong>: I added some extra formatting, and corrected some expressions.</li>
-</ul></li>
-</ul>
+* **Updates** to the post:
+    * **2022-12-16**: I added a cover photo for the article, and clarified the final detail I had forgotten.
+    * **2022-12-14**: I added some extra formatting, and corrected some expressions.
\ No newline at end of file
diff --git a/en/blog/2023-03-18-Cattiva-Interfaccia-Partizione-Distrutta.md b/en/blog/2023-03-18-Cattiva-Interfaccia-Partizione-Distrutta.md
new file mode 100644
index 0000000..0bf8db8
--- /dev/null
+++ b/en/blog/2023-03-18-Cattiva-Interfaccia-Partizione-Distrutta.md
@@ -0,0 +1,170 @@
++++
+Title = "🥴 Ugly interface? Files all destroyed!"
+Date = 2023-03-18
+Description = "To do things in a hurry, I accidentally deleted part of the PC disk. But it's not just my fault: the program I used is poorly designed."
+Downsync = "/it/blog/Bad-Interface-Partition-Destroyed.html"
+Aliases = [ "/Posts/2023-03-18-Bad-Interface-Partition-Destroyed.html" ]
+Categories = [ "Sysadmin" ]
+Lastmod = 2023-03-20
++++
+
+{{< noticeAutomaticTranslation it >}}
+
+
+
+<!-- Autogenerated by ListedDownsync.js. Do not edit (unless also set "% Downsync = False") - it would be overwritten. -->
+
+Let's **visually compare** two PC applications: **GNOME Disks, and GParted**.
+
+![The windows of the two programs compared.]({{< assetsRoot >}}/Media/Partioning-Mar-2023/SideBySide.png)
+
+Both are disk partitioning tools, and broadly serve the same tasks; there is just **some difference** in extra features or more support in favor of one program or the other. Despite this, the two tools present **obvious differences** in their **graphical interface**.
+
+## You have to have both
+
+I generally keep both of these two programs installed, and I **use them in a rather **alternate** way, because:
+
+<table><thead><tr><th>GParted</th><th>GNOME Disks</th></tr></thead><tbody><tr><td><img src="{{ < assetsRoot >}}/Media/Partioning-Mar-2023/GParted-Advanced.png" alt="GParted's view of in-depth information about a disk."></td><td><img src="{{ < assetsRoot >}}/Media/Partioning-Mar-2023/GNOME-Advanced.png" alt="GNOME Disks' global pop-up menu, which has some special features."></td></tr><tr ><td><strong>GParted</strong> has <strong>fewer distinct functions</strong>, but everything has its place, and a <strong>sufficient</strong> level of <strong>depth</strong> strong> and features: low-level disk information, formatting in tons of formats, and a few other details.</td><td><strong>GNOME Disks</strong> has <strong>less depth</strong> > with individual operations, but offers some <strong>extra functions</strong> not strictly linked to the modification of partitions, which is always useful: energy and performance management of disks, an interface for the SMART protocol, and also a tool to test memory performance!</td></tr></tbody></table>
+
+## It was a simple mission!
+
+The day before yesterday, when I booted a **live USB** Linux on [my laptop](https://sitoctt.octt.eu.org/Posts/2022-07-09-Come-ho-Riparato-il- my-Portatile-con-25-Euro.html), I had in mind to complete **without damage** a _theoretically_ easy and painless mission:
+
+1. **Free up space** on the PC disk, deleting most of the files, except for those that I wanted to keep for a moment (to manage perhaps in the future).
+2. **Resize the partition** on the disk, as it will be quite empty at this point.
+3. **Create a new** partition large enough to install the new operating system on.<sup id="fnref1"><a href="#fn1">1</a></sup>
+4. **Move files** from the old partition to the new one, gradually shrinking the first and widening the second, **until** being able to **delete the old**.
+
+## Too much mess.
+
+...In practice, _something went slightly wrong_. It couldn't have been a quiet evening! 😾
+
+This time, for the simple fact that when looking for a partition editor among the pre-installed apps of the live system in question, **wanting to get it done straight away**, the first program my eyes fell on was **GNOME Disks** .
+Oh, I should have stayed away. And there are many reasons:
+
+#### 1\. Physical disks are mixed with virtual partitions mounted from physical disks, in the list on the left of the window
+
+Already at this point, if (as in my case) you have _strange type_ partitions, i.e. [LVM](https://wiki.archlinux.org/title/LVM), the situation becomes ugly, because **it is not It's clear where** you have to go** to make changes.<sup id="fnref2"><a href="#fn2">2</a></sup>
+
+<table><thead><tr><th>GParted</th><th>GNOME Disks</th></tr></thead><tbody><tr><td><img src="{{ < assetsRoot >}}/Media/Partioning-Mar-2023/GParted-List.png" alt="The disk list selector in GParted."></td><td><img src="{{< assetsRoot >}}/Media/Partioning-Mar-2023/GNOME-List.png" alt="The disk and partition list view on GNOME Disks."></td></tr><tr><td>< strong>GParted</strong> only has a <strong>list of devices</strong> (real disks for sure, but I think also virtual devices) to select first, and then the large view with all the partitions for the chosen device. It is <strong>orderly</strong> and logical.</td><td><strong>On GNOME Disks</strong>, however, to do what you need to do, <strong>you go</strong> to disk view or <strong>where?</strong> In the first case there are <strong>some options</strong> and others <strong>are missing</strong>. Shall we try from the view dedicated to the virtual partition? Here too, the list of options is decidedly neutered, among other things both in the sense of quick icon buttons and in the sense of pop-up menu buttons... but now let's see what problems they have.</td></ tr></tbody></table>
+
+#### 2\. As appropriate, the quick icons available for each partition appear and disappear
+
+While on **GParted**, the list of **icon-buttons** at the top of the window **never changes** - rather the individual buttons darken or lighten, depending on whether they can be operated on the selection current or not - **on GNOME Disks the hotkeys** - indeed, positioned in a strange way too, stuck under the partition table area, which honestly I can't even comment on - they **appear or disappear** completely .
+Below are the cases I have seen, but perhaps there are even more possible ones, who knows:
+
+* On the far left, for some selections you see a **play/stop** button (mount/unmount partition), other times in the exact same point there is a **padlock** (lock/unlock encrypted partition), other times a **cross** (creates partition in empty space), and in some cases **nothing**.
+* Immediately to the right, a **gear**, button that opens a pop-up menu with a more complete list of options for the partition - we note that this ends up **climbing to the far left**, if before it there is nothing, just to confuse more.
+* Finally, on the extreme right, in some cases a button with a **dash on a red background** (destroy partition) may appear.
+
+Ehh, this thing isn't so good, because it makes it **impossible to mentally associate** a specific _microzone_ of the window as dedicated to a specific operation. And this is potentially **dangerous**, if you take into account the big problem 5 (below).
+
+#### 3\. The options pop-up menu on a partition uses only text labels, never a single icon
+
+A seemingly small detail, but which is actually quite important.
+A text string allows you to unequivocally understand what a certain key does, unlike what can happen when you only have icons, but **the best would be obtained** by combining the two things: **keys accompanied by icons**.
+
+<table><thead><tr><th>GParted</th><th>GNOME Disks</th></tr></thead><tbody><tr><td><img src="{{< assetsRoot >}}/Media/Partioning-Mar-2023/GParted-Context-Menu.png" alt="The context menu of a partition in GParted."></td><td><img src="{{< assetsRoot >}}/Media/Partioning-Mar-2023/GNOME-Context-Menu.png" alt="The options menu of a partition on GNOME Disks."></td></tr><tr>< td><strong>GParted does this for its contextual menus (at least on the most important items), and this allows you to immediately memorize the <strong>action</strong> corresponding to each option, and recall it immediately <strong>at a glance</strong>.</td><td>Personally, <strong>using GNOME Disks</strong> I always find myself <strong>having to re-read</strong> a good part of the list to select something, although it is no longer than that of GParted, precisely because <strong>the icons are missing</strong>.</td></tr></tbody></table>
+
+#### 4\. Hotkeys and pop-up menus are not alternatives to each other
+
+<table><thead><tr><th>GParted</th><th>GNOME Disks</th></tr></thead><tbody><tr><td><img src="{{< assetsRoot >}}/Media/Partioning-Mar-2023/GParted-Buttons.png" alt="The quick icon bar on GParted."></td><td><img src="{{< assetsRoot >}}/Media/Partioning-Mar-2023/GNOME-Buttons-1.png" alt="Buttons create and options on a partition in GNOME Disks."> <img src="{{< assetsRoot >}}/Media/ Partioning-Mar-2023/GNOME-Buttons-2.png" alt="Unmount buttons and options on a partition in GNOME Disks."> <img src="{{< assetsRoot >}}/Media/Partioning-Mar-2023 /GNOME-Buttons-3.png" alt="Block and options buttons on a partition in GNOME Disks."> <img src="{{< assetsRoot >}}/Media/Partioning-Mar-2023/GNOME-Buttons- 4.png" alt="Options button on a partition in GNOME Disks."></td></tr><tr><td>On <strong>GParted</strong> you first have the <strong>task bar menu</strong> (of which various menus can also be recalled as contextual in some areas), which truly contains <strong>all the operations</strong> possible in the program; only <strong>the</strong> is there a bar with <strong>icons</strong> useful for quickly recalling the probably most common actions. In practice, as long as you have the menu bar, <strong>you can</strong> even <strong>forget</strong> about the existence of <strong>those little icons</strong> there.</td>< td>With <strong>GNOME Disks</strong> this is <strong>not possible</strong>. Actually, on <a href="https://duckduckgo.com/?q=gtk3+examples&ia=images&iax=images" rel="noopener nofollow" target="_blank">several GTK3 apps</a> it is like this: there are <strong>actions</strong> fixed to <strong>label-keys</strong> in a menu, and others fixed to <strong>icon-keys</strong> directly visible. Generally, however, those buttons do not <strong>disappear or partially appear</strong> when the state changes within the same application view! Maybe I have strange tastes, but this thing messes with my brain when using the software.</td></tr></tbody></table>
+
+To understand, just compare the buttons in this table to the contextual menu options seen in the one above!
+
+## What have I done?
+
+All these factors together led to a huge **patatrac**!
+So, what do I do? I need to **unmount** the **partition**, before I can **resize** it.
+
+I go from **disk view**, and there is **only the button** for the **options** menu - plus what will come to mind _only after_ when I will have **already broken** by now to break up , is the button to **destroy** the partition.
+In the list of options I read everything and **I don't even see** an entry to **unmount** the partition. _Meh_.
+
+I go through the **screen** dedicated to that mounted **partition**, and I call up that menu again for I don't know what reason, and rightly so I still can't find anything.
+Next to the options menu button **there was in theory the stop button**, to unmount the partition, but it is clear that I really **didn't** notice it**.
+
+I go **back and forth** between the two screens about ten times, and nothing, I'm really **blind**.
+
+At a certain point, my unconscious gets bored of all this **circling**, and finally allows me to notice another **button**... the dangerous **red** one. _Ouch ouch_.
+I press it and honestly I don't even remember if I delete the confirmation dialogue once - which I was absolutely in no psychological condition to read - and then I press the button again for immediately afterwards confirm the dialogue, but one thing is clear:
+
+If up until that moment I couldn't think straight, because **with every breath** a rough **"WTF?!"** rang in my head, it was a matter of a few seconds from the moment of the **fatal click** because a **bad feeling** began to appear in my pierced, deformed head, full of expired peanuts... 😰️
+
+...Well, so what? What is it?
+...
+_Ohhhhah_, okay, **you win**. I admit it: **I hit too**. Yes. Happy? In the end I moved the hand to click, of course... But in my life **I have done** these operations **many times**! Even using GNOME Disks, sometimes among many! 😭️
+
+In any case, no, I won't put all the blame on **poor Octt** from three days ago. Now I play my _trap card_, and expose the real **touch of misfortune** without which I would probably have saved myself:
+
+#### 5\. Each action is performed when you request it, there is no queue
+
+I must admit that sometimes **in GParted** I have come close to tragedy** - but really tragedy, not like this time which, all things considered, I'm still experiencing.
+The difference, however, lies precisely in this little word: with **GParted** the disaster has always at most **_almost_** happened, but with **GNOME Disks** this time it has **consumed** and that's it.
+
+On **GParted** the operations you order end up in a **queue**, which must be manually applied once you decide to continue.
+And here too, we are down to the ** minutiae **, yet something like this weighs heavily on the final bill. We can see it like this: **in that case**, you have to **make a mistake** two (**2**) **times** to make a mess, while with the GNOME program one (1) mistake is enough.
+
+![The operation queue view on GParted.]({{< assetsRoot >}}/Media/Partioning-Mar-2023/GParted-Queue.png)
+
+## "Is there any damage?"
+
+In any case, I noticed that, **after** giving the order to **delete the partition**, it **remained** mountable, and the file system was all **navigable**.
+Probably, what Linux needed to use the partition remained in memory (RAM), and since all the data was never deleted with a simple quick deletion of a partition, it was all still readable.
+
+To be honest, looking at the situation like this I **wasn't even** realizing** the reality, I still **didn't understand** whether my **data** had been **condemned** or not. ..
+Unclear interface, _I said so_.
+
+As the feeling of rush passed and gave way to **discomfort**, I searched for GParted**, found that it's included in the live system, and started it.
+Instead of the partition I see "empty space"... oh **yes, it's done**. But how come he let me **delete the partition** without** forcing me to **unmount** it first? What barbarism! GParted doesn't allow this, for good reasons.
+
+Yet, deep down, I still **haven't accepted** that it was cancelled.
+I want to see if, after a reboot, it disappears permanently.
+
+And so it is, **without** even **worrying** about copying a shred of file - because it was about late and I had to get ready to go to sleep - that I **restart**.
+Oh yes, I see the GRUB black screen, and not the system booting! ...**It's all lost**, there's no point in going around it now.
+
+"_After you did the damage did you think about restarting immediately without even saving the most important files?!?! But then you're a certified bruh-idiot, twice, not once!_"
+_Ooooooooooooo_, how dare you? How dare YOU be **so right** if the blog is MINE??
+
+The only thing we can do now is the **damage count**. I have not lost unique and very important data, what I **no longer have I should** in theory be able to **redownload or reconstruct**. Let's talk about:
+
+* 40 GB of data exported from my old Google account; account that I planned to delete, but I hadn't finished transferring everything and so I think it's **all still in the cloud**.
+
+* Various large and small **files** downloaded **from the Web**, possibly some hard to find, but **nothing vital**.
+
+* **Source codes changed**; we're talking about porting attempts for obscure platforms that I tried and failed, or other **very forgettable experiments**.
+
+* **Dumps of disks** that I still have at home (some already uploaded to [Archive.org](https://archive.org/details/@andrigamerita)), **or additional copies** of other data.
+
+* Documents whose current **relevance** is **nil**.
+
+
+If I **forgot something** important in this list, however, maybe maybe it **wasn't important**, and we can rest assured. Otherwise I would remember, right? _Well, knowing me..._
+
+## Avoid...
+
+The **moral** of this **bad story** can be condensed into:
+
+1. Avoid GNOME Disks.
+2. **Be careful** when dealing with partitions, even if you have done it 50 times in the past.
+3. **Avoid**, absolutely, **GNOME Disks**!
+
+And I close with a **advice**, or rather, a **development philosophy**, that all those who design **UI** (even I, in my things, don't hide it) forget too often: [The user is drunk](https://www.youtube.com/watch?v=r2CbbBLVaPk).
+
+<iframe src="https://www.youtube-nocookie.com/embed/r2CbbBLVaPk" style="height: calc(100vh / 16 * 9);" class="YouTube"></iframe>
+
+So, greetings. For the future I **hope** not to **lose data** in a stupid way (to you, and to me!). 👋
+
+_**P.S:** The Linux distribution I installed this time is [Pop!\_OS](https://pop.system76.com/). I really wanted to try it, but on 2 occasions I tried to install it on the desktop PC and it always gave an error. Here on the laptop it worked, wow, so it's not a broken distro! (**Maybe** 👀)_
+
+## {{% i18n notes-refs %}}
+
+---
+
+1. The system I had up to that point, Linux Mint, version 19.3, after 3 years:
+
+<dl><dt><strong>It has become stale:</strong></dt><dd>Version 19.3 is discontinued, and the repositories no longer receive new software. So, I should have upgraded to the current version of Mint, but apparently <strong>I should have anyway</strong> done it by reinstalling <strong>from scratch</strong> (on <code class="prettyprint">apt dist-upgrade </code> there are no new updates)</dd><dt><strong>It's broken:</strong></dt><dd>Some things (like broken video drivers, and the desktop environment that only starts in fallback mode) are definitely my fault (<em>I screwed up</em> with the drivers <a href="https://en.wikipedia.org/wiki/Nvidia#:%7E:text=Nvidia" rel="noopener nofollow" target="_blank">ACCIDIA</a> in recent weeks), but others (Bluetooth no longer working!?) I would say no :/. In any case, <strong>when the system is so broken, it's quicker to reinstall everything</strong>...</dd></dl>
+
+ [↩](#fnref1)
+
+2. Maybe yes, I'm an idiot, but not to the point of voluntarily setting up the partitions with a structure that's alien to me. At the time, very simply, I installed Linux Mint with the default guided settings. Whenever I installed Linux I used manual partitioning, instead of choosing to erase the entire disk and let the installation program decide things, I instead always created normal partitions. So... **don't blame me**, [kthx](https://en.m.wiktionary.org/wiki/kthx#:%7E:text=\(Internet%20slang\)%20Abbreviation %20of%20okay%2C%20thanks.)? [↩](#fnref2)
diff --git a/en/blog/2023-04-16-Che-Impatto-Nuova-Legge-Anti-Pirateria-Italiana.md b/en/blog/2023-04-16-Che-Impatto-Nuova-Legge-Anti-Pirateria-Italiana.md
index 0cedce4..91a3486 100644
--- a/en/blog/2023-04-16-Che-Impatto-Nuova-Legge-Anti-Pirateria-Italiana.md
+++ b/en/blog/2023-04-16-Che-Impatto-Nuova-Legge-Anti-Pirateria-Italiana.md
@@ -1,12 +1,12 @@
 +++
-Title= "🏴‍☠️ What impact will the new Italian anti-piracy law have?"
-Date= 2023-04-16
-Downsync= "/it/blog/Che-Impatto-Nuova-Legge-Anti-Pirateria-Italiana.html"
-Aliases= [ "/Posts/2023-04-16-Che-Impatto-Nuova-Legge-Anti-Pirateria-Italiana.html" ]
-Description= "They have approved a law in Italy for a strong fight against piracy. The fact is that it entails important risks for Internet users."
-Featured_Image= "@/Media/Misc/Keep-Seeding-Monitor.webp"
-Categories= [ "Internet" ]
-Lastmod= 2023-04-17
+Title = "🏴‍☠️ What impact will the new Italian anti-piracy law have?"
+Date = 2023-04-16
+Downsync = "/it/blog/Che-Impatto-Nuova-Legge-Anti-Pirateria-Italiana.html"
+Aliases = [ "/Posts/2023-04-16-Che-Impatto-Nuova-Legge-Anti-Pirateria-Italiana.html" ]
+Description = "They have approved a law in Italy for a strong fight against piracy. The fact is that it entails important risks for Internet users."
+Featured_Image = "@/Media/Misc/Keep-Seeding-Monitor.webp"
+Categories = [ "Internet" ]
+Lastmod = 2023-04-17
 +++
 
 {{< noticeAutomaticTranslation it >}}
@@ -15,78 +15,66 @@ Lastmod= 2023-04-17
 
 <!-- Autogenerated by ListedDownsync.js. Do not edit (unless also set "% Downsync = False") - it would be overwritten. -->
 
-<p>Some will know, in Italy the <strong>new anti-piracy law</strong> has been <strong>approved</strong>, and now the <strong>doubts</strong> with which we enthusiasts of sharing free we have to deal with are different:</p>
+Some will know, in Italy the **new anti-piracy law** has been **approved**, and now the **doubts** that we enthusiasts of free sharing have to deal with are different:
 
-<ul>
-<li>When will it come into force? (I hope not exactly at the time I'm writing this post 😰)</li>
-<li>How much money will the entertainment lobbies have spent to ensure that the law was passed with total unanimity?</li>
-<li>What <strong>real consequences</strong> will it bring to us <strong>ordinary citizens</strong>?</li>
-</ul>
+* When will it come into force? (I hope not exactly at the time I'm writing this post 😰)
+* How much money will the entertainment lobbies have spent to ensure that the law was passed with total unanimity?
+* What **real consequences** will this bring to us **ordinary citizens**?
 
+## Blocks (instant and per IP)
 
+The point that perhaps struck me most about the law (here [the PDF examined by the Commission](https://documenti.camera.it/leg19/pdl/pdf/leg.19.pdl.camera.217_A.19PDL0028100.pdf) , and [the final report](https://temi.camera.it/leg19/dossier/OCD18-17872/disposizioni-contrasto-illecita-trasmissione-o-diffusione-diretta-e-della-fruizione-illegale-contenuti- protected-by-right-d.html)) - perhaps because I own various online properties, totally personal, which have zero economic value for me, but unquantifiable sentimental value - it is the **obligation for the providers** of Internet services to respond to **instant block requests**.
 
-<h2>Blocks (instant and per IP)</h2>
+A **copyright** holder can send a **blackout request** which, when it is **urgent** - think of a live sports match, which is being illegally rebroadcast in real time - must be honored in **no later than 30 minutes** by all providers, without **any adversarial or formal process**: it will be **the owner** of the blocked website who will then have to open legal proceedings for * *dispute the block** and request reinstatement.  
+For illicit sites, all **domain and subdomain names** (DNS), and **IP addresses**, present and, I have no idea according to what limits, all possible future ones are blocked.
 
-<p>The point that perhaps struck me most about the law (here <a href="https://documenti.camera.it/leg19/pdl/pdf/leg.19.pdl.camera.217_A.19PDL0028100.pdf" rel="noopener nofollow" target="_blank">the PDF examined by the Commission</a>, and <a href="https://temi.camera.it/leg19/dossier/OCD18-17872/disposizioni-contrasto- illicit-direct-transmission-or-dissemination-and-illegal-use-of-contents-protected-by-law-d.html" rel="noopener nofollow" target="_blank">the final report</a>) - perhaps because I own various online properties, totally personal, which have zero economic value for me, but unquantifiable sentimental value - it is the <strong>obligation for Internet service providers to respond to <strong>blocking requests snapshots</strong>.</p>
+### The new responsibilities
 
-<p>A <strong>copyright</strong> holder can send a <strong>blackout request</strong> which, when it is <strong>urgent</strong> - think of a meeting live sports, which is being illegally retransmitted in real time - must be honored in <strong>no more than 30 minutes</strong> by all providers, without <strong>any adversarial or formal process</strong>: it will be <strong> >the owner</strong> of the blocked website will then have to open legal proceedings to <strong>challenge the blocking</strong> and request its restoration.<br>
-For illicit sites, all <strong>domain and subdomain names</strong> (DNS), and <strong>IP addresses</strong>, present will be blocked and, I have no idea under what limits , all possible futures.</p>
+By "suppliers" we do not mean only telephone operators, who provide the connection to the Internet, but in general those "**involved in any capacity in the accessibility**" of illegal services, and explicit reference is even made to ** search engines**.
 
-<h3>The new responsibilities</h3>
+Search engines do nothing other than return _links_ accompanied by a description, and actually **do not** directly provide **pirated material**: in practice, this law even aims to **hinder those who only provide links**, not just those who allow the downloading of data physically.
 
-<p>By "suppliers" we do not mean only the telephone operators who provide the connection to the Internet, but in general those "<strong>involved in any capacity in the accessibility</strong>" of illegal services, and it is even explicit reference to <strong>search engines</strong>.</p>
+For this logic, the managers of **_social networks_** will also be held **responsible** (and I imagine that "information society" in the text refers precisely to them), and possibly **small communities* * online.
 
-<p>Search engines do nothing but return <em>links</em> accompanied by a description, and in reality <strong>they do not directly provide <strong>pirate material</strong>: in practice , this law even aims to <strong>hinder those who only provide links</strong>, not just those who physically allow the downloading of data.</p>
+### An expensive firewall
 
-<p>For this logic, the managers of <strong><em>social networks</em></strong> will also be held <strong>responsible</strong> (and I imagine that with "information society" in text refers specifically to them), and possibly <strong>small online communities</strong>.</p>
+The **potential for abuse and errors** is very high, and in fact, viewed impartially, this move can in any case be summarized as the **obligation** for ISPs to **build a [mega-firewall] (https://torrentfreak.com/anti-piracy-mega-firewall-could-render-italian-isps-liable-for-over-blocking-230413/)**, for all intents and purposes under the **control** last **of the State**, with all the other **problems** that derive from it (even accidental).  
+Sooner or later an **over-blocking** incident will happen, and there will be **problems with Web services** that have nothing to do with piracy, if they start messing with IPv4 address blocks.
 
-<h3>An expensive firewall</h3>
+In any case, a **big hit** will probably be seen **on everyone's bill**, even those who do not consume or share pirated material!  
+**Centralizing a network** that has existed for decades, built from the beginning as decentralized, is **a tough business**, and other states that work to control information know this well.
 
-<p>The <strong>potential for abuse and errors</strong> is very high, and in fact, seen impartially, this move can in any case be summarized in the <strong>obligation</strong> for ISPs to <strong>build a <a href="https://torrentfreak.com/anti-piracy-mega-firewall-could-render-italian-isps-liable-for-over-blocking-230413/" rel="noopener nofollow " target="_blank">mega-firewall</a></strong>, to all intents and purposes under the <strong>ultimate control</strong> of the State</strong>, with all the others <strong> >problems</strong> that arise from it (even accidental).<br>
-Sooner or later an <strong>over-blocking</strong> incident will happen, and there will be <strong>problems with Web services</strong> that have nothing to do with piracy, if they start messing around with address blocks IPv4.</p>
+An **example** can be given by comparing Russia and China: both states have a certain **desire to control** political dissent on the Internet, but:
 
-<p>In any case, a <strong>big hit</strong> will probably be seen <strong>on everyone's bill</strong>, even those who do not consume or share pirated material!<br>
-<strong>Centralizing a network</strong> that has existed for decades, built from the beginning as decentralized, is <strong>a tough business</strong>, and other states that work to control information know this well .</p>
+* For **Russia it is difficult**, as it has a more **traditional** Internet **infrastructure**, which began to develop as decentralized well **before Putin's arrival**, when the present government was of another type.
+* For **China it is easier**, because the government in office **at the time** (the Communist Party, like today), understood the potential of the Internet, and ensured that development took place **immediately ** according to a **centralized** scheme.
 
-<p>An <strong>example</strong> can be given by comparing Russia and China: both states have a certain <strong>desire to control</strong> political dissent on the Internet, but:</p >
+It is therefore inevitable that raising this _mega-wall-of-fire_ now, out of nothing_, will entail **substantial costs**, which however will be at the **total expense** of all of us **consumers**, instead of being at expenses of the billion-dollar entertainment multinationals (which will only be burdened by the costs of the unified state platform that will connect rights holders and ISPs).
 
-<ul>
-<li>For <strong>Russia it is difficult</strong>, as it has a more <strong>traditional</strong> Internet infrastructure, which began to develop as decentralized well < strong>before Putin's arrival</strong>, when the present government was of a different type.</li>
-<li>For <strong>China it is easier</strong>, because the government in office <strong>at the time</strong> (the Communist Party, like today), understood the potential of the Internet, and made sure that development took place <strong>immediately</strong> according to a <strong>centralized</strong> scheme.</li>
-</ul>
+But this last detail, rightly, does not matter to our parliamentarians and senators, who fortunately for many years have received respectively [1200 and 1650 € per year just for telephone costs](https://www.laleggepertutti.it/ 353259_how-much-do-parliamentarians-earn), thanks to those of us, idiot citizens, who pay taxes.
 
-<p>It is therefore inevitable that raising this <em>mega-wall-of-fire</em> now, out of nothing, will entail <strong>substantial costs</strong>, which however will be at the <strong>total expense< /strong> of all of us <strong>consumers</strong>, instead of being at the expense of billion-dollar entertainment multinationals (which will only be burdened by the costs of the unified state platform that will connect rights holders and ISPs).</p >
+## Hunting for users
 
-<p>But this last detail, rightly, does not matter to our parliamentarians and senators, who fortunately for many years have received respectively <a href="https://www.laleggepertutti.it/353259_quanto-guadagnano-i -parliamentarians" rel="noopener nofollow" target="_blank">1200 and 1650 € per year just for telephone costs</a>, thanks to those of us, idiot citizens, who pay taxes.</p>
+In addition to wanting to **counter** in a specific and now unequivocal way the "**live broadcast**" of duplicate content - something that is already generating **discontent** among those football fans with a **tight budget* * - apart from the usual contents in general (audiovisual, press, or IT), the law expressly goes **against end users**, [at least a certain category](https://torrentfreak.com/ew- pirate-iptv-bill-moved-to-senate-as-italy-takes-on-digital-mafias-230324/).
 
+In fact, **fines of up to €5000** are foreseen in case of repeat offenses, for those who (as far as I can understand, from reading the law and watching other people's videos and articles), purchase subscriptions to paid pirate services, like the famous "**pezzotti**", the illegal _IPTV_ packets.
 
+### Are some okay?
 
-<h2>Hunting for users</h2>
+All in all, despite the initial general fear and alarmism, it seems that the only users who have something to fear are precisely the latter, because - although it must be said that I know relatively little about the law, and it is not easy to apply generic understanding skills some text on legal bricks, so who knows - the **text talks about buying or renting**, and **not** even things like **downloading for free**.
 
-<p>In addition to wanting to <strong>counter</strong> in a specific and now unequivocal way the "<strong>live broadcast</strong>" of duplicate content - something that is already generating <strong>discontent</strong> among those football fans with a <strong>tight budget</strong> - apart from the usual content in general (audiovisual, print, or IT), the law expressly goes against end users , <a href="https://torrentfreak.com/ew-pirate-iptv-bill-moved-to-senate-as-italy-takes-on-digital-mafias-230324/" rel="noopener nofollow" target ="_blank">at least a certain category</a>.</p>
+If, therefore, up to now, surfing the Internet to **find links** to "crunchy" football matches, with pixels as big as biscuits and the habit of _buffering_, has never actually been prohibited, or **download** the tenth movie of the week via _torrent_, or even **stock up** on repackaged video games for free, one can well imagine that **things will remain as they are** in this sense.
 
-<p>In fact, <strong>fines of up to €5000</strong> are foreseen in the event of a repeat offense, for those who (as far as I can understand, from reading the law and watching other people's videos and articles) purchase subscriptions to paid pirate services, such as the famous "<strong>pezzotti</strong>", the illegal <em>IPTV</em> packages.</p>
+#### ...Maybe not at all
 
-<h3>Are some okay?</h3>
+Decidedly **less calm** moments could instead be experienced by those who **participate in sharing** copied content, even with a torrent left in _**seeding**_.  
+In Italy it seems that no single _seeder_ has **never been prosecuted**, nor has their connection ever been blocked, but with the authorization to **block** of **IP addresses** the situation risks **changing **, and perhaps from today ISPs will have to **stop trashing** lawyers' letters**; if not the hundreds who arrive every day from the United States, with the presumption of wanting a US-only law to be respected in Europe (the [DMCA](https://en.wikipedia.org/wiki/Digital_Millennium_Copyright_Act)), at least those few Italian annuals do (assuming they actually exist!).
 
-<p>All in all, despite the initial fear and general alarmism, it seems that the only users who have something to fear are precisely the latter, because - although it must be said that I know relatively little about the law, and it is not easy to apply generic text comprehension skills on legal bricks, so who knows - the <strong>text talks about purchasing or renting</strong>, and <strong>not</strong> also things like <strong>downloading at no cost</strong> >.</p>
+## Not only the "digital mafia" will suffer
 
-<p>If, therefore, up to now, surfing the Internet to <strong>find links</strong> to "crisp" football matches, with pixels has never actually been prohibited as big as biscuits and the habit of <em>buffering</em>, or <strong>download</strong> the tenth film of the week via <em>torrent</em>, or even <strong>stocking up</strong> > of free video games repackaged, one can well imagine that <strong>things will remain as they are</strong> in this sense.</p>
+Those who **are worse off** in this whole story are certainly the members of the "**digital mafia**" - as Massimiliano Capitanio, commissioner of [AGCOM] calls it(https://it.wikipedia.org/wiki /Autorit%C3%A0_per_le_garanzie_nelle_communications) - i.e. those who **sell premium** pirated packages, **profiting**: for them, **fines of up to €15.5m** and **prison of up to 3 years** .
 
-<h4>...Maybe not absolutely</h4>
+Perhaps, if this new law targeted **only them**, there wouldn't be much to discuss: they have no passion for sharing, only that of **money* *.  
+Perhaps you wouldn't object much even if, by going against the platforms that make certain links available, you considered acting **only against** those **profit-making companies**: Google, Microsoft (with Bing), Facebook, Twitter, and so on.
 
-<p>Definitely <strong>less peaceful</strong> moments could be experienced by those who <strong>participate in the sharing</strong> of copied content, even with a torrent left in <em><strong>seeding</strong> ></em>.<br>
-In Italy it seems that no single <em>seeder</em> has ever been prosecuted, nor has his connection ever been blocked, but with the authorization to <strong>block</strong> <strong>IP addresses</strong> the situation risks <strong>changing</strong>, and perhaps from today ISPs will have to <strong>stop throwing away</strong> lawyers' letters</strong> ; if not the hundreds who arrive every day from the United States, with the presumption of wanting a US-only law to be respected in Europe (the <a href="https://en.wikipedia.org/wiki/Digital_Millennium_Copyright_Act" rel=" noopener nofollow" target="_blank">DMCA</a>), at least those few Italian annuals do (assuming they really exist!).</p>
-
-
-
-<h2>It's not just the "digital mafia" that will suffer</h2>
-
-<p>Those who are worse off in this whole story are certainly the members of the "<strong>digital mafia</strong>" - as Massimiliano Capitanio, commissioner of <a href="https, calls it ://it.wikipedia.org/wiki/Autorit%C3%A0_per_le_garanzie_nelle_comunicazioni" rel="noopener nofollow" target="_blank">AGCOM</a> - that is, those who <strong>sell premium pirated packages</strong> , <strong>profiting</strong>: for them, <strong>fines of up to €15.5m</strong> and <strong>prison of up to 3 years</strong>.</p>
-
-<p>Perhaps, if this new law targeted <strong>only them</strong>, <strong>there wouldn't be much to <strong>discuss</strong>: <strong>they have no passion </strong> for sharing, only that of <strong>money</strong>.<br>
-Perhaps there would not be much of an objection even if, by going against the platforms that make certain links available, we considered acting <strong>only</strong> against those <strong>profit-making companies</strong>: Google, Microsoft ( with Bing), Facebook, Twitter, and so on.</p>
-
-<p>But in Italy they have already <em>blown up</em> TNTVillage, and I don't want the <strong>decimation</strong> of all the other <strong>online marketplaces</strong> created < strong>by the people for the people</strong> - non-profit, and indeed <strong>often disposable</strong>, both in time and money - just because <strong>it bothers someone</strong> that the <strong>main functionality of the Web</strong> is used: hypertext links, invented to encourage the <strong>free and free sharing</strong> of culture and entertainment, <strong>without barriers</strong>. </p>
-
-<hr>
\ No newline at end of file
+But in Italy they have already _blown up_ TNTVillage, and I don't want the **decimation** of all the other **online squares** created **by the people for the people** - non-profit, and indeed **often wasteful**, both in time and money - just because **someone is annoyed** by using the **main functionality of the Web**: hyperlinks, invented to encourage **free sharing and free** of culture and entertainment, **without barriers**.
\ No newline at end of file
diff --git a/en/blog/2023-05-02-Piu-Che-un-Esame-Ho-Fatto-una-Guerra.md b/en/blog/2023-05-02-Piu-Che-un-Esame-Ho-Fatto-una-Guerra.md
index 9845558..d131570 100644
--- a/en/blog/2023-05-02-Piu-Che-un-Esame-Ho-Fatto-una-Guerra.md
+++ b/en/blog/2023-05-02-Piu-Che-un-Esame-Ho-Fatto-una-Guerra.md
@@ -1,11 +1,11 @@
 +++
-Title= "😭 More than an exam, I went to war."
-Date= 2023-05-02
-Downsync= "/it/blog/Piu-Che-un-Esame-Ho-Fatto-una-Guerra.html"
-Aliases= [ "/Posts/2023-05-02-Piu-Che-un-Esame-Ho-Fatto-una-Guerra.html" ]
-Description= "Because of people who don't know how to read the rules, demons came to me while I was taking an exam that was supposed to be very easy."
-Categories= [ ]
-Lastmod= 2023-05-03
+Title = "😭 More than an exam, I went to war."
+Date = 2023-05-02
+Downsync = "/it/blog/Piu-Che-un-Esame-Ho-Fatto-una-Guerra.html"
+Aliases = [ "/Posts/2023-05-02-Piu-Che-un-Esame-Ho-Fatto-una-Guerra.html" ]
+Description = "Because of people who don't know how to read the rules, demons came to me while I was taking an exam that was supposed to be very easy."
+Categories = [ ]
+Lastmod = 2023-05-03
 +++
 
 {{< noticeAutomaticTranslation it >}}
@@ -14,79 +14,69 @@ Lastmod= 2023-05-03
 
 <!-- Autogenerated by ListedDownsync.js. Do not edit (unless also set "% Downsync = False") - it would be overwritten. -->
 
-<p>As <strong>the title</strong> suggests, this was the <strong>poetic thought</strong> dispensed by my mother today, after I returned home in the afternoon with a <strong>psyche</strong> > completely <strong>obliterated</strong>, unrecognizable.</p>
+As **from the title**, this was the **poetic thought** dispensed by my mother today, after I returned home in the afternoon with a completely **obliterated**, unrecognizable **psyche**.
 
-<p>Until 30 minutes before, <em>good maremma</em>, <strong>I just wanted</strong> to <strong>explode</strong>. Be careful, though: not for the exam itself (the last in a series of extra-curricular ones, precisely), very simple for me, which I don't care about except the certification!<sup id="fnref1">< a class="footnote-ref" href="#fn1">1</a></sup> Something else happened</strong>.</p>
+Up until 30 minutes before, _good Maremma_, I just **wanted** to explode**. Be careful, though: not for the exam itself (the last in a series of extra-curricular ones, precisely), very simple for me, which I don't care about except the certification!<sup id="fnref1">< a href="#fn1">1</a></sup> Something else happened.
 
-<h2>Let's go back</h2>
+## Let's go back
 
-<p>When I went through the first sessions <strong>two years ago</strong>, everything went <strong>very smoothly</strong>, almost in the name of <em><a href="https://www.urbandictionary .com/define.php?term=chill%20vibes" rel="noopener nofollow" target="_blank">chilling</a></em>: those were still the times of anti-COVID restrictions, and those 2 exams that I faced at school they were in a <strong>classroom</strong> which was however <strong>not very crowded</strong>.</p>
+When I went through the first sessions **two years ago**, everything went **very smoothly**, almost _[chilling](https://www.urbandictionary.com/define.php?term=chill%20vibes )_: those were still the times of anti-COVID restrictions, and those 2 exams I took at school were in a **classroom** that was not very crowded**.
 
-<p><strong>This year</strong>, however, <strong>crap</strong>. I took the card without repeating anything, so my parents didn't waste money on that matter, but the <strong>experience</strong> was <strong>terrifying</strong>.<br>
-The <strong>class</strong> at these rounds was always <strong>packed</strong>, and this very thing ended up being a <strong>problem for my soul</strong>.<br>
-I don't think I deserve all this...</p>
+**This year**, however, **crap**. I got the card without repeating anything, so my parents didn't waste money on that matter, but the **experience** was **terrifying**.  
+The **classroom** at these rounds was always **packed**, and this very thing ended up being a **problem for my soul**.  
+I don't think I deserve all this...
 
-<h3>There are problems in the air</h3>
+### Problems in the air
 
-<p><strong>Last month</strong> I took 2 tests out of the 3 I was missing, and already <strong>nothing went</strong> smoothly at all:</p>
+Last **month** I took 2 tests out of the 3 I was missing, and already **nothing** went smoothly, at all:
 
-<ol>
-<li><p>My professor (project contact) hadn't told me that I should have received a private link in the email address of the school domain to create an account on the online exam platform... Too bad that access I only have it at the post office on <a href="https://sitoctt.octt.eu.org/Posts/Archive/2022-05-07-Gli-Inspettiti-Vantaggi-della-Chiavetta-Linux.html" rel=" noopener nofollow" target="_blank">Puppy Linux thumb drive</a> and on the tablet, and I can't access anywhere else<sup id="fnref2"><a class="footnote-ref" href="#fn2" >2</a></sup>. Result: <strong>I had to rush</strong> home <strong>to get the tablet</strong> and go back to school... Luckily I live nearby.</p></li>
-<li><p>The <strong>testing platform totally broke</strong> when I finished one of the exams (not without difficulty, some questions were <em>[glitchate](<a href="https:// en.wikipedia.org/wiki/Glitch#Computer" rel="noopener nofollow" target="_blank">https://en.wikipedia.org/wiki/Glitch#Computer</a></em>glitch)_ !): as soon as I started the second one, the system said that I had run out of time, and closed the test I had just started in my face... The prof. he had to <strong>waste time</strong> calling support to explain the matter, and after quite a mess the exam was reset as not taken.</p></li>
-</ol>
+1. My professor (project contact) hadn't told me that I should have received a private link in the email address of the school domain to create an account on the online exam platform... Too bad I have access to email only on the [Puppy Linux stick](https://sitoctt.octt.eu.org/Posts/Archive/2022-05-07-Gli-Inexpetiti-Vantaggi-della-Chiavetta-Linux.html) and on the tablet, and I can't log in elsewhere<sup id="fnref2"><a href="#fn2">2</a></sup>. Result: **I had to rush** home **to get the tablet** and go back to school... Luckily I live nearby.
+    
+2. The **testing platform** totally broke when I finished one of the exams (not without difficulty, some questions were _\[glitchate\]([https://en.wikipedia.org/wiki/Glitch#Computer ](https://en.wikipedia.org/wiki/Glitch#Computer)_glitch)\_!): as soon as I started the second one, the system said that I had run out of time, and closed the test I had just started in my face. .. The prof. he had to **waste time** calling support to explain the matter, and after quite a mess the exam was reset as not taken.
+    
 
-<p>Between both things, then, a good amount of <strong>time</strong> was lost. And if it hadn't been like this, <strong>maybe</strong> I would have managed to finish <strong>all the exams that day</strong>.</p>
+Between both things, then, a good amount of **time** was **wasted**. And if that hadn't been the case, **maybe** I would have** made it through **all the exams that day**.
 
-<h2>The present</h2>
+## The present
 
-<p>Let's go back to today.<br>
-Once the hassle of waiting was over (not too problematic, thanks to the rectangle of plastic, glass, metal, with Internet connection, and pocket book, which I also always carry around), due to the fact that all the stations were occupied initially, <strong >start</strong>.<br>
-<em>...But I had never done it!</em></p>
+Let's go back to today.  
+Once the hassle of waiting was over (not too problematic, thanks to the rectangle of plastic, glass, metal, with Internet connection, and pocket book, which I also always carry around), due to the fact that all the stations were initially occupied, ** start**.  
+_...But I had never done it!_
 
-<p>My <strong>first few minutes</strong> go <strong>fine</strong>, <strong>until</strong> even a good selection (random, or did destiny choose them carefully?) of <strong>monkeys</strong>, who from the rows behind everything were <strong>babbling</strong> with those who (I imagine in confidence) had not yet finished, at an exaggerated volume and in contemporary.<br>
-Here, now, slowly, the <strong>blood</strong> starts to boil <strong>in my body, as if it were a coffee pot, because with that mess <strong>I can't read</strong> > half of a question <strong>without getting</strong> totally distracted. Even having earphones in my ears (but detached) didn't attenuate the noise enough. <strong>Finish the exam like that</strong>? <strong>Impossible</strong>.</p>
+My **first few minutes** go **fine**, **until** a good selection (random, or did destiny carefully choose them?) of **monkeys also start finishing the exam **, who from the rows behind everything were **babbling** with those who (I imagine in confidence) still hadn't finished, at an exaggerated volume and at the same time.  
+Here, now, slowly, the **blood** starts to **boil** in my body, as if it were a coffee pot, because with that mess **I can't read** half of a question **without getting distracted ** totally. Even having earphones in my ears (but detached) didn't attenuate the noise enough. **Finish that way** the exam? **Impossible**.
 
-<h3>I tried</h3>
+### I tried
 
-<p>Before it was too late, <strong>I tried</strong> to <strong>call the teacher</strong> — who, damn the <em>extreme</em>, was quite <strong>distracted </strong>, because another person at that moment had the same glitch as my previous time (and here I have to: what a shitty backend this platform has, throw it away and rewrite it from scratch, please!! !).<br>
-I wanted to <strong>kindly</strong> tell him to keep all those who had no right to speak in silence, and after a few minutes (to his credit, of his own accord, a moment before he heard me ) blathered something (unconvincing) to tell the audience to calm down. The audience <strong>did not calm down</strong>, and the prof. he was going crazy due to the general problems, unfortunately, so <strong>he could pay little attention</strong> to me.</p>
+Before it was too late, I **tried** to **call the teacher** — who, damn the _badass_, was pretty **distracted**, because another person at that moment had the same glitch happen of my previous time (and here I have to: what a shitty backend this platform has, throw it away and rewrite it from scratch, please!!!).  
+I wanted to **kindly** tell him to keep all those who didn't have the right to speak in **silence**, and after a few minutes (to his credit, of his own accord, a moment before he heard me) he babbled something (about unconvincing) to tell the audience to calm down. The audience **did not quiet down**, and the prof. he was going crazy due to the general problems, unfortunately, so **little could he listen** to me.
 
-<p>The <strong>last time</strong> there was <strong>less mess</strong>. Perhaps because there were fewer wrong individuals, perhaps because I was at the PC in the far corner of the room (which today was not turned on), perhaps because, given that there was an external commissioner, the rules could only be violated without making any noise. I don't know.</p>
+The **last time** there was **less mess**. Perhaps because there were fewer wrong individuals, perhaps because I was at the PC in the far corner of the room (which today was not turned on), perhaps because, given that there was an external commissioner, the rules could only be violated without making any noise. I do not know.
 
-<p>I even decide to <strong>call my father</strong> on the phone, upon arriving here, to tell him to <strong>call</strong> the professor on the phone; maybe this time around <strong>he can understand</strong>. In fact, this time the call for silence was more convincing. Was it?</p>
+I even decide to **call my father**, upon arriving here, to tell him to **call** the professor on the phone; maybe this time **he can understand**. In fact, this time the call for silence was more convincing. Was it?
 
-<h3>A disaster</h3>
+### A disaster
 
-<p>But, by now, <strong>too late</strong> anyway: my tension has risen too much, <strong>I can't regain</strong> a minimum of <strong>concentration</strong>, forcing myself, after perhaps a good 21 months in which I was able to do without it, scratching myself to convert a minimal part of the mental load (which requires major mental energies to be managed, the same ones that I needed at that moment to complete my session) into skin burning (which, to a certain level, is managed by the brain in the background). What a drag.</p>
+But, now, **too late** anyway: my tension has risen too much, **I am unable to regain** a minimum of **concentration**, forcing myself, after perhaps 21 good months in which I was able to do without it , scratching myself to convert a minimal part of the mental load (which requires major mental energy to be managed, the same that I needed at that moment to complete my session) into skin burning (which, up to a certain level, is managed by the brain in the background). What a drag.
 
-<p>I've already done the <strong>damage</strong>, <em>alas and what the fuck</em>, and it seemed that everything was slowly calming down and concentration could return... but instead No. The <strong>call</strong> of the prof. However, it was <strong>too soft</strong> and <strong>did not stop the bad behavior of that part of the other students, it just put them on hold a bit.</p>
+I've now done the **damage**, _alas and what the fuck_, and it seemed that everything was slowly calming down and concentration could return... but no. The **call** of the prof. it was however **too soft** and **didn't put down the bad** behaviors of that part of the other students, he just put them on hold a bit.
 
-<h3>The real solution</h3>
+### The real solution
 
-<p><strong>Well</strong>, at this point I simply feel like <strong>throwing a fist</strong> on the desk and "screaming" (not that I know how to do it, but the fist just makes up for the this is useful; <em>I unconsciously learned from another professor of mine</em>) to <strong>be silent</strong>, otherwise I wouldn't have been able to accomplish anything, and... <strong>it worked< /strong>. <em>Oh?...</em><br>
-Yes, <strong>that's all</strong>. I can't say anything else about this moment, it immediately crystallized into goodness. From there, until I finished and was able to leave, not a fly flew again.</p>
+**Dunno**, at this point I simply feel like **punching** the desk and "screaming" (not that I know how to do it, but the punch is needed to make up for this; _I unconsciously learned it from another professor of mine_) to **be quiet**, because otherwise I wouldn't have been able to accomplish anything, and... **it worked**. _Oh?..._  
+Yes, **that's all**. I can't say anything else about this moment, it immediately crystallized into goodness. From there, until I finished and could leave, not a fly flew again.
 
-<p>At that point, unfortunately, I had <strong>accumulated</strong> the <strong>irritation</strong> anyway, and it took me <em>hours and hours and <strong>hours</strong> ></em> <strong>to dispose of it</strong>, between doing various random things and writing this article.<br>
-The only thing I can logically <strong>regret</strong> is not having made that bench resonate a few precious minutes before</strong> seriously reaching the limit, given that gentle methods didn't work. Unfortunately or fortunately, damn, it's not <strong>a reflex that arises in me</strong> too often; <strong>only when</strong> I am already <strong>over</strong> that limit, and perhaps I have <strong>already committed other avoidable</strong> damage.</p>
+At that point, unfortunately, I had still **accumulated** the **irritation**, and it took me _hours and hours and **hours** to get rid of it**, between doing various things to case and writing this article.  
+The only thing I can logically **regret** is that I didn't ring that **bench a few precious minutes before** seriously reaching the limit, since the gentle methods didn't work. Unfortunately or fortunately, damn, it's not **a reflection that arises** too often; **only when** I am **already beyond** that limit, and perhaps I have **already committed other avoidable** damage.
 
-<hr>
+---
 
-<p>And yet, that doubt still remains: but <strong>what have I done</strong> that was so bad in the world <strong>to deserve</strong> these things? And let's understand...</p>
+Yet, that doubt still remains: but **what have I done** that was so bad in the world **to deserve** these things? And let me understand...
 
+## {{% i18n notes-refs %}}
 
+---
 
-<h2>{{% i18n notes-refs %}}</h2>
-
-<div class="footnotes">
-<ol>
-
-<li id="fn1">
-<p>The <strong>certification</strong>... oh God, even this last one, <strong>not that I care</strong> personally: on my <strong>deathbed I don't</strong> strong> I will certainly be <strong>counting the cards</strong> that I could have but didn't want to get; mainly my parents convinced me, so whatever. (<em>If <strong>even this were to expire</strong> before it can be seriously useful for anything, <strong>I'll be seriously pissed off</strong>, but never mind...</em>) < a href="#fnref1">↩</a></p>
-</li>
-
-<li id="fn2">
-<p><strong>It's Google's fault</strong> (GSuite, shit), the <strong>school network</strong> is not recognized as trustworthy and <strong>doesn't let me log in</strong>. That day I couldn't even log in from my smartphone by connecting to my home VPN, for some reason! <strong>I explained the general problem better</strong> in my <strong>article on the Puppy flash drive</strong>, however, so I'll refer you there for those who are interested. <a href="#fnref2">↩</a></p>
-</li>
-
-</ol>
-</div>
\ No newline at end of file
+1. The **certification**... oh God, even the latter, **not that I personally care**: on my **deathbed I certainly won't** be **counting cards ** which I could have but didn't want to get; mainly my parents convinced me, so whatever. (_If even this one **expires** before it can be seriously useful for anything, I'll really **be pissed** off, but never mind..._) [↩](#fnref1)
+    
+2. **Google's fault** (GSuite, shit), the **school network** is not recognized as trustworthy and **doesn't let me log in**. That day I couldn't even log in from my smartphone by connecting to my home VPN, for some reason! **I explained** the general problem better in my **Puppy stick article**, however, so I'll post it there for those who are interested. [↩](#fnref2)
\ No newline at end of file
diff --git a/en/miscellanea/Donazioni.md b/en/miscellanea/Donazioni.md
index 6a5f89b..a496810 100644
--- a/en/miscellanea/Donazioni.md
+++ b/en/miscellanea/Donazioni.md
@@ -1,10 +1,9 @@
 +++
 Title = "💰 Donations"
-Aliases = [
+Alias = [
   "/Donations.html",
 ]
-#Index: True
-#Order: 45
+Categories = [ "Meta" ]
 Lastmod = 2022-11-12
 +++
 
@@ -29,20 +28,20 @@ Open my Coindrop page to see the cryptocurrencies I accept and their addresses:
 _Note: Coindrop requires (free) JavaScript code to run. It's a problem that needs to be solved somehow, in my opinion, but for now this is it._
 
 _Note: ETH is listed for completeness, but the Ethereum network sucks and is unusable for fees; However, donations on the Binance network for that address are welcome._  
-Should I accept other currencies in the future, for example I would be interested in trying [Nano](https://nano.org), which claims to have a low environmental impact.
+I should accept other currencies in the future, for example I would be interested in trying [Nano](https://nano.org), which claims to have a low environmental impact.
 
 If you really want, you can choose to install, on your machines, mining software for the cryptocurrency you would like to donate to me, setting the program to send payments to my address. By following this path, you don't even need a wallet for the currency in question, and you will simply use your electricity to get the money to donate to me.  
 Bear in mind that I haven't been interested in mining for a while, so I don't know which programs to recommend, I would tell you to ask more experienced people. But please don't create a mining farm fueled by dead dinosaurs, oil, methane gas, I have no idea, just to donate to me (or, actually, don't do it in general, please)! The best would be to use a [Rasperino Solare](./Posts/2022-06-23-0000-Rasperino-Solare-ed-Altri-Esperimenti-Andati-a-Male.html), if you can.
 
 ## Donate via gift cards
 
-Another good way to exchange money over the Internet, in my opinion, is with gift cards.
+Another good way to exchange money via the Internet, in my opinion, is with gift cards.
 
 I am currently accepting gift cards for these stores:
 
 - Amazon.it
 
-To send me the code of a gift voucher that you have and would like to donate to me, consult the list of my public contacts, where you can message me and do nice things 😸: [Who-I-Am.html#-My-contacts](./Who -I'm.html#-My-contacts)
+To send me the code of a gift voucher that you have and would like to donate to me, consult the list of my public contacts, where you can message me and do nice things 😸: [Who-I-am.html#-My-contacts](./Who -I'm.html#-My-contacts)
 
 ## Donate via cash
 
@@ -52,7 +51,7 @@ At the moment, I definitely accept the following tax currencies:
 
 - [EUR] Euro
 
-The list here makes known the currencies that I definitely accept, because I have the opportunity to put them to good use.  
+The list here makes known the currencies that I definitely accept, because I have a way to put them to good use.  
 If you have cash of any other currency with you, and you really want to donate it to me anyway, I will probably accept it, but know that it is very likely that I will never be able to use it, and your donation will therefore have been in vain.
 
 ## Donation history
diff --git a/en/miscellanea/Raccolta-Videogiochi/_index.md b/en/miscellanea/Raccolta-Videogiochi/_index.md
index 3e4f505..ec12be2 100644
--- a/en/miscellanea/Raccolta-Videogiochi/_index.md
+++ b/en/miscellanea/Raccolta-Videogiochi/_index.md
@@ -5,7 +5,7 @@ Aliases = [
 ]
 Categories = [ "Gaming" ]
 #Style = @import "[staticoso:Site:RelativeRoot]Assets/Pages/Videogame-Collection.css";
-Lastmod = 2023-02-01
+Lastmod = 2024-09-20
 PagerSize = -1
 +++
 
@@ -52,4 +52,6 @@ I prefer to have this subsection to mention games that, although I liked them en
 _Titles that have only one of these two characteristics may also be found in sections above._
 -->
 
-It may be that I don't have the time, or maybe I don't want to, or maybe it's Antani's fault, but in any case there would be several other works that I haven't yet mentioned here. Perhaps you can easily find many of them on **OcttKB** anyway, under the tag [Gaming](https://kb.octt.eu.org/#Gaming).
\ No newline at end of file
+~~It may be that I don't have the time, or maybe I don't want to, or maybe it's Antani's fault, but in any case there would be several other works that I haven't yet mentioned here. Perhaps you can find many of them easily on **OcttKB** anyway, under the tag [Gaming](https://kb.octt.eu.org/#Gaming).~~
+
+There are also many other games, retro and modern, which I haven't explored in detail here (or haven't included at all), but they are available (with some encyclopedic information to accompany them) to be **played in the browser** on my site dedicated to gaming , **Sala Museo Games**: <https://gamingshitposting.github.io/SalaMuseoGames>!
\ No newline at end of file
diff --git a/en/miscellanea/Sul-sitoctt.md b/en/miscellanea/Sul-sitoctt.md
new file mode 100644
index 0000000..b50b5c8
--- /dev/null
+++ b/en/miscellanea/Sul-sitoctt.md
@@ -0,0 +1,212 @@
++++
+Title = "On sitectt"
+Lastmod = 2024-08-25
+#Template = WM.html
+#Style = @import "[staticoso:Site:RelativeRoot]Assets/Pages/index.css";
+Categories = [ "Meta" ]
+Featured_Image = "@/RichPreview/index.png"
++++
+
+{{< noticeAutomaticTranslation it >}}
+
+
+
+This here was initially the home page of the site, but it has become so problematically long that... never mind, everything is explained on the [new home](/). Here, therefore, is the classic series of loose information regarding the ✨sitoctt✨ (some of it old, it will be updated based on what's new)! 😊
+
+<!-- Credits: https://codepen.io/jh3y/pen/WNrXqYz -->
+<div style="Position:Relative;"><br/>
+<h1 class="NoTitle WavyText" style="--x: 6; --y: -6;"><span style="--index: 0; --alpha-l: 0.125; --alpha-u : 0.25;">✨</span><span style="--index: 1; --alpha-l: 0.125; --alpha-u: 0.25;">s</span><span style="- -index: 2; --alpha-l: 0.125; --alpha-u: 0.25;">i</span><span style="--index: 3; --alpha-l: 0.125; -u: 0.25;">t</span><span style="--index: 4; --alpha-l: 0.125; --alpha-u: 0.25;">o</span><span style= "--index: 5; --alpha-l: 0.125; --alpha-u: 0.25;">c</span><span style="--index: 6; --alpha-l: 0.125; - -alpha-u: 0.25;">t</span><span style="--index: 7; --alpha-l: 0.125; --alpha-u: 0.25;">t</span><span style="--index: 8; --alpha-l: 0.125; --alpha-u: 0.25;">✨</span>
+</h1>
+<h1 class="NoTitle WavyText" style="--x: 3; --y: -3;"><span style="--index: 0; --alpha-l: 0.25; --alpha-u : 0.5;">✨</span><span style="--index: 1; --alpha-l: 0.25; --alpha-u: 0.5;">s</span><span style="- -index: 2; --alpha-l: 0.25; --alpha-u: 0.5;">i</span><span style="--index: 3; --alpha-l: 0.25; -u: 0.5;">t</span><span style="--index: 4; --alpha-l: 0.25; --alpha-u: 0.5;">o</span><span style= "--index: 5; --alpha-l: 0.25; --alpha-u: 0.5;">c</span><span style="--index: 6; --alpha-l: 0.25; - -alpha-u: 0.5;">t</span><span style="--index: 7; --alpha-l: 0.25; --alpha-u: 0.5;">t</span><span style="--index: 8; --alpha-l: 0.25; --alpha-u: 0.5;">✨</span>
+</h1>
+<h1 class="NoTitle WavyText"><span style="--index: 0; --alpha-l: 0.5; --alpha-u: 1;">✨</span><span style="-- index: 1; --alpha-l: 0.5; --alpha-u: 1;">s</span><span style="--index: 2; --alpha-l: 0.5; u: 1;">i</span><span style="--index: 3; --alpha-l: 0.5; --alpha-u: 1;">t</span><span style=" --index: 4; --alpha-l: 0.5; --alpha-u: 1;">o</span><span style="--index: 5; alpha-u: 1;">c</span><span style="--index: 6; --alpha-l: 0.5; --alpha-u: 1;">t</span><span style ="--index: 7; --alpha-l: 0.5; --alpha-u: 1;">t</span><span style="--index: 8; --alpha-l: 0.5; --alpha-u: 1;">✨</span>
+</h1><br/>
+</div>
+
+Where does the name **✨**<strong class="MainIdTextGradientL">sitoctt</strong>**✨** come from?
+From the fact that it's literally my site, because I'm octt and so
+<i style="Color:#8040d0;">site</i> + <i style="Color:#d000d0;">octt</i>
+= **✨**<strong class="MainIdTextGradientR">sitoctt</strong>**✨**
+(<a href="{{< assetsRoot >}}/Media/sitoctt-pronunciation.flac" target="_blank" rel="noopener">pronunciation: "sitòctt"</a>).
+If you prefer, you can call it <i class="MainIdTextGradientL">sitocto</i>. Or even <i class="MainIdTextGradientR">postoctt</i>! This is still a place - my place - even if virtual!
+
+## Site status and how to navigate
+
+Despite already having a bit more substance, all this ambaradan is still heavily under construction. And it always will be, because I will always have new stuff to share. ~~And, when I am dead, it will still be unfinished because in my life I will not have written all the universal knowledge theoretically possible on the sitectt.~~
+Updates to the site are of different types: the publication of new blog articles happens, well, 3 times a month, it is a good idea to use <a href="#-Feed-e-notifiche">feeds</a> which I make available; changes for normal pages are continuous and happen at random, so you should check the ones that interest you perhaps every week, if you expect news.
+
+<p><b>To keep in mind</b> (from Web): when the following buttons are on the screen, it is because they can hide collapsible menus.
+They can be in different positions on different pages, because I like to experiment with different themes; but I try to keep their meaning consistent throughout.<br/>A stack of books emoji icon (<big class="twa twa-books twa-📚">📚</big>) signals the menu main page of the site, essential to be able to navigate by jumping between completely different and unconnected pages.
+Instead, the icon with the emoji of a sheet with a bookmark (<big class="twa twa-bookmark-tabs twa-📑">📑</big>) indicates the list of sections of the current page - it is not essential, but can be useful for jumping between different parts of a long text.
+</p>
+
+### Client-side scripting
+
+<p>The website does not use any client-side scripts for basic functions, because I don't want to force those (for valid security reasons and otherwise) who don't want to enable JavaScript to have a degraded experience. Regarding this thorny issue, I also wrote an article: <a href="Posts/2022-06-14-0000-I-Documenti-Non-Devono-Diventare-Applications.html"><span class="twa twa- page-facing-up"><span>📄</span></span> Documents should not become applications</a>.<br/>Anyway, though.. to provide some extra functionality, I have to have some JS, there is little you can do. Below is the list of what I use. <i>All files are uploaded from my site's servers, so it is difficult for malicious entities to hide malware inside</i>.</p>
+<details>
+<summary>
+<h4>List of client-side scripts used in the website (Expand)</h4>
+</summary>
+<div>
+<ul>
+<li>Internal scripts, written by me: <del>Auto-expanding menus on sitoctt themed pages in desktop mode</del> (I'm trying to fix this..), Full screen display of page backgrounds.</del> li>
+<li>
+<del>Polyfill to support AVIF images on older browsers: <a href="https://github.com/Kagami/avif.js" rel="noopener" target="_blank">avif.js by Kagami</ a></del> (<i>Not activated yet...
+<del>it will be soon</del> <small>when the hell will I do it? I've been putting it off for months, the problem is that it's not a plug-and-play solution, I have to understand it first and then create a wrapping script 😭</small></i>)
+</li>
+</ul>
+</div>
+</details>
+<p>Below, I put my ranking of the possible ways to view this site, from best to worst. By standardization, they all assume full color support (where possible).</p>
+<details>
+<summary>
+<h4>My useless digressions on absolutely absurd ways of consulting the sitectt (Expand)</h4>
+</summary>
+<div>
+<dl>
+<dt><b>• Web browser, with full CSS3 support</b></dt>
+<dd>(Perfect!)</dd>
+<dt><b>• Print on holographic paper, fully rendered GIF and CSS3 where possible</b></dt>
+<dd>(Requires moving the paper by hand but excellent!)</dd>
+<dt><b>• Web browser, with incomplete CSS3 support</b></dt>
+<dd>(Meh, OK..)</dd>
+<dt><b>• Print on plain paper, CSS3 animations and non-rendered GIFs</b></dt>
+<dd>(Boo, animations are missing..)</dd>
+<dt><b>• Old browser (Old Web, Text Web, or Gemini) / Print on plain paper, no CSS support </b></dt>
+<dd>(What is this rubbish?!?!)</dd>
+</dl>
+</div>
+</details>
+
+## But what is it about?
+
+On this Internet space of mine I will put everything. I hope.
+
+For now, I definitely put up shallow pages on specific topics, but also long, conversational blog posts. I also want to put up lots of collections on the things I like, in both textual and media form. A kind of gallery of things that are valuable to me.
+
+In addition to the actual contents, however, I want the site (the Web version, obviously) to be a gallery of itself. I want to create something that has its own unique character, like the amateur websites of the years 1995-2005, where every place on the Internet always had a different atmosphere from everything visited a moment before.<br/><span style="Color :#404040;">The rise of social media as we have them today has unfortunately ruined the web from this point of view, leading to complete standardization and the death of creativity expressed through form.</span><br/>I want this web space of mine is different from all the others, characterized by monochromatic text and recycled themes, because it is a shame to have very powerful tools and not really exploit them.
+
+For this reason, I will constantly try to invent ways to embellish the pages with CSS, not only with layout or fixed text effects, but above all with animations.<br/>To the rest of the form, such as the tree order of the pages on the site or paragraphs on the pages, I won't think much, otherwise I get distracted from creating content and the desire passes.
+
+## Site availability
+
+At the moment, this site is available for browsing on various different addresses (the contents are always identical).
+For those who don't know, however, the name changed a month ago to sitoctt from postoctt, because the old name gave me the impression of some postal service...
+I should also think about many other cloud mirrors from different providers (obviously free), if I want the site to survive octt itself and stand the test of time... But this is a long question.
+
+### Web
+
+<p>The website is available from several sources.</p>
+<ul>
+<li>On the <b>clearweb</b> HTTPS, on the <span style="Color:#fc6d26;">GitLab</span> servers: <a href="https://sitoctt.octt.eu. org">sitoctt.octt.eu.org</a>.</li>
+<li>On the <b>Onion Web</b> (<span style="Color:#59316b;">Tor</span>), on Replit servers: <a href="http://sitoctt2fxjvx3lc2iqqef2aeulflprjaasv2xl4zi7sxxbmvjy5b5yd. onion">sitoctt2fxjvx3lc2iqqef2aeulflprjaasv2xl4zi7sxxbmvjy5b5yd.onion</a>. In the end it is no longer hosted in my house, but maybe it's for the best, it's one less load for the poor little makeshift server I have (at the moment,
+<del>a Nintendo Switch console with Ubuntu</del> the Raspberry Pi 3).
+</li>
+</ul>
+<details>
+<summary>
+<h4><span class="twa twa-💾"><span>💾</span></span> Compatibility options for obsolete or exotic systems (Expand)</h4>
+</summary>
+<div>
+<dl>
+<dt><b>• Basic HTTP version</b></dt>
+<dd>The site includes complex and relatively modern CSS functions, in order to provide epic graphic (and functional) effects. Ironically, although viewing the pages on really old browsers, which lack total or almost total CSS support, everything looks ugly but is readable... on browsers that are <i>both too old and too new</i > very serious bugs appear, which make it impossible to use some menus or even read the text!<br/>In addition to the fact that (where possible) I want to support old systems, these damned problems also appear on less popular but current devices, like the Kindle! In short, for too many browsers that do not include a setting to completely disable CSS, it was a must to do what I did: to the path <a href="./Plain">/Plain</a> on my domains clearweb there is a parallel root, and pages with the same content but CSS reduced to the bare bones.</dd>
+<dt><b>• Unencrypted HTTP</b></dt>
+<dd>To avoid problems I dedicated a dedicated subdomain to it, keeping HTTPS forced on the main one; but, since it doesn't require maintenance, I made sure that from the fifth (!) level domain "<span style="Font-Style: Monospace;">http</span>" you can access the site via unencrypted HTTP ( hosted by GitHub, this time): in short, the address is <code style="Text-Decoration:Underline;">http://http.sitoctt.octt.eu.org</code>. The contents are identical, of course, but finally you can browse the sitectt on stuff like <i>Internet Explorer 4</i> directly by contacting the server.</dd>
+</dl>
+</div>
+</details>
+
+### Gemini
+
+<p>From now on, the CTTT site is also available as a Gemini capsule. To go there, you have to use a Gemini browser.<br/>Obviously (for those who know Gemini), everything is more neutered, and the form is not exactly the best because all the pages are a direct conversion from the HTML of the website ( and the program I use to do it is a bit broken, too).<br/>Go to the octocapsule, kindly hosted by koyu.space: <a href="gemini://koyu.space/octt"> gemini://koyu.space/octt</a></p>
+
+### Feeds and notifications
+
+<p>From now on the site (the blogoctt and the MicroBlog, specifically) has integrated feeds, which are automatically updated when I publish a new article!</p>
+<p><b style="color:#ff6a00;">Atom Feed</b> (modern, <b>recommended</b>, contains complete posts): <b><a href="./feed/ atom.xml">feed/atom.xml</a></b><br/>RSS feed (obsolete, available for compatibility): <a href="./feed/rss.xml">feed/rss. xml</a></p>
+<p>You need a compatible feed aggregator to use them.<br/>- On desktop PC I recommend <a href="https://thunderbird.net" rel="noopener" style="Color:#0080FF;" target="_blank">Thunderbird </a>o <a href="https://www.seamonkey-project.org" rel="noopener" style="Color:#003399;" target="_blank">SeaMonkey Mail</a>.<br/>- On Android I recommend <a href="https://f-droid.org/packages/com.nononsenseapps.feeder" rel="noopener" target ="_blank">Feeder</a> or <a href="https://f-droid.org/packages/com.poloure.simplerss" rel="noopener" target="_blank">Simple Rss</a >.<br/>- If you want to use a device like an e-ink e-book reader, the only universal software that - among other things - includes a feed aggregator, which I know and can recommend, is <a href="https://github.com/koreader/koreader" rel="noopener" target="_blank">KOReader</a>.<br/>- Tip: If you use Friendica, you can copy the link to the feed and paste it into the search bar, to be able to follow it as if it were a profile!</p>
+<p>
+<del>Furthermore, if you use any platform of the <b>Fediverso ActivityPub</b> (Mastodon, Pleroma, Misskey, ...) you can follow the bot of the ctt site, so as to receive new posts in your Home feed: < a href="https://botsin.space/@sitoctt" rel="me noopener" target="_blank">@sitoctt@botsin.space</a>!</del> For some complications that started at the end of August 2022 , the bot is not accessible from the largest Italian Mastodon instance, <i>mastodon.uno</i>, so it is almost practically useless now. I'm not taking it away just because it would cost me more to do that than to leave it where it is <b>:P</b>; However, I would have to create a new one, sooner or later.
+</p>
+
+## Sources and licenses
+
+### Content Licenses
+
+<p>All content on this site that I created (my own writing, original media, and most source code) is licensed under <a href="https://creativecommons.org/licenses/by- sa/4.0/deed.it" rel="noopener" target="_blank">"Creative Commons Attribution - Share Alike 4.0 International" (CC BY-SA 4.0) (<span class="CCIcons"><img class ="i1em" src="https://sitoctt-assets.octt.eu.org/Media/Icons/CC/CC.svg"/> <img class="i1em" src="https://sitoctt-assets .octt.eu.org/Media/Icons/CC/BY.svg"/> <img <="" class="i1em" span="" src="https://sitoctt-assets.octt.eu.org /Media/Icons/CC/SA.svg"/>)</span></a>, a free license that promotes sharing, and does not affect the legitimate rights to culture and collaboration of humanity in general.</ p>
+<p>However, there are also contents that are not mine.<br/>In any case, if something comes from my hand, it will not have any indication of credits nearby. <br/>For the borrowed stuff, however, the source from which I took it and the license will always be indicated, whether this is in the public domain, Creative Commons, or not specified.<br/>Be careful, the credits for I often just leave the HTML and CSS stuff in the page's sources. So, just in case, check there for these kinds of credits. For things like images or texts, however, any credits are often a visible part of the page, close to the borrowed object (like a description); other times, the same object is a link which, if clicked, takes you back to the source. However, I thought of creating a section of the page <a href="#-Special-Credits">below</a> , dedicated to special credits (which I fill in when I remember).</p>
+
+### Source code
+
+<p>Speaking of site sources, the HTML source of the actual page loaded by the browser may be difficult to read. This is because I don't actually write the complete HTML directly to compose the pages. Not only would it be a mess to replicate my various navigation bars and sections across all the pages, and if I have to make changes to these then it's a hell to replicate this anywhere, but the HTML syntax is dirty and hard to write.</p>
+<p>Precisely for these reasons, I created my own static site generator (also, like this site itself, incomplete but updated from time to time when I need it), which preprocesses my source code to include my bars in all the pages, generate the sections of the page (which appear in the menu on the right), generate the list of pages of the site (from the menu on the left), and <i>other little things</i>. Important step, any Markdown or Pug files are translated into HTML to be understandable by normal browsers, and here you go.<br/>Ah, yes, I'm saying "<i>other little things</i>" because this is stuff that at the time of writing this chapter the page is absent or incomplete, and by writing as I write I cover my ass and don't have to make future changes.
+<pre class="Inline"><i>H and h .</i></pre>
+</p>
+
+#### Take it all!
+
+<p>To finish, find all my sources on the respective Git repos.<br/>Those of my site (divided into multiple repos to keep the history clean), under the conditions described above: <a href="https:// gitlab.com/octtspacc/sitoctt" rel="noopener" target="_blank">gitlab.com/octtspacc/sitoctt</a>; <a href="https://gitlab.com/octtspacc/sitoctt-assets" rel="noopener" target="_blank">sitoctt-assets</a>.<br/>The ones from my generator, also released under a free license, the AGPL: <a href="https://gitlab.com/octtspacc/staticoso" rel="noopener" target="_blank">gitlab.com/octtspacc/staticoso</a>.</a> p>
+<p>Another thing: in case it is of interest, to immediately preserve and/or share (excluding files that are on separate repositories, because they are absolutely linked) offline copies of the site, you can download a <b>zip </b> containing all compiled pages <a href="https://gitlab.com/octtspacc/sitoctt/-/jobs/artifacts/main/download?job=pages" rel="noopener" target="_blank" >here</a>!</p>
+
+### Special credits
+
+<details>
+<summary>
+<h4>List of credits and special thanks to those who borrowed material (Expand)</h4>
+</summary>
+<div>
+<ul>
+<li>List of <a href="#-Script-client-side">client-side scripts</a>, including some third-party scripts</li>
+<li>Waaaves animated title: <a href="https://codepen.io/jh3y/pen/WNrXqYz" rel="noopener" target="_blank">Waaaves by jh3y</a></li>
+<li>Font family: <a href="https://fonts.google.com/specimen/Space+Mono" rel="noopener" target="_blank">Space Mono by Colophon Foundry</a></li >
+<li>CSS emoji package: <a href="https://twemoji.twitter.com" rel="noopener" target="_blank">Twemoji from Twitter</a>, via <a href="https:/ /gitlab.com/octtspacc/twemoji-astonishing" rel="noopener" target="_blank">Twemoji Astonishing</a></li>
+<li>Some non-identifying 88x31 buttons: <a href="https://cyber.dabamos.de/88x31" rel="noopener" target="_blank">88x31 GIF Collection by cyber.dabamos.de</a> </li>
+</ul>
+</div>
+</details>
+
+## Confidentiality and transparency
+
+As my legitimate interest, I use an analytics service on this website; both to improve what I do and to satisfy my pure curiosity to discover data.
+
+The analytics service is based on completely <a href="https://github.com/arp242/goatcounter/blob/master/LICENSE" rel="noopener" target="_blank">free and open-source</ a>, hosted for free for low traffic sites by <b>GoatCounter.com</b>.
+
+Apparently, with GoatCounter you don't need to include an on-screen warning that disturbs users to comply with the GDPR (see <a href="https://www.goatcounter.com/help/gdpr" rel="noopener " target="_blank">goatcounter.com/help/gdpr</a>), but, for honesty and transparency, I'm writing this paragraph anyway.
+
+Only non-personal data is collected, anonymously, for the sole purposes of general statistics, and not for individual tracking. The service does not use cookies, and the data is not transferred to third parties. For further information, I can only recommend reading the <a href="https://www.goatcounter.com/help/privacy" rel="noopener" target="_blank">GoatCounter privacy policy</a >.
+
+<style>
+.CCIcons > Img, .CCIcon {
+Display: Inline !Important;
+Max-Height: 1em !Important;
+Vertical-Align: Sub;
+}
+.CCIcons > Img, .CCIcon {
+Margin-Left: 3px;
+}
+
+/*!-- Credits: https://codepen.io/jh3y/pen/WNrXqYz ---*/
+.WavyText {
+Text-Align: Center;
+Position: Absolute;
+Left: 50%;
+White Space: NoWrap;
+Transform: Translate(-50%, -50%) Translate(Calc(Var(--x, 0) * 1%), Calc(Var(--y, 0) * 1%));
+font-variation-settings: 'wght' Var(--lower);
+Margin: 0;
+}
+.WavyText Span {
+Color: HSLA(300, 100%, 20%, Var(--alpha-l));
+Animation: Rise 2.25s infinite ease-in-out;
+Animation-Delay: Calc((Var(--index) - 6) * 0.225s);
+Display: Inline Block;
+}
+@keyframes Rise {
+50% {
+font-variation-settings: 'wght' Var(--upper);
+Color: HSLA(300, 100%, 30%, Var(--alpha-u));
+Transform: Translate(0, -15%);
+}
+}
+</style>
diff --git a/en/note/2023-10-17-Gaming-Sincronizzato-PS2-Smartphone.md b/en/note/2023-10-17-Gaming-Sincronizzato-PS2-Smartphone.md
index 546ce83..85a4746 100644
--- a/en/note/2023-10-17-Gaming-Sincronizzato-PS2-Smartphone.md
+++ b/en/note/2023-10-17-Gaming-Sincronizzato-PS2-Smartphone.md
@@ -1,11 +1,11 @@
 +++
-Title= "2️⃣ Gaming synchronized between PlayStation 2 and smartphone"
-Date= 2023-10-17
-Downsync= "/it/note/Gaming-Sincronizzato-PS2-Smartphone.html"
-Aliases= [ "/Posts/Notes/2023-10-17-Gaming-Sincronizzato-PS2-Smartphone.html" ]
-Description= "In detail, how I designed a system to have games and saves always synchronized between the emulator and the real PS2 console, shared here."
-Categories= [ "Gaming" ]
-Lastmod= 2023-10-18
+Title = "2️⃣ Gaming synchronized between PlayStation 2 and smartphone"
+Date = 2023-10-17
+Downsync = "/it/note/Gaming-Sincronizzato-PS2-Smartphone.html"
+Aliases = [ "/Posts/Notes/2023-10-17-Gaming-Sincronizzato-PS2-Smartphone.html" ]
+Description = "In detail, how I designed a system to have games and saves always synchronized between the emulator and the real PS2 console, shared here."
+Categories = [ "Gaming" ]
+Lastmod = 2023-10-18
 +++
 
 {{< noticeAutomaticTranslation it >}}
@@ -14,83 +14,69 @@ Lastmod= 2023-10-18
 
 <!-- Autogenerated by ListedDownsync.js. Do not edit (unless also set "% Downsync = False") - it would be overwritten. -->
 
-<p>Those who have been following my adventures for long enough and with due attention perhaps know this, but the biggest problem in computer science is: how to properly reconcile the discrepancies that are created when we face the problem of playing video games both at home than in portability? Between games that in one case are comfortable to play and in another perhaps don't even run, and the saves that are spread across countless different devices, solving this problem completely will never be possible...<br>
-Yet, sometimes, the entropy of the brain is able to generate particularly useful ideas in this regard too, as happened to me the other day for the PS2.</p>
+Those who have been following my adventures for long enough and with due attention perhaps know this, but the biggest problem in IT is: how to properly reconcile the discrepancies that are created when the problem of playing video games both at home and on a portable computer arises. ? Between games that in one case are comfortable to play and in another maybe don't even run, and the saves that are spread across countless different devices, solving this problem completely will never be possible...  
+Yet, sometimes, the entropy of the brain is able to generate particularly useful ideas in this regard too, as happened to me the other day for the PS2.
 
-<p>In fact, I have a real PlayStation 2, a home console which when you find a way to use it is certainly appreciable... and which I often found myself not using, for the reasons mentioned above: not directly, because at home I often don't goes, nor with an emulator on the smartphone, because I would feel that at home I wouldn't use the real console since the updated saves would only be on the phone.<br>
-And then, just the other day, staring at the console (I'm not sure why), I think there should be a way to have the saves easily synchronized between it and the phone...</p>
+In fact, I have a real PlayStation 2, a home console which when you find a way to use it is certainly appreciable... and which I often found myself not using, for the reasons mentioned above: neither directly, because I often don't feel like it at home, nor with emulator on the smartphone, because I would feel that at home I wouldn't use the real console since the updated saves would only be on the phone.  
+And then, just the other day, staring at the console (I'm not sure why), I think there should be a way to have the saves easily synchronized between it and the phone...
 
-<h2>Snag 1: USB stick or memory card?</h2>
+## Problem 1: USB stick or memory card?
 
-<p>At the time, the simplest idea I thought of was: they exist <a href="https://www.amazon.it/Adattatore-Memoria-Lettore-Sostitutivo-trasparente/dp/B0C8TTQFJY" rel= "noopener nofollow" target="_blank">adapters</a> to use a microSD card as a PlayStation memory card (which use a non-standard interface instead)... it might be worth buying one of those, so I keep them all there the saves, and if desired I can also access them from other devices by moving the card around.<sup id="fnref1"><a class="footnote-ref" href="#fn1">1</a></sup> <br>
-With a card of several GB (there aren't any small ones around anymore anyway), furthermore, I could even do without the USB stick and keep all the games only on the memory card!</p>
+At the time, the simplest idea I thought of was: there are [adapters](https://www.amazon.it/Adattatore-Memoria-Lettore-Sostitutivo-trasparente/dp/B0C8TTQFJY) to use a microSD card like PlayStation memory cards (which instead use a non-standard interface)... it might be better to buy one of those, so I keep all the saves there, and if desired I can also access them from other devices by moving the card around.<sup id= "fnref1"><a href="#fn1">1</a></sup>  
+With a card of several GB (there aren't any small ones around anymore anyway), furthermore, I could even do without the USB stick and keep all the games only on the memory card!
 
-<p>Fortunately, this is not the only way, at least for certain games: <a href="https://github.com/ps2homebrew/Open-PS2-Loader" rel="noopener nofollow" target="_blank ">Open PS2 Loader</a>, the homebrew that runs commercial games from backup storage (such as USB sticks), supports the use of virtual memory cards (VMCs) that are saved as files on the USB drive. Games are quite slow to save on it (the PS2 only supports USB 1.1, plus there's some strange overhead), but it's an apparently workable solution.</p>
+Luckily, this is not the only way, at least for certain games: [Open PS2 Loader](https://github.com/ps2homebrew/Open-PS2-Loader), the homebrew that runs commercial games from backup memories (like USB sticks), supports the use of virtual memory cards (VMC) which are saved as files on the USB drive. Games are quite slow to save on that (the PS2 only supports USB 1.1, plus there's some strange overhead), but it's a seemingly workable solution.
 
-<h2>Hitch 2: Save conversion</h2>
+## Hitch 2: Save conversion
 
-<p>Regardless of the previous choice, however, I discover another obstacle: the saves should be converted to be passed from the console to the emulator (at least <a href="https://aethersx2.com" rel="noopener nofollow" target=" _blank">AetherSX2</a>, for better or worse the only truly decent one to date) and then vice versa.<br>
-Fortunately, I immediately find <a href="http://www.csclub.uwaterloo.ca:11068/mymc" rel="noopener nofollow" target="_blank">mymc</a>, a program so old that it requires Python 2 (while at the moment we've been at 3 for years and years), which however works, and thank goodness it offers a command line interface.</p>
+Regardless of the previous choice, however, I discover another obstacle: the saves should be converted to be passed from the console to the emulator (at least [AetherSX2](https://aethersx2.com), for better or for worse the only truly decent one to date ) and then vice versa.  
+Fortunately, I immediately found [mymc](http://www.csclub.uwaterloo.ca:11068/mymc), a program so old that it requires Python 2 (while at the moment we've been at 3 for years and years), but it works, and thank goodness it offers a command line interface.
 
-<p>It doesn't do true virtual memory card conversions per se, but it allows you to manipulate the contained files in various ways. All very crude, but fortunately exploitable enough to do just what I need, after assembling an ideal script.<br>
-I won't try to explain how it works, at the bottom of the article you can download it and read it, it's boring. I packaged mymc inside the script, so that it doesn't have to be installed separately.</p>
+It doesn't do true virtual memory card conversions per se, but it allows you to manipulate the files contained in it in various ways. All very crude, but fortunately exploitable enough to do just what I need, after assembling an ideal script.  
+I won't try to explain how it works, at the bottom of the article you can download it and read it, it's boring. I packaged mymc inside the script, so that it doesn't have to be installed separately.
 
-<h3>Snag 3: Converting from your phone</h3>
+### Hitch 3: Converting from your phone
 
-<p><em>Note 2023-10-18: I found a modern fork (in Python 3) of mymc, <a href="https://sr.ht/%7Ethestr4ng3r/mymcplus/" rel="noopener nofollow " target="_blank">mymc+</a>... I haven't tried it (yet), but it's possible that this could work on Android too, eliminating the fiddly setup that follows, so I'll mention it.</em> </p>
+_Note 2023-10-18: I found a modern fork (in Python 3) of mymc, [mymc+](https://sr.ht/%7Ethestr4ng3r/mymcplus/)... haven't tried it (yet), but it's possible that this could work on Android too, eliminating the fiddly setup that follows, so I mention it._
 
-<p>Unfortunately, mymc has some problems running in <a href="https://termux.dev/en" rel="noopener nofollow" target="_blank">Termux</a> (the native Linux environment very convenient for this type of integrations) on my Android: I don't know what's to blame, but in practice the program has problems reading VMC files, throwing an error like <code class="prettyprint">file.vmc : Bad file descriptor</code>. I couldn't find any solutions online, not even for general searches of the problem, so I had to make do. Maybe using a containerized GNU+Linux system in root, with its libraries and a different build of Python 2.7, would be enough to solve the problem, but who knows.<br>
-For my part, I was starting to get annoyed, and so I opted to delegate the conversion to my Debian server, having a Termux script carry out the simple task of loading the VMC on the server, executing the actual conversion script there, and then download the converted file to the right location locally.</p>
+Unfortunately, mymc has some problems working in [Termux](https://termux.dev/en) (the very convenient native Linux environment for this type of integrations) on my Android: I don't know what's to blame, but in practice the program has problems reading VMC files, throwing an error of the type `file.vmc: Bad file descriptor`. I couldn't find any solutions online, not even for general searches of the problem, so I had to make do. Maybe using a containerized GNU+Linux system in root, with its libraries and a different build of Python 2.7, would be enough to solve the problem, but who knows.  
+For my part, I was starting to get annoyed, and so I opted to delegate the conversion to my Debian server, having a Termux script carry out the simple task of loading the VMC on the server, running the actual conversion script there, and then download the converted file to the right location locally.
 
-<p>Before I forget: on Android 13 and above (but already from some past versions) root permissions are needed to read and write files from/on external memories (such as the USB stick) and private application folders (such as the one where AetherSX2 stores the virtual memory cards).<br>
-From what I have been able to prove, if you don't have root you will necessarily have to use a suitable file manager (and I don't think there are scriptable ones, so you have to use your hands), or perhaps ADB, to move the files around... thank Google.<br>
-In any case, my scripts have written in the special paths used for all the ambaradan.</p>
+Before I forget: on Android 13 and above (but already from some past versions) root permissions are needed to read and write files from/to external memories (such as the USB stick) and private application folders (such as the one where AetherSX2 preserves virtual memory cards).  
+From what I have been able to prove, if you don't have root you will necessarily have to use a suitable file manager (and I don't think there are scriptable ones, so you have to use your hands), or perhaps ADB, to move the files around... thank Google.  
+In any case, my scripts have written in the special paths used for all the ambaradan.
 
-<p>Using <a href="https://wiki.termux.com/wiki/Termux:Widget" rel="noopener nofollow" target="_blank">Termux:Widget</a>, I finally added two links to my system launcher, for VMC conversion:</p>
+Using [Termux:Widget](https://wiki.termux.com/wiki/Termux:Widget), I finally added two shortcuts to my system launcher, for VMC conversion:
 
-<ul>
-<li>one that goes from the PS2 format to the emulator one, to be run when I want to play on my phone but the saves on the pen drive were last modified by the PS2;</li>
-<li>the other for the reverse conversion, to be performed when I want to go and play on the PS2 once the emulator has updated my saves.</li>
-</ul>
+* one that goes from PS2 to emulator format, to run when I want to play on my phone but the saves on the pen drive were last modified by the PS2;
+* the other for the reverse conversion, to be performed when I want to go and play on the PS2 once the emulator has updated my saves.
 
-<p>To explain it I realize that it seems very complicated, in practice I just have to press a button and wait a few seconds.</p>
+To explain it I realize that it seems very complicated, in practice I just have to press a button and wait a few seconds.
 
-<h2>In practice: the value of unique memory</h2>
+## In practice: the value of unique memory
 
-<p>Once the kinks have been eliminated, the configuration is done, and its strong point lies in the centralization of games and saves on a single device: the USB key. Like this:</p>
+Once the problems have been eliminated, the configuration is done, and its strong point lies in the centralization of games and saves on a single device: the USB key. In this way:
 
-<ul>
-<li>I avoid the confusion generated by games that I have on one side but not the other, especially when I want to modify my collection;</li>
-<li>I don't need a much larger microSD in my smartphone to contain all the games I already have on another portable memory, with advantages for the stability of the other data and the weight of the wallet;</li>
-<li>there is no extra confusion for the management of even the saves, these being managed as I said before.</li>
-</ul>
+* I avoid the confusion generated by games that I have on one side but not the other, especially when I want to modify my collection;
+* I don't need a much larger microSD in my smartphone to contain all the games I already have on another portable memory, with advantages for the stability of the other data and the weight of the wallet;
+* there is no extra confusion for managing saves too, these being managed as I said before.
 
-<p>On the PS2 I normally connect the pen drive when I need it, however on the smartphone I have to use a USB-C OTG adapter, which is on average inconvenient but there is little that can be done. To avoid losing these things around, I then attached a carabiner to the USB stick, and a key ring in the hole for the lanyards on the phone cover.</p>
+On the PS2 I normally attach the pen drive when I need it, however on the smartphone I have to use a USB-C OTG adapter, which is on average inconvenient but there is little that can be done. To avoid losing these things around, I then attached a carabiner to the USB stick, and a key ring in the hole for the lanyards on the phone cover.
 
-<h2>Concluding: chain ideas</h2>
+## In conclusion: chain ideas
 
-<p>I believe that this is the most ideal system given my initial conditions, and in the following days I will test it thoroughly.<br>
-However, I will probably have to get a larger external memory to store more games, because the 32 GB one I use now has always been too small for me.</p>
+I believe this is the most ideal system given my initial conditions, and in the following days I will test it thoroughly.  
+However, I will probably have to get a larger external memory to store more games, because the 32 GB one I use now has always been too small for me.
 
-<p>Maybe, by taking a large enough one, and writing a special homebrew, I think I can adapt this system of mine for Wii games too, using the same memory for those too... spoilers? 👀</p>
+Maybe, by taking a large enough one, and writing a specific homebrew, I think I can adapt this system of mine for Wii games too, using the same memory for those too... spoilers? 👀
 
-<p>Finally, here are the additional resources for this article:</p>
+In true end, here are the additional resources for this article:
 
-<ul>
-<li>My initial question and brief system discussion on Sony Hacking Zone: <a href="https://t.me/SonyHacking/46784" rel="noopener nofollow" target="_blank">https:/ /t.me/SonyHacking/46784</a>;</li>
-<li>Guide to using VMC on OPL: <a href="https://youtube.com/watch?v=tBrKcJC_E4U" rel="noopener nofollow" target="_blank">https://youtube.com /watch?v=tBrKcJC_E4U</a></li>
-<li>My conversion scripts (on GitLab): <a href="https://gitlab.com/octospacc/Snippets/-/blob/main/Ps2EmuVmcConvert.sh" rel="noopener nofollow" target="_blank ">direct</a>, <a href="https://gitlab.com/octospacc/Snippets/-/blob/main/Ps2EmuVmcConvertCloud.sh" rel="noopener nofollow" target="_blank">via server< /a>;</li>
-<li>AetherSX2 Android build I play (latest without adware): <a href="https://www.apkmirror.com/apk/aethersx2/aethersx2/aethersx2-v1-4-3060-release/aethersx2-v1 -4-3060-android-apk-download/" rel="noopener nofollow" target="_blank">https://www.apkmirror.com/apk/aethersx2/aethersx2/aethersx2-v1-4-3060-release/ aethersx2-v1-4-3060-android-apk-download/</a>.</li>
-</ul>
+* My initial question and brief system discussion on Sony Hacking Zone: [https://t.me/SonyHacking/46784](https://t.me/SonyHacking/46784);
+* Guide to using VMC on OPL: [https://youtube.com/watch?v=tBrKcJC\_E4U](https://youtube.com/watch?v=tBrKcJC_E4U)
+* My conversion scripts (on GitLab): [direct](https://gitlab.com/octospacc/Snippets/-/blob/main/Ps2EmuVmcConvert.sh), [via server](https://gitlab.com /octospacc/Snippets/-/blob/main/Ps2EmuVmcConvertCloud.sh);
+* AetherSX2 Android build I play (latest without adware): [https://www.apkmirror.com/apk/aethersx2/aethersx2/aethersx2-v1-4-3060-release/aethersx2-v1-4-3060-android -apk-download/](https://www.apkmirror.com/apk/aethersx2/aethersx2/aethersx2-v1-4-3060-release/aethersx2-v1-4-3060-android-apk-download/).
 
+---
 
-
-<div class="footnotes">
-<ol>
-
-<li id="fn1">
-<p>On this issue I find conflicting opinions or not very clear advice, so be careful: it is not clear whether these adapters also work as normal memory cards for saving games (and therefore also possibly as an FMCB card), or only as external memory for homebrews like OPL... in any case it would be a potentially valid purchase, considering the technical drawbacks of USB on PS2. <a href="#fnref1">↩</a></p>
-</li>
-
-</ol>
-</div>
\ No newline at end of file
+1. On this finding, I find conflicting opinions or advice that is not too clear, so be careful: it is not clear whether these adapters also work as normal memory cards for saving games (and therefore also possibly as cards for FMCB), or only as external memory for homebrew like OPL... in any case it would be a potentially valid purchase, considering the technical drawbacks of USB on PS2. [↩](#fnref1)
\ No newline at end of file
diff --git a/es/blog/2022-10-31-Storia-Antica-del-DSpacc.md b/es/blog/2022-10-31-Storia-Antica-del-DSpacc.md
new file mode 100644
index 0000000..5d6f6c4
--- /dev/null
+++ b/es/blog/2022-10-31-Storia-Antica-del-DSpacc.md
@@ -0,0 +1,102 @@
++++
+Title = "🎮 Historia antigua de DSpacc"
+Description = "La primera consola de juegos de mi vida fue a la guerra, luego acumuló polvo y hasta el día de hoy no está muy bien; pero le di un propósito."
+Aliases = [
+  "/Posts/2022-10-31-Storia-Antica-del-DSpacc.html",
+]
+Categories = [ "Juegos", "Tecnología" ]
+Date = 2022-10-31
++++
+
+{{< noticeAutomaticTranslation it >}}
+
+
+
+Hace casi dos meses, me vino a la mente el **DSpacc** un poco por casualidad; primero como concepto, hablando de ello con personas en línea, y luego directamente como el pequeño objeto que poseo con orgullo.
+
+Esta cosa mía ha visto **polvo**, **gloria**, **guerra** y **desesperación**. Esto es exactamente de lo que debería haber hablado hoy, lo que hice recientemente para quitar algo de polvo y así devolverle la gloria a mi dispositivo.
+Sin embargo, mientras escribía me di cuenta de cómo el contexto se habría confundido si no le hubiera dado el espacio adecuado a la historia; pero, por desgracia, la historia en sí es larga y merece un artículo detallado, así que aquí estamos.
+
+## Los comienzos
+
+Todo empezó cuando, a la edad de 6 años, recibí esta **Nintendo DS Lite** como regalo por mi cumpleaños... no, no estoy divagando, ya estoy llegando a ese punto. Durante unos buenos 3 años fue mi única consola de juegos y, durante al menos 1 o 2 de esos años, mi único dispositivo de juegos, antes de adquirir el Galaxy Player o la _tableta scassone_.
+Para mí era un objeto de batalla absolutamente indispensable, necesario siempre y en todas partes como mi smartphone de hoy, y quizás por eso tuvo una vida particularmente intensa en sus primeros años. No tenía muchos juegos, porque solo tenía 2 GB de memoria en el flashcart y ningún juego físico (aparte de uno oscuro, que no compré hasta más tarde), pero tenía algunos de los mejores. . En resumen, con Pokémon, todos los juegos principales de Mario e incluso cosas como Cooking Mama (que era muy popular en ese momento), el disfrute siempre estuvo presente.
+
+[![Nintendo DS Lite (lado derecho)]({{< assetsRoot >}}/Media/Misc/Nintendo_DS_Lite_(right_side)/4.jpg)](https://commons.wikimedia.org/wiki/File:Nintendo_DS_Lite_ (lado_derecho).jpg)
+_Un DS Lite... no es mío, por razones obvias, pronto - <small>Havok en en.wikipedia, CC BY 2.5 <https://creativecommons.org/licenses/by/2.5>, vía Wikimedia Commons</small> _
+
+## El día del aplastamiento
+
+A pesar de un par de contratiempos con el flashcart (el primero dejó de funcionar misteriosamente un día, el segundo comenzó a mostrar serios signos de falla después de aproximadamente 2 años) **la pequeña consola luchó** y me mantuvo entretenido.
+Un mal día a principios de julio sin embargo, a primera hora de la tarde, regresando del mar, mis ganas de jugar se hicieron **_crack_**, junto con el plástico de la cremallera al abrir el caparazón. Oh, sí, exactamente esto es un "DSpacc": un **DS dividido**. Puede que el nombre no signifique mucho, lo sé, porque no sólo lo acuñé yo, sino también hace muy poco.
+
+De momento me pareció absurdo que con solo abrir la consola se hubiera podido romper; y a día de hoy me sigue pareciendo absurdo, aunque he descubierto que es un problema muy extendido: basta con escribir "nintendo ds rota" en cualquier buscador de imágenes para ver cómo no sólo son mayoritarias las imágenes que muestran la bisagra rota, sino que también cómo aquellos que representan DS y DS Lite son mayoría. Parece que, a partir de la DSi, Nintendo ha rediseñado el mecanismo de concha, que hasta entonces había resultado inadecuado, y lo ha perfeccionado aún más con la 3DS; evidentemente, el _did cahà_ original.
+
+### Las consecuencias del daño.
+
+La desesperación estuvo a punto de invadirla, aunque en aquel momento la consola seguía funcionando perfectamente, porque simplemente se había roto un trozo de plástico situado a la derecha de la bisagra, que tiene la única función de garantizar la **integridad estructural**. La desesperación realmente comenzó a aparecer en el momento en que vi que los colores en la pantalla comenzaban a cambiar mientras movía la cubierta: ahí lo tienes, **el cable** de la pantalla **comenzó a sufrir daños**.
+Un poco más tarde, creo que esa misma tarde, fui con mi padre a una tienda al otro lado de la ciudad, para ver cuánto costaría **una reparación**. No recuerdo el precio ahora, pero decidí que **no valía la pena**, y que sería mejor comprarme una bonita 3DS, dados los juegos interesantes que se habían lanzado o estaban a punto de lanzarse. para la nueva familia de consolas.
+
+No recuerdo si seguí usando la DS Lite en los días siguientes, porque muchos de los títulos que quería jugar requerían la pantalla superior, y no me gustaba jugar con colores _disminuidos_ (hoy no me molesta). demasiado, sin embargo). En cualquier caso, al final de esa semana, después de varias búsquedas en tiendas locales en busca del precio más barato, [obtuve mi o3DS XL](https://mastodon.uno/@octo/109262437212406002).. y eso es una historia completamente diferente.
+
+## La era del polvo
+
+A partir de ese momento, por supuesto, el nuevo y antiguo **DSpacc pasó a un segundo plano**. Quizás todavía lo tomé a veces, al menos para juegos como Animal Crossing que solo requieren el panel inferior, porque (según la aplicación _Diary_, ciertamente más precisa que mi memoria) en las primeras 2 semanas de la 3DS no tenía nada. para jugar con aplicaciones distintas a las del sistema. Luego, sin embargo, por un lado poco a poco pude poblar la nueva consola con software, por otro lado el DS Lite **siguió estropeándose** - más temprano que tarde, de hecho, la pantalla superior empezó a dejar de funcionar completamente, mostrando solo una pantalla blanca con un punto negro (?) - **polvo** comenzó a atacar el DSpacc. Como si eso no fuera suficiente, ¡el flashcart un día _dijo adiós_! 🙄
+Incluso después de años, a pesar de mi nueva consola, de vez en cuando todavía tenía que **recoger la vieja**... No estoy seguro de por qué, dado que ya no podía hacer nada especial con ella, ya que no tengo juegos en una tarjeta dedicada que pueda usar sin la pantalla superior. Incluso años después, tal vez porque con el tiempo comencé a coleccionar algunos cartuchos originales de DS y tenía ganas de encenderlos, **a veces volvía a encender **el DS Lite** por unos minutos.
+
+Todo iba genial, hasta que, en cierto momento, **¡incluso jugué **la _SLOT-1_** (la de las tarjetas DS) en la pobre consola! Recuerdo que mostró cierta dificultad para leer incluso las hojas originales, pero mis otros recuerdos sobre el tema son muy confusos. Recuerdo que cuando miré dentro de la ranura vi unos **alfileres doblados**, y que intenté insertar algo para enderezarlos, pero fue en vano. No creo que al hacer esto dañé a otros, pero ya hace al menos 3 años (comparado con el presente) recuerdo que en la ranura algunos pines estaban **rotos, faltantes**... así que, ya sea cuando cosas atascadas en el puerto he debilitado o incluso desconectado otros pines sin darme cuenta, o es el poner y quitar ocasionalmente cartuchos, con la esperanza de que alguno se leyera, lo que ha roto los contactos ya debilitados (y sería grave, porque demostraría la mala calidad de la slot).
+
+Después de este nuevo evento inesperado, seguramente aún podría, a través de _Descargar DS_, usar la consola para software volátil y técnicamente limitado, sin posibilidad de guardar ninguna configuración (o progreso, en los juegos), pero **no nos andemos con rodeos* *:¿Qué haces útil y continuo así? Prácticamente nada, y **la consola** se había convertido por tanto en **un pisapapeles**... hasta que, un tiempo después, en una feria encontré y **compré accidentalmente un cartucho de Pokémon Rubí**. Aunque ni siquiera tenía caja, tenía que tenerla: **¡por fin pude jugar** algo completo en mi pobre consola!
+
+## Editar arreglado
+
+Sin embargo, **ese panel roto estaba empezando a pasar factura**, _literalmente_. La bisagra dividida desequilibró el peso de todo el dispositivo, y la parte superior de la carcasa quedó colgando sólo gracias a los _cables surtidos_.
+Ya había descubierto el concepto de **GBA Macro** hace un tiempo. Para los no expertos, se trata de darle una segunda vida a una DS que ha perdido su pantalla superior, para jugar a títulos (emulados, o no como los de GBA, para los cuales la consola ofrece retrocompatibilidad de hardware) de consolas anteriores que su naturaleza poseía. solo una pantalla.
+En Internet ya veía a gente creando sus propios modelos personalizados con cuerpos coloreados a mano de forma única, o añadiendo tubos LED que crean un efecto neón, colocados en lugar de la cremallera. Todo es fantástico, pero si no tuviera el deseo (y la forma, al menos en ese momento no se podía encontrar en Amazon.it) de comprar una nueva pantalla para reparar adecuadamente la consola, ¿podría alguna vez empezar a gastar? ¿Sobre detalles que, por bellos que sean, son objetivamente superfluos?
+
+Tomo un par de tijeras y **corto** los cables para que la mitad superior de la caja permanezca unida a la principal. ¿Y esto es todo? ¿Podemos volver a jugar? Bueno, _no exactamente_.
+Para ser honesto, hacer una buena Game Boy Macro requiere algo de trabajo en el hardware _un poco más elaborado_ que arrancar violentamente la pantalla rota, y por esta razón mi historia ha sido **un poco problemática**. En primer lugar, una **operación particular** es prácticamente obligatoria, si no quieres perder las **funciones DS**: abrir el dispositivo y - además de _correctamente_ desconectar la pantalla, los parlantes, el micrófono y la antena. cables, _sin cortarlos_ - soldar una pequeña **resistencia** en 2 puntos de prueba de la placa base. Normalmente, la consola falla en la POST y se apaga si no detecta la pantalla superior (es decir, si no detecta el consumo de energía que se esperaría de la luz de fondo de la pantalla superior); Soldar una resistencia de un valor entre 300 y 1000 ohmios en los lugares correctos sirve precisamente para hacer creer al sistema que nada está fuera de lugar.
+
+Sin embargo, había hecho **mis búsquedas** en la Web, descubriendo así que el POST no se realiza para iniciar un cartucho desde el _SLOT-2_ (el GBA), si **el inicio automático está configurado en la configuración del sistema* * de una tarjeta de juego si está presente. Por lo tanto, mucho antes de cometer mi _acto violento_, porque después ya no podría acceder al menú del sistema, configuré el inicio automático y me aseguré de que la pantalla inferior estuviera seleccionada como el panel utilizado en el modo Game Boy Advance.
+Una vez cometido _el crimen_, veo que la consola funciona exactamente como habían dicho _desconocidos en Internet_: **es prácticamente una GBA**, como si nunca hubiera sido una DS... excepto que no tiene parlantes. , porque los tengo recortados. 😅
+
+## Un nuevo plan
+
+Un poco más tarde, sin embargo, comencé a **querer cosas** como el modo _Descargar DS_... o el ajuste de la luz de fondo. Decidí comprar online un kit de puntas de destornillador, que entre muchas también incluía la maldita punta para tornillos tri-wing, esos tornillos amados por Nintendo exactamente tanto como odiados por los idiotas que compramos sus productos.
+Con mi nueva **arma muy peligrosa** (esta no es mi opinión, sino la de aquellos que insisten en usar tornillos de mierda para los objetos que producen) finalmente puedo abrir mi DSpacc, para **soldar la resistencia** .. resistencia **¡que no tengo**! Pero **tengo un chicle**.
+De hecho, otras almas bondadosas en Internet ilustran cómo las gomas conductoras utilizadas para los botones de los mandos a distancia (y del propio DS) a menudo tienen el valor de resistencia adecuado y necesario en este caso. Quiso la suerte que un viejo control remoto roto que tenía a mano tenía almohadillas de goma adecuadas: cortando una y manteniéndola presionada con el dedo en los infames puntos de prueba, **la consola se encendió** como antes de cortar la panel apagado.
+Aquí **lo difícil** fue lograr **fijar** esa _cosita_ a la placa base, para que hiciera la presión correcta, y por lo tanto el contacto eléctrico correcto, en los puntos donde en teoría se debería hacer la soldadura - _por la razón que sugiere la propia palabra "soldadura". Unos centímetros de **cinta aislante** después, que tuve que aplicar y volver a aplicar hasta poder asegurarla con la tensión adecuada, y parecía que ya había terminado; pero el destino decidió burlarse de mí.
+
+![Foto del área del punto de prueba, con una mezcla de cinta aislante y adhesivo aplicada sobre ella.]({{< assetsRoot
+ >}}/Media/Misc/GBA-Macro-Button-Resistor.avif)
+
+### Otro problema más
+
+Teniendo en cuenta que el dispositivo de gran calidad - pero no sólo éste, ahora también los teléfonos "inteligentes" desde hace 15 años - no enciende sin la batería conectada (sólo con el cable de alimentación externo, por así decirlo), y que sólo el cuerpo de plástico que mantiene el celular pegado y alineado, ahora que la consola estaba desarmada tuve que **sostener la batería con las manos** cerca de los contactos del resorte, en esos momentos de unos segundos en los que simplemente quería * *verificar que la consola funcionó**.
+Bueno, por estas maniobras (y esto lo entendí recién después), quizás por mi mal manejo de la batería o quién sabe qué, de repente **¡el DS ya no encendía**! El POST no falló como antes, eh, pero simplemente **no mostró señales de vida**. La _desesperación_ aumentó rápidamente, no tenía idea de lo que había pasado y dónde poner las manos. Fue sólo gracias a _Ashfly_, que me estaba ayudando en el chat con mi desorden, que llegué a la conclusión de que se acababa de fundir el fusible dedicado a la conexión de la batería.
+
+No te sientas mal por mí, pero al no tener la resistencia que sabía exactamente que necesitaba, ¿podría alguna vez tener el fusible que nunca imaginé que se quemaría? Así que tuve que hacer un bonito puente con hojalata... Vamos, no tiene sentido hacer mucho escándalo, nunca sucederá que conecte **por error**, en el compartimento de las pilas, una fuente de energía más potente. que lo que el circuito de la consola puede manejar; El fusible del puerto de carga está separado, por lo que está fuera de toda duda que una fuente de alimentación defectuosa pueda descargar un rayo en la CPU de la consola.
+
+![Foto del puente de hojalata realizado (con dificultad) sobre el fusible de la batería, con la posición de la zona marcada en todo el tablero.]({{<assetsRoot >}}/Media/Misc/DSpacc-Fuse-Bridge.png )
+
+### Problema resuelto
+
+Me hubiera gustado volver a conectar el altavoz (el lugar está situado en la parte inferior de la consola) pero, por un lado, haber cortado el cable y mi absoluta incompetencia a la hora de soldar hace tiempo (_la foto del jumper habla por sí sola_) - incluso si, hasta la fecha, sé soldar al menos un cable en un gran punto de prueba - y por otro lado el frenesí de cerrar todo por temor a que mi desastre de cinta aislante pudiera moverse, **preferí cerrar todo** y fingir que no pasó nada. Al menos, todavía tengo el puerto jack 3.5 para escuchar audio en auriculares.
+
+Posteriormente (bueno, **13 meses después**... ¡¿Pensé todo este tiempo que la consola era hermosa a la vista tal como estaba?!?) **repiné** un poco el cuerpo**, principalmente usando papel de lija para Aplana completamente la otra protuberancia que normalmente sirve al mecanismo de concha, llevándola al estado en el que **todavía se encuentra**.
+
+![Foto antigua que muestra el DSpacc y un trozo de papel de lija en mi escritorio, mientras trabajo.]({{< assetsRoot >}}/Media/Misc/GBA-Macro-Sandpaper-Job-Detail.avif)
+
+## La secuela
+
+**Jugar** Pokémon Rubí en mi nueva GBA Macro, mucho más compacta y liviana que la DS en su forma original, **tomó** un sabor completamente nuevo**. Jugué durante decenas de horas, pero de vez en cuando se me ocurrió que quería divertirme con otras cosas en la elegante consola.
+Excluyendo totalmente los flashcarts de DS, porque la ranura está, como dije, **muerta**, miré los de GBA. En Amazon.it, la única tienda online donde pude y puedo comprar, me parece que ya en su momento **encontré** una _scassona_ por no más de **veinte euros**, pero no lo sé. por qué **solo miré* * - y lo he hecho más de una vez - sin siquiera tocar (comprar).
+
+Así que ha pasado otro buen año y apenas hace **unas semanas**. Un poco al azar, recuerdo mi DSpacc y, como lamento que esté fuera de uso, intento hacer **algunas cosas un poco locas**, de las que hablé en [esta entrada del 2022-09-18 de el MicroBlog](./MicroBlog/2022-09-18-Quando-Metto-Mano-Io-Spacc.html).
+En este punto, sin embargo, entro en la historia de la **era contemporánea del DSpacc**, que tiene **demasiadas implicaciones** de las que hablar. En el **próximo artículo detallado** sobre el tema, habrá mucho tiempo para hablar sobre cómo, finalmente, desempolvé con estilo este **valiente** dispositivo de juego, que sigue siendo válido a pesar de la mala suerte.
+
+**¡Gracias por leer!** Si la historia te pareció intrigante, ¡mantén los ojos bien abiertos para ver la secuela! 😄
+
+---
+
+_Pss... La historia sobre la modificación de Macro en sí merece un pequeño dossier por sí solo, en mi opinión. Gracias a la existencia de mensajes escritos antiguos puedo redactarlo.. ¿debería?_
diff --git a/es/blog/2022-12-17-Distrazioni-di-Natale-Albero-Padoru.md b/es/blog/2022-12-17-Distrazioni-di-Natale-Albero-Padoru.md
new file mode 100644
index 0000000..ca11948
--- /dev/null
+++ b/es/blog/2022-12-17-Distrazioni-di-Natale-Albero-Padoru.md
@@ -0,0 +1,144 @@
++++
+Title = "🎄 Distracciones navideñas: el árbol de Padoru"
+Date = 2022-12-17
+Downsync = "/it/blog/Distracciones-de-Navidad-Albero-Padoru.html"
+Aliases = [ "/Publicaciones/2022-12-17-Distracciones-de-Navidad-Albero-Padoru.html" ]
+Description = "Navidad, para descongelar los Padoru y ponerlos en el árbol. Sin embargo, durante este tranquilo bricolaje, descubro que tengo poca memoria..."
+Featured_Image = "@/Media/Padoru/Padoru-Tree-Old-New-Fragments.webp"
+Categories = [ "DIY" ]
++++
+
+{{< noticeAutomaticTranslation it >}}
+
+
+
+<!-- Generado automáticamente por ListedDownsync.js. No lo edite (a menos que también establezca "% Downsync = False"); se sobrescribirá. -->
+
+Ahhh, y aquí estamos nuevamente en noviembre de este año. Yo diría que es hora de iniciar el procedimiento necesario para _descongelar el **Padoru**_.
+...No, espera un minuto. YA ES **MEDIO DE DICIEMBRE?!?!?!** 😐 😶 🤯
+Los meses pasan rápido... _oh bueno_.
+
+## ¿Qué es "Padoru"?
+
+Para muchos un **tema polémico** y una **costumbre despreciada**, la de **Padoru**.
+Para esas 3 personas que viven bajo las piedras _(y que no sé cómo pueden estar leyendo este blog ahora, pero lo ignoraré)_: es un **meme** que, según [Know Your Meme](https://knowyourmeme.com/memes/padoru), nació de un videojuego, _Fate/EXTRA_.
+En una [escena de juego](https://youtu.be/efdN69QscAg), [Nero Claudius Caesar Augustus Germanicus (no es broma)](https://typemoon.fandom.com/it/wiki/Nero) viste un disfraz de **Santa Claus**, y baila alrededor de lo que creo que es un pasillo, cantando una **parodia** original de _Jingle Bells_, de solo 4 versos.
+
+<video class="SmallVideoQuote Blockquote NoImgCenter" title="El vídeo de la escena del juego." src="{{< assetsRoot >}}/Media/Padoru/PadoruPadoru.webm" controles="true" muted="true" loop="true" autoplay="true">El vídeo de la escena del juego.</video >
+
+> HASHIRE SORI YO
+> KAZE NO TU NI
+> TSUKIMIHARA WO
+> PADORU PADORU
+
+Intenté buscar el significado de la pequeña canción, pero [no obtuve resultados satisfactorios] (https://anime.stackexchange.com/questions/43895/what-does-padoru-padoru-mean).
+Lo único que sé es que el **último verso** (de donde proviene el nombre popular del meme), "_padoru padoru_", es el **equivalente japonés** de "_cloppete cloppete_" italiano, la **onomatopeya** del sonido de **pezuñas de reno**. No sé cómo es posible pero, sinceramente, es el detalle menos extraño.
+
+## Costumbres de Internet
+
+**En línea**, se han desarrollado varias **tradiciones** en torno a este meme durante varios años.
+Los más banales son el excesivo **recompartir** del **vídeo** original o sus imágenes GIF, o la producción y el intercambio de **memes originales** que hacen referencia al concepto inicial.
+Luego, la gente empezó a desaprobar la expresión "temporada de Navidad", en favor de una más mágica "**_temporada de Padoru_**" - que en realidad no es un término de reemplazo 1:1, porque también puede indicar las semanas un momento antes. quizás los de Adviento, los de noviembre que mencioné al principio y en los que ya estamos arrancando con la **guerrilla Padoru** en las plataformas comunicativas.
+
+La mejor costumbre (por su pasivo-agresividad), según mi gusto, es cambiar las fotos de los distintos perfiles con la imagen de **un Padoru**.
+Hay personas que utilizan su sentido del humor compartido para implementar esto como una operación (muy relativamente) **masiva**. Luego están quienes observan el fenómeno pero no son conscientes del significado, no entienden, se enojan y se **confunden** hasta el punto de golpearse; o, que lo conoce perfectamente, y se enoja aún más porque bueno, _a lo mejor desprecia la Navidad_.
+
+Si estás leyendo con **atención**, te habrás dado cuenta de que acabo de utilizar, como era de esperar, el artículo indefinido... <small>Si no te has dado cuenta, te estás distrayendo, y por tanto, <del >como castigo </del> por tu bien, ahora debo obligarte a cantar la canción anterior en voz alta 3 veces 👺.</small>
+
+## Alta personalización
+
+Un **factor importante** que ha permitido que este meme se convierta en el fenómeno que es se puede ver en que es **extremadamente personalizable**.
+No sé cuándo empezó esta tendencia, pero en algún momento hubo quienes vieron que **el** Padoru, el **dibujo** original de Nero en la secuencia de vídeo que desencadenó todo, es realmente **simple para remezclar**.
+
+Si lo miras con una inventiva ausente o al menos con los pies en la tierra, te das cuenta de que puedes **cambiar los colores** en un abrir y cerrar de ojos por otros que también pueden quedar bien, y casi tienes un nuevo diseño.
+Sin embargo, aquellos que tengan un mínimo de **creatividad** pueden sin dificultad intentar **modificar** algunas de las **formas** del personaje, cambiando las derechas aquí y allá para reconstruir un **personaje** totalmente. ** otro** - ya sea original o ya existente, pero sólo diseñado en otros estilos - en la forma de esa cosita sonriente que corre de un lado a otro riendo con su verso festivo.
+
+Esto es tan extremadamente fácil que **incluso yo**, que normalmente creo _glitches_ reales si intento dibujar algo artístico (o algo menos técnico), **pude crear mi propio** Padoru muy personal sin ningún sufrimiento.
+En apenas 2 rarísimas horas, una mañana del 1 de diciembre en el colegio -no recuerdo si era día de asamblea o de sustitutos varios- un poco **trazando** las líneas básicas del aspecto Padoru, un poco* *presentando características originales** (que derivé de mi personaje 3D, el que aparece en algunas de mis fotos de perfil durante todo el año), con una aplicación de dibujo genérica en mi teléfono inteligente hice lo que sentí que tenía que hacer.
+El resultado fue que, simplemente, salió **algo** normal; ¡sin horror! Muy bien.
+
+[![Captura de pantalla de los mensajes del año pasado sobre la creación del Octt Padoru. En el primero había terminado los delineados y estaba empezando a teñirme el cabello de morado. En el segundo, completé el trabajo y envié el archivo PNG.]({{< assetsRoot >}}/Media/Padoru/OctoVoLTE-15989.avif)]({{< assetsRoot >}}/Media/Padoru/Octt- Padoru .png)
+
+## Mis "participaciones"
+
+Por lo tanto, el año pasado **creé** mi Padoru específicamente para usarlo como **foto de perfil** (en Telegram), y lo hice.
+El año anterior había usado uno que no era mío, inspirado en el [kitsune Senko-san](http://web.archive.org/web/20221217073124/https://teddit.net/r/Padoru/comments /czxoa7/ senko_san_at_your_service), y el año anterior había publicado otros tipos de memes de Padoru.
+
+**Este año** no he hecho absolutamente nada**... y lo curioso es que no sé cómo explicarlo. Cero. 😶
+Lo que sospecho es que, simplemente, **me olvido 💀** (_Me olvidé de ello 💀_). Hace 2 semanas desafortunadamente tenía **demasiadas cosas en mente**: primero mi instancia de Misskey que no funciona correctamente y tengo que ejecutarla, luego la solución con ChatGPT, está claro que realmente no había forma de reservar 30 segundos de tiempo. No actualizo la foto de ni una sola de mis cuentas en línea.
+A estas alturas no sé si hacer el **cambio** ahora y por tanto aprovechar todo el tiempo que queda hasta el final del periodo navideño para ser _Padoruante_, o seguir una lógica mínima y esperar a que empiecen las fiestas. la próxima semana: la última semana de Adviento y la primera semana de vacaciones, tendría sentido.
+
+El año pasado quizás hice todo lo posible con las fotografías digitales, pero **el lado físico** fue accidentalmente **descuidado** por mí.
+Vayamos en orden.
+
+De hecho, todos mis padres pusieron las **decoraciones** navideñas genéricas** en la casa** - **mi madre** en particular, que también tiene **poder de veto** sobre cualquier propuesta demasiado progresista con respecto al árbol de la gran Navidad - en los primeros días de diciembre.
+Entre las cosas que se recuperan del ático cada año, también hay un pequeño **árbol de escritorio** que es _prácticamente_ mío. Tiene **luces integradas**, alimentadas por pilas AA, pero en sí mismo no es nada especial. O mejor dicho, así era antes de que lo **revolucionara**, hace **3 años** (¡era 2019!).
+
+## Modificación del retoño
+
+Creo que el **destello de genialidad** llegó después de ver una foto en **Internet**, que mostraba un **árbol de Navidad** (de tamaño normal) con un par de **adheridos** a él. padrinos**; Exactamente como otro tipo de decoraciones que cuelgan, pero menos aceptables socialmente.
+La idea se había apoderado de mí y en ese momento tuve que recrear lo mismo yo mismo. Abrí lo que era mi motor de búsqueda web de confianza en ese momento y busqué "imágenes de padorus" (o algo así) para crear un **conjunto variado** de algunos de esos pequeños dibujos, **descargando** los que más me llamaron la atención y **me gustaron** estéticamente.
+
+En ese momento tuve una **elección** frente a mí: ¿los imprimo lo suficientemente grandes y los pongo en el **árbol grande**, o los imprimo pequeños para poder ponerlos en el **pequeño? árbol**?
+Para ser honesto, **no era una pregunta**, ya que la primera opción automáticamente se descartaría debido al **veto** de mi madre, pero la segunda opción ciertamente me intrigó: el arbolito era (y es) en **mi habitación**, por lo que su normalidad se desperdiciaría por completo sin algún adorno creativo.
+
+Una vez terminada la **impresión**, todo lo que tuve que hacer fue **recortar**, más o menos toscamente (sin embargo, extrañamente fue necesario una buena cantidad de trabajo), los distintos Padoru, y luego **adjuntarlos **al árbol con un poco de pegamento caliente.
+Resultó ser **lo que quería**, así que agradecí el trabajo y tomé una foto para establecerla como mi foto de perfil. Al año siguiente, el árbol **permaneció como estaba**.
+
+![El mini-árbol como estaba hasta el otro día, antes de hacer lo que hice ahora. Hay menos de una docena de Padoru]({{< assetsRoot >}}/Media/Padoru/Padoru-Tree-2019-2022.avif)
+
+## En el presente
+
+En cuanto a **este año**, una vez que finalmente entré mentalmente en la _atmósfera de Padorizia_, **contemplando** ese objeto que lleva días ahí en mi **mesita de noche**, pensé que lo mismo era un poco' * *vacío** y se necesita **otro Padoru**.
+
+El otro día **pensé** que entonces debería **buscar** algunos **nuevos** en línea para imprimirlos, pero un momento después recuerdo **una carpeta**, que encontré el mes pasado en el PC mientras estaba limpiando.
+Contiene **mi Padoru** original, **y varios otros** que recordé haber descargado, pero que **no** estaba muy **seguro de haber** **impreso** alguna vez. Todos los archivos tienen fecha de diciembre de 2021, lo cual es obvio para el único que creé, pero realmente curioso para los demás, si se considera el escenario completo.
+
+![Algunas de las imágenes individuales de Padoru presentes en la carpeta; en total 23. Tenga en cuenta que tienen fecha del 8 de diciembre de 2022.]({{<assetsRoot >}}/Media/Padoru/Padoru-Folder-2021.png)
+
+Aún más curioso, uno de los archivos presentes allí es una imagen, con una relación de aspecto igual a la de una hoja A4, donde están ordenadas todas las imágenes individuales de la carpeta.<sup id="fnref1"><a href= " #fn1">1</a></sup>
+"_Lo habré compuesto el año pasado y al final quizás nunca lo tenga impreso_", pienso; y, sin embargo, algo más en el fondo de mi mente me dice que **en realidad lo imprimí** bien, y tal vez simplemente **nunca lo usé** al final. Seguramente nunca he pegado esos Padoru al árbol, porque solo están los de hace 3 años.
+Durante menos de un cuarto de hora busco esta desafortunada **hoja** en mi habitación pero, al no encontrarla, **decido reimprimirla**. Oh Dios, de hecho encontré una hoja de Padoru... más o menos: encontré un fragmento de la hoja de 2019, con 3 imágenes que nunca usé en ese momento.
+
+Sin perder más tiempo, envío el documento a la **impresora** de casa, que al instante **me devuelve**... ¿una **hoja en blanco**? Lo parecía, pero luego lo levanté y noté que había sido impreso. ¿La imagen? **¡NO! ¡UNA MANCHA! 🤬**
+Inmediatamente, **la ira** aparece, pero un segundo después es **abrumada** por un sentimiento aún más fuerte: uno de "**ya visto**".
+
+![Foto de hoja mal impresa. En el lugar de algunos Padoru hay manchas de color, en otros solo se ven los contornos, en otros nada.]({{<assetsRoot >}}/Media/Padoru/Padoru-Failed-Print.jpg)
+
+### ...Un poco antes
+
+En este punto, **algo** vuelve a mí**, y abro el historial de mi canal de Telegram (que uso como micro-microblog) para buscar respuestas a mis sospechas: bueno, **había impreso ** estas imágenes **el año pasado**. ¡Ahora lo recuerdo bien!
+**Exactamente el mismo **problema** ocurrió con la impresión yendo al infierno lo cual, extrañamente, ocurre en 2 impresoras diferentes, solo cuando se imprime a través de la aplicación oficial **Epson** (fabricante de la impresora) para Android, y solo para esto imagen (PNG 2480x3472 de 9 MB), entre todas las que me ha tocado imprimir en mi vida.
+Por primera vez perdí el tiempo con mi padre, que ya había utilizado la impresora sin problemas especiales, primero cambiando un cartucho marcado como vacío y luego limpiando los cabezales; después de no sé cuántos minutos perdidos, al **tercer intento** imprimí desde la PC con Windows de mi padre, y la imagen **finalmente** salió. 😶u200d🌫️🔪
+
+Esta vez sin embargo, tan pronto como conecté todos los puntos por un momento, inmediatamente intenté nuevamente desde la PC...
+¿Es realmente demasiado esperar que la aplicación oficial funcione como debería, o al menos dé un error, que nunca me dio, si por alguna razón no puede manejar un archivo correctamente? Debería enviar **al infierno** de una vez por todas estas impresoras **patentadas**, podridas y malolientes, recién salidas del infierno, y construir la mía propia: con un microcontrolador, servomotores y marcadores, como la mayoría de la gente ya sabe [ lo han hecho](https://youtu.be/AlBPFC41FsM).
+
+Sin embargo, mi intención, ese día lejano, era **trollear**<sup id="fnref2"><a href="#fn2">2</a></sup> **mi madre**: imprimir unos nuevos Padoru, todos diferentes y **de colores**, para **pegarlos** en el gran árbol de Navidad, que ese año había sido decorado por ella con adornos categóricamente **tendiendo al blanco**.
+En resumen, imprimí todos los que estaban allí, pero puse **solo 1** número en el árbol (entre otras cosas, parece que pasaron 2 días antes de que mi madre se diera cuenta 😂), así que está claro que **planeé* * hacer algo **con esos otros**. Probablemente quería **ponerlos** en el **miniárbol**, pero (aún así, evidentemente) **nunca lo he hecho**. _¿Me falsifiqué (💀)?_ Muy probablemente: estas últimas diciembre también fueron semanas algo movidas, pero dejé llegar enero (momento de volver a congelar la Navidad y todos los adornos, Padoru y demás) sin hacer nada, así que la cosa tendrá que acabar. **se fue** de mi mente**.
+
+## Conclusión concreta
+
+Entre **ayer y anteayer**, primero **recorté** una buena parte del **Padoru**; no todos, porque sino paso muchas horas con ellos, y porque no quedará ninguno en mi árbol de escritorio. 🤷u200d♀️
+Esta vez usé las tijeras de manera muy meticulosa, y **recorté las figuras** con una muy alta **definición**; según mis _estándares de trituración_ de _dibujos que tienen muchos detalles minuciosos de formas complejas_, al menos lo es.
+Después de esta tarea - que también sería relajante, si no hubiera tenido que agacharme por la luz - con el **pegamento caliente**, lentamente (que todavía requiere mucho menos tiempo que cortar) **pegué** todas las figuras a las paredes externas de hojas del **árbol**. **Aproveché** para **arreglar** los elementos pegados hace 3 años, que aguantaban pero no muy sólidamente... Probablemente **hice mal el trabajo**, **en ese momento **.
+
+![Foto del retoño después del ataque]({{< assetsRoot >}}/Media/Padoru/Padoru-Tree-New-0.webp)
+Este aquí es el resultado, realmente me gusta mucho.
+
+Aparte de la **belleza del objeto** a nivel **personal** para mí, y de haberme dado cuenta de cómo podría - ya sólo ante mis ojos - volverse más hermoso, si se hubiera vuelto aún **más nuevo* * y menos estándar, lo que está en juego al **escribir** un artículo aquí **funcionó de maravilla**: me hizo **completar** una tarea **manual** muy simple* *, prácticamente un bricolaje de jardín de infantes, sin mi ¡Cerebro cancelándolo después de medio día!
+
+Para concluir, en esencia podemos - no irónicamente - decir que **me tomó un año entero** lograr finalmente **unir** una cantidad satisfactoria de pequeño Padoru a mi arbolito.
+**Anteayer** comencé a **escribir** este artículo, **creyendo** que simplemente hablaría de cómo **surgió** la idea para mí y qué hice para expandirla en estos dos días. , pero luego **redescubrí** estos **detalles** que están directamente **entrelazados** con **el año pasado**... maravilloso. Creo que la **historia** en realidad se volvió **más interesante** de contar, **después de estas desventuras** debido al funcionamiento cuestionable de mi cerebro.
+
+## {{% i18n notas-refs %}}
+
+* **Actualización** a partir del **24-12-2022**: He subido algunas fotos más a la historia en Pixelfed: [pixelfed.uno/p/octo/512223099419845225](https://pixelfed. uno/p/octo/512223099419845225).
+
+---
+
+1. En el canal encontré el comando **[ImageMagick](https://imagemagick.org)** que utilicé para crear la imagen grande que contiene todas las demás dispuestas en una cuadrícula, lo pongo aquí para aquellos que necesitan para imprimir cosas de este tipo: (a ejecutar en la carpeta con todas las imágenes a incluir) `montage -define png:size=496x496 -geometry 496x496 -tile 5x7 -auto-orient *OUTPUT.png`. Los valores de "496x496" y "5x7" se pueden modificar como se desee, aquí están colocados para que el archivo resultante tenga **dimensiones** muy cercanas a las de **A4**, con **35 imágenes* * máximo en una sola hoja, todas escaladas **iguales** y **cuadradas**. Quizás la imagen final deba imprimirse **agregando** algunos buenos **márgenes** primero; de lo contrario, corre el riesgo de quedar ligeramente recortada. [↩](#fnref1)
+
+2. **trolling**: En este caso, gastar una broma inofensiva. [↩](#fnref2)
+
+3. **stare bend**: "_to bend_" en inglés significa "_to bend_". Utilizo la expresión deliberadamente incorrecta "_stare bend_" para significar "_stare bend_" (con la espalda o el cuello). Es un meme estúpido mío que nació en circunstancias curiosas, tal vez algún día lo explique. [↩](#fnref3)
diff --git a/es/blog/2023-03-18-Cattiva-Interfaccia-Partizione-Distrutta.md b/es/blog/2023-03-18-Cattiva-Interfaccia-Partizione-Distrutta.md
new file mode 100644
index 0000000..1689f69
--- /dev/null
+++ b/es/blog/2023-03-18-Cattiva-Interfaccia-Partizione-Distrutta.md
@@ -0,0 +1,170 @@
++++
+Title = "🥴 ¿Interfaz fea? ¡Todos los archivos destruidos!"
+Date = 2023-03-18
+Description = "Para hacer las cosas con prisa, accidentalmente borré parte del disco de la PC. Pero no es sólo culpa mía: el programa que utilicé está mal diseñado."
+Downsync = "/it/blog/Bad-Interface-Partition-Destroyed.html"
+Aliases = [ "/Publicaciones/2023-03-18-Bad-Interface-Partition-Destroyed.html" ]
+Categories = [ "Administrador de sistemas" ]
+Lastmod = 2023-03-20
++++
+
+{{< noticeAutomaticTranslation it >}}
+
+
+
+<!-- Generado automáticamente por ListedDownsync.js. No lo edite (a menos que también establezca "% Downsync = False"); se sobrescribirá. -->
+
+**Comparemos visualmente** dos aplicaciones para PC: **Discos GNOME y GParted**.
+
+![Las ventanas de los dos programas comparadas.]({{< assetsRoot >}}/Media/Partioning-Mar-2023/SideBySide.png)
+
+Ambas son herramientas de partición de discos y, en términos generales, cumplen las mismas tareas; sólo hay **alguna diferencia** en funciones adicionales o más soporte a favor de un programa u otro. A pesar de esto, las dos herramientas presentan **diferencias obvias** en su **interfaz gráfica**.
+
+## Tienes que tener ambos
+
+Generalmente mantengo estos dos programas instalados y los **uso de una manera bastante **alterna**, porque:
+
+<table><thead><tr><th>GParted</th><th>Discos GNOME</th></tr></thead><tbody><tr><td><img src="{{< assetsRoot >}}/Media/Partioning-Mar-2023/GParted-Advanced.png" alt="Vista de GParted de información detallada sobre un disco."></td><td><img src="{{< assetsRoot >}}/Media/Partioning-Mar-2023/GNOME-Advanced.png" alt="Menú emergente global de discos GNOME, que tiene algunas características especiales."></td></tr><tr ><td><strong>GParted</strong> tiene <strong>menos funciones distintas</strong>, pero todo tiene su lugar y un nivel <strong>suficiente</strong> de <strong>profundidad</strong>. strong> y características: información de disco de bajo nivel, formateo en toneladas de formatos y algunos otros detalles.</td><td><strong>Discos GNOME</strong> tiene <strong>menos profundidad</strong> > con operaciones individuales, pero ofrece algunas <strong>funciones extra</strong> no estrictamente vinculadas a la modificación de particiones, lo que siempre es útil: gestión de energía y rendimiento de los discos, una interfaz para el protocolo SMART y también una herramienta para realizar pruebas. ¡Rendimiento de la memoria!</td></tr></tbody></table>
+
+## ¡Era una misión sencilla!
+
+Anteayer, cuando inicié un **USB en vivo** Linux en [mi computadora portátil](https://sitoctt.octt.eu.org/Posts/2022-07-09-Come-ho-Riparato-il- my-Portatile-con-25-Euro.html), tenía en mente completar **sin daños** una misión _teóricamente_ fácil e indolora:
+
+1. **Liberar espacio** en el disco de la PC, eliminando la mayoría de los archivos, excepto aquellos que quería conservar por un momento (para administrar quizás en el futuro).
+2. **Cambie el tamaño de la partición** del disco, ya que en este momento estará bastante vacía.
+3. **Cree una nueva** partición lo suficientemente grande para instalar el nuevo sistema operativo.<sup id="fnref1"><a href="#fn1">1</a></sup>
+4. **Mueva archivos** de la partición antigua a la nueva, reduciendo gradualmente la primera y ampliando la segunda, **hasta** poder **eliminar la antigua**.
+
+## Demasiado desorden.
+
+...En la práctica, _algo salió un poco mal_. ¡No pudo haber sido una velada tranquila! 😾
+
+Esta vez, por el simple hecho de que al buscar un editor de particiones entre las aplicaciones preinstaladas del sistema live en cuestión, **queriendo hacerlo de inmediato**, el primer programa que me llamó la atención fue **GNOME Discos** .
+Oh, debería haberme mantenido alejado. Y hay muchas razones:
+
+#### 1\. Los discos físicos se mezclan con particiones virtuales montadas a partir de discos físicos, en la lista a la izquierda de la ventana
+
+Ya en este punto, si (como en mi caso) tienes particiones de _tipo extraño_, es decir, [LVM](https://wiki.archlinux.org/title/LVM), la situación se vuelve fea, porque **no lo es. deja claro dónde** tienes que ir** para realizar cambios.<sup id="fnref2"><a href="#fn2">2</a></sup>
+
+<table><thead><tr><th>GParted</th><th>Discos GNOME</th></tr></thead><tbody><tr><td><img src="{{< assetsRoot >}}/Media/Partioning-Mar-2023/GParted-List.png" alt="El selector de lista de discos en GParted."></td><td><img src="{{< assetsRoot >}}/Media/Partioning-Mar-2023/GNOME-List.png" alt="La vista de lista de discos y particiones en discos GNOME."></td></tr><tr><td>< strong>GParted< /strong> solo tiene una <strong>lista de dispositivos</strong> (discos reales con seguridad, pero creo que también dispositivos virtuales) para seleccionar primero, y luego la vista grande con todas las particiones para el dispositivo elegido. Es <strong>ordenado</strong> y lógico.</td><td><strong>En los discos GNOME</strong>, sin embargo, para hacer lo que necesitas hacer, <strong>vas</strong> ¿A vista de disco o <strong>dónde?</strong> En el primer caso hay <strong>algunas opciones</strong> y otras <strong>faltan</strong>. ¿Probamos desde la vista dedicada a la partición virtual? Aquí también la lista de opciones está decididamente neutralizada, entre otras cosas tanto en el sentido de los botones de iconos rápidos como en el de los botones del menú emergente... pero ahora veamos qué problemas tienen.</td></ tr></tbody></table>
+
+#### 2\. Según corresponda, los íconos rápidos disponibles para cada partición aparecen y desaparecen
+
+Mientras está en **GParted**, la lista de **botones de íconos** en la parte superior de la ventana **nunca cambia**; más bien, los botones individuales se oscurecen o aclaran, dependiendo de si se pueden operar en la selección actual. o no - **en los Discos GNOME las teclas de acceso rápido** - de hecho, también están colocadas de una manera extraña, atrapadas debajo del área de la tabla de particiones, sobre lo cual honestamente ni siquiera puedo comentar - **aparecen o desaparecen** por completo.
+A continuación se muestran los casos que he visto, pero quizás haya incluso más posibles, quién sabe:
+
+* En el extremo izquierdo, para algunas selecciones ves un botón **reproducir/detener** (montar/desmontar partición), otras veces exactamente en el mismo punto hay un **candado** (bloquear/desbloquear partición cifrada), otras veces una **cruz** (crea una partición en un espacio vacío) y en algunos casos **nada**.
+* Inmediatamente a la derecha, un botón **engranaje**, que abre un menú emergente con una lista más completa de opciones para la partición - notamos que esto termina **subiendo hacia el extremo izquierdo**, si antes No hay nada, solo para confundir más.
+*Por último, en el extremo derecho, en algunos casos puede aparecer un botón con un **guión sobre fondo rojo** (destruir partición).
+
+Ehh, esto no es tan bueno, porque hace **imposible asociar mentalmente** una _microzona_ específica de la ventana como dedicada a una operación específica. Y esto es potencialmente **peligroso**, si se tiene en cuenta el gran problema 5 (a continuación).
+
+#### 3\. El menú emergente de opciones en una partición usa solo etiquetas de texto, nunca un solo ícono
+
+Un detalle aparentemente pequeño, pero que en realidad es bastante importante.
+Una cadena de texto permite entender inequívocamente qué hace una determinada clave, a diferencia de lo que puede pasar cuando solo tienes iconos, pero **lo mejor se obtendría** combinando las dos cosas: **teclas acompañadas de iconos**.
+
+<table><thead><tr><th>GParted</th><th>Discos GNOME</th></tr></thead><tbody><tr><td><img src="{{< assetsRoot >}}/Media/Partioning-Mar-2023/GParted-Context-Menu.png" alt="El menú contextual de una partición en GParted."></td><td><img src="{{< assetsRoot >}}/Media/Partioning-Mar-2023/GNOME-Context-Menu.png" alt="El menú de opciones de una partición en discos GNOME."></td></tr><tr>< td ><strong>GParted hace esto para sus menús contextuales (al menos en los elementos más importantes), y esto le permite memorizar inmediatamente la <strong>acción</strong> correspondiente a cada opción y recuperarla inmediatamente <strong>en un vistazo</strong>.</td><td>Personalmente, <strong>al usar discos GNOME</strong> siempre me encuentro <strong>teniendo que releer</strong> una buena parte de la lista para seleccionar algo, aunque no es más largo que el de GParted, precisamente porque <strong>faltan los iconos</strong>.</td></tr></tbody></table>
+
+#### 4\. Las teclas de acceso rápido y los menús emergentes no son alternativas entre sí
+
+<table><thead><tr><th>GParted</th><th>Discos GNOME</th></tr></thead><tbody><tr><td><img src="{{< assetsRoot >}}/Media/Partioning-Mar-2023/GParted-Buttons.png" alt="La barra de iconos rápidos en GParted."></td><td><img src="{{< assetsRoot >}}/Media/Partioning-Mar-2023/GNOME-Buttons-1.png" alt="Creación de botones y opciones en una partición en discos GNOME."> <img src="{{< assetsRoot >}}/Media/ Partioning -Mar-2023/GNOME-Buttons-2.png" alt="Desmontar botones y opciones en una partición en Discos GNOME."> <img src="{{< assetsRoot >}}/Media/Partioning-Mar-2023 / GNOME-Buttons-3.png" alt="Botones de bloqueo y opciones en una partición en Discos GNOME."> <img src="{{< assetsRoot >}}/Media/Partioning-Mar-2023/GNOME-Buttons- 4 .png" alt="Botón Opciones en una partición en Discos GNOME."></td></tr><tr><td>En <strong>GParted</strong> primero tienes el <strong>menú de la barra de tareas </strong> (de los cuales varios menús también pueden recordarse como contextuales en algunas áreas), que realmente contiene <strong>todas las operaciones</strong> posibles en el programa; sólo <strong>el</strong> hay una barra con <strong>iconos</strong> útiles para recordar rápidamente las acciones probablemente más comunes. En la práctica, mientras tengas la barra de menú, <strong>puedes</strong> incluso <strong>olvidarte</strong> de la existencia de <strong>esos pequeños íconos</strong> allí.</td> < td>Con los <strong>discos GNOME</strong> esto <strong>no es posible</strong>. En realidad, en <a href="https://duckduckgo.com/?q=gtk3+examples&ia=images&iax=images" rel="noopener nofollow" target="_blank">varias aplicaciones GTK3</a> es así : hay <strong>acciones</strong> fijadas en <strong>teclas-etiquetas</strong> en un menú, y otras fijadas en <strong>teclas-iconos</strong> directamente visibles. Sin embargo, en general, esos botones no <strong>desaparecen ni aparecen parcialmente</strong> cuando el estado cambia dentro de la misma vista de la aplicación. Tal vez tenga gustos extraños, pero esto afecta mi cerebro cuando uso el software.</td></tr></tbody></table>
+
+Para comprenderlo, simplemente compare los botones de esta tabla con las opciones del menú contextual que se ven en la de arriba.
+
+## ¿Qué he hecho?
+
+¡Todos estos factores juntos condujeron a un enorme **patatrac**!
+Entonces, ¿qué hago? Necesito **desmontar** la **partición** antes de poder **cambiar su tamaño**.
+
+Salgo de **vista de disco**, y allí está **solo el botón** para el menú **opciones** - además de lo que me vendrá a la mente _solo después_ cuando ya esté **ya roto** para break up, es el botón para **destruir** la partición.
+En la lista de opciones leo todo y **ni siquiera veo** una entrada para **desmontar** la partición. _Meh_.
+
+Paso por la **pantalla** dedicada a esa **partición** montada, y vuelvo a abrir ese menú por no sé qué motivo, y con razón, sigo sin encontrar nada.
+Al lado del botón del menú de opciones **estaba en teoría el botón de detener**, para desmontar la partición, pero está claro que realmente **no** lo noté**.
+
+Voy **de ida y vuelta** entre las dos pantallas unas diez veces, y nada, estoy realmente **ciega**.
+
+En cierto momento, mi inconsciente se aburre de todo este **dar vueltas**, y finalmente me permite notar otro **botón**... el peligroso **rojo**. _Ay ay_.
+Lo presiono y, sinceramente, ni siquiera recuerdo si eliminé el diálogo de confirmación una vez, que no estaba en condiciones psicológicas de leer, y luego presioné el botón nuevamente para inmediatamente después confirmar el diálogo, pero una cosa está clara:
+
+Si hasta ese momento no podía pensar con claridad, porque **con cada respiración** un áspero **"WTF?!"** sonaba en mi cabeza, fue cuestión de unos segundos desde el momento del * *clic fatal** porque un **mal presentimiento** comenzó a aparecer en mi cabeza perforada, deformada, llena de maní caducado... 😰️
+
+...Bueno, ¿y qué? ¿Qué es?
+...
+_Ohhhhah_, está bien, **tú ganas**. Lo admito: **Yo también golpeo**. Sí. ¿Feliz? Al final moví la mano para hacer clic, claro... ¡Pero en mi vida **he hecho** estas operaciones **muchas veces**! Incluso usando Discos GNOME, ¡a veces entre muchos! 😭️
+
+En cualquier caso, no, no le echaré toda la culpa al **pobre Octt** de hace tres días. Ahora juego mi _carta trampa_ y expongo el verdadero **toque de desgracia** sin el cual probablemente me habría salvado:
+
+#### 5\. Cada acción se realiza cuando tú la solicitas, no hay cola
+
+Debo admitir que a veces **en GParted** he estado cerca de la tragedia** - pero realmente una tragedia, no como esta vez que, considerando todo, todavía estoy experimentando.
+La diferencia, sin embargo, radica precisamente en esta palabrita: con **GParted** el desastre siempre ha sucedido como máximo **_casi_**, pero con **Discos GNOME** esta vez se ha **consumido** y eso es él.
+
+En **GParted** las operaciones que solicitas terminan en una **cola**, que debe aplicarse manualmente una vez que decidas continuar.
+Y aquí también nos centramos en los **pequeños detalles**, pero algo como esto pesa mucho en la factura final. Lo podemos ver así: **en ese caso**, hay que **equivocarse** dos (**2**) **veces** para hacer un desastre, mientras que con el programa GNOME una ( 1) el error es suficiente.
+
+![La vista de la cola de operaciones en GParted.]({{< assetsRoot >}}/Media/Partioning-Mar-2023/GParted-Queue.png)
+
+## "¿Hay algún daño?"
+
+En cualquier caso, noté que, **después** de dar la orden de **eliminar la partición**, ésta **permaneció** montable y todo el sistema de archivos era **navegable**.
+Probablemente, lo que Linux necesitaba para usar la partición permanecía en la memoria (RAM), y dado que todos los datos nunca se eliminaban con una simple eliminación rápida de una partición, todos seguían siendo legibles.
+
+Para ser honesto, viendo la situación así, **ni siquiera** me estaba dando** la realidad, todavía **no entendía** si mis **datos** habían sido **condenados** o no. ..
+Interfaz poco clara, _lo dije_.
+
+Cuando la sensación de prisa pasó y dio paso a **incomodidad**, busqué GParted**, descubrí que estaba incluido en el sistema en vivo y lo inicié.
+En lugar de la partición veo "espacio vacío"... oh **sí, ya está hecho**. ¿Pero cómo es que me dejó **eliminar la partición** sin** obligarme a **desmontarla** primero? ¡Qué barbarie! GParted no permite esto, por buenas razones.
+
+Sin embargo, en el fondo todavía **no he aceptado** que fue cancelado.
+Quiero ver si, después de reiniciar, desaparece permanentemente.
+
+Y así es, **sin** siquiera **preocuparme** por copiar un fragmento de archivo - porque ya era tarde y tenía que prepararme para irme a dormir - que **reinicio**.
+¡Oh, sí, veo la pantalla negra de GRUB y no el sistema arrancando! ...**Está todo perdido**, no tiene sentido darle la vuelta ahora.
+
+"_Después de que hiciste el daño, ¿¡¿pensaste en reiniciar inmediatamente sin siquiera guardar los archivos más importantes?!?! Pero entonces eres un idiota certificado, ¡dos veces, no una!_"
+_Ooooooooooooo_, ¿cómo te atreves? ¿Cómo te atreves a tener **tanta razón** si el blog es MÍO?
+
+Lo único que podemos hacer ahora es **recuento de daños**. No he perdido datos únicos y muy importantes, lo que **ya no tengo debería** en teoría poder **volver a descargarlo o reconstruir**. Hablemos de:
+
+* 40 GB de datos exportados desde mi antigua cuenta de Google; Cuenta que planeaba eliminar, pero no había terminado de transferir todo, así que creo que **todavía está todo en la nube**.
+
+* Varios **archivos** grandes y pequeños descargados **de la Web**, posiblemente algunos difíciles de encontrar, pero **nada vital**.
+
+* **Códigos fuente cambiados**; Estamos hablando de intentos de portabilidad para plataformas oscuras que probé y fallé, u otros **experimentos muy olvidables**.
+
+* **Volcados de discos** que todavía tengo en casa (algunos ya subidos a [Archive.org](https://archive.org/details/@andrigamerita)), **o copias adicionales** de otros datos .
+
+* Documentos cuya **relevancia** actual es **nula**.
+
+
+Sin embargo, si **olvidé algo** importante en esta lista, tal vez **no era importante**, y podemos estar tranquilos. De lo contrario lo recordaría, ¿verdad? _Bueno, conociéndome..._
+
+## Evitar...
+
+La **moraleja** de esta **mala historia** se puede condensar en:
+
+1. Evite los discos GNOME.
+2. **Tenga cuidado** al trabajar con particiones, incluso si lo ha hecho 50 veces en el pasado.
+3. **¡Evita**, absolutamente, los **Discos GNOME**!
+
+Y cierro con un **consejo**, o mejor dicho, una **filosofía de desarrollo**, que todos los que diseñamos **UI** (incluso yo, en mis cosas, no lo escondo) olvidamos con demasiada frecuencia: [El usuario está borracho](https://www.youtube.com/watch?v=r2CbbBLVaPk).
+
+<iframe src="https://www.youtube-nocookie.com/embed/r2CbbBLVaPk" style="altura: calc(100vh / 16 * 9);" clase="YouTube"></iframe>
+
+Entonces, saludos. Para el futuro **espero** no **perder datos** de manera estúpida (¡para ti y para mí!). 👋
+
+_**P.D:** La distribución de Linux que instalé esta vez es [Pop!\_OS](https://pop.system76.com/). Tenía muchas ganas de probarlo, pero en 2 ocasiones intenté instalarlo en la PC de escritorio y siempre daba error. Aquí en la laptop funcionó, ¡guau, así que no es una distro rota! (**Quizás** 👀)_
+
+## {{% i18n notas-refs %}}
+
+---
+
+1. El sistema que tenía hasta ese momento, Linux Mint, versión 19.3, después de 3 años:
+
+<dl><dt><strong>Se ha vuelto obsoleto:</strong></dt><dd>La versión 19.3 está descontinuada y los repositorios ya no reciben software nuevo. Entonces, debería haber actualizado a la versión actual de Mint, pero aparentemente <strong>debería haberlo hecho de todos modos</strong> reinstalándolo <strong>desde cero</strong> (en <code class="prettyprint">apt dist-upgrade </code> no hay nuevas actualizaciones)</dd><dt><strong>Está roto:</strong></dt><dd>Algunas cosas (como controladores de video rotos y el entorno de escritorio que solo se inicia en modo alternativo) son definitivamente culpa mía (<em>me equivoqué</em> con los controladores <a href="https://en.wikipedia.org/wiki/Nvidia#:%7E:text=Nvidia "rel="noopener nofollow" target="_blank">ACCIDIA</a> en las últimas semanas), pero a otros (¿¡Bluetooth ya no funciona!?) Yo diría que no :/. En cualquier caso, <strong>cuando el sistema está tan roto, es más rápido reinstalar todo</strong>...</dd></dl>
+
+ [↩](#fnref1)
+
+2. Quizás sí, soy un idiota, pero no hasta el punto de montar voluntariamente los tabiques con una estructura que me es ajena. En ese momento, de manera muy simple, instalé Linux Mint con la configuración guiada predeterminada. Cada vez que instalaba Linux utilizaba la partición manual, en lugar de elegir borrar todo el disco y dejar que el programa de instalación decidiera las cosas, siempre creaba particiones normales. Entonces... **no me culpes**, [kthx](https://en.m.wiktionary.org/wiki/kthx#:%7E:text=\(Internet%20slang\)%20Abbreviation % 20de%20bien%2C%20gracias.)? [↩](#fnref2)
diff --git a/es/miscellanea/Raccolta-Videogiochi/_index.md b/es/miscellanea/Raccolta-Videogiochi/_index.md
index a1d9f5f..215d4ff 100644
--- a/es/miscellanea/Raccolta-Videogiochi/_index.md
+++ b/es/miscellanea/Raccolta-Videogiochi/_index.md
@@ -5,7 +5,7 @@ Aliases = [
 ]
 Categories = [ "Juegos" ]
 #Style = @import "[staticoso:Site:RelativeRoot]Assets/Pages/Videogame-Collection.css";
-Lastmod = 2023-02-01
+Lastmod = 2024-09-20
 PagerSize = -1
 +++
 
@@ -52,4 +52,6 @@ Prefiero tener esta subsección para mencionar juegos que, aunque me gustaron lo
 _Los títulos que tienen sólo una de estas dos características también se pueden encontrar en las secciones anteriores._
 -->
 
-Puede ser que no tenga tiempo, o tal vez no quiera, o tal vez sea culpa de Antani, pero en cualquier caso habría varios otros trabajos que aún no he mencionado aquí. Quizás puedas encontrar fácilmente muchos de ellos en **OcttKB** de todos modos, bajo la etiqueta [Gaming](https://kb.octt.eu.org/#Gaming).
\ No newline at end of file
+~~Puede ser que no tenga tiempo, o tal vez no quiera, o tal vez sea culpa de Antani, pero en cualquier caso habría varios otros trabajos que aún no he mencionado aquí. Quizás puedas encontrar muchos de ellos fácilmente en **OcttKB** de todos modos, bajo la etiqueta [Gaming](https://kb.octt.eu.org/#Gaming).~~
+
+También hay muchos otros juegos, retro y modernos, que no he explorado en detalle aquí (o no he incluido en absoluto), pero están disponibles (con información enciclopédica que los acompaña) para **jugar en el navegador** en mi sitio dedicado a los juegos, **Sala Museo Games**: <https://gamingshitposting.github.io/SalaMuseoGames>!
\ No newline at end of file
diff --git a/es/miscellanea/Sul-sitoctt.md b/es/miscellanea/Sul-sitoctt.md
new file mode 100644
index 0000000..e562e61
--- /dev/null
+++ b/es/miscellanea/Sul-sitoctt.md
@@ -0,0 +1,212 @@
++++
+Title = "En el sitio"
+Lastmod = 2024-08-25
+#Template = WM.html
+#Style = @import "[staticoso:Site:RelativeRoot]Assets/Pages/index.css";
+Categories = [ "Meta" ]
+Featured_Image = "@/RichPreview/index.png"
++++
+
+{{< noticeAutomaticTranslation it >}}
+
+
+
+Esta era inicialmente la página de inicio del sitio, pero se ha vuelto tan problemáticamente larga que... no importa, todo se explica en el [nuevo hogar](/). ¡Aquí, por lo tanto, está la serie clásica de información suelta sobre el ✨sitoctt✨ (parte de ella es antigua, se actualizará según las novedades)! 😊
+
+<!-- Créditos: https://codepen.io/jh3y/pen/WNrXqYz -->
+<div style="Posición:Relativa;"><br/>
+<h1 class="NoTitle WavyText" style="--x: 6; --y: -6;"><span style="--index: 0; --alpha-l: 0.125; --alpha-u : 0.25;">✨</span><span style="--index: 1; --alpha-l: 0.125; --alpha-u: 0.25;">s</span><span style="- -índice: 2; --alpha-l: 0,125; --alpha-u: 0,25;">i</span><span style="--index: 3; --alpha-l: 0,125; 0.25;">t</span><span style="--index: 4; --alpha-l: 0.125; --alpha-u: 0.25;">o</span><span style= "-- índice: 5; --alpha-l: 0,125; --alpha-u: 0,25;">c</span><span style="--index: 6; --alpha-l: 0,125; u: 0.25;">t</span><span style="--index: 7; --alpha-l: 0.125; --alpha-u: 0.25;">t</span><span style=" --index: 8; --alpha-l: 0.125; --alpha-u: 0.25;">✨</span>
+</h1>
+<h1 class="NoTitle WavyText" style="--x: 3; --y: -3;"><span style="--index: 0; --alpha-l: 0.25; --alpha-u : 0.5;">✨</span><span style="--index: 1; --alpha-l: 0.25; --alpha-u: 0.5;">s</span><span style="- -índice: 2; --alfa-l: 0,25; --alfa-u: 0,5;">i</span><span style="--índice: 3; --alfa-l: 0,25; 0.5;">t</span><span style="--index: 4; --alpha-l: 0.25; --alpha-u: 0.5;">o</span><span style= "-- índice: 5; --alpha-l: 0,25; --alpha-u: 0,5;">c</span><span style="--index: 6; --alpha-l: 0,25; u: 0.5;">t</span><span style="--index: 7; --alpha-l: 0.25; --alpha-u: 0.5;">t</span><span style=" --index: 8; --alpha-l: 0,25; --alpha-u: 0,5;">✨</span>
+</h1>
+<h1 class="NoTitle WavyText"><span style="--index: 0; --alpha-l: 0.5; --alpha-u: 1;">✨</span><span style="-- índice: 1; --alpha-l: 0,5; --alpha-u: 1;">s</span><span style="--index: 2; --alpha-l: 0,5; ">i</span><span style="--index: 3; --alpha-l: 0.5; --alpha-u: 1;">t</span><span style=" --index: 4; --alpha-l: 0.5; --alpha-u: 1;">o</span><span style="--index: 5; alfa-u: 1;">c</span>< span style="--index: 6; --alpha-l: 0.5; --alpha-u: 1;">t</span><span style ="--index: 7; --alpha-l: 0.5; --alpha-u: 1;">t</span><span style="--index: 8; --alpha-l: 0.5; --alpha-u: 1;">✨</span >
+</h1><br/>
+</div>
+
+¿De dónde viene el nombre **✨**<strong class="MainIdTextGradientL">sitoctt</strong>**✨**?
+Por el hecho de que es literalmente mi sitio, porque soy oct y así
+<i style="Color:#8040d0;">sitio</i> + <i style="Color:#d000d0;">octt</i>
+= **✨**<strong class="MainIdTextGradientR">sitoctt</strong>**✨**
+(<a href="{{< assetsRoot >}}/Media/sitoctt-pronunciation.flac" target="_blank" rel="noopener">pronunciación: "sitòctt"</a>).
+Si lo prefieres, puedes llamarlo <i class="MainIdTextGradientL">sitocto</i>. ¡O incluso <i class="MainIdTextGradientR">postoctt</i>! Éste sigue siendo un lugar, mi lugar, ¡aunque sea virtual!
+
+## Estado del sitio y cómo navegar
+
+A pesar de que ya tiene un poco más de sustancia, todo este ambaradan todavía está en construcción. Y siempre lo será, porque siempre tendré cosas nuevas que compartir. ~~Y, cuando esté muerto, todavía estará inacabado porque en mi vida no habré escrito todo el conocimiento universal teóricamente posible en el sitio.~~
+Las actualizaciones del sitio son de diferentes tipos: la publicación de nuevos artículos del blog ocurre, bueno, 3 veces al mes, es una buena idea utilizar <a href="#-Feed-e-notifiche">feeds</a> que pongo a disposición; Los cambios en las páginas normales son continuos y ocurren al azar, por lo que deberías revisar las que te interesan quizás cada semana, si esperas noticias.
+
+<p><b>A tener en cuenta</b> (desde Web): cuando los siguientes botones están en pantalla es porque pueden ocultar menús plegables.
+Pueden estar en diferentes posiciones en diferentes páginas, porque me gusta experimentar con diferentes temas; pero trato de mantener su significado consistente en todo momento.<br/>Un ícono emoji de pila de libros (<big class="twa twa-books twa-📚">📚</big>) señala la página principal del menú del sitio, imprescindible poder navegar saltando entre páginas completamente diferentes y desconectadas.
+En cambio, el icono con el emoji de una hoja con un marcador (<big class="twa twa-bookmark-tabs twa-📑">📑</big>) indica la lista de secciones de la página actual; no es imprescindible. , pero puede resultar útil para saltar entre diferentes partes de un texto extenso.
+</p>
+
+### Secuencias de comandos del lado del cliente
+
+<p>El sitio web no utiliza ningún script del lado del cliente para funciones básicas, porque no quiero forzar a aquellos (por razones válidas de seguridad y de otro tipo) que no quieren habilitar JavaScript a tener una experiencia degradada. Respecto a este espinoso tema, también escribí un artículo: <a href="Posts/2022-06-14-0000-I-Documenti-Non-Devono-Diventare-Applications.html"><span class="twa twa- page -hacing-up"><span>📄</span></span> Los documentos no deberían convertirse en aplicaciones</a>.<br/>Sin embargo, de todos modos... para proporcionar alguna funcionalidad adicional, tengo que tener algo de JS, hay poco que puedas hacer. A continuación se muestra la lista de lo que uso. <i>Todos los archivos se cargan desde los servidores de mi sitio, por lo que es difícil para entidades maliciosas ocultar malware en su interior</i>.</p>
+<detalles>
+<resumen>
+<h4>Lista de scripts del lado del cliente utilizados en el sitio web (Expandir)</h4>
+</summary>
+<div>
+<ul>
+<li>Scripts internos, escritos por mí: <del>Menús que se expanden automáticamente en páginas temáticas de sitoctt en modo de escritorio</del> (estoy intentando solucionar este problema...), visualización en pantalla completa de los fondos de la página.</del >li>
+<li>
+<del>Polyfill para admitir imágenes AVIF en navegadores antiguos: <a href="https://github.com/Kagami/avif.js" rel="noopener" target="_blank">avif.js de Kagami</ a ></del> (<i>Aún no activado...
+<del>será pronto</del> <small>¿cuándo diablos lo haré? Lo he estado posponiendo durante meses, el problema es que no es una solución plug-and-play, primero tengo que entenderlo y luego crear un script envolvente 😭</small></i>)
+</li>
+</ul>
+</div>
+</detalles>
+<p>A continuación, pongo mi clasificación de las posibles formas de ver este sitio, de mejor a peor. Por estandarización, todos asumen soporte a todo color (cuando sea posible).</p>
+<detalles>
+<resumen>
+<h4>Mis digresiones inútiles sobre formas absolutamente absurdas de consultar el sitectt (Ampliar)</h4>
+</summary>
+<div>
+<dl>
+<dt><b>• Navegador web, totalmente compatible con CSS3</b></dt>
+<dd>(¡Perfecto!)</dd>
+<dt><b>• Imprima en papel holográfico, GIF completamente renderizado y CSS3 cuando sea posible</b></dt>
+<dd>(¡Requiere mover el papel a mano pero es excelente!)</dd>
+<dt><b>• Navegador web, con soporte CSS3 incompleto</b></dt>
+<dd>(Bueno, está bien...)</dd>
+<dt><b>• Imprima en papel normal, animaciones CSS3 y GIF no renderizados</b></dt>
+<dd>(Boo, faltan animaciones...)</dd>
+<dt><b>• Navegador antiguo (Web antiguo, Web de texto o Gemini) / Impresión en papel normal, sin compatibilidad con CSS </b></dt>
+<dd>(¡¿Qué es esta basura?!?!)</dd>
+</dl>
+</div>
+</detalles>
+
+## ¿Pero de qué se trata?
+
+En este espacio mío de Internet pondré todo. Espero.
+
+Por ahora, definitivamente coloco páginas poco profundas sobre temas específicos, pero también publicaciones de blog largas y conversacionales. También quiero crear muchas colecciones sobre las cosas que me gustan, tanto en forma textual como mediática. Una especie de galería de cosas que son valiosas para mí.
+
+Sin embargo, además del contenido real, quiero que el sitio (la versión web, obviamente) sea una galería en sí mismo. Quiero crear algo que tenga su propio carácter único, como los sitios web de aficionados de los años 1995-2005, donde cada lugar en Internet siempre tenía una atmósfera diferente a todo lo visitado un momento antes.<br/><span style=" Color :#404040;">El auge de las redes sociales tal como las conocemos hoy lamentablemente ha arruinado la web desde este punto de vista, lo que ha llevado a una estandarización completa y a la muerte de la creatividad expresada a través de la forma.</span><br/>I Quiero que este espacio web mío sea diferente a todos los demás, caracterizado por textos monocromáticos y temas reciclados, porque es una pena tener herramientas muy poderosas y no explotarlas realmente.
+
+Por esta razón, intentaré constantemente inventar formas de embellecer las páginas con CSS, no sólo con diseño o efectos de texto fijos, sino sobre todo con animaciones.<br/>Al resto del formulario, como el orden del árbol de Las páginas del sitio o los párrafos de las páginas, no pensaré mucho, de lo contrario me distraigo de la creación de contenido y el deseo pasa.
+
+## Disponibilidad del sitio
+
+Actualmente, este sitio está disponible para la navegación en varias direcciones diferentes (los contenidos son siempre idénticos).
+Para aquellos que no lo saben, sin embargo, el nombre cambió hace un mes a sitoctt de postoctt, porque el nombre antiguo me dio la impresión de algún servicio postal...
+También debería pensar en muchos otros espejos en la nube de diferentes proveedores (obviamente gratuitos), si quiero que el sitio sobreviva por sí solo y resista la prueba del tiempo... Pero esta es una pregunta larga.
+
+### Web
+
+<p>El sitio web está disponible desde varias fuentes.</p>
+<ul>
+<li>En el HTTPS <b>clearweb</b>, en los servidores <span style="Color:#fc6d26;">GitLab</span>: <a href="https://sitoctt.octt.eu .org">sitoctt.octt.eu.org</a>.</li>
+<li>En <b>Onion Web</b> (<span style="Color:#59316b;">Tor</span>), en servidores Replit: <a href="http://sitoctt2fxjvx3lc2iqqef2aeulflprjaasv2xl4zi7sxxbmvjy5b5yd. cebolla ">sitoctt2fxjvx3lc2iqqef2aeulflprjaasv2xl4zi7sxxbmvjy5b5yd.onion</a>. Al final ya no está alojado en mi casa, pero quizás sea lo mejor, es una carga menos para el pobre servidor improvisado que tengo (de momento,
+<del>una consola Nintendo Switch con Ubuntu</del> la Raspberry Pi 3).
+</li>
+</ul>
+<detalles>
+<resumen>
+<h4><span class="twa twa-💾"><span>💾</span></span> Opciones de compatibilidad para sistemas obsoletos o exóticos (Expandir)</h4>
+</summary>
+<div>
+<dl>
+<dt><b>• Versión HTTP básica</b></dt>
+<dd>El sitio incluye funciones CSS complejas y relativamente modernas, para proporcionar efectos gráficos (y funcionales) épicos. Irónicamente, aunque al ver las páginas en navegadores muy antiguos, que carecen total o casi totalmente de soporte CSS, todo se ve feo pero es legible... en navegadores que son <i>tanto demasiado antiguos como demasiado nuevos</i> aparecen errores muy graves. , ¡lo que hace imposible usar algunos menús o incluso leer el texto!<br/>Además del hecho de que (cuando sea posible) quiero admitir sistemas antiguos, estos malditos problemas también aparecen en dispositivos menos populares pero actuales, como el ¡Encender! En resumen, para muchos navegadores que no incluyen una configuración para deshabilitar completamente CSS, era imprescindible hacer lo que yo hice: ir a la ruta <a href="./Plain">/Plain</a> en mis dominios. clearweb hay una raíz paralela y páginas con el mismo contenido pero CSS reducido al mínimo.</dd>
+<dt><b>• HTTP sin cifrar</b></dt>
+<dd>Para evitar problemas le dediqué un subdominio dedicado, manteniendo HTTPS forzado en el principal; pero, como no requiere mantenimiento, me aseguré de que desde el dominio de quinto (!) nivel "<span style="Font-Style: Monospace;">http</span>" puedas acceder al sitio a través de HTTP sin cifrar. (alojado en GitHub, esta vez): en resumen, la dirección es <code style="Text-Decoration:Underline;">http://http.sitoctt.octt.eu.org</code>. Los contenidos son idénticos, por supuesto, pero finalmente puedes navegar por el sitio en cosas como <i>Internet Explorer 4</i> directamente contactando al servidor.</dd>
+</dl>
+</div>
+</detalles>
+
+### Géminis
+
+<p>A partir de ahora, el sitio CTTT también está disponible como cápsula Gemini. Para ir allí, hay que utilizar un navegador Gemini.<br/>Obviamente (para aquellos que conocen Gemini), todo está más castrado y la forma no es precisamente la mejor porque todas las páginas son una conversión directa del HTML de el sitio web (y el programa que uso para hacerlo también está un poco roto).<br/>Vaya a la octocápsula, amablemente alojada en koyu.space: <a href="gemini://koyu.space/octt" > géminis://koyu.space/octt</a></p>
+
+### Feeds y notificaciones
+
+<p>A partir de ahora el sitio (el blogoctt y el MicroBlog, específicamente) tiene feeds integrados, que se actualizan automáticamente cuando publico un nuevo artículo.</p>
+<p><b style="color:#ff6a00;">Atom Feed</b> (moderno, <b>recomendado</b>, contiene publicaciones completas): <b><a href="./feed/ atom.xml">feed/atom.xml</a></b><br/>Feed RSS (obsoleto, disponible por compatibilidad): <a href="./feed/rss.xml">feed/rss. xml</a></p>
+<p>Necesitas un agregador de feeds compatible para usarlos.<br/>- En PC de escritorio recomiendo <a href="https://thunderbird.net" rel="noopener" style="Color:#0080FF;" target="_blank">Thunderbird </a>o <a href="https://www.seamonkey-project.org" rel="noopener" style="Color:#003399;" target="_blank">SeaMonkey Mail</a>.<br/>- En Android recomiendo <a href="https://f-droid.org/packages/com.nononsenseapps.feeder" rel="noopener" target="_blank">Alimentador</a> o <a href="https://f-droid.org/packages/com.poloure.simplerss" rel="noopener" target="_blank">Rss simple</ a >.<br/>- Si desea utilizar un dispositivo como un lector de libros electrónicos de tinta electrónica, el único software universal que, entre otras cosas, incluye un agregador de feeds, que conozco y puedo recomendar, es <a href="https://github.com/koreader/koreader" rel="noopener" target="_blank">KOReader</a>.<br/>- Consejo: si usas Friendica, puedes copiar el enlace a el feed y pégalo en la barra de búsqueda, para poder seguirlo como si fuera un perfil!</p>
+<p>
+<del>Además, si utilizas cualquier plataforma del <b>Fediverso ActivityPub</b> (Mastodon, Pleroma, Misskey, ...) puedes seguir el bot del sitio ctt, para recibir nuevas publicaciones en tu Feed de inicio: < a href="https://botsin.space/@sitoctt" rel="me noopener" target="_blank">@sitoctt@botsin.space</a>!</del> Para algunas complicaciones que iniciado a finales de agosto de 2022, no se puede acceder al bot desde la instancia italiana más grande de Mastodon, <i>mastodon.uno</i>, por lo que ahora es prácticamente inútil. No lo voy a quitar sólo porque me costaría más hacerlo que dejarlo donde está <b>:P</b>; Sin embargo, tarde o temprano tendría que crear uno nuevo.
+</p>
+
+## Fuentes y licencias
+
+### Licencias de contenido
+
+<p>Todo el contenido de este sitio que creé (mis propios escritos, medios originales y la mayor parte del código fuente) tiene licencia <a href="https://creativecommons.org/licenses/by-sa/4.0/deed. it" rel="noopener" target="_blank">"Creative Commons Attribution - Share Alike 4.0 International" (CC BY-SA 4.0) (<span class="CCIcons"><img class ="i1em" src="https ://sitoctt-assets.octt.eu.org/Media/Icons/CC/CC.svg"/> <img class="i1em" src="https://sitoctt-assets .octt.eu.org/Media /Icons/CC/BY.svg"/> <img <="" class="i1em" span="" src="https://sitoctt-assets.octt.eu.org /Media/Icons/CC/SA .svg"/>)</span></a>, una licencia gratuita que promueve el intercambio, y no afecta los legítimos derechos a la cultura y la colaboración de la humanidad en general.</ p>
+<p>Sin embargo, también hay contenidos que no son míos.<br/>En cualquier caso, si algo viene de mi mano, no tendrá ninguna indicación de créditos cerca. <br/>Para el material prestado, sin embargo, siempre se indicará la fuente de donde lo tomé y la licencia, ya sea de dominio público, Creative Commons o no especificada.<br/>Cuidado con los créditos. porque a menudo dejo el material HTML y CSS en las fuentes de la página. Así que, por si acaso, consulte allí para ver este tipo de créditos. Sin embargo, para cosas como imágenes o textos, los créditos suelen ser una parte visible de la página, cerca del objeto prestado (como una descripción); otras veces, el mismo objeto es un enlace que, si se hace clic, te lleva de regreso a la fuente. Sin embargo, pensé en crear una sección de la página <a href="#-Special-Credits">a continuación</a>. dedicado a créditos especiales (que completo cuando recuerdo).</p>
+
+### Código fuente
+
+<p>Hablando de fuentes del sitio, la fuente HTML de la página real cargada por el navegador puede ser difícil de leer. Esto se debe a que en realidad no escribo el HTML completo directamente para componer las páginas. No solo sería un desastre replicar mis diversas barras de navegación y secciones en todas las páginas, y si tengo que hacer cambios en ellas, entonces es un problema. Es un infierno replicar esto en cualquier lugar, pero la sintaxis HTML es sucia y difícil de escribir.</p>
+<p>Precisamente por estas razones, creé mi propio generador de sitios estáticos (también, como este sitio, incompleto pero actualizado de vez en cuando cuando lo necesito), que preprocesa mi código fuente para incluir mis barras en todas las páginas. generar las secciones de la página (que aparecen en el menú de la derecha), generar la lista de páginas del sitio (desde el menú de la izquierda), y <i>otras cositas</i>. Paso importante, todos los archivos Markdown o Pug se traducen a HTML para que sean comprensibles para los navegadores normales, y aquí lo tienes.<br/>Ah, sí, digo "<i>otras pequeñas cosas</i>" porque esto Es una cosa que al momento de escribir este capítulo la página está ausente o incompleta, y al escribir como escribo me cubro el trasero y no tengo que hacer cambios futuros.
+<pre class="Inline"><i>H y h .</i></pre>
+</p>
+
+#### ¡Tómalo todo!
+
+<p>Para terminar, busque todas mis fuentes en los respectivos repositorios de Git.<br/>Las de mi sitio (divididas en varios repositorios para mantener limpio el historial), en las condiciones descritas anteriormente: <a href="https:/ / gitlab.com/octtspacc/sitoctt" rel="noopener" target="_blank">gitlab.com/octtspacc/sitoctt</a>; <a href="https://gitlab.com/octtspacc/sitoctt-assets" rel="noopener" target="_blank">sitoctt-assets</a>.<br/>Los de mi generador, también liberados bajo licencia libre, la AGPL: <a href="https://gitlab.com/octtspacc/staticoso" rel="noopener" target="_blank">gitlab.com/octtspacc/staticoso</a>.</ a>p>
+<p>Otra cosa: en caso de que sea de su interés, para preservar y/o compartir inmediatamente (excluyendo archivos que están en repositorios separados, porque están absolutamente vinculados) copias fuera de línea del sitio, puede descargar un <b>zip < /b> que contiene todas las páginas compiladas <a href="https://gitlab.com/octtspacc/sitoctt/-/jobs/artifacts/main/download?job=pages" rel="noopener" target="_blank" >aquí </a>!</p>
+
+### Créditos especiales
+
+<detalles>
+<resumen>
+<h4>Lista de créditos y agradecimientos especiales a quienes pidieron material prestado (Ampliar)</h4>
+</summary>
+<div>
+<ul>
+<li>Lista de <a href="#-Script-client-side">scripts del lado del cliente</a>, incluidos algunos scripts de terceros</li>
+<li>Título animado de Waaaves: <a href="https://codepen.io/jh3y/pen/WNrXqYz" rel="noopener" target="_blank">Waaaves de jh3y</a></li>
+<li>Familia de fuentes: <a href="https://fonts.google.com/specimen/Space+Mono" rel="noopener" target="_blank">Space Mono de Colophon Foundry</a></li >
+<li>Paquete de emojis CSS: <a href="https://twemoji.twitter.com" rel="noopener" target="_blank">Twemoji de Twitter</a>, a través de <a href="https:/ /gitlab.com/octtspacc/twemoji-astonishing" rel="noopener" target="_blank">Twemoji asombroso</a></li>
+<li>Algunos botones de 88x31 no identificables: <a href="https://cyber.dabamos.de/88x31" rel="noopener" target="_blank">Colección GIF de 88x31 de cyber.dabamos.de</a > </li>
+</ul>
+</div>
+</detalles>
+
+## Confidencialidad y transparencia
+
+Como mi interés legítimo, utilizo un servicio de análisis en este sitio web; tanto para mejorar lo que hago como para satisfacer mi pura curiosidad por descubrir datos.
+
+El servicio de análisis se basa en un código completamente <a href="https://github.com/arp242/goatcounter/blob/master/LICENSE" rel="noopener" target="_blank">gratuito y abierto</ a> , alojado de forma gratuita para sitios de poco tráfico por <b>GoatCounter.com</b>.
+
+Aparentemente, con GoatCounter no es necesario incluir una advertencia en pantalla que moleste a los usuarios para cumplir con el GDPR (ver <a href="https://www.goatcounter.com/help/gdpr" rel="noopener " target="_blank">goatcounter.com/help/gdpr</a>), pero, por honestidad y transparencia, escribo este párrafo de todos modos.
+
+Sólo se recopilan datos no personales, de forma anónima, con el único fin de realizar estadísticas generales y no para el seguimiento individual. El servicio no utiliza cookies y los datos no se transfieren a terceros. Para obtener más información, solo puedo recomendar leer la <a href="https://www.goatcounter.com/help/privacy" rel="noopener" target="_blank">política de privacidad de GoatCounter</a >.
+
+<estilo>
+.CCIcons > Imagen, .CCIcon {
+Pantalla: ¡En línea! Importante;
+Altura máxima: 1em !Importante;
+Alineación vertical: Sub;
+}
+.CCIcons > Imagen, .CCIcon {
+Margen izquierdo: 3px;
+}
+
+/*!-- Créditos: https://codepen.io/jh3y/pen/WNrXqYz ---*/
+.Texto ondulado {
+Alineación de texto: Centro;
+Posición: Absoluta;
+Izquierda: 50%;
+Espacio en blanco: Sin ajuste;
+Transformar: Traducir(-50%, -50%) Traducir(Calc(Var(--x, 0) * 1%), Calc(Var(--y, 0) * 1%));
+configuración de variación de fuente: 'wght' Var(--lower);
+Margen: 0;
+}
+.WavyText Intervalo {
+Color: HSLA(300, 100%, 20%, Var(--alfa-l));
+Animación: Rise 2,25s con infinita facilidad de entrada y salida;
+Retardo de animación: Calc((Var(--index) - 6) * 0,225s);
+Pantalla: Bloque en línea;
+}
+@keyframes Subir {
+50% {
+configuración de variación de fuente: 'wght' Var(--upper);
+Color: HSLA(300, 100%, 30%, Var(--alfa-u));
+Transformar: Traducir(0, -15%);
+}
+}
+</estilo>
diff --git a/fr/blog/2022-10-31-Storia-Antica-del-DSpacc.md b/fr/blog/2022-10-31-Storia-Antica-del-DSpacc.md
new file mode 100644
index 0000000..bba278e
--- /dev/null
+++ b/fr/blog/2022-10-31-Storia-Antica-del-DSpacc.md
@@ -0,0 +1,101 @@
++++
+Title = "🎮 Histoire ancienne de DSpacc"
+Description = "La première console de jeu de ma vie est partie en guerre, puis a pris la poussière, et à ce jour elle ne va pas très bien ; mais je lui ai donné un but."
+Aliases = [
+  "/Posts/2022-10-31-Storia-Antica-del-DSpacc.html",
+]
+Categories = [ "Jeux", "Technologie" ]
+Date = 2022-10-31
++++
+
+{{< noticeAutomaticTranslation it >}}
+
+
+
+Il y a presque deux mois, le **DSpacc** m'est venu à l'esprit un peu par hasard ; d'abord comme concept, j'en parle avec des gens en ligne, puis directement comme petit objet que je possède fièrement.
+
+Cette chose à moi a vu de la **poussière**, de la **gloire**, de la **guerre** et du **désespoir**. C'est exactement ce dont j'aurais dû parler aujourd'hui, ce que j'ai fait récemment pour enlever un peu de poussière et ainsi redonner de la gloire à mon appareil.
+Cependant, en écrivant, j'ai réalisé à quel point le contexte aurait été confus si je n'avais pas donné la bonne place à l'histoire ; mais hélas, l’histoire elle-même est longue et mérite un article détaillé, alors nous y sommes.
+
+## Les débuts
+
+Tout a commencé lorsque, vers l'âge de 6 ans, j'ai reçu cette **Nintendo DS Lite** en cadeau pour mon anniversaire... non, je ne divague pas, j'y arrive maintenant. Pendant 3 bonnes années, c'était ma seule console de jeu - et, pendant au moins 1 à 2 de ces années, mon seul appareil de jeu, avant d'avoir le Galaxy Player ou la _tablette scassone_.
+Pour moi, c'était un objet de combat absolument indispensable, nécessaire toujours et partout comme mon smartphone aujourd'hui, et peut-être pour cette raison il a eu une vie particulièrement intense au cours de ses premières années. Je n'avais pas beaucoup de jeux, car je n'avais que 2 Go de mémoire dans le flashcart et aucun jeu physique (à part un obscur, que je n'ai acheté que plus tard), mais j'avais certains des meilleurs . Bref, avec Pokémon, tous les grands jeux Mario, et même des trucs comme Cooking Mama (qui était très populaire à l'époque), le plaisir était toujours présent.
+
+[![Nintendo DS Lite (côté droit)]({{<assetsRoot >}}/Media/Misc/Nintendo_DS_Lite_(right_side)/4.jpg)](https://commons.wikimedia.org/wiki/File:Nintendo_DS_Lite_ (côté droit).jpg)
+_Un DS Lite... pas le mien, pour des raisons évidentes bientôt - <small>Havok sur en.wikipedia, CC BY 2.5 <https://creativecommons.org/licenses/by/2.5>, via Wikimedia Commons</small> _
+
+## Le jour du smash
+
+Malgré quelques incidents de flashcart - la première a mystérieusement cessé de fonctionner un jour, la seconde commençait à montrer de sérieux signes de panne après environ 2 ans - **la petite console s'est battue** et m'a diverti.
+Mais un mauvais jour de début juillet, en début d'après-midi, en revenant de la mer, mon envie de jouer s'est **_crack_**, ainsi que le plastique de la fermeture éclair lorsque j'ai ouvert la coque. Oh oui, c'est exactement un "DSpacc" : un **DS split**. Ce nom ne veut peut-être pas dire grand-chose, j'en suis conscient, car non seulement je l'ai inventé, mais aussi très récemment.
+
+Sur le moment, il me paraissait absurde qu'en ouvrant simplement la console, elle ait pu se casser ; et cela me semble encore absurde aujourd'hui, même si j'ai découvert qu'il s'agit d'un problème très répandu : il suffit de taper "nintendo ds cassée" sur n'importe quel moteur de recherche d'images pour constater que non seulement les images montrant la charnière cassée sont majoritaires, mais aussi comment ceux représentant DS et DS Lite sont majoritaires. Il semble qu'à partir de la DSi, Nintendo ait en fait repensé le mécanisme à clapet, qui s'était jusqu'alors révélé inadapté, et l'ait encore perfectionné avec la 3DS ; évidemment, l'original _did cahà_.
+
+### Les conséquences des dommages
+
+Le désespoir était sur le point de s'installer, même si à l'époque la console continuait à fonctionner parfaitement, car un morceau de plastique à droite de la charnière était simplement cassé, ce qui a pour seule tâche d'assurer **l'intégrité structurelle**. Le désespoir a vraiment commencé à s'installer au moment où j'ai vu les couleurs de l'écran commencer à changer au fur et à mesure que je déplaçais le clapet : voilà, **le câble** de l'écran **a commencé à subir des dommages**.
+Un peu plus tard, je pense le même après-midi, je suis allé avec mon père dans un magasin de l'autre côté de la ville, pour voir combien coûterait une **réparation**. Je ne me souviens plus du prix maintenant, mais j'ai décidé que **ça n'en valait pas la peine**, et qu'il valait mieux acheter une belle 3DS, étant donné les jeux intéressants qui étaient sortis ou étaient sur le point de sortir pour la nouvelle famille de consoles.
+
+Je ne me souviens pas si j'ai continué à utiliser la DS Lite les jours suivants, car beaucoup de titres auxquels je voulais jouer nécessitaient l'écran supérieur, et je n'aimais pas jouer avec des couleurs _diminuées_ (aujourd'hui, cela ne me dérange pas trop cependant). En tout cas, à la fin de cette semaine, après plusieurs recherches dans les magasins locaux à la recherche du prix le moins cher, [j'ai reçu mon o3DS XL](https://mastodon.uno/@octo/109262437212406002).. et c'est une toute autre histoire.
+
+## L'ère de la poussière
+
+À partir de ce moment, bien sûr, l'ancien nouveau **DSpacc est passé au second plan**. Peut-être que je l'ai encore pris parfois, du moins pour des jeux comme Animal Crossing qui ne nécessitent que le panneau inférieur, car (d'après l'application _Diary_, certainement plus précise que ma mémoire) pendant les 2 premières semaines de la 3DS, je n'avais rien pour jouer avec d'autres que les applications système. Ensuite, cependant, d'une part, j'ai pu progressivement remplir la nouvelle console avec des logiciels, d'autre part, la DS Lite ** a continué à tomber en panne ** - tôt ou tard, en fait, l'écran supérieur a commencé à cesser de fonctionner complètement, affichant seulement un écran blanc avec un point noir (?) - la **poussière** a commencé à attaquer le DSpacc. Comme si cela ne suffisait pas, le flashcart a un jour dit au revoir ! 🙄
+Même après des années, malgré ma nouvelle console, de temps en temps je devais encore **reprendre l'ancienne**... Je ne sais pas pourquoi, étant donné que je ne pouvais plus rien faire de spécial avec, car je n'ai pas de jeux sur une carte dédiée que je pourrais utiliser sans l'écran supérieur. Même des années plus tard, peut-être parce qu'au fil du temps, j'ai commencé à collectionner des cartouches DS originales et que j'avais envie de les démarrer, **parfois j'ai rallumé **la DS Lite** pendant quelques minutes.
+
+Tout allait bien, jusqu'à ce qu'à un moment donné, **je joue même au **_SLOT-1_** (celui des cartes DS) sur la pauvre console ! Je me souviens qu'il avait quelques difficultés à lire même les feuillets originaux, mais mes autres souvenirs à ce sujet sont très troubles. Je me souviens que lorsque j'ai regardé à l'intérieur de la fente, j'ai vu des **épingles tordues**, et que j'ai essayé d'insérer quelque chose pour les redresser, mais en vain. Je ne pense pas qu'en faisant ça j'en ai endommagé d'autres, mais déjà il y a au moins 3 ans (par rapport à aujourd'hui) je me souviens que dans la fente certaines broches étaient **cassées, manquantes**... donc, soit quand je des trucs coincés dans le port j'ai affaibli voire déconnecté d'autres pins sans m'en rendre compte, ou bien c'est la mise et le retrait occasionnel de cartouches, en espérant que certaines seraient lues, qui a cassé les contacts déjà fragilisés (et ce serait grave, car cela démontrerait la mauvaise qualité du slot).
+
+Après ce nouvel événement inattendu, je pourrais certainement encore, via _Download DS_, utiliser la console pour des logiciels techniquement limités et volatiles, sans possibilité de sauvegarder une quelconque configuration (ou progression, dans les jeux), mais **n'allons pas tourner autour du pot* *: tu fais quoi d'utile et continu comme ça ? Pratiquement rien, et **la console était** devenue **un presse-papier**... jusqu'à ce que, quelque temps plus tard, lors d'une foire, je trouve et **achete par hasard une cartouche Pokémon Ruby**. Même s'il n'y avait même pas de boîte, il me fallait l'avoir : **enfin je pouvais jouer** à quelque chose de complet sur ma pauvre petite console !
+
+## Modification organisée
+
+Cependant, **ce panneau cassé commençait à faire des ravages**, _littéralement_. La charnière fendue déséquilibrait le poids de l'ensemble de l'appareil, et la partie supérieure de la coque restait suspendue uniquement grâce aux _câbles assortis_.
+J'avais déjà découvert le concept de **GBA Macro** il y a quelque temps. Pour les non-experts, il s'agit de donner une seconde vie à une DS qui a perdu son écran supérieur, de jouer à des titres (émulés, ou pas comme ceux de la GBA, pour lesquels la console offre une rétrocompatibilité matérielle) des consoles précédentes que leur nature possédait un seul écran.
+En ligne, je voyais déjà des gens créer leurs propres modèles personnalisés avec des corps uniques colorés à la main, ou en ajoutant des tubes LED qui créent un effet néon, placés à la place de la fermeture éclair. Tous des trucs fantastiques, mais si je n'avais pas l'envie (et la manière, du moins à l'époque, de ne pas le trouver sur Amazon.it) d'acheter un nouvel écran pour réparer correctement la console, pourrais-je un jour commencer à dépenser sur des détails qui, aussi beaux soient-ils, sont objectivement superflus ?
+
+Je prends une paire de ciseaux et **coupe** les câbles pour que la moitié supérieure du boîtier reste attachée à la moitié principale. Et c'est ça ? Pouvons-nous rejouer ? Eh bien, _pas exactement_.
+Pour être honnête, créer une bonne Game Boy Macro nécessite un travail matériel _un peu plus élaboré_ que d'arracher violemment l'écran cassé, et pour cette raison mon histoire a été **un peu troublée**. Tout d'abord, une **opération particulière** est pratiquement obligatoire, si vous ne voulez pas perdre les **fonctionnalités DS** : ouvrez l'appareil et - en plus de déconnecter _correctement_ l'écran, les haut-parleurs, le microphone et l'antenne câbles, _sans les couper_ - soudez une petite **résistance** sur 2 points de test de la carte mère. Normalement, la console échoue au POST et s'arrête si elle ne détecte pas l'écran supérieur (c'est-à-dire si elle ne détecte pas la consommation d'énergie qu'elle attend du rétroéclairage de l'écran supérieur) ; souder une résistance d'une valeur comprise entre 300 et 1000 Ohm environ aux bons endroits sert justement à faire croire au système que rien n'est déplacé.
+
+Cependant, j'avais fait **mes recherches** sur le Web, découvrant ainsi que le POST n'est pas effectué pour démarrer une cartouche depuis le _SLOT-2_ (celui du GBA), si le **démarrage automatique est paramétré dans les paramètres système* * d'une carte de jeu si présente. Bien avant de commettre mon _acte violent_ donc, parce qu'après je ne pourrais plus accéder au menu système, j'ai réglé le démarrage automatique, et je me suis assuré que l'écran du bas était sélectionné comme panneau utilisé en mode Game Boy Advance.
+Une fois _le crime_ commis, je constate que la console fonctionne exactement comme _des inconnus sur Internet_ l'avaient dit : **c'est pratiquement une GBA**, comme si elle n'avait jamais été une DS... sauf qu'elle n'a pas de haut-parleurs , parce que je les ai coupés. 😅
+
+## Un nouveau plan
+
+Un peu plus tard, cependant, j'ai commencé à **vouloir des choses** comme le mode _Télécharger DS_... ou le réglage du rétroéclairage. J'ai décidé d'acheter un kit d'embouts de tournevis en ligne, qui, parmi tant d'autres, comprenait également le foutu embout pour vis tri-wing, ces vis aimées par Nintendo exactement autant qu'elles sont détestées par nous, les idiots qui achetons leurs produits.
+Avec ma nouvelle **arme très dangereuse** (ce n'est pas mon avis, mais celui de ceux qui s'entêtent à utiliser des vis merdiques pour les objets qu'ils fabriquent) je peux enfin ouvrir mon DSpacc, afin de **souder la résistance** .. résistance **que je n'ai pas** ! Mais **j'ai un morceau de chewing-gum**.
+D'autres bonnes âmes sur Internet illustrent en effet comment les caoutchoucs conducteurs utilisés pour les boutons des télécommandes (et de la DS elle-même) ont souvent la bonne valeur de résistance nécessaire dans ce cas. Comme par hasard, une vieille télécommande cassée que j'avais sous la main avait des patins en caoutchouc adaptés : en en coupant un, et en le maintenant appuyé avec mon doigt sur les fameux points de test, **la console s'allumait** comme avant de couper le panneau éteint.
+Ici **le plus dur** a été de réussir à **fixer** ce _petit truc_ à la carte mère, pour qu'il fasse la bonne pression, et donc le bon contact électrique, sur les points où en théorie il fallait faire la soudure - _pour la raison que le mot même « soudage » suggère_. Quelques centimètres de **ruban électrique** plus tard, que j'ai dû appliquer et réappliquer jusqu'à ce que je puisse le fixer avec la bonne tension, et il semblait que j'avais terminé ; mais _le destin a décidé de se moquer de moi_.
+
+![Photo de la zone du point de test, avec un mélange de ruban isolant et d'adhésif appliqué dessus.]({{<assetsRoot >}}/Media/Misc/GBA-Macro-Button-Resistor.avif)
+
+### Encore un autre problème
+
+Étant donné que l'appareil de _grande qualité_ - mais pas seulement lui, maintenant aussi les _"téléphones""intelligents_" depuis 15 ans maintenant - ne s'allume pas sans batterie connectée (uniquement avec le câble d'alimentation externe, pour ainsi dire), et qu'il est uniquement le corps en plastique qui maintient la cellule collée et alignée, maintenant que la console était démontée, je devais **tenir la batterie avec mes mains** près des contacts à ressort, dans ces instants de quelques secondes où je voulais simplement * *vérifiez que la console a fonctionné**.
+Et bien, à cause de ces manœuvres (et je ne l'ai compris que plus tard), peut-être à cause de ma mauvaise manipulation de la batterie ou qui sait quoi, tout d'un coup **la DS ne s'allumait plus** ! Le POST n'a pas échoué comme avant, hein, mais il **n'a montré aucun signe de vie**. Le _Désespoir_ est monté rapidement, je n'avais aucune idée de ce qui s'était passé et où mettre mes mains. Ce n'est que grâce à _Ashfly_, qui m'aidait à discuter avec mon désordre, que j'en suis arrivé à la conclusion que le fusible dédié à la connexion de la batterie venait de sauter.
+
+Ne vous sentez pas mal dans ma peau, mais n'ayant pas la résistance dont je savais exactement dont j'avais besoin, pourrais-je un jour avoir le fusible dont je n'aurais jamais imaginé qu'il sauterait ? Il m'a donc fallu faire un beau pont en étain... Allez, ça ne sert à rien d'en faire trop d'histoires, il n'arrivera jamais que je connecte **par erreur**, dans le compartiment à piles, une source d'énergie plus puissante que ce que les circuits de la console peuvent gérer ; le fusible du port de charge est séparé, il est donc hors de question qu'une alimentation défectueuse puisse décharger un _littéral éclair_ dans le processeur de la console.
+
+![Photo du pont en étain réalisé (avec difficulté) sur le fusible de la batterie, avec la position de la zone marquée sur l'ensemble de la carte.]({{< assetsRoot >}}/Media/Misc/DSpacc-Fuse-Bridge.png )
+
+### Problème résolu
+
+J'aurais aimé rebrancher le haut-parleur (l'endroit est situé en partie basse de la console) mais, d'une part, ayant coupé le fil et mon incompétence absolue à souder quelque temps (_la photo du cavalier parle d'elle-même_) - même si, à ce jour, je sais souder au moins un fil sur un gros point de test - et d'un autre côté la frénésie de tout fermer de peur que mon désastre de ruban isolant puisse bouger, **j'ai préféré tout fermer** et faire comme si de rien n'était. Au moins, j'ai toujours le port jack 3,5 pour écouter l'audio au casque.
+
+Par la suite (enfin **13 mois plus tard**... Je pensais tout ce temps que la console était belle à regarder telle qu'elle était ?!?) j'ai **refait** un peu la carrosserie**, principalement en utilisant du papier de verre pour aplatissez complètement l'autre saillie qui sert normalement au mécanisme à clapet, l'amenant à l'état dans lequel elle **se trouve toujours**.
+
+![Vieille photo montrant le DSpacc et un morceau de papier de verre sur mon bureau, pendant que je travaillais.]({{<assetsRoot >}}/Media/Misc/GBA-Macro-Sandpaper-Job-Detail.avif)
+
+## La suite
+
+**Jouer** à Pokémon Ruby sur ma nouvelle GBA Macro, beaucoup plus compacte et plus légère que la DS sous sa forme originale, **a pris** une toute nouvelle saveur**. J'ai joué pendant des dizaines d'heures, mais de temps en temps, je me suis dit que je voulais m'amuser avec d'autres choses sur cette élégante console.
+En excluant totalement les linkers DS, car le slot est, comme je l'ai dit, **mort**, j'ai regardé ceux de GBA. Sur Amazon.it, la seule boutique en ligne où je pouvais et peux acheter, il me semble que j'avais déjà **trouvé** à l'époque une _scassona_ pour pas plus de **vingt euros**, mais je ne sais pas pourquoi **je viens de regarder* * - et je l'ai fait plus d'une fois - sans jamais toucher (acheter).
+
+Une autre bonne année s'est donc écoulée et je suis là **il y a juste quelques semaines**. Un peu par hasard, je me souviens de mon Dpacc et, comme je suis désolé qu'il soit hors d'usage, j'essaye de faire **des trucs un peu fous**, dont j'avais parlé dans [cette entrée du 2022-09-18 de le MicroBlog](./MicroBlog/2022-09-18-Quando-Metto-Mano-Io-Spacc.html).
+À ce stade, cependant, j'entre maintenant dans l'histoire de **l'ère contemporaine du DSpacc**, qui a beaucoup **trop d'implications** pour en parler. Dans le **prochain article détaillé** sur le sujet, vous aurez tout le temps de parler de la façon dont j'ai finalement dépoussiéré avec style ce **vaillant** appareil de jeu, qui reste toujours valable malgré la malchance.
+
+**Merci d'avoir lu !** Si vous avez trouvé l'histoire intrigante, alors gardez les yeux ouverts pour la suite ! 😄
+
+---
+
+_Pss... L'histoire concernant la modification Macro elle-même mérite à elle seule un petit dossier, à mon avis. Grâce à l'existence d'anciens messages écrits je peux le composer.. dois-je ?_
diff --git a/fr/blog/2023-03-18-Cattiva-Interfaccia-Partizione-Distrutta.md b/fr/blog/2023-03-18-Cattiva-Interfaccia-Partizione-Distrutta.md
new file mode 100644
index 0000000..b77804b
--- /dev/null
+++ b/fr/blog/2023-03-18-Cattiva-Interfaccia-Partizione-Distrutta.md
@@ -0,0 +1,170 @@
++++
+Title = "🥴 Interface moche ? Fichiers tous détruits !"
+Date = 2023-03-18
+Description = "Pour faire les choses dans la précipitation, j'ai accidentellement supprimé une partie du disque du PC. Mais ce n'est pas seulement de ma faute : le programme que j'ai utilisé est mal conçu."
+Downsync = "/it/blog/Bad-Interface-Partition-Destroyed.html"
+Aliases = [ "/Posts/2023-03-18-Bad-Interface-Partition-Destroyed.html" ]
+Categories = [ "Administrateur système" ]
+Lastmod = 2023-03-20
++++
+
+{{< noticeAutomaticTranslation it >}}
+
+
+
+<!-- Généré automatiquement par ListedDownsync.js. Ne modifiez pas (sauf si vous définissez également "% Downsync = False") - cela serait écrasé. -->
+
+Comparons **visuellement** deux applications PC : **GNOME Disks et GParted**.
+
+![Les fenêtres des deux programmes comparées.]({{<assetsRoot >}}/Media/Partioning-Mar-2023/SideBySide.png)
+
+Les deux sont des outils de partitionnement de disque et remplissent globalement les mêmes tâches ; il y a juste **une certaine différence** dans les fonctionnalités supplémentaires ou plus de support en faveur d'un programme ou de l'autre. Malgré cela, les deux outils présentent des **différences évidentes** dans leur **interface graphique**.
+
+## Il faut avoir les deux
+
+Je garde généralement ces deux programmes installés et je **les utilise de manière plutôt **alternative**, car :
+
+<table><thead><tr><th>GParted</th><th>Disques GNOME</th></tr></thead><tbody><tr><td><img src="{{ < assetsRoot >}}/Media/Partioning-Mar-2023/GParted-Advanced.png" alt="Vue GParted des informations détaillées sur un disque."></td><td><img src="{{ < actifsRoot >}}/Media/Partioning-Mar-2023/GNOME-Advanced.png" alt="Menu contextuel global des disques GNOME, qui présente des fonctionnalités spéciales."></td></tr><tr ><td><strong>GParted</strong> a <strong>moins de fonctions distinctes</strong>, mais chaque chose a sa place, et un niveau <strong>suffisant</strong> de <strong>profondeur</strong> strong> et fonctionnalités : informations de bas niveau sur le disque, formatage dans des tonnes de formats et quelques autres détails.</td><td><strong>Les disques GNOME</strong> ont <strong>moins de profondeur</strong> > avec des opérations individuelles, mais propose quelques <strong>fonctions supplémentaires</strong> non strictement liées à la modification des partitions, ce qui est toujours utile : gestion de l'énergie et des performances des disques, une interface pour le protocole SMART, et aussi un outil pour tester performances de la mémoire !</td></tr></tbody></table>
+
+## C'était une mission simple !
+
+Avant-hier, lorsque j'ai démarré un Linux **live USB** sur [mon ordinateur portable](https://sitoctt.octt.eu.org/Posts/2022-07-09-Come-ho-Riparato-il- mon-Portatile-con-25-Euro.html), j'avais en tête de réaliser **sans dommage** une mission _théoriquement_ facile et indolore :
+
+1. **Libérer de l'espace** sur le disque du PC, en supprimant la plupart des fichiers, à l'exception de ceux que je souhaitais conserver un instant (pour les gérer peut-être dans le futur).
+2. **Redimensionnez la partition** sur le disque, car elle sera pratiquement vide à ce stade.
+3. **Créez une nouvelle** partition suffisamment grande pour y installer le nouveau système d'exploitation.<sup id="fnref1"><a href="#fn1">1</a></sup>
+4. **Déplacez les fichiers** de l'ancienne partition vers la nouvelle, en réduisant progressivement la première et en élargissant la seconde, **jusqu'à** pouvoir **supprimer l'ancienne**.
+
+## Trop de désordre.
+
+...Dans la pratique, _quelque chose s'est légèrement mal passé_. Cela n'aurait pas pu être une soirée tranquille ! 😾
+
+Cette fois-ci, pour le simple fait qu'en recherchant un éditeur de partition parmi les applications préinstallées du système live en question, **en voulant le faire tout de suite**, le premier programme sur lequel mon regard est tombé était **GNOME Disques** .
+Oh, j'aurais dû rester à l'écart. Et il y a plusieurs raisons :
+
+#### 1\. Les disques physiques sont mélangés avec des partitions virtuelles montées à partir de disques physiques, dans la liste à gauche de la fenêtre
+
+Déjà à ce stade, si (comme dans mon cas) vous avez des partitions de type étrange, c'est-à-dire [LVM](https://wiki.archlinux.org/title/LVM), la situation devient laide, car ** ce n'est pas le cas. indiquez où** vous devez aller** pour apporter des modifications.<sup id="fnref2"><a href="#fn2">2</a></sup>
+
+<table><thead><tr><th>GParted</th><th>Disques GNOME</th></tr></thead><tbody><tr><td><img src="{{ <assetsRoot>}}/Media/Partioning-Mar-2023/GParted-List.png" alt="Le sélecteur de liste de disques dans GParted."></td><td><img src="{{<assetsRoot >}}/Media/Partioning-Mar-2023/GNOME-List.png" alt="Vue de la liste des disques et partitions sur les disques GNOME."></td></tr><tr><td>< strong>GParted< /strong> n'a qu'une <strong>liste de périphériques</strong> (de vrais disques bien sûr, mais je pense aussi des périphériques virtuels) à sélectionner en premier, puis la grande vue avec toutes les partitions du périphérique choisi. C'est <strong>ordonné</strong> et logique.</td><td><strong>Sur les disques GNOME</strong>, cependant, pour faire ce que vous devez faire, <strong>vous y allez</strong> vers la vue disque ou <strong>où ?</strong> Dans le premier cas il y a <strong>certaines options</strong> et d'autres <strong>manquent</strong>. On essaie depuis la vue dédiée à la partition virtuelle ? Ici aussi, la liste des options est décidément neutralisée, entre autres à la fois au sens des boutons d'icônes rapides et au sens des boutons du menu contextuel... mais voyons maintenant quels problèmes elles ont.</td></ tr></tbody></table>
+
+#### 2\. Le cas échéant, les icônes rapides disponibles pour chaque partition apparaissent et disparaissent
+
+Lorsque vous êtes sur **GParted**, la liste des **boutons-icônes** en haut de la fenêtre **ne change jamais** - les boutons individuels s'assombrissent ou s'éclaircissent, selon qu'ils peuvent être utilisés sur la sélection actuelle. ou pas - **sur les disques GNOME, les raccourcis clavier** - en effet, positionnés d'une manière étrange également, coincés sous la zone de la table de partition, sur laquelle honnêtement je ne peux même pas commenter - ils **apparaissent ou disparaissent** complètement.
+Voici les cas que j'ai vus, mais il y en a peut-être encore d'autres possibles, qui sait :
+
+* À l'extrême gauche, pour certaines sélections, vous voyez un bouton **play/stop** (monter/démonter la partition), d'autres fois exactement au même endroit il y a un **cadenas** (verrouiller/déverrouiller la partition cryptée), d'autres fois, une **croix** (crée une partition dans un espace vide), et dans certains cas **rien**.
+* Immédiatement à droite, un **engrenage**, bouton qui ouvre un menu pop-up avec une liste plus complète d'options pour la partition - on constate que cela finit par **monter tout à gauche**, si avant il n'y a rien, juste pour confondre davantage.
+* Enfin, à l'extrême droite, dans certains cas, un bouton avec un **tiret sur fond rouge** (détruire la partition) peut apparaître.
+
+Ehh, ce truc n'est pas si bon, car il rend **impossible d'associer mentalement** une _microzone_ spécifique de la fenêtre comme dédiée à une opération spécifique. Et c'est potentiellement **dangereux**, si l'on prend en compte le gros problème 5 (ci-dessous).
+
+#### 3\. Le menu contextuel des options sur une partition utilise uniquement des étiquettes de texte, jamais une seule icône
+
+Un détail en apparence mineur, mais qui est en réalité assez important.
+Une chaîne de texte vous permet de comprendre sans équivoque ce que fait une certaine touche, contrairement à ce qui peut arriver lorsque vous n'avez que des icônes, mais **le meilleur serait obtenu** en combinant les deux choses : **touches accompagnées d'icônes**.
+
+<table><thead><tr><th>GParted</th><th>Disques GNOME</th></tr></thead><tbody><tr><td><img src="{{ < actifsRoot >}}/Media/Partioning-Mar-2023/GParted-Context-Menu.png" alt="Le menu contextuel d'une partition dans GParted."></td><td><img src="{{ < assetsRoot >}}/Media/Partioning-Mar-2023/GNOME-Context-Menu.png" alt="Le menu d'options d'une partition sur les disques GNOME."></td></tr><tr>< td ><strong>GParted fait cela pour ses menus contextuels (au moins sur les éléments les plus importants), et cela permet de mémoriser immédiatement l'<strong>action</strong> correspondant à chaque option, et de la rappeler immédiatement <strong>à un coup d'oeil</strong>.</td><td>Personnellement, <strong>en utilisant les disques GNOME</strong> je me retrouve toujours <strong>à devoir relire</strong> une bonne partie de la liste pour sélectionner quelque chose, même si ce n'est pas plus long que celui de GParted, précisément parce que <strong>les icônes manquent</strong>.</td></tr></tbody></table>
+
+#### 4\. Les raccourcis clavier et les menus contextuels ne sont pas des alternatives les uns aux autres
+
+<table><thead><tr><th>GParted</th><th>Disques GNOME</th></tr></thead><tbody><tr><td><img src="{{ <assetsRoot>}}/Media/Partioning-Mar-2023/GParted-Buttons.png" alt="La barre d'icônes rapide sur GParted."></td><td><img src="{{<assetsRoot >}}/Media/Partioning-Mar-2023/GNOME-Buttons-1.png" alt="Création de boutons et options sur une partition dans les disques GNOME."> <img src="{{< assetsRoot >}}/Media/ Partitionnement -Mar-2023/GNOME-Buttons-2.png" alt="Démonter les boutons et les options d'une partition dans les disques GNOME."> <img src="{{< assetsRoot >}}/Media/Partioning-Mar-2023 / GNOME-Buttons-3.png" alt="Blocs et boutons d'options sur une partition dans les disques GNOME."> <img src="{{< assetsRoot >}}/Media/Partioning-Mar-2023/GNOME-Buttons- 4 .png" alt="Bouton Options sur une partition dans les disques GNOME."></td></tr><tr><td>Sur <strong>GParted</strong> vous avez d'abord le <strong>menu de la barre des tâches </strong> (dont divers menus peuvent également être rappelés comme contextuels dans certaines zones), qui contient véritablement <strong>toutes les opérations</strong> possibles dans le programme ; seul <strong>le</strong> existe une barre avec des <strong>icônes</strong> utiles pour rappeler rapidement les actions probablement les plus courantes. En pratique, tant que vous disposez de la barre de menus, <strong>vous pouvez</strong> même <strong>oublier</strong> l'existence de <strong>ces petites icônes</strong> là-bas.</td> < td>Avec les <strong>disques GNOME</strong>, ce n'est <strong>pas possible</strong>. En fait, sur <a href="https://duckduckgo.com/?q=gtk3+examples&ia=images&iax=images" rel="noopener nofollow" target="_blank">plusieurs applications GTK3</a>, c'est comme ça : il y a des <strong>actions</strong> fixées aux <strong>touches-étiquettes</strong> dans un menu, et d'autres fixées aux <strong>touches-icônes</strong> directement visibles. Cependant, généralement, ces boutons ne <strong>disparaissent pas ou n'apparaissent pas partiellement</strong> lorsque l'état change au sein de la même vue d'application ! J'ai peut-être des goûts étranges, mais cette chose me dérange le cerveau lorsque j'utilise le logiciel.</td></tr></tbody></table>
+
+Pour comprendre, il suffit de comparer les boutons de ce tableau aux options de menu contextuel vues dans celui ci-dessus !
+
+## Qu'ai-je fait ?
+
+Tous ces facteurs réunis ont conduit à un énorme **patatrac** !
+Alors, qu'est-ce que je fais ? Je dois **démonter** la **partition** avant de pouvoir la **redimensionner**.
+
+Je passe de **la vue disque**, et il n'y a **que le bouton** pour le menu **options** - plus ce qui me viendra à l'esprit _seulement après_ quand j'aurai **déjà cassé** maintenant pour break up , est le bouton pour **détruire** la partition.
+Dans la liste des options, j'ai tout lu et **je ne vois même pas** une entrée pour **démonter** la partition. _Meh_.
+
+Je parcours l'**écran** dédié à cette **partition** montée, et j'appelle à nouveau ce menu pour je ne sais quelle raison, et à juste titre donc je ne trouve toujours rien.
+A côté du bouton du menu options **il y avait en théorie le bouton stop**, pour démonter la partition, mais force est de constater que je ne l'ai vraiment **pas** remarqué**.
+
+Je fais des **allers-retours** entre les deux écrans une dizaine de fois, et rien, je suis vraiment **aveugle**.
+
+À un moment donné, mon inconscient s'ennuie de tout ce **cerclage**, et me permet enfin de remarquer un autre **bouton**... le dangereux **rouge**. _Aïe aïe_.
+J'appuie dessus et honnêtement, je ne me souviens même pas si j'efface une fois le dialogue de confirmation - que je n'étais absolument pas dans un état psychologique pour lire - et puis j'appuie à nouveau sur le bouton pour confirmer immédiatement après le dialogue, mais une chose est claire :
+
+Si jusqu'à ce moment-là je n'arrivais pas à penser clairement, parce que **à chaque respiration** un **"WTF ?!"** rugueux résonnait dans ma tête, ce n'était qu'une question de quelques secondes à partir du moment du * *clic fatal** car un **mauvais pressentiment** commençait à apparaître dans ma tête percée, déformée, pleine de cacahuètes périmées... 😰️
+
+...Eh bien, et alors ? Qu'est-ce que c'est?
+...
+_Ohhhhah_, d'accord, **tu gagnes**. Je l'admets : **J'ai frappé aussi**. Oui. Heureux ? Au final j'ai bougé la main pour cliquer, bien sûr... Mais dans ma vie **j'ai fait** ces opérations **plusieurs fois** ! Même en utilisant des disques GNOME, parfois parmi tant d'autres ! 😭️
+
+De toute façon, non, je ne rejetterai pas toute la faute sur le **pauvre Octt** d'il y a trois jours. Maintenant, je joue ma _carte piège_, et expose la vraie **touche de malheur** sans laquelle je me serais probablement sauvé :
+
+#### 5\. Chaque action est effectuée lorsque vous la demandez, il n'y a pas de file d'attente
+
+Je dois admettre que parfois **dans GParted** j'ai frôlé la tragédie** - mais vraiment la tragédie, pas comme cette période que, tout bien considéré, je vis encore.
+La différence, cependant, réside précisément dans ce petit mot : avec **GParted**, le désastre s'est toujours produit au maximum **_presque_**, mais avec **GNOME Disks** cette fois, il a **consommé** et c'est tout. il.
+
+Sur **GParted**, les opérations que vous commandez se retrouvent dans une **file d'attente**, qui doit être appliquée manuellement une fois que vous décidez de continuer.
+Et là aussi, nous en sommes aux ** minuties **, et pourtant quelque chose comme ça pèse lourdement sur la facture finale. On peut le voir comme ceci : **dans ce cas**, il faut **faire une erreur** deux (**2**) **fois** pour faire des dégâts, alors qu'avec le programme GNOME une ( 1) une erreur suffit.
+
+![La vue de la file d'attente des opérations sur GParted.]({{<assetsRoot >}}/Media/Partioning-Mar-2023/GParted-Queue.png)
+
+## "Y a-t-il des dégâts ?"
+
+Dans tous les cas, j'ai remarqué qu'**après** avoir donné l'ordre de **supprimer la partition**, elle **restait** montable et le système de fichiers était entièrement **navigable**.
+Probablement, ce dont Linux avait besoin pour utiliser la partition restait en mémoire (RAM), et comme toutes les données n'étaient jamais supprimées avec une simple suppression rapide d'une partition, tout était toujours lisible.
+
+Pour être honnête, en regardant une telle situation, je **ne me rendais même pas** compte** de la réalité, je **ne comprenais toujours pas** si mes **données** avaient été **condamnées** ou pas. ..
+Interface peu claire, _Je l'ai dit_.
+
+Alors que le sentiment de précipitation passait et cédait la place à **l'inconfort**, j'ai recherché GParted**, j'ai découvert qu'il était inclus dans le système live et je l'ai démarré.
+Au lieu de la partition, je vois "espace vide"... oh **oui, c'est fait**. Mais comment se fait-il qu'il m'ait laissé **supprimer la partition** sans** m'obliger à la **démonter** au préalable ? Quelle barbarie ! GParted ne le permet pas, pour de bonnes raisons.
+
+Pourtant, au fond, je n'ai toujours **pas accepté** qu'il soit annulé.
+Je veux voir si, après un redémarrage, il disparaît définitivement.
+
+Et c'est donc, **sans** même **s'inquiéter** de copier un lambeau de fichier - car il était tard et je devais me préparer à m'endormir - que je **redémarre**.
+Oh oui, je vois l'écran noir de GRUB, et pas le démarrage du système ! ...**Tout est perdu**, ça ne sert à rien d'en faire le tour maintenant.
+
+"_Après avoir fait les dégâts, as-tu pensé à redémarrer immédiatement sans même sauvegarder les fichiers les plus importants ?!?! Mais alors tu es un idiot certifié, deux fois, pas une fois !_"
+_Ooooooooooooo_, comment oses-tu ? Comment oses-tu avoir **aussi raison** si le blog est le MIEN ??
+
+La seule chose que nous pouvons faire maintenant est le **compte des dégâts**. Je n'ai pas perdu de données uniques et très importantes, ce que je **n'ai plus, je devrais** en théorie pouvoir **retélécharger ou reconstruire**. Parlons de :
+
+* 40 Go de données exportées depuis mon ancien compte Google ; compte que j'avais prévu de supprimer, mais je n'avais pas fini de tout transférer et donc je pense que tout est **toujours dans le cloud**.
+
+* Divers **fichiers** grands et petits téléchargés **à partir du Web**, peut-être certains difficiles à trouver, mais **rien de vital**.
+
+* **Codes sources modifiés** ; nous parlons de tentatives de portage pour des plates-formes obscures que j'ai essayées et échouées, ou d'autres **expériences très oubliables**.
+
+* **Dumps de disques** que j'ai encore chez moi (certains déjà téléchargés sur [Archive.org](https://archive.org/details/@andrigamerita)), **ou copies supplémentaires** d'autres données .
+
+* Documents dont la **pertinence** actuelle est **nul**.
+
+
+Si j'ai **oublié** quelque chose d'important dans cette liste, peut-être que ce n'était **pas important**, et nous pouvons être rassurés. Sinon je m'en souviendrais, non ? _Eh bien, me connaissant..._
+
+## Éviter...
+
+La **morale** de cette **mauvaise histoire** peut être condensée en :
+
+1. Évitez les disques GNOME.
+2. **Soyez prudent** lorsque vous manipulez des partitions, même si vous l'avez fait 50 fois dans le passé.
+3. **Évitez**, absolument, les **disques GNOME** !
+
+Et je termine par un **conseil**, ou plutôt une **philosophie de développement**, que tous ceux qui conçoivent des **UI** (même moi, dans mes affaires, je ne le cache pas) oublient trop souvent : [L'utilisateur est ivre](https://www.youtube.com/watch?v=r2CbbBLVaPk).
+
+<iframe src="https://www.youtube-nocookie.com/embed/r2CbbBLVaPk" style="hauteur : calc(100vh / 16 * 9);" class="YouTube"></iframe>
+
+Alors, salutations. Pour l'avenir, j'espère **ne pas **perdre de données** de manière stupide (pour vous et pour moi !). 👋
+
+_**P.S :** La distribution Linux que j'ai installée cette fois est [Pop!\_OS](https://pop.system76.com/). Je voulais vraiment l'essayer, mais à 2 reprises j'ai essayé de l'installer sur le PC de bureau et cela donnait toujours une erreur. Ici, sur l'ordinateur portable, cela a fonctionné, wow, donc ce n'est pas une distribution cassée ! (**Peut-être** 👀)_
+
+## {{% i18n notes-réfs %}}
+
+---
+
+1. Le système que j'avais jusqu'alors, Linux Mint, version 19.3, après 3 ans :
+
+<dl><dt><strong>Elle est devenue obsolète :</strong></dt><dd>La version 19.3 est abandonnée et les référentiels ne reçoivent plus de nouveaux logiciels. Donc, j'aurais dû passer à la version actuelle de Mint, mais apparemment <strong>j'aurais dû quand même</strong> le faire en réinstallant <strong>à partir de zéro</strong> (sur <code class="prettyprint">apt dist-upgrade </code> il n'y a pas de nouvelles mises à jour)</dd><dt><strong>C'est cassé :</strong></dt><dd>Certaines choses (comme les pilotes vidéo cassés et l'environnement de bureau qui ne démarre qu'en mode de secours) sont définitivement de ma faute (<em>j'ai foiré</em> avec les pilotes <a href="https://en.wikipedia.org/wiki/Nvidia#:%7E:text=Nvidia " rel="noopener nofollow" target="_blank">ACCIDIA</a> ces dernières semaines), mais d'autres (Bluetooth ne fonctionne plus !?) je dirais non :/. De toute façon, <strong>quand le système est à ce point en panne, c'est plus rapide de tout réinstaller</strong>...</dd></dl>
+
+ [↩](#fnref1)
+
+2. Peut-être que oui, je suis un idiot, mais pas au point d'ériger volontairement les cloisons avec une structure qui m'est étrangère. A l’époque, très simplement, j’avais installé Linux Mint avec les paramètres guidés par défaut. Chaque fois que j'ai installé Linux, j'ai utilisé le partitionnement manuel, au lieu de choisir d'effacer tout le disque et de laisser le programme d'installation décider des choses, j'ai toujours créé des partitions normales. Alors... **ne me blâmez pas**, [kthx](https://en.m.wiktionary.org/wiki/kthx#:%7E:text=\(Internet%20slang\)%20Abbreviation % 20sur%20ok%2C%20merci.) ? [↩](#fnref2)
diff --git a/fr/miscellanea/Donazioni.md b/fr/miscellanea/Donazioni.md
index d456531..5068f2d 100644
--- a/fr/miscellanea/Donazioni.md
+++ b/fr/miscellanea/Donazioni.md
@@ -3,8 +3,7 @@ Title = "💰 Dons"
 Alias = [
   "/Donations.html",
 ]
-#Index: True
-#Order: 45
+Categories = [ "Méta" ]
 Lastmod = 2022-11-12
 +++
 
@@ -36,7 +35,7 @@ Gardez à l'esprit que le minage ne m'intéresse plus depuis un moment, donc je
 
 ## Faites un don via des cartes cadeaux
 
-À mon avis, un autre bon moyen d’échanger de l’argent sur Internet consiste à utiliser des cartes-cadeaux.
+À mon avis, un autre bon moyen d’échanger de l’argent via Internet consiste à utiliser des cartes-cadeaux.
 
 J'accepte actuellement les cartes-cadeaux pour ces magasins :
 
diff --git a/fr/miscellanea/Raccolta-Videogiochi/_index.md b/fr/miscellanea/Raccolta-Videogiochi/_index.md
index e3e2473..7fbb70d 100644
--- a/fr/miscellanea/Raccolta-Videogiochi/_index.md
+++ b/fr/miscellanea/Raccolta-Videogiochi/_index.md
@@ -5,7 +5,7 @@ Aliases = [
 ]
 Categories = [ "Jeux" ]
 #Style = @import "[staticoso:Site:RelativeRoot]Assets/Pages/Videogame-Collection.css";
-Lastmod = 2023-02-01
+Lastmod = 2024-09-20
 PagerSize = -1
 +++
 
@@ -16,7 +16,7 @@ PagerSize = -1
 Pourquoi ne pas faire un recueil pour parler, brièvement, des jeux vidéo que j'apprécie ? <!-- (Par ordre alphabétique) -->  
 Peut-être réussir à mettre en lumière une expérience de jeu à moitié méconnue qui mériterait pourtant bien plus. Et il ne peut être exclu qu'à l'avenir, en trouvant l'inspiration, je puisse prendre et écrire des articles longs et approfondis sur certains des jeux que je loue toujours brièvement ici, pour commencer.
 
-Pour chaque jeu, en plus d'une courte revue ponctuée de quelques avis, j'essaierai également d'inclure du matériel multimédia (photos, vidéos et musique). Enfin, lorsque cela sera possible, il y aura (via une page d'entracte/redirection) des liens d'achat physique et de téléchargement.  
+Pour chaque jeu, en plus d'une courte revue agrémentée de quelques avis, j'essaierai également d'inclure du matériel multimédia (photos, vidéos et musique). Enfin, lorsque cela sera possible, il y aura (via une page d'entracte/redirection) des liens d'achat physique et de téléchargement.  
 <!--
 Les liens externes qui ne sont pas officiels mais **précédés d'une coche verte** (<span class="twa twa-✅">✅</span>) **ont** été personnellement **vérifiés** par mes soins, les deux sont aussi sûrs que ceux qui fonctionnent - ceux non marqués ne sont pas vérifiés, mais pointent toujours vers une source fiable connue.
 --->
@@ -52,4 +52,6 @@ Je préfère avoir cette sous-section pour mentionner des jeux qui, même si je
 _Les titres qui n'ont qu'une seule de ces deux caractéristiques peuvent également être trouvés dans les sections ci-dessus._
 -->
 
-Il se peut que je n'aie pas le temps, ou que je n'aie pas envie, ou que ce soit la faute d'Antani, mais en tout cas il y aurait plusieurs autres travaux que je n'ai pas encore évoqués ici. Peut-être pouvez-vous facilement en trouver beaucoup sur **OcttKB**, sous la balise [Gaming](https://kb.octt.eu.org/#Gaming).
\ No newline at end of file
+~~C'est peut-être que je n'ai pas le temps, ou peut-être que je n'ai pas envie, ou peut-être que c'est la faute d'Antani, mais en tout cas il y aurait plusieurs autres travaux que je n'ai pas encore évoqués ici. Peut-être pouvez-vous en trouver beaucoup facilement sur **OcttKB**, sous la balise [Gaming](https://kb.octt.eu.org/#Gaming).~~
+
+Il existe également de nombreux autres jeux, rétro et modernes, que je n'ai pas explorés en détail ici (ou que je n'ai pas inclus du tout), mais ils sont disponibles (avec quelques informations encyclopédiques pour les accompagner) pour être **joués dans le navigateur** sur mon site dédié au gaming , **Sala Museo Games** : <https://gamingshitposting.github.io/SalaMuseoGames> !
\ No newline at end of file
diff --git a/fr/miscellanea/Sul-sitoctt.md b/fr/miscellanea/Sul-sitoctt.md
new file mode 100644
index 0000000..30a4f46
--- /dev/null
+++ b/fr/miscellanea/Sul-sitoctt.md
@@ -0,0 +1,212 @@
++++
+Title = "Sur place"
+Lastmod = 2024-08-25
+#Template = WM.html
+#Style = @import "[staticoso:Site:RelativeRoot]Assets/Pages/index.css";
+Categories = [ "Méta" ]
+Featured_Image = "@/RichPreview/index.png"
++++
+
+{{< noticeAutomaticTranslation it >}}
+
+
+
+Ici, c'était initialement la page d'accueil du site, mais elle est devenue si problématiquement longue que... qu'à cela ne tienne, tout est expliqué sur la [nouvelle maison](/). Voici donc la série classique d'informations libres concernant le ✨sitoctt✨ (certaines anciennes, elles seront mises à jour en fonction des nouveautés) ! 😊
+
+<!-- Crédits : https://codepen.io/jh3y/pen/WNrXqYz -->
+<div style="Position:Relative;"><br/>
+<h1 class="NoTitle WavyText" style="--x: 6; --y: -6;"><span style="--index: 0; --alpha-l: 0,125; --alpha-u : 0,25;">✨</span><span style="--index : 1; --alpha-l : 0,125;">s</span><span style="- -index : 2 ; --alpha-l : 0,125 ; --alpha-u : 0,25 ;">i</span><span style="--index : 3 ; 0,25;">t</span><span style="--index : 4; --alpha-l : 0,125 ; --alpha-u : 0,25;">o</span><span style= "-- indice : 5 ; --alpha-l : 0,125 ; --alpha-u : 0,25 ;">c</span><span style="--index : 6 ; u : 0,25 ;">t</span><span style="--index : 7 ; --alpha-l : 0,125 ; --alpha-u : 0,25 ;">t</span><span style=" --index : 8 ; --alpha-l : 0,125 ; --alpha-u : 0,25 ;">✨</span>
+</h1>
+<h1 class="NoTitle WavyText" style="--x: 3; --y: -3;"><span style="--index: 0; --alpha-l: 0,25; --alpha-u : 0.5;">✨</span><span style="--index: 1; --alpha-l: 0.25; --alpha-u: 0.5;">s</span><span style="- -index : 2 ; --alpha-l : 0,25 ; --alpha-u : 0,5 ;">i</span><span style="--index : 3 ; 0.5;">t</span><span style="--index : 4; --alpha-l : 0.25;">o</span><span style= "-- indice : 5 ; --alpha-l : 0,25 ; --alpha-u : 0,5;">c</span><span style="--index : 6 ; --alpha-l : 0,25 ; u : 0,5;">t</span><span style="--index : 7; --alpha-l : 0,25 ;">t</span><span style=" --index : 8 ; --alpha-l : 0,25 ; --alpha-u : 0,5 ;">✨</span>
+</h1>
+<h1 class="NoTitle WavyText"><span style="--index : 0; --alpha-l : 0,5; --alpha-u : 1;">✨</span><span style="-- indice : 1 ; --alpha-l : 0,5 ; --alpha-u : 1;">s</span><span style="--index : 2 ; ">i</span><span style="--index : 3; --alpha-l : 0,5; --alpha-u : 1;">t</span><span style=" --index : 4 ; --alpha-l : 0,5 ; --alpha-u : 1;">o</span><span style="--index : 5;">c</span>< span style="--index : 6 ; --alpha-l : 0,5 ; --alpha-u : 1;">t</span><span style="--index : 7; --alpha-l : 0,5 ; --alpha-u : 1;">t</span><span style="--index : 8; --alpha-u : 1;">✨</span >
+</h1><br/>
+</div>
+
+D'où vient le nom **✨**<strong class="MainIdTextGradientL">sitoctt</strong>**✨** ?
+Du fait que c'est littéralement mon site, parce que je suis octo et donc
+<i style="Color:#8040d0;">site</i> + <i style="Color:#d000d0;">octt</i>
+= **✨**<strong class="MainIdTextGradientR">sitoctt</strong>**✨**
+(<a href="{{< assetsRoot >}}/Media/sitoctt-pronunciation.flac" target="_blank" rel="noopener">prononciation : "sitòctt"</a>).
+Si vous préférez, vous pouvez l'appeler <i class="MainIdTextGradientL">sitocto</i>. Ou même <i class="MainIdTextGradientR">postoctt</i> ! C'est toujours un endroit - mon endroit - même s'il est virtuel !
+
+## Statut du site et comment naviguer
+
+Bien qu'il ait déjà un peu plus de substance, tout cet ambaradan est encore en construction. Et ce sera toujours le cas, car j'aurai toujours des nouveautés à partager. ~~Et, quand je serai mort, ce sera encore inachevé car de ma vie je n'aurai pas écrit toutes les connaissances universelles théoriquement possibles sur le sitectt.~~
+Les mises à jour du site sont de différents types : la publication de nouveaux articles de blog a lieu, enfin, 3 fois par mois, c'est une bonne idée d'utiliser des <a href="#-Feed-e-notifiche">flux</a> que je mets à disposition ; les changements pour les pages normales sont continus et se produisent de manière aléatoire, vous devriez donc vérifier celles qui vous intéressent peut-être chaque semaine, si vous attendez des nouvelles.
+
+<p><b>À garder à l'esprit</b> (du Web) : lorsque les boutons suivants sont à l'écran, c'est qu'ils peuvent masquer les menus pliables.
+Ils peuvent être dans différentes positions sur différentes pages, car j'aime expérimenter différents thèmes ; mais j'essaie de garder leur signification cohérente partout.<br/>Une icône emoji de pile de livres (<big class="twa twa-books twa-📚">📚</big>) signale le menu de la page principale du site, indispensable pour pouvoir naviguer en sautant entre des pages complètement différentes et sans lien entre elles.
+A la place, l'icône avec l'emoji d'une feuille avec un signet (<big class="twa twa-bookmark-tabs twa-📑">📑</big>) indique la liste des sections de la page en cours - ce n'est pas indispensable , mais peut être utile pour passer d'une partie à l'autre d'un long texte.
+</p>
+
+### Scripts côté client
+
+<p>Le site Web n'utilise aucun script côté client pour les fonctions de base, car je ne veux pas forcer ceux (pour des raisons de sécurité valables et autres) qui ne souhaitent pas activer JavaScript à vivre une expérience dégradée. Concernant cette épineuse question, j'ai également écrit un article : <a href="Posts/2022-06-14-0000-I-Documenti-Non-Devono-Diventare-Applications.html"><span class="twa twa- page -facing-up"><span>📄</span></span> Les documents ne doivent pas devenir des applications</a>.<br/>Quoi qu'il en soit, cependant... pour fournir des fonctionnalités supplémentaires, je dois avoir du JS, vous ne pouvez pas faire grand-chose. Ci-dessous la liste de ce que j'utilise. <i>Tous les fichiers sont téléchargés depuis les serveurs de mon site, il est donc difficile pour les entités malveillantes d'y cacher des logiciels malveillants</i>.</p>
+<détails>
+<résumé>
+<h4>Liste des scripts côté client utilisés dans le site Web (Développer)</h4>
+</résumé>
+<div>
+<ul>
+<li>Scripts internes, écrits par moi : <del>Menus à expansion automatique sur les pages thématiques sitoctt en mode bureau</del> (j'essaie de résoudre ce problème..), affichage plein écran des arrière-plans des pages.</del > li>
+<li>
+<del>Polyfill pour prendre en charge les images AVIF sur les anciens navigateurs : <a href="https://github.com/Kagami/avif.js" rel="noopener" target="_blank">avif.js par Kagami</ a ></del> (<i>Pas encore activé...
+<del>ce sera bientôt</del> <small>quand vais-je le faire ? Je le remets à plus tard depuis des mois, le problème c'est que ce n'est pas une solution plug-and-play, je dois d'abord le comprendre puis créer un script de packaging 😭</small></i>)
+</li>
+</ul>
+</div>
+</détails>
+<p>Ci-dessous, je mets mon classement des manières possibles de consulter ce site, du meilleur au pire. Par standardisation, ils prennent tous en charge la totalité des couleurs (dans la mesure du possible).</p>
+<détails>
+<résumé>
+<h4>Mes digressions inutiles sur des manières absolument absurdes de consulter le sitectt (Expand)</h4>
+</résumé>
+<div>
+<dl>
+<dt><b>• Navigateur Web, avec prise en charge complète de CSS3</b></dt>
+<dd>(Parfait !)</dd>
+<dt><b>• Imprimez sur du papier holographique, avec un rendu GIF et CSS3 complet si possible</b></dt>
+<dd>(Nécessite de déplacer le papier à la main mais excellent !)</dd>
+<dt><b>• Navigateur Web, avec prise en charge incomplète de CSS3</b></dt>
+<dd>(Meh, OK..)</dd>
+<dt><b>• Impression sur papier ordinaire, animations CSS3 et GIF non rendus</b></dt>
+<dd>(Boo, il manque des animations..)</dd>
+<dt><b>• Ancien navigateur (Old Web, Text Web ou Gemini) / Impression sur papier ordinaire, pas de prise en charge CSS </b></dt>
+<dd>(Qu'est-ce que c'est que ces conneries ?!?!)</dd>
+</dl>
+</div>
+</détails>
+
+## Mais de quoi s'agit-il ?
+
+Sur mon espace Internet, je mettrai tout. J'espère.
+
+Pour l’instant, je publie définitivement des pages superficielles sur des sujets spécifiques, mais aussi de longs articles de blog conversationnels. Je souhaite également constituer de nombreuses collections sur les choses que j'aime, tant sous forme textuelle que médiatique. Une sorte de galerie de choses qui me sont précieuses.
+
+Cependant, en plus du contenu lui-même, je souhaite que le site (la version Web, évidemment) soit une galerie en soi. Je veux créer quelque chose qui ait son propre caractère, à l'instar des sites Web amateurs des années 1995-2005, où chaque endroit sur Internet avait toujours une atmosphère différente de tout ce qui était visité un instant auparavant.<br/><span style=" Couleur :#404040;">L'essor des médias sociaux tels que nous les connaissons aujourd'hui a malheureusement ruiné le Web de ce point de vue, conduisant à une standardisation complète et à la mort de la créativité exprimée par la forme.</span><br/>I Je veux que mon espace web soit différent de tous les autres, caractérisé par des textes monochromes et des thèmes recyclés, car c'est dommage d'avoir des outils très puissants et de ne pas vraiment les exploiter.
+
+Pour cette raison, je vais constamment essayer d'inventer des façons d'embellir les pages avec CSS, non seulement avec des effets de mise en page ou de texte fixes, mais surtout avec des animations.<br/>Au reste du formulaire, comme l'arborescence des les pages du site ou les paragraphes des pages, je ne réfléchirai pas beaucoup, sinon je me laisse distraire de la création de contenu et l'envie passe.
+
+## Disponibilité du site
+
+Ce site est actuellement consultable à différentes adresses (le contenu est toujours identique).
+Pour ceux qui ne le savent pas, cependant, le nom a changé il y a un mois pour sitoctt de postoctt, car l'ancien nom me donnait l'impression d'un service postal...
+Je devrais aussi penser à de nombreux autres miroirs cloud de différents fournisseurs (évidemment gratuits), si je veux que le site survive à lui-même et résiste à l'épreuve du temps... Mais c'est une longue question.
+
+###Web
+
+<p>Le site Web est disponible à partir de plusieurs sources.</p>
+<ul>
+<li>Sur le HTTPS <b>clearweb</b>, sur les serveurs <span style="Color:#fc6d26;">GitLab</span> : <a href="https://sitoctt.octt.eu .org">sitoctt.octt.eu.org</a>.</li>
+<li>Sur le <b>Onion Web</b> (<span style="Color:#59316b;">Tor</span>), sur les serveurs Replit : <a href="http://sitoctt2fxjvx3lc2iqqef2aeulflprjaasv2xl4zi7sxxbmvjy5b5yd. onion ">sitoctt2fxjvx3lc2iqqef2aeulflprjaasv2xl4zi7sxxbmvjy5b5yd.onion</a>. Au final il n'est plus hébergé chez moi, mais c'est peut-être pour le mieux, c'est une charge de moins pour le pauvre petit serveur de fortune que j'ai (en ce moment,
+<del>une console Nintendo Switch avec Ubuntu</del> le Raspberry Pi 3).
+</li>
+</ul>
+<détails>
+<résumé>
+<h4><span class="twa twa-💾"><span>💾</span></span> Options de compatibilité pour les systèmes obsolètes ou exotiques (Agrandir)</h4>
+</résumé>
+<div>
+<dl>
+<dt><b>• Version HTTP de base</b></dt>
+<dd>Le site inclut des fonctions CSS complexes et relativement modernes, afin de fournir des effets graphiques (et fonctionnels) épiques. Ironiquement, même si l'on consulte les pages sur des navigateurs très anciens, qui ne supportent pas totalement ou presque totalement CSS, tout semble moche mais est lisible... sur des navigateurs <i>à la fois trop anciens et trop récents</i > des bugs très sérieux apparaissent , ce qui rend impossible l'utilisation de certains menus ou même la lecture du texte !<br/>En plus du fait que (dans la mesure du possible) je souhaite supporter d'anciens systèmes, ces foutus problèmes apparaissent également sur des appareils moins populaires mais actuels, comme le Allumer! Bref, pour trop de navigateurs qui n'incluent pas de paramètre pour désactiver complètement le CSS, il fallait faire ce que j'ai fait : vers le chemin <a href="./Plain">/Plain</a> sur mes domaines clearweb, il y a une racine parallèle et des pages avec le même contenu mais du CSS réduit à l'essentiel.</dd>
+<dt><b>• HTTP non chiffré</b></dt>
+<dd>Pour éviter les problèmes, je lui ai dédié un sous-domaine dédié, en gardant HTTPS forcé sur le principal ; mais, comme il ne nécessite pas de maintenance, je me suis assuré qu'à partir du domaine de cinquième (!) niveau "<span style="Font-Style: Monospace;">http</span>" vous puissiez accéder au site via HTTP non crypté ( hébergé par GitHub, cette fois) : en bref, l'adresse est <code style="Text-Decoration:Underline;">http://http.sitoctt.octt.eu.org</code>. Le contenu est identique, bien sûr, mais finalement vous pouvez parcourir le site sur des trucs comme <i>Internet Explorer 4</i> directement en contactant le serveur.</dd>
+</dl>
+</div>
+</détails>
+
+### Gémeaux
+
+<p>Désormais, le site CTTT est également disponible sous forme de capsule Gemini. Pour y accéder, il faut utiliser un navigateur Gemini.<br/>Évidemment (pour ceux qui connaissent Gemini), tout est plus castré, et la forme n'est pas exactement la meilleure car toutes les pages sont une conversion directe du HTML de le site Web (et le programme que j'utilise pour le faire est également un peu cassé).<br/>Allez sur l'octocapsule, aimablement hébergée par koyu.space : <a href="gemini://koyu.space/octt" > gemini://koyu.space/octt</a></p>
+
+### Flux et notifications
+
+<p>Désormais le site (le blogoctt et le MicroBlog notamment) intègre des flux, qui sont automatiquement mis à jour lorsque je publie un nouvel article !</p>
+<p><b style="color:#ff6a00;">Atom Feed</b> (moderne, <b>recommandé</b>, contient des articles complets) : <b><a href="./feed/ atom.xml">feed/atom.xml</a></b><br/>Flux RSS (obsolète, disponible pour compatibilité) : <a href="./feed/rss.xml">feed/rss. XML</a></p>
+<p>Vous avez besoin d'un agrégateur de flux compatible pour les utiliser.<br/>- Sur PC de bureau, je recommande <a href="https://thunderbird.net" rel="noopener" style="Color:#0080FF;" target="_blank">Thunderbird </a>o <a href="https://www.seamonkey-project.org" rel="noopener" style="Color:#003399;" target="_blank">SeaMonkey Mail</a>.<br/>- Sur Android, je recommande <a href="https://f-droid.org/packages/com.nononsenseapps.feeder" rel="noopener" target="_blank">Feeder</a> ou <a href="https://f-droid.org/packages/com.poloure.simplerss" rel="noopener" target="_blank">Rss simple</ a >.<br/>- Si vous souhaitez utiliser un appareil comme une liseuse de livres électroniques e-ink, le seul logiciel universel qui - entre autres - inclut un agrégateur de flux, que je connais et que je peux recommander, est <a href="https://github.com/koreader/koreader" rel="noopener" target="_blank">KOReader</a>.<br/>- Astuce : Si vous utilisez Friendica, vous pouvez copier le lien vers le flux et collez-le dans la barre de recherche, pour pouvoir le suivre comme s'il s'agissait d'un profil !</p>
+<p>
+<del>De plus, si vous utilisez n'importe quelle plateforme du <b>Fediverso ActivityPub</b> (Mastodon, Pleroma, Misskey, ...) vous pouvez suivre le bot du site ctt, afin de recevoir de nouveaux messages dans votre Flux d'accueil : < a href="https://botsin.space/@sitoctt" rel="me noopener" target="_blank">@sitoctt@botsin.space</a>!</del> Pour certaines complications qui lancé fin août 2022, le bot n'est pas accessible depuis la plus grande instance italienne de Mastodon, <i>mastodon.uno</i>, il est donc presque pratiquement inutile maintenant. Je ne l'enlève pas simplement parce que cela me coûterait plus cher que de le laisser là où il est <b>:P</b>; Cependant, il me faudrait en créer un nouveau, tôt ou tard.
+</p>
+
+## Sources et licences
+
+### Licences de contenu
+
+<p>Tout le contenu de ce site que j'ai créé (mes propres écrits, les médias originaux et la plupart du code source) est sous licence <a href="https://creativecommons.org/licenses/by-sa/4.0/deed. it" rel="noopener" target="_blank">"Creative Commons Attribution - Partage dans les mêmes conditions 4.0 International" (CC BY-SA 4.0) (<span class="CCIcons"><img class ="i1em" src="https ://sitoctt-assets.octt.eu.org/Media/Icons/CC/CC.svg"/> <img class="i1em" src="https://sitoctt-assets .octt.eu.org/Media /Icons/CC/BY.svg"/> <img <="" class="i1em" span="" src="https://sitoctt-assets.octt.eu.org /Media/Icons/CC/SA .svg"/>)</span></a>, une licence gratuite qui favorise le partage, et n'affecte pas les droits légitimes à la culture et à la collaboration de l'humanité en général.</ p>
+<p>Cependant, il y a aussi des contenus qui ne sont pas de moi.<br/>Dans tous les cas, si quelque chose sort de ma main, il n'y aura aucune indication de crédits à proximité. <br/>Pour les éléments empruntés, cependant, la source d'où je les ai pris et la licence seront toujours indiquées, que ce soit dans le domaine public, Creative Commons, ou non précisé.<br/>Attention, les crédits car je laisse souvent les éléments HTML et CSS dans les sources de la page. Donc, juste au cas où, vérifiez ce genre de crédits. Cependant, pour des choses comme des images ou des textes, les crédits sont souvent une partie visible de la page, proche de l'objet emprunté (comme une description) ; d'autres fois, le même objet est un lien qui, si vous cliquez dessus, vous ramène à la source. Cependant, j'ai pensé à créer une section de la page <a href="#-Special-Credits">ci-dessous</a> , dédié aux crédits spéciaux (que je remplis quand je me souviens).</p>
+
+###Code source
+
+<p>En parlant de sources du site, la source HTML de la page chargée par le navigateur peut être difficile à lire. En effet, je n'écris pas le code HTML complet directement pour composer les pages. Non seulement ce serait un désastre de reproduire mes différentes barres et sections de navigation sur toutes les pages, et si je dois y apporter des modifications, c'est un problème. Bon sang pour reproduire cela n'importe où, mais la syntaxe HTML est sale et difficile à écrire.</p>
+<p>C'est précisément pour ces raisons que j'ai créé mon propre générateur de site statique (également, comme ce site lui-même, incomplet mais mis à jour de temps en temps lorsque j'en ai besoin), qui prétraite mon code source pour inclure mes barres dans toutes les pages, générer les sections de la page (qui apparaissent dans le menu de droite), générer la liste des pages du site (depuis le menu de gauche), et <i>autres petites choses</i>. Étape importante, tous les fichiers Markdown ou Pug sont traduits en HTML pour être compréhensibles par les navigateurs normaux, et voilà.<br/>Ah oui, je dis "<i>autres petites choses</i>" parce que cela c'est des choses qui, au moment de la rédaction de ce chapitre, la page est absente ou incomplète, et en écrivant pendant que j'écris, je me couvre les fesses et je n'ai pas à faire de modifications futures.
+<pre class="Inline"><i>H et h .</i></pre>
+</p>
+
+#### Prenez tout !
+
+<p>Pour finir, retrouvez toutes mes sources sur les dépôts Git respectifs.<br/>Ceux de mon site (divisés en plusieurs dépôts pour garder l'historique propre), dans les conditions décrites ci-dessus : <a href="https:/ / gitlab.com/octtspacc/sitoctt" rel="noopener" target="_blank">gitlab.com/octtspacc/sitoctt</a>; <a href="https://gitlab.com/octtspacc/sitoctt-assets" rel="noopener" target="_blank">sitoctt-assets</a>.<br/>Ceux de mon générateur, également publiés sous licence libre, l'AGPL : <a href="https://gitlab.com/octtspacc/staticoso" rel="noopener" target="_blank">gitlab.com/octtspacc/staticoso</a>.</ une> p>
+<p>Autre chose : si cela est intéressant, pour conserver et/ou partager immédiatement (à l'exclusion des fichiers qui se trouvent dans des référentiels séparés, car ils sont absolument liés) des copies hors ligne du site, vous pouvez télécharger un <b>zip < /b> contenant toutes les pages compilées <a href="https://gitlab.com/octtspacc/sitoctt/-/jobs/artifacts/main/download?job=pages" rel="noopener" target="_blank" >ici </a>!</p>
+
+### Crédits spéciaux
+
+<détails>
+<résumé>
+<h4>Liste des crédits et remerciements particuliers à ceux qui ont emprunté du matériel (Développer)</h4>
+</résumé>
+<div>
+<ul>
+<li>Liste des <a href="#-Script-client-side">scripts côté client</a>, y compris certains scripts tiers</li>
+<li>Titre animé Waaaves : <a href="https://codepen.io/jh3y/pen/WNrXqYz" rel="noopener" target="_blank">Waaaves par jh3y</a></li>
+<li>Famille de polices : <a href="https://fonts.google.com/specimen/Space+Mono" rel="noopener" target="_blank">Space Mono par Colophon Foundry</a></li >
+<li>Pack emoji CSS : <a href="https://twemoji.twitter.com" rel="noopener" target="_blank">Twemoji de Twitter</a>, via <a href="https:/ /gitlab.com/octtspacc/twemoji-astonishing" rel="noopener" target="_blank">Twemoji étonnant</a></li>
+<li>Quelques boutons 88 x 31 non identifiants : <a href="https://cyber.dabamos.de/88x31" rel="noopener" target="_blank">Collection GIF 88 x 31 par cyber.dabamos.de</a > </li>
+</ul>
+</div>
+</détails>
+
+## Confidentialité et transparence
+
+Dans le cadre de mon intérêt légitime, j'utilise un service d'analyse sur ce site Web ; à la fois pour améliorer ce que je fais et pour satisfaire ma pure curiosité de découvrir des données.
+
+Le service d'analyse est entièrement basé sur <a href="https://github.com/arp242/goatcounter/blob/master/LICENSE" rel="noopener" target="_blank">gratuit et open source</ a>. , hébergé gratuitement pour les sites à faible trafic par <b>GoatCounter.com</b>.
+
+Apparemment, avec GoatCounter, vous n'avez pas besoin d'inclure un avertissement à l'écran qui dérange les utilisateurs pour se conformer au RGPD (voir <a href="https://www.goatcounter.com/help/gdpr" rel="noopener " target="_blank">goatcounter.com/help/gdpr</a>), mais, par souci d'honnêteté et de transparence, j'écris quand même ce paragraphe.
+
+Seules les données non personnelles sont collectées, de manière anonyme, à des seules fins de statistiques générales, et non à des fins de suivi individuel. Le service n'utilise pas de cookies et les données ne sont pas transférées à des tiers. Pour plus d'informations, je ne peux que vous recommander de lire la <a href="https://www.goatcounter.com/help/privacy" rel="noopener" target="_blank">Politique de confidentialité de GoatCounter</a >.
+
+<style>
+.CCIcons > Img, .CCIcon {
+Affichage : en ligne !Important ;
+Hauteur maximale : 1em !Important ;
+Alignement vertical : Sub ;
+}
+.CCIcons > Img, .CCIcon {
+Marge gauche : 3 px ;
+}
+
+/*!-- Crédits : https://codepen.io/jh3y/pen/WNrXqYz ---*/
+.TexteOndulé {
+Alignement du texte : Centre ;
+Position : Absolue ;
+Gauche : 50 % ;
+Espace blanc : NoWrap ;
+Transformer : Traduire(-50%, -50%) Traduire(Calc(Var(--x, 0) * 1%), Calc(Var(--y, 0) * 1%));
+paramètres de variation de police : 'poids' Var(--lower);
+Marge : 0 ;
+}
+.WavyText Portée {
+Couleur : HSLA (300, 100 %, 20 %, Var (--alpha-l) );
+Animation : Rise 2,25 s, facilité d'entrée et de sortie infinie ;
+Animation-Délai : Calc((Var(--index) - 6) * 0,225s);
+Affichage : bloc en ligne ;
+}
+@keyframes Montée {
+50% {
+paramètres de variation de police : 'poids' Var(--upper);
+Couleur : HSLA (300, 100 %, 30 %, Var (--alpha-u)) ;
+Transformer : Traduire (0, -15 %) ;
+}
+}
+</style>