skilltheamps

Das BS ist ja egal, das kann man einfach kostenlos wieder runterladen und installieren. Die ganzen persönlichen Daten wie Passwörter, Geburtsdatum/Ort usw. was man alles so im Dokumente-Ordner und den E-Mails findet ist doch viel interessanter! Für Identitätsdiebstahl zum Beispiel, oder Bestellung von Zeugs mit dem Konto von jemandem anders.

Also Dinge die mir spontan einfallen wären z.B. private kostenlose Wlans wie Freifunk, staatliche kostenlose Wlans die oft an öffentlichen Plätzen und Gebäuden zu finden sind wie BayernWlan und sowas, kostenlose Wlans in Geschäften (z.B. viele Supermärkte), Bahnhöfen und Zügen. In jedem Supermarkt kann man einfach eine Prepaid Karte mitnehmen. Abseits des Mobilfunks gibt es auch öffentlich zugängliche Computer, z.B. in Bibliotheken. Also du kannst es auf jeden Fall unbequemer machen ein online Casino zu erreichen, ob das reicht hängt dann wahrscheinlich davon ab wie groß das Verlangen der Person ist trotzdem zu spielen.

Es sei an dieser Stelle angemerkt, dass DNS Blacklists keine Sperre darstellen. Sie führen lediglich dazu, dass das Netzwerk selbst keine Auskunft darüber gibt mit welcher IP-Adresse diese Inhalte zu erreichen sind. Das hat allerdings keinerlei Auswirkungen darauf, dass sich jedes Gerät im Netzwerk diese Information wo anders besorgen kann, oder das möglicherweise eh schon macht, und der entsprechende Benutzer deine "Sperre" nicht einmal bemerkt. Je nachdem auf wen du mit deiner Aktion abziehlst, und welche Kenntnisse und Hoheit derjenige über das Gerät hat, ist deine Maßnahme also wirkungslos. Schlussendlich ist es aber praktisch auch immer möglich sich ziemlich einfach einen anderen Internetzugang zu besorgen, sollte es sich z.B. um einen spielsüchtigen Erwachsenen handeln.

It is not that easy to understand what you want, to me it reads like you want something like Nextcloud - i.e. your own little cloud, where you can put all your stuff, and view it through the webbrowser or the nextcloud apps, and also keep selected parts of your stuff in sync with your devices (or automatically upload photos take with your smartphone for example).

Backup of Nextcloud (or whatever you want to use) is a seperate topic. Any incremental backup tool would apply though, so there's much to choose from. I personally use btrbk which uses Btrfs Send+Receive to push incremental snapshots to an offsite server.

Partly yes, but just installing a package without running into conflicts does not yet guarantee a working system. You have to cater for the right configurations too, for example when you think about a corporate setting with all kinds of networking whoes (like shares, vpns and such). I think you could get this to work with Nix somehow, but you want to test these things beforehand, and if you do so using images then you have the thing to ship to machines in your hands already, there's no need to compose the OS and configurations over and over again for every machine.

Another aspect with non-atomic OS composition on the target is that you have to deal with the transient phase from one state to the next. In this phase all kinds of things could happen, for example an update of nvidia drivers would render cuda disfunctional until the next reboot, as the userspace and kernelspace parts do not fit together anymore. With something like any of the fedora atomic variants, transient phases with basically undefined behaviour do not exist, and the time the system is not guaranteed to be in working order gets reduced to just the reboot.

Nix is cool and definetely better than any traditional package manager. But it is not an ultimate solution, to be honest so far it seems to me like it is living in a nieche of enthusiasts that are smart enough to put up with its unique declaration language. And below that niche you have ordinary linux users that may just be happy with silverblue without any modifications, and above that niche you have corporate doing their own images in CI/CD, CoreOS and all that jazz.

that doesn't require I keep a full local copy of all the data

If you don't do that, the place that you call "backup" is the only place where it is stored - that is not a Backup. A backup is an additional place where it is stored, for the case when your primary storage gets destroyed.

It is not a fork aiming to replace it. It is rather a spin with saner defaults to cater to companies as customers. The product which shall carry ondsel financially is their freecad compatible cloud offering, and the hope is to use that for elevating freecad itself too. They need their spin to be able to ship an ootb experience fitting their motive and brand. So if you would like a less confusing experience it might be something for you. Currently there's a lot of borderline deprecated and also redundant functionality in freecad, so I hope that ondsel's cleanup mantra will make it to the ootp upstream experience as well.

As far as I remember ondsel is working on upstreaming realthunder's approach to freecad, but it is a lot of work to polish up because it touches so many parts of the application.

Here is a nice interview with one cofounder of ondsel where I have this information from: https://shows.acast.com/ohm-podcast/episodes/ep-12-brad-cto-of-ondsel

/dev/fb is mostly one thing: deprecated. Also it is not really a interface of your graphics card, it is a legacy way kindly still provided for pushing fullscreen pixels to your monitor in an unaccelerated fashion for things that have not made it to kms drm (which at this point is pretty much merely the console emulation on the TTYs). It is not an interface to the graphics card, because it doesn't provide any capabilities a graphics card has (like shaders etc). In fact for just pushing pixels you can leave any graphics card completely out of your computer if you connect your screen by other means (think stuff like SPI which is common in embedded devices; you can find many examples of such drivers in the kernel source at drivers/gpu/drm/tiny ).

Well maybe you youself are too new to recognize some of the appeals ;)

One large advantage with silverblue is, that the whole composition of the OS does not take place on the target machine. That means that all the issues that could arise will not take place on the target machine, and can be dealt with beforehand. In the simple case this could mean just enjoying vanilla silverblue without having to think about possibly borking the machine. In an advanced usecase this could mean for example building the os images in a GitLab CI/CD pipeline (with well working tooling that exists already for docker etc), then having automatic tests in the pipeline ensure that everything important works as expected. And only if the tests pass, the image will be added to the repositorie's image registry, where the target machines will fetch it from automatically and rebase to it.

This covers just the basic cpu instructions, no proprietary extensions, no architecture of additional necessities like a gpu, no proprietary firmare for the gpu or anything else. The instruction set of Arm, x86 or whatever is not a secret though. The freedoms in risc-v are mostly concerning the manufacturers, which can build chips using this instruction set without paying any royalties. From a consumer point of view, that at most means one can at most choose from a more organically grown landscape of risc-v chips. Which in turn bears the risk of ending up in a situation, where all we have is a vast jingle of cluttered proprietary extensions, that make it harder to write libre drivers for than it is for Arm today.

Don't get me wrong, risc-v is absolutely amazing! But in terms of freedomness, it would take a manufacturer to extend the spirit of open hardware to the complete SOC - and the basic instruction set is pretty much the smallest piece in that.

Yes. But the more advanced LLMs get, the less it matters in my opinion. I mean of you have two boxes, one of which is actually intelligent and the other is "just" a very advanced parrot - it doesn't matter, given they produce the same output. I'm sure that already LLMs can surpass some humans, at least at certain disciplines. In a couple years the difference of a parrot-box and something actually intelligent will only merely show at the very fringes of massively complicated tasks. And that is way beyond the capability threshold that allows to do nasty stuff with it, to shed a dystopian light on it.