Thanks. Very interesting. I’m not sure I see such a stark contrast pre/post 9-11. However, the idea that the US public’s approach to the post-9-11 conflict would have an influence makes sense and isn’t something I’d ever have considered on my own.

Me too, but I’d put Usenet in there before Slashdot.

The South. Just below Indiana, the middle finger of the South. And I say this as a Hoosier for much of my life.

As a guy responsible for a 1,000 employee O365 tenant, I’ve been watching this with concern.

I don’t think I’m a target of state actors. I also don’t have any E5 licenses.

I’m disturbed at the opaqueness of MS’ response. From what they have explained, it sounds like the bad actors could self-sign a valid token to access cloud resources. That’s obviously a huge concern. It also sounds like the bad actors only accessed Exchange Online resources. My understanding is they could have done more, if they had a valid token. I feel like the fact that they didn’t means something’s not yet public.

I’m very disturbed by the fact that it sounds like I’d have no way to know this sort of breach was even occurring.

Compared to decades ago, I have a generally positive view of MS and security. It bothers me that this breach was a month in before the US government notified MS of it. It also bothers me that MS hasn’t been terribly forthcoming about what happened. Likely, there’s no need to mention I’m bothered that I’m so deep into the O365 environment that I can’t pull out.

Does the GPL cover having to give redistribution rights to the exact same code used to replicate a certain build of a product?

It does, and very explicitly and intentionally. What it doesn’t say is that you have to make that source code available publically, just that you have to make it available to those you give or sell the binary to.

What Red Hat is doing is saying you have the full right to the code, and you have the right to redistribute the code. However, if you exercise that right, we’ll pull your license to our binaries and you lose access to code fixes.

That’s probably legal under the GPL, though smarter people than me are arguing it isn’t. However, if those writing GPLv2 had thought of this type of attack at the time, I suspect it wouldn’t be legal under the GPL.

Yeah, runaway global warming might not happen. Plant monocultures would begin to disappear. New invasive species wouldn’t happen, though existing ones might have a better time for a bit. Major thoroughfares wouldn’t create barriers to migration. Dams might take centuries to collapse, but I think humans going extinct might have one of the biggest impacts.

I believe you are correct. Any paying Red Hat customer consuming GPL code has the right to redistribute that code. What Red Hat seems to be suggesting is that if you exercise that right, they’ll cut you as a customer, and thus you no longer have access to bug fixes going forward.

I suspect it’s legal under the GPL. I’m certain it violates the spirit of the GPL.

Upvotes and downvotes.

Right now, I can browse by New on my subscribed communities and see every post since the last time I did that.

I can view or re-view posts and read every response. If the responses are legion, I can play with hot/top and get the meat of the discussion.

Did you notice that last sentence? On the few posts where there are too many responses to view all, I’ll try to get at those that are relevant.

If the Lemmy community grows large enough, I’ll need to do the same for posts. I will no longer be able to regularly view by new and have time to see everything.

So, I’ll need to rely on some sorting method to make certain I see relevant stuff.

Someone with millions of bots that never post have millions of upvotes and downvotes to influence the score used by the sorting algorithm that I’ll use to decide what to read.

But aren’t thumbnails local?

Part of what prompted my question is that I doubt I have the correct worldview because I believe I’m influenced.

That’s a Red Hat employee that has nothing to do with code. The comments about emabargoed stuff appearing in Red Hat before CentOS Stream are for coordinated code releases to fix a bug that’s not been released yet. (e.g. there’s a remote code exploit in the network stack related to intel NICs. Intel will coordinate with people like Red Hat and MS to get the release out in a coordinated fashion, but the data Intel supplies is embargoed until the coordinated release.)

Rocky reports their release cycles are all tied to automation of the git repos that are going away. https://forums.rockylinux.org/t/has-red-hat-just-killed-rocky-linux/10378

So, while in theory someone who has a license can use source RPM’s to get at code, Rocky, and likely Alma, aren’t set up to deal with that as upstream sources. Plus, even though that matches the GPL (if someone sells you code, they have to supply source without restitrictions), I’d imagine the GPL doesn’t say that if someone sells a GPL’d product, they have to sell to you.

My guess is Alma and Rocky will figure a way around this, but id also guess it’s going to be tough.

No. They can be used in influence campaigns. They can upvote the posts and comments the controllers want you to see and downvote those they don’t.

Spam’s obvious and can be dealt with. Bots altering what shows up in your feed is impossible to combat as an end user.

In some ways, this shows Lemmy is winning. It means Lemmy’s important enough to start trying to influence. It also means we’re about to go through some interesting times.

It’s ironic that the link on the GitHub to point out the owner of bash-hackers.org goes to a Reddit post that is currently unavailable, presumably because of a subreddit shutdown.

Hardly surprising. Any popular app is going to have enough users that it doesn’t make economic sense to stay. A niche app that’s halfway decent will soon have enough users they’ll need to fold to.

Thanks. Based on some of the other answers, particularly in https://sh.itjust.works/comment/12511, I know understand better.

I appreciate everyone helping to explain some pretty basic questions in such detail.