RedHat creates a product called RHEL (Red Hat Enterprise Linux) that is a paid support product, mostly targeted at businesses (and things like Academia/Laboratories/etc).
At one point, there was a Wholly seperate product, created outside the RedHat umbrella, called CentOS, that quite literally took the sources of RHEL, removed the RHEL branding, and rebuilt it, allowing folks to "mostly" be able to use RHEL, without paying RedHat for a support contract.
In 2014, the CentOS Project/Product was "purchased" by RedHat, and then in 2020, RedHat decided that CentOS would no longer just be a "rebuilt" RHEL, but instead would become the development space for RHEL, called CentOS Stream. This made many people very unhappy, and they decided to start the Rocky Linux and AlmaLinux projects to provide roughly the same product that prior versions of CentOS had provided.
Additionally (I don't actually know exactly when), at some point, Oracle started doing basically the same thing that CentOS had been doing, and rebuilding the RHEL sources, and selling it, as "Oracle Linux"
So net effect of what this means, is that RHEL sources will no longer be publicly available at git.centos.org, and will only be available to RedHat customers (i.e. you must have signed up for an account/license with RedHat for RHEL). This may make things more difficult for Rocky, Alma, and Oracle, to provide the same "Bug for Bug" compatible product to RHEL.
Most of what people are upset about, is because they're willfully misreading the GPL (GNU Public License) which covers an awful lot of the RHEL sources.
The GPL requires that if you distribute software, licensed under the GPL, that you also must provide the folks that you distribute that software to, with the sources you used. It doesn't specify how you have to provide them, you could make them available for download, you could mail folks a DVD with all the sources on it, (honestly, I think you might be able to just print them all out and send them on dead trees, and still be compliant).
What most of the folks are upset about, is there is a clause within the GPL, that says something about providing the sources "without restriction on redistribution" or some such. And they view that RedHat can choose to terminate your license to RHEL, if you redistribute RHEL sources/software as violating the GPL. But the GPL cannot dictate business relationships. Redhat cannot stop one of their customers from distributing sources that they are licensed to have. But they are well within their legal rights to terminate that license, and provide no further access, if you distribute them. (i.e. you have an RHEL license, and version 1.0 of a library is covered under that license, you redistribute that source, and RedHat must allow that, but they're under no obligation to continue that business relationship, and provide you continuing access to version 1.1)
That's a rough rundown on the history. What does this mean for the average linux user? Nothing, really. Unless you happen to use Rocky Linux, AlmaLinux, or Oracle Linux. It doesn't affect Debian, or Ubuntu, or openSUSE, or Arch, or anybody else. RedHat will continue to contribute back upstream to projects like the linux kernel, or GNOME, or what have you, they will continue to sponsor and hire developers, they just will no longer be providing free and open access to the RHEL Sources.
It's not a question of legality really, but more one of an ethical nature. It sort of depends on you, as to whether or not you're bothered by RedHat doing this or not.
This is a horrible idea. Don't do this. Let more servers get spun up in the kbin fediverse, or you're just going to be sending people to bad experiences, as the existing kbin instances are all basically overloaded at the moment. kbin has almost literally only been available to the public for a Month at this point, and the "ez hosting" for instances isn't established yet, and the "instructions" for rolling your own still have some quirks.
I've got no issue kicking Ernest a fiver (and in fact I did), but part of the issue is, we shouldn't be advocating for kbin.social or any of their other instances becoming the "Big Kahuna" That defeats half the purpose of being a federated protocol in the first place. Get a VPS of your own, spin up an instance, invite your friends and family, and spread the load. If you poke around, you can get a suitable VPS that can support a small number of users quite inexpensively.
I don't have mine up and running yet, but it's in the works, as soon as I muddle through how.
No. While SUSE the corporation supports, and does have some limited input into the community project, openSUSE Tumbleweed is fully community developed and controlled (I don't believe there is anybody on the SUSE payroll who's job description is working on openSUSE, the SUSE Employees contributions to openSUSE are at their own discretion and interest). openSUSE Leap is also a fully community supported and developed point release distribution, that is based on the SUSE Linux Enterprise sources.
openSUSE Tumbleweed -> SUSE Linux -> openSUSE Leap
I'd probably drop openSUSE Tumbleweed with LXQt on it. But that's my preference for low-spec machines. There's any number of distros with "lightweight" GUI's that you can use. XFCE/MATE/LXQt probably being the ones that will give you the least headaches.
Famke Janssen, if she's reprising her character from Goldeneye
Kate Beckinsdale, in her role as Selene from Underworld
Kathleen Turner, as Jessica Rabbit.
kbin, the software and kbin.social, the site are two different things. I can't speak for ernest, as I've never actually talked to the man, but I don't believe he ever intended kbin.social (or any other individual instance) to "replace" reddit.
anybody can theoretically create an instance for kbin, and federate to other kbin instances, or federate with lemmy, or mastodon, or anybody else they want to, it's how the fediverse works. It's not the "One site to rule them all" model. It's "We have a network of much smaller sites, that cooperate with each other"
If somebody wanted to take the kbin software, and toss cubic dollars at setting up a monster instance (site) that can handle millions and millions of users, and then monetize it through ad revenue, just like reddit, they certainly could (I think, I actually haven't looked to see the license that kbin is being offered under), but that's not how the fediverse is intended to work.
I suspect that kbin/lemmy/mastodon/pixelfed/peertube probably won't ever kill their respective "name brand" corporate counterparts. They probably won't ever be as big. But I'm ok with that.