“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”
That is not the case for every country though. In France and Germany for example almost 3/4 of google requests are via IPv6.
If you have a working config, thats exactly the point. Before you built your config, you don’t know. If you deploy silverblue, you know it will work beforehand because exactly this config, including /etc, has been tested upstream before. What you are to your buddy, Fedora Atomic is to me. The difference is, it is not just one person that tested some config they decided on on their single piece of hardware, it is the effort of a full blown distro team.
No, just because it is reproducible doesn’t mean you are able to (re)produce something that works. With something like fedora silverblue you know that this specific composition of packages and their versions has been tested, and that all the other users run this exact composition as well.
When you roll your own composition, where you install whatever stuff, you may be the one finding out that there’s some conflict between package a version u.v.w and package b version x.y.z.
I encourage you to go to town with whatever crazy setup you come up.
I just want to note that the reboot-to-update mechanism also has its positive sides, as ancient as it may seem (we do not succumb to windows level backwardness, because that fails to reap the benefits despite requiring so many reboots). Namely, you get atomic updates, hence the name “fedora atomic” for example. That means you have no transient periods where your OS is running in an inconsistent state. Like when you update a traditional distro, the new files/libraries/binaries/kernel-modules do not match anymore what is in RAM, including the currently running kernel. That leads to stuff like the nvidia driver / cuda not working until reboot, running applications failing to load a library they need now etc… The vast majority of times this is no huge problem, but in theory the only way of maintaining a system with it never running in basically undefined state is with atomic udpates.
And the firmware inside that rp2040 is stored on plain old flash memory. So while the data may still be on the memory chip, the controller chip dies at just the same pace than every other usb drive - and then you can’t access it.
Hab ich mir auch mal gedacht, und habs bereut.
Ich vermute bei einer solchen Frage lebst du in einer Stadt, und nicht iwo auf dem Land mit Haus und Hof. Suche mal nach Rad-Waschboxen/-Waschanlagen in deiner Umgebung, so Zeug gibt’s. Es gibt sogar Tankstellen die in den Waschboxen für Autos ausklappbare Fahrradständer haben. Und zur Not würd ich es einfach in ner Auto-Waschbox auf den Boden legen und fertig.
The problem is not the EU demanding that, it rather is Apples blatant incompetence at implementing it
This is the correct answer, every device you use a bitwarden-client regularly on automatically becomes a backup
Yes I know it, and sometimes use it for a little. But the vast majority of things it presents to complete to me feel rather unimportant. My leisure time isn’t exactly plenty, and then I rather do other things I see more value in. Even surface type is mapped most of the time, and I don’t take the effort to map surface quality because it is not used for anything. Maybe I’ll make an App at some point that infers surface quality automatically while road biking from the acceleration sensor in the phone mounted to the handlebar…
At least for the more fundamental information like paths or trails this is true. I only really get to map stuff when in holidays abroad, because here you have to check a 100 times if something is mapped to find a handful of chances to contribute anything, which has a frustrating feel to it 😅
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:
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.
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/
You do not want Octoprint on a machine that is busy. Otherwise you have load spikes that cause Octoprint to not be able to send the move-commands (gcode) as fast as the printer executes the movements. This problem is pronounced with faster printers and slicers that break up arcs into small straight lines (which is practically all slicers). Otherwise your printer stutters because it has to take small breaks to wait for the next command from octoprint.
What privacy concerns do you have? I’m all for privacy, but I don’t really see where registrars are a delicate topic in that. The most that comes to mind is that some (most?) have a service where they do not give out your name and address for whois requests, but instead the details of the registrar (namecheap has that for example).
True words. The sustained effort to keep something in decent shape over years is not to be underestimated. Now when life changes and one is not able or willing anymore to invest that amount of time, ill-timed issues can become quite the burden. At one point I decided to cut down on that by doing a better founded setup, that does backup with easy rollback automatically, and updates semi-automatically. I rely on my server(s), and all from having this idea to having it decently implemented took me a number of months. Just because time for such activities is limited, and getting a complex and intertwined system like this reliably and fault tolerant automated and monitored is simply something else than spinning up a one off service
And they believe all employees actually remember so many wildly different and long passwords, and change them regularly to wildly different ones? All this leads to is a single password that barely makes it over the minimum requirements, and a suffix for the stage (like 1 for boot, 2 for bitlocker etc), and then another suffix for the month they changed it. All of that then on sticky notes on the screen.
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.