It’s the same problem as with any other software development: Politics (literally). Some decisions are made by people who are not qualified to make them. Because of the scale of the project, these decisions affect hundreds of devs across dozens of teams with millions of euros swinging one way or the other. Apart from that, when divide and conquer is done properly, the work of each individual team isn’t too different compared to software development in commercial companies. Everything is a bit more relaxed, though. That can be a boon but can also be infuriating if you’re waiting for licenses, hardware, or some team to act.

We will see 😅

Oh, it can be rewritten and it should be. But it’s a very time consuming and expensive process. It may take a long time to amortize indirectly though a system that is more stable, easier to maintain, adapt to new laws, and requires less effort to use and operate. It’s not a quick win and not a win in the time frame of one administration - which is why it’s usually not considered a high priority.

I’m part of a project that does something extremely close to this in Germany. After two or three years we’ve barely scratched the surface. The complexity of such a system with the wide range of rules, regulations and best practices is mind bogging. Just reverse engineering the legacy system alone takes years.

Don’t shoot the messenger. The regulations are pretty draconic. I have to ensure the training for that every year.

Seemingly one of the contributors has visited a disputed region and logged into GitHub from there. By law (export controls) Microsoft must not provide service to that place. So some automatism flagged the account and also the organic maps repo. So far so normal. But either Microsoft dragged it’s feet in communicating and resolving the issue or the organic maps team was not doing their part in the process. Doesn’t matter, the outcome is still worth it.

That’s what containers are for. Fucking up the container won’t fuck up the host. That was the best decision in self hosting I’ve done. Even that one virtual machine feels weird and uncomfortably legacy now but it needs to interact with hardware in a certain way that just won’t fully work with docker.

Or with small children. 😅

My (self-hosted) cloud storage is larger than the disk drive on my laptop. On demand sync is important to me. I really, really hope Linux will catch up to Windows in that regard.

Currently we have an experimental VFS feature on all platforms that is using some suffix appended to files when they are virtual empty placeholders. https://github.com/nextcloud/desktop/issues/3668

Yeah, no thanks. It’s a very hacky work-around and breaks the moment you use an application that tries to access the files directly.

OS-level support for cloud storage. OneDrive, Dropbox and all the others work seamlessly on Windows through the Windows API. You can browse all the files on the file system and once you access them, the OS will call back the cloud provider to download them. It works through all applications, all cloud providers. I am aware that some tools on Linux have something similar to work around the issue in user land. Some solutions are less worse than others but none of them are as good as on Windows.

No, I said they hadn’t demonstrated it. But 95% is close enough, I stand corrected.

In that case I stand corrected on the whole orbit bit. Thanks for taking the time.

I didn’t say “a little” money. It may be important or critical for the business but from a technical perspective, demonstrating how it can safely bring loads up and down decides whether the whole concept is actually feasible. That’s when people will start to get excited.

As far as I understood it, SpaceX uses the word “orbit” liberally. If it reaches the hight where an orbit would be possible, that’s “being in orbit” for them. In an actual orbit, the rocket would not fall back down again in an hour or so without active breaking. If my understanding is incorrect, I’m happy to be corrected. And even of that was achieved soon, it’s still all without demonstrating that the starship could actually carry a load and return it safely. Not even an inexpensive dummy load. All SpaceX is showing in their live feeds are empty cargo holds that fill up with hot gases and fumes during reentry.

I think the average person gets it right. It’s a nice feat to catch the booster and it will save money. But that’s a side quest. The main quest of getting an actual load to orbit and beyond is still pretty far away. At least compared with the official time line where they wanted to achieve much more than that three years ago.

And whoever is way up his ass, is also a racist climate change denier. (Or has that changed in the last decade or so that I wouldn’t watch these shows?)

Termination without notice in Germany? That’s a major challenge even in situations that warrant it.

Ansible playbook is perfect for this. All your configuration is repeatable, whether on a running system or a new one. Plus you can start with a completely fresh newest version image and apply from there, instead of starting from a soon-to-be outdated custom image.

Cool, thanks