This commit is contained in:
2024-08-23 15:18:32 +02:00
parent 3e3159f5b7
commit cf7c0ff225
20 changed files with 1385 additions and 3 deletions

View File

@ -0,0 +1,25 @@
+++
Title = "What's happening"
Categories = [ "MicroBlog" ]
Dates = 2022-09-11
+++
These last 7 days, very little has been said or done here on the ctt site.
I created this section to use as a general journal, but I'm just now writing something.
First of all, school started again the day before yesterday for me.
It's still too early for it to steal my time in the afternoon, but in the morning the story is a bit what it is. Just as the mess when you start again is always the same, with the timetables being messed up and in general still having holidays on your mind.
Due to these factors, I have a little less time in total to do little things.
Let's add that, due to a curious need of mine, in the last few days I have had to start programming [yet another new instrument](https://gitlab.com/octospacc/links){[:MdTgtBlank:]}... I'm not starting to blather on about the thing itself, because this section is for everything except my development adventures, but the travails can be told: I started developing on Thursday, and only had a minimal working tool last night.
All this, because I wanted to exaggerate with the idea (as usual), and because every afternoon from Thursday to Sunday, until early evening, I was [at the fair](./PicoBlog.html#-2022-09-11 -La-fiera) and, returning home tired, the desire to plan was low.
To this mix we add another distraction: after 5 years, a new chapter of the Splatoon saga has been released, and therefore there is little to do, you have to play. However, after a brief analysis, I am trying not to play with it too much, to try to sip it as much as possible so as not to consume it immediately.
Today I didn't play it at all, for example, and I think I'll end the evening without it; but maybe it's because today I had experiments to do regarding dumping digital school books, to have them without DRM.
By the way, when I've finished the story and have tried even a minimal amount of multiplayer, I'll publish a review of the game, which I'm already writing along the way.
At the beginning I tried to put the game on a PC emulator, but between glitches (which will soon be resolved), a bit of lag, and the inability to play decently away from the desktop, I had to try on real hardware.
My Switch console, however, had been working as a server for 7 months now. Enough, Spoon is vital: I'm putting the Raspino back out.
I haven't put all my software back yet, but the important ones (SpaccCraft and my bots) are there. I also added a new little thing, qbittorrent, which takes care of seeding some torrents even when my PC is turned off.
I also need to tidy up some things regarding backups, for some of my bots, it takes a while.

View File

@ -0,0 +1,43 @@
+++
Title = "When I get my hands on I rock"
Categories = [ "MicroBlog" ]
Dates = 2022-09-18
+++
The other day I was, let's say, reminded of the fact that I have a [Nintendo DSpacc](https://wikispacc.miraheze.org/wiki/DSpacc){[:MdTgtBlank:]} in my drawer.
![My DSpacc, running Pokémon Ruby from its cartridge.]({{< assetsRoot >}}/Media/Misc/DSpacc_Pokemon_Rubino.jpg)
I'm not ashamed to admit that it's disused, because the only thing I can play with it is Pokémon Ruby.
But not because there is only one screen left! It's because...
**The console's DS slot is broken**
: I don't really understand how, but slot 1 is broken: some pins are simply bent, but 2 are really missing, and the latter unfortunately are some of the important ones, not duplicates like the ground ones. So, no playing any of my physically owned DS games, nor using a flashcart.
<meta>
**Pokémon is the only GBA cartridge I own**
: I don't have any other cartridges from the GBA! I only have this Pokémon one because I found it at a fair years ago and, not having any GBA cartridge but the DS already broken at the time, I decided to buy it. I've played it quite a bit, but I want more. But I don't have any other cartridges or even a GBA flashcart.
The fact is that, also because I had to take a photo for the WikiSpacc article, I took it out the other day. When I see it I regret not using it, but unfortunately there is little that can be done.
My crazy mind, however, today recalled an idea that, if I were capable of doing these things, maybe it would have even been good... but that's me.
I thought: what if I soldered a DS flashcart in place of the slot?** I didn't think of this out of nowhere, I saw it some time ago in a modification of the DS made by a person who does these things well . In some videos from a year ago, like [this](https://invidious.nerdvpn.de/2wxKDzUO23c?t=156){[:MdTgtBlank:]}, you can see that this other form of DS has a soldered flashcart on the motherboard.
I take the screwdriver and bits, and disassemble the console. All OK, I've done this at least 4 times counting just the DS Lite.
But then, I arm myself with a welder... honestly they should take away my gun license, considering the damage I do.
The first thing I find myself having to do is desolder the slot. _Ouch_.
After cutting the non-electrical points that held the slot to the motherboard - which looked like solder points, but didn't melt - I first started by trying to heat up all the pins slowly, pulling the slot out slightly. But it doesn't work. So I try to heat every single pin and remove the solder with that strange tool used to suck it up... but little or nothing comes of it. In the end I go back to the initial method, but done faster and more smoothly.. **what a disaster**!
<div class="MediaRow2" markdown="1">
![Photo of the area where the DS slot was.]({{< assetsRoot >}}/Media/Misc/IMG_20220918_170148.avif)
![Macro photo of the area where the DS slot was.]({{< assetsRoot >}}/Media/Misc/IMG_20220918_170157.avif)
</div>
Almost all the soldering points have come off, and now there is brown. I know the trick of scratching away the green layer of the PCB, to expose clean metal to solder on, but there's just no room here. On this card everything is close together, there is not the slightest room for manoeuvre.
There are some very small holes with the conductive diameter around them (just as wide as a single copper wire), testpoint type, which actually appear to be connected to where the solder pads I destroyed were connected. Just to, I try to solder up there, but there's absolutely no way to do it. Those are small and there is no good space around them, so the pond doesn't settle.
I just wasted time, and once again demonstrated to myself that I'm just not capable of doing soldering work that goes beyond connecting 2 wires to huge pads (which I do badly anyway, with a dirty job).
I'm going to buy a GBA flashcart now, and use it.. to boot DS software. To my surprise, it's possible, and maybe I'll talk about it next time.

View File

@ -0,0 +1,23 @@
+++
Title = "New frontiers"
Categories = [ "MicroBlog" ]
Dates = 2022-09-23
+++
Since I discovered it a few days ago. I'm trying that epic software that is [TiddlyWiki](https://tiddlywiki.com){[:MdTgtBlank:]}.
I initially found it while looking for something to organize notes in a rich format, that I could use for school, and that was obviously free.
It is a wiki software, practically in the same category as MediaWiki (the software on which Wikipedia is based), but it has very particular characteristics.
First of all, it doesn't need a server, it's an app that works locally... but how absurd (in a good way)! The entire app with all your personal data is a single, self-editing HTML file, meaning you can copy and secure an entire site in an instant. It cannot save data on its own, but you have to download the modified HTML file locally each time, or use synchronization systems (I use Git, supported in-app).
If I started using it for the sole limited purpose of school study, but then these days I ended up starting to use it a lot also to create my so-called personal and public knowledge base, on everything I can write to the I fly in a non-linear document format that is very well suited to small, quick interconnected notes... which means it's really interesting.
I'm a bit sorry to say it, but it's possible that part of the time I would normally dedicate to the ctt site will be taken away from it, to be dedicated to the newly created OcttKB - which, in this regard, is here on <https://kb.octt .eu.org>{[:MdTgtBlank:]}.
As much as I like everything I have built in recent months, which in fact will continue to live - both as a place in which to express my design style, and as a place in which to publish elaborate and never fragmented content - I must say that I have found a tool which manages to channel some of my thoughts well, those that the CTTT site cannot manage.
I'm not going to explain too much about the technical side of the advantages or disadvantages of TiddlyWiki, because we're talking about a software that is easy to start using, and absolutely very complicated to master (it will take me time!).
What I will say is that: with its being oriented towards the arrangement of information in small fundamental elements (the _tiddlers_), which can then be connected to each other to build elaborate information - both with links and with transclusion (when the content of a element appears completely copied in the middle of another, which is done simply by writing <span>`{`</span><span>`{`</span><span>`Element Name`</span><span> `}`</span><span>`}`<span>) - lends itself really well to well-rounded thinking organization in general.
As a bonus, TiddlyWiki can be used as a more traditional static site generator: you can write elements into many files, and use the CLI program to compile everything into the monolithic file described above. The official site of the project uses this technique, but for a personal site it is not necessary and in fact, it cancels out the advantage that TiddlyWiki has, of being able to be used as a modern notes app: open, write, everything is saved in the cloud automatically.
However, the CLI program has a function that I find useful: the ability to generate static versions of the site, which do not require JavaScript for navigation. This is great, and I think anyone with a public TiddlyWiki, if they have the tools, should set up a build system to automatically make static pages available on the server.

View File

@ -0,0 +1,38 @@
+++
Title = "DSpacc Updates - Cursed Key"
Categories = [ "MicroBlog" ]
Dates = 2022-10-16
Lastmod = 2022-10-20
+++
A month ago, in the [post of October 18](./2022-09-18- Quando-Metto-Mano-Io-Spacc.html), I briefly said that it was the DSpacc, and what a new mess I had caused.
Well, this time I did even worse; to understand the proportions, it is good to brush up on what I had written for a second.
The card I mentioned has arrived, the software modification to improve it works, and I'm still exploring it all a bit. I will have time to talk about everything in a long article, which I am already writing (but I don't know how much longer it will take me).
What is important to talk about now is a problem that arose... I don't even know exactly when, but I only noticed it now: the L back button was causing some problems.
I saw that pressing key combinations to access the flashcart system menus had no effect. Getting suspicious, I decide to download a homebrew to test the keys, Diagnose (which can be found from [GameBrew.org](https://www.gamebrew.org/wiki/Diagnose){[:MdTgtBlank:]} [[pag. archived](https://web.archive.org/web/20220818023822/https://www.gamebrew.org/wiki/Diagnose){[:MdTgtBlank:]}]), and I actually confirm that the L button does not respond to the inputs.
On Nlhlehde's chat they advise me to soak the button in alcohol to clean it, and then give it some exercise - or, if I wanted to repair it correctly, unsolder the button and put a new one on.
At that moment I get bored of opening the console, but I see that two minutes of exercise magically makes the button work again. The operating state, in reality, lasts just a few minutes, and was questionable at the time: on average, 1 click out of 3 was recorded.
Today I finally decide to disassemble the DSpacc, to see if I can do the service on the key. To my surprise, I see that this is sort of raised from the side; one of the many GND pins has desoldered, while the only one that closes the other side of the circuit, you can barely notice, has broken.
![Macro photo of raised key.]({{< assetsRoot >}}/Media/Misc/DSpacc-Shoulder-Macro-Front.avif)
Now, it cannot be said whether the problems registering the presses were due to the externally smashed button, or to internal problems that have nothing to do with the initial malfunction of the button (and the final destruction occurred due to my pressing the button a hundred of times a minute to make him exercise).. what is certain is that alcohol is not enough to fix 😅.
Initially, I try to solder just above the broken leg, which in itself should solve the problem; unfortunately, the side of the pins is so short, and the button in such an awkward position (since we are talking about a back button), that the solder on my pin touches a little next to it and shorts the ground. This makes the button always pressed, and therefore it's even worse (my flashcart menu doesn't open if any button is pressed at startup!) than what I had before.
I try to fix the soldering a bit, but no, I can't improve anything.
At this point, I think about desoldering the button, because anyway... and it works fine, perhaps due to the size of the SMD device, small but not too much: the board has remained clean.
Time to take a new button from the many I have aside, even if much larger than the dorsal one on the DS, and solder it.
Oh well, enough, I'm bored of going around it any more: I try to solder a wire on the main contact, but the solder doesn't stick. The DSpacc PCB is deadly, oh. I try and try again... and in the end the metal pad to solder on comes away. A classic, dare I say, always ends like this! 😑
![Macro photo of the soldering area of the backbone, with the central pad destroyed.]({{< assetsRoot >}}/Media/Misc/DSpacc-Shoulder-PCB-Pad-Broken.avif)
Was it better to have a back button that works with great difficulty, or is it better not to have one at all? I don't know, and I don't want to know. The fact is that now I will have to find solutions to the numerous problems resulting from this bad story,...,,,..,
_**P.S, update 2022-10-20:** I'll give you a photo of the broken button disassembled, before throwing it away, why not? The microSD in the corner acts as a scale, to make the dimensions clear._
![Macro photo of detached and disassembled button.]({{< assetsRoot >}}/Media/Misc/DSpacc-Shoulder-Button-Disassembled-Macro.avif)

View File

@ -0,0 +1,202 @@
// % Categories: MicroBlog
// % URLs: Posts/MicroBlog-Archive/2019/09/index.html
## September 2019 MicroBlog archives
<div markdown="1" class="BorderBoxContainer NoImgCenter Img36 ImgSidePadding">
<details markdown="1"><summary>
#### [2019-09-18 20:58] Lagwei lazur </summary>
> A.y: ooooo
> ![Photo of A.y's Huawei, which appears to emit a purple laser from the proximity sensor.]({{< assetsRoot >}}/Media/Misc/A.y-Huawei-Laser.avif)
> Oct: what to wear that purple lazur
> Oct: the mysteries of lagwei
[...]
{: .Center }
> A.y: be proximity sensor
> A.y: if you smash glass over that
> ![Sticker of a violinist playing. In this chat context it implies something gone wrong.]({{< assetsRoot >}}/Media/Stickers/Violin.avif)
> A.y: I know from experience
>   no that's not true
</details>
<details markdown="1"><summary>
#### [2019-09-17 15:16] Various tests with the Galaxy Player </summary>
> : Good Lagsung
> ![Photo of the Galaxy Player, showing the Telegram channel in Plus Messenger.]({{< assetsRoot >}}/Media/Galaxy-Player-3.6/Galaxy-Player-3.6-OctoVoLTE.avif)
> : 512 MB of RAM and runs better than the Lagwei
> !["RAM" screen in Galaxy Player's "Activity Manager". 215 MB of 488 MB of RAM are indicated occupied.]({{< assetsRoot >}}/Media/Galaxy-Player-3.6/Galaxy-Player-3.6-Task-Manager-RAM.avif)
> : Now let's try the N64 and DS emulator, so it explodes
[...]
{: .Center }
> : Eeee the DS games run better on an 8 year old Android than on my PC [the Android in this case is ARMv7, while the PC is x86_64, ed.], perfect
> <video controls><source src="{{< assetsRoot >}}/Media/Galaxy-Player-3.6/GP3.6-Pokemon-Platino.webm" type="video/webm">Pokemon Platinum</video>
> **[Survey]** I have to try some DS for my next game
> | Total | 3 |
> |----------------------------|---|
> | Mario Kart DS | 2 |
> | Pokemon B/W 2 | 0 |
> | Animal Crossing Wild World | 0 |
> | Super Mario 64 DS | 1 |
> : OK I've been told by groups to try Mario 64, so I'm going to try both Mario Kart and Mario 64
[...]
{: .Center }
> : I found something in the lag memory
> ![Screenshot of a folder, containing the files of a NANDroid backup of the Galaxy Player dating back to 2017-12-09.]({{< assetsRoot >}}/Media/Galaxy-Player-3.6/CWM-Backup-2017 -12-09.avif)
> : Here's a reason why the new versions of Android suck [they handle the connection as a USB memory worse than Android 2.3, ed.]
> ![Photo of the Galaxy Player showing the "USB storage in use" screen.]({{< assetsRoot >}}/Media/Galaxy-Player-3.6/Galaxy-Player-3.6-USB-storage.avif)
> : Actually there are many, we'll talk about them later
> : And now let's test the other games
[...]
{: .Center }
> : Super Mario 64 DS
> <video controls><source src="{{< assetsRoot >}}/Media/Galaxy-Player-3.6/GP3.6-SM6464DS.webm" type="video/webm">Super Mario 64 DS</video>
> : Mario Kart DS
> <video controls><source src="{{< assetsRoot >}}/Media/Galaxy-Player-3.6/GP3.6-MKDS.webm" type="video/webm">Mario Kart DS</video>
> : So, I would like to record other games but the Memewei is broken and, despite having deleted the videos from before, it says that I have no memory
> : Oh yes right, I've only had this Huameme for a year and a half, but there are LOTS of things to talk about regarding it
> : Screenshots of the N64 emulator are now arriving
> : I didn't record but the framerate of the games was always stable and playable.. unfortunately the games are not so playable, but only because there are serious graphic glitches
> : I think it's the fault of the emulator which is old (unfortunately I can't do much on Android 2.3.6)
> ![Screenshot of Mario Kart 64 emulated on the Galaxy Player.]({{< assetsRoot >}}/Media/Galaxy-Player-3.6/N64/Mario-Kart-64/GP3.6-MK64-0.avif)
> ![Screenshot of Mario Kart 64 emulated on the Galaxy Player.]({{< assetsRoot >}}/Media/Galaxy-Player-3.6/N64/Mario-Kart-64/GP3.6-MK64-1.avif)
> ![Screenshot of Mario Kart 64 emulated on the Galaxy Player.]({{< assetsRoot >}}/Media/Galaxy-Player-3.6/N64/Mario-Kart-64/GP3.6-MK64-2.avif)
> ![Screenshot of Mario Kart 64 emulated on the Galaxy Player.]({{< assetsRoot >}}/Media/Galaxy-Player-3.6/N64/Mario-Kart-64/GP3.6-MK64-3.avif)
> ![Screenshot of Super Mario 64 emulated on the Galaxy Player.]({{< assetsRoot >}}/Media/Galaxy-Player-3.6/N64/Super-Mario-64/GP3.6-SM64-0.avif)
> ![Screenshot of Super Mario 64 emulated on the Galaxy Player.]({{< assetsRoot >}}/Media/Galaxy-Player-3.6/N64/Super-Mario-64/GP3.6-SM64-1.avif)
> ![Screenshot of Super Mario 64 emulated on the Galaxy Player.]({{< assetsRoot >}}/Media/Galaxy-Player-3.6/N64/Super-Mario-64/GP3.6-SM64-2.avif)
> ![Screenshot of Wave Race 64 emulated on Galaxy Player.]({{< assetsRoot >}}/Media/Galaxy-Player-3.6/N64/Wave-Race-64/GP3.6-WR64-0.avif)
> ![Screenshot of Wave Race 64 emulated on Galaxy Player.]({{< assetsRoot >}}/Media/Galaxy-Player-3.6/N64/Wave-Race-64/GP3.6-WR64-1.avif)
> ![Screenshot of Wave Race 64 emulated on Galaxy Player.]({{< assetsRoot >}}/Media/Galaxy-Player-3.6/N64/Wave-Race-64/GP3.6-WR64-2.avif)
> ![Screenshot of Wave Race 64 emulated on Galaxy Player.]({{< assetsRoot >}}/Media/Galaxy-Player-3.6/N64/Wave-Race-64/GP3.6-WR64-3.avif)
> : I took the screens directly on the Lagsung with an app
> : Now comes the video of some games vah
> : Apart from Zelda which I tried now, the other games have a stable framerate if you see, nice, a Lagsung from 8 years ago is redeeming itself.
> : I warn you that there might be an epileptic trigger when I start quake 2 eh xd
> <video controls><source src="{{< assetsRoot >}}/Media/Galaxy-Player-3.6/N64/GP3.6-N64-Misc.webm" type="video/webm">N64</video >
> : Okay, enough of the Lagsung tests for now
</details>
<details markdown="1"><summary>
#### [2019-09-16 18:35] Memewei memory full </summary>
> !["P9 Lite Mini screen saying the memory is almost full and this would slow down the device."]({{< assetsRoot >}}/Media/P9-Lite-Mini/Memewei-Memoria-Full.avif)
> : The Memewei proves itself valid kek
>: Fuck you, one day I'll rock this thing
>: Except that he's already kind of bent, because he got beaten up so many times because he was a meme
> : But Lagsoong can have just 1 KB free and doesn't break with Chinese popups
A bit of context is in order here: this crap smartphone, when it only has like ~100 MB free on the internal memory, pops up this popup about every 3 minutes, which is annoying to say the least. And believe me, it is easy to fill the memory of a smartphone with Android 7 which, after taking out the space occupied by the system components, only has 7.5 GB of space available to the user.
</details>
<details markdown="1"><summary>
#### [2019-09-16 18:24] Brick and rebirth of the Galaxy Player </summary>
> : So, as you know today I unbricked the Lagsung, and the internal memory was not formatted
> : This means I found worlds from 2013 and beyond that I didn't remember existed
> : At 10 subscribers you will see the worlds
[...]
{: .Center }
> : Ah, the old Lagsung keyboard has a nice thing about it
> : He doesn't have those toxic emojis because he has better things
>   MUCH BETTER
> ![Photo of the Galaxy Player showing the notes app, with the keyboard open on the emoticons tab, which are the old symbol style, not emoji.]({{< assetsRoot >}}/Media/Galaxy-Player- 3.6/Galaxy-Player-3.6-Notepad-Emoticon-Keyboard.avif)
[...]
{: .Center }
> : Ok, now I will tell you the detailed story of the briquetted Lagsung, and now fixed why
>   Now you will find out why
> : So
>   The lag in question is Galaxy Player 3.6
>   Aka a thinner S1 with no phone part
> : What happened
> : A year ago, since my brain is lagging, "yeah, why don't I put a custom rom??!1!1!" comes to mind.
>   And then I put a custom ROM, which was also ugly
>   Three hours later I wanted to remove it, because the WiFi was broken
> : So what do I do
>   I prepare Odin, look for the stock ROM and flash it
>   It's not clear why (that is, I know why, because Odin is an asshole program that will steal your phone if it wants to) towards the end [of the flash process, ed.] it freezes, it doesn't move forward
>   I left the thing hanging there for almost half an hour and it wasn't working, so I'm disconnecting
> : I turn it back on and
> ![Distorted sticker of Kanna and Tohru (two dragon lolis) reading a book called "Am I retarded?".]({{< assetsRoot >}}/Media/Stickers/Lolis-Reading-Am-I-Retarded- Book.avif)
> : Yes, because there was a nice screen that said
> ![Photo of the Galaxy Player which, on the bootloader, shows a warning triangle and the writing "Firmware update encountered an issue. Please select recovery mode in Kies & try again."]({{< assetsRoot >}}/Media /Galaxy-Player-3.6/Galaxy-Player-3.6-Softbrick-Bootloader.avif)
> : And so, nothing, since I have sawdust in my brain, for literally almost a year I thought it was my corrupt ROM, because even if I reflashed it always gave an error at the end, and for literally a year I wasted time looking for other ROM to no avail
>: Oh and, obviously I tried to connect to Kies simply, but it didn't recognize the phone, it kept charging, and if I went into Kies' manual recovery mode it asked me for a code (?)
> : Then just the day before yesterday the good Ashflee told me that all I needed was the right PIT file and it would be fixed
> : I didn't know because I'm laggy
> : So today I find the PIT file of the US version and I don't care about the fact that I have the European Galaxy, I put PIT and flash the US ROM and
> : E
> : It's in bootloop because well, there was sawdust in /data and it wouldn't mount
> : I format /data from recovery and the lag comes on, and now it works and is better than my meme
> : However, the internal archive has not been deleted, and all the old files are there
>   Including my very old Minecraft worlds
> : And nothing will be, this is Lagsoong back to life after a year in a coma
> ![Photo of the Galaxy Player lock screen, with a non-canon Astolfo wallpaper.]({{< assetsRoot >}}/Media/Galaxy-Player-3.6/Galaxy-Player-3.6-Astolfo-Lockscreen.avif )
</details>
<details markdown="1"><summary>
#### [2019-09-16 18:14] The beginning of OctoVoLTE </summary>
> : So, there will be Lagsung stuff on this channel
> : And Memewei, but maybe also Xiaomime
> : Oh and, of course, ways to get 🅱oLTE on your phone
> ![VoLTE]({{< assetsRoot >}}/Media/Misc/phh-VoLTE-JiOwO.avif)
The history of OctoVoLTE officially began from these messages. Memewei has been talked about there in recent years, perhaps too much; Of methods to have VoLTE, there hasn't been even one, like. Sad.
</details>
</div>