Tori. Play music in your terminal. Built in rust and has great performance, and low trace on memory impact.

This is such a great way to look at the situation from a different angle. This is actually insightful.

So then we shall propose to let them in at our own terms ?

That’s quite reasonable to me, and less radical in my humble opinion.

But I also see how one may arrive at such a conclusion, as all parties may not be as welling to accept such terms and conditions, or even be able to make such terms and conditions enforceable.

One instance may accept favours from meta, and then it spreads out uncontrollably… And then … Its gets more complex.

Perhaps the safest option is to limit their present shares to a maximum of 40% in our servers. That is, they cannot be allowed to have more than a set amount of API exposure to the feeds - and they must allow us to reciprocate, like wise, by being able to have access to theirs by more than 40%. The value of assets can surely be established and estimated par costs of maintenance and OA, etc…

Absolutely!

I started with mint. Hated it.

Ubuntu, Pop_Os. Hated it.

Fedora. Hated it.

Archlinux, okay, but not so much.

Manjaroo, hated it.

And now I settled with Garuda and Nobara. Like them.

I used Nobara for niche gaming (rarely use it now).

And Garuda Linux for dev work, and downloading and installing stuff, including proprietary packages. And I don’t have to configure all the things to make it capable of allowing me to download stuff from all the nice mirrors, such as the community arch mirror.

Nobara, on the other hand, is great at handling compatibility issues kinda out of the box. Such [Edit1: as GPU] drivers.

The reason I disliked the aforementioned distros was solely because of how much involved I had to be to configure them to integrate with my rare WiFi chip drivers, which triggered me when I banged my head at the keyboard for hours only to find out that my WiFi driver was not supported.

But Garuda and Nobara or a blessing, and a chef’s kiss.

That’s coming from a person who tried more than 20+ distros and/or their derivatives.

[Edit2:] All in all, I would recommend what the comment above suggested, as that will help you find your own path. The samurai path, the kenjutsu path, or the kendo path, the peaceful path, or the hackers path. ;)

[Edit3: sorry Debian users, but I DID try your distros, I just didn’t want to bother with them much as they had compatibility issues too !]

There are teachings I have read/ discovered through YouTube (can’t remember exactly where) about the reasons and the philosophy behind moving to docker, or having it as a state machine.

Have you considered looking into dockers alternatives, also ?

Here is 1 of the sources that may give you insights:

https://www.cloudzero.com/blog/docker-alternatives/

– There has been some concerns over docker’s licensing and, as such, some people have started preferring solutions such as podman and containerd.

Both are good in terms of compatibility and usability, however I have not used them extensively.

Nonetheless, I am currently using docker for my own hyperserver [Edit2: oops, I meant hypervisor ✓, not hyperserver] purposes. And I am also a little concerned about the future of docker, and would consider changing sometime in the future.

[Edit1: I am using docker because it is easy to make custom machines, with all files configurations, and deploy them that way. It is a time saver. But performance wise, I would not recommend it for major machines that contain major machine processes and services. And that’s just the gist of it].