That power efficiency is a direct result of the instructions. Namely smaller chips due to the reduced instructions set, in contrast to x86’s (legacy bearing) complex instruction set.

With something like this, how do you handle the period of time while copying? I mean you can’t really leave it running as it wouldn’t be in a consistent state. A “under maintenance” page instead? Copy to a fresh folder and when done tell the webserver to serve the new location?

“almost all of the most technical employees in framework are using either ubuntu, fedora or nixos. I’m mostly on Windows because we need actually people that are using Windows because our employee base in framework is all Linux users”

• Nirav Patel

https://m.youtube.com/watch?v=EIEc43CxIvY

Specifically the shitty IPU6 situation is on Intel, and is invariant to any laptop manufacturers. I also have a Thinkpad X1 with that issue. So for that the situation that one manufacturer would support it properly (i.e. upstream) and others don’t can’t exist, as soon as anybody puts it upstream it works for everybody. Thankfully there’s some progress (search for libcamera) and in the not too distant future it should work ootb. For fingerprint readers it is a different story though, as there are many different ones, so that one is on Dell indeed

One possibility would be Huginn I guess https://github.com/huginn/huginn

You have this view because your hardware is from an era where fingerprint reader largely weren’t a thing and webcams were connected via internal usb. The issue is not that the Linux kernel drops anything (between you and op, you’re the one with the old hardware). The issue is, that fingerprint readers became a commodity without ever gaining universal driver support, and shengians like Intel pushing its stupid IPU6 webcam stuff without paving the way upstream beforehand

As far as I understand, in this case opaque binary test data was gradually added to the repository. Also the built binaries did not correspond 1:1 with the code in the repo due to some buildchain reasons. Stuff like this makes it difficult to spot deliberately placed bugs or backdors.

I think some measures can be:

• establish reproducible builds in CI/CD pipelines
• ban opaque data from the repository. I read some people expressing justification for this test-data being opaque, but that is nonsense. There’s no reason why you couldn’t compress+decompress a lengthy creative commons text, or for binary data encrypt that text with a public password, or use a sequence from a pseudo random number generator with a known seed, or a past compiled binary of this very software, or … or … or …
• establish technologies that make it hard to place integer overflows or deliberately miss array ends. That would make it a lot harder to plant a misbehavement in the code without it being so obvious that others note easily. Rust, Linters, Valgrind etc. would be useful things for that.

So I think from a technical perspective there are ways to at least give attackers a hard time when trying to place covert backdoors. The larger problem is likely who does the work, because scalability is just such a hard problem with open source. Ultimately I think we need to come together globally and bear this work with many shoulders. For example the “prossimo” project by the Internet Security Research Group (the organisation behind Let’s Encrypt) is working on bringing memory safety to critical projects: https://www.memorysafety.org/ I also sincerely hope the german Sovereign Tech Fund ( https://www.sovereigntechfund.de/ ) takes this incident as a new angle to the outstanding work they’re doing. And ultimately, we need many more such organisations and initiatives from both private companies as well as the public sector to protect the technology that runs our societies together.

That’s odd, I upgraded my ender 3 with bed leveling and removed the knobs to mount it fixed, because the damn knobs keep moving and then you have to redo the bed calibration. To be honest I can imagine one reason might be that a loosely mounted bed gives you more fault tolerance against the nozzle being too low. I put my bed on two parallel linear rollers for more rigidity, and combined with dual z screws the nozzle has no chance anymore to produce any sort of first layer when it is slightly too low. That made me realize just how much the stock ender 3 is flopping around, but also how this can give you mostly okayish results most of the time without having to deal with a ton of small tolerances.

Ah thank you, that wasn’t obvious to me from its website

Why do you prefer it over syncthing?

I don’t have one, I can only tell you that you can change the keyboard layout. The Readme of the firmware sourcecode says:

To change the keyboard layout, adjust the matrix arrays in keyboard.c.

https://source.mnt.re/reform/reform/-/tree/master/reform2-keyboard-fw

You might find more information in the mnt forum, it is here: https://community.mnt.re/

I ordered some parts from them a couple weeks ago to build my own custom laptop, and they’re finally on their way and I’m super excited! The article is missing this, but you can order hinges, keyboard (with or without case), trackball/-pad and all these things individually from them, and use them for your own purposes.

It is just mind boggeling how much MNT encourages hacking with their stuff. They even went and made a dedicated logo you can put on things that are made to work with the reform ecosystem / derivatives: https://source.mnt.re/reform/reform/-/blob/master/symbol-for-derived-works/mnt-based-reform.svg

You can also search for the founder Lukas F. Hartmann and find a couple interviews out there.

I don’t get your second paragraph. There are many markdown editors, and you can use their inbuilt methods or pandoc to convert that to epub/pdf/whatever. What features are missing from those editors?

Ja genau das ist es. Man muss es aber selbst betreiben, ich glaube es gibt noch niemanden der immich hosting als service anbietet.

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.

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.

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