• 16 Posts
  • 573 Comments
Joined 10 months ago
cake
Cake day: January 9th, 2026

help-circle


  • More info at https://github.com/bsgcl/SmartTubeLocal/blob/master/FAQ.md . One thing to note is, that this is developed and maintained by a single person. And according to the README https://github.com/bsgcl/SmartTubeLocal:

    This repository is maintained offline for private use, but I push updates here as a backup, and for your entertainment.

    its a personal project without community involvement.

    Also every sentence in the README is its own paragraph. I don’t now why this abomination of style is done. Wish this modern style of writing documents would stop.

    To that end, I’m publishing the current 32.71 source code and final release, with the source code frozen at this version.

    Download the APKs from the SmartTube LOCAL GitHub Releases page.

    I’ll continue to publish updated APKs as I hatch them.

    So only the initial release is Open Source. Any further development is closed source. I would recommend to use a different application instead. Otherwise you cannot update if you don’t want to use a proprietary tool in the future. Not really Open Source in my opinion and probably vibe coded and vibe maintained too.








  • Sounds like a memory leak. Is it really KDE? Maybe its the browser or some kind of service running in the background. If memory got leaked out of the app, that it doesn’t matter if you close the app or not, because those are ghost memory now. I had this issue with a local Ai program just yesterday. It doesn’t matter if I close everything, somehow the memory usage shows high amount; because a software leaked and it was not KDE, as this was reproducable.

    My point is. you might not know where this leak come from without careful analyzing it. You can’t just conclude its KDEs fault because you don’t know why this happens. You should investigate which program does that.



  • You can absolutely prove the absence of bugs via formal verification.

    You can’t have a formal verification for an open ended system like the Linux Kernel. You can only have that with extremely narrow defined functions that only operate mathematical and the input and output are 100% deterministic. Someone has to make the test cases, and to my knowledge its not possible to do this with complex systems like the Linux Kernel.

    The card example does not really make sense because the kernel is not a random set of syntax and bugs do not happen randomly.

    It makes sense, because it proofs my point that a finite number is irrelevant if its that big. The randomness of it is absolutely not the point, its the sheer amount of possibilities.

    Well we now have software really good at finding these things, as well as system languages that cannot have these bugs.

    No software can test a complex system like this in its entirety to make sure there are no bugs. Those software itself need to be perfect themselves too. Therefore you introduce enormous complexity in solving bugs, which itself can have bugs.

    If bugs are closed faster than they are opened, the total amount goes down.

    I wasn’t arguing against that. I am arguing that a finite number of bugs is not a good argument to have none in the future. Because of the sheer amount of possibilities, and also because we cannot proof that Linux Kernel is perfect without any bugs. It is impossible.



  • Amount of bugs is finite.

    Resources are also finite. You can’t proof the absence of bugs, you can only proof the existence of it.

    Did you know, there are more ways to arrange a deck of cards than there are atoms on Earth. A standard deck has only 52 cards. Now imagine how many possibilities are there to have bugs in a code like the Linux Kernel. Just because something is finite does not mean we will ever reach that point.


  • I think its a good sign, because it means the Kernel gets more secure. And it also means there is not just slop produced with Ai, if people know what they are doing off course. Any of these CVEs not found could have been abused by anyone else.

    Edit: I was thinking and speaking of the Linux Kernel itself, but this applies to any other important code or service too.

    The number of reported security vulnerabilities has gone up drastically.

    I think of the number of FOUND security vulnerabilities has gone up drastically.


  • Wow. But as we see again, this was done with Ai too:

    initial bootstrap was done with a bunch of agentic tools, which helped a lot in reverse-engineering the brilliant niri codebase and surgically extracting the pieces relevant to ewm. Today, coding agents are used mainly to compare ewm against niri and other

    I am sure there is orchestration and understanding of the material involved in order to even make this kind of thing work. What I don’t understand is, why its needed to “reverse-engineer” Niri codebase? I mean its open source, there is nothing to reverse engineer. I just don’t understand the statement here.




  • Currently there are two alternative options to have something similar:

    To see file hierarchy at a glance.

    One could also use the “Details View” with the “Expandable” option enabled. It’s not quiet the same as a Columns, but one can see the hierarchy:

    Alternatively use the “Folders” panel on the side. This has the advantage to use any “View” mode in the files listing: