Fruit of the Loom is cheap. They have all the advanced underwear technology too. These are what I’m wearing now. They’re that spandex crap or whatever that are tight against your leg so they don’t clump up, they don’t absorb a lot of moisture, and have thinly woven spots to increase ventilation. What else do you need in an underwear? Every other brand’s version of that is like $20+ more expensive for no reason.

I spent 95% of my time shitposting on one forum in the early 2000’s. It was a similar experience to spending 95% of my time on reddit or one of the other major social media sites, except that crazy new ideas for social media didn’t really exist back then. They were all traditional forums where everything is posted in chronological order. I remember occasionally sumbling across a threaded forum back then, where you could reply directly to a comment and start a new thread chain like lemmy and reddit can. That was about it as far as innovation went, or at least from what I remember.

The other 5% where I was browsing those old web 1.0 sites with basic html and flash and all that stuff, I don’t miss that stuff too much. It would be nice to browse through an archive of stuff like that once or twice for nostalgia’s sake, but the modern internet is good too. I have no qualms with the modern internet.

The suggestions in their direction for future improvement section should be implemented sooner rather than later. There’s no point in growing this platform if it’s going to be left wide open for abuse like it is.

I also think, in lieu of lemmy devs making any improvements, another good solution would be for a third party to prop something up that scrapes every lemmy post and runs it through an automated service for detecting known CSAM. The third party service would be forcing at least one of those future improvements on lemmy, as it exists today. Any known CSAM that’s found would be automatically reported, and if the instance owners can’t deal with it, then they would rightfully have to deal with the consequences of their inactions.

Edit: I’m beginning to think reddit was maybe not so bad. Getting mad about more robust tools for moderating CSAM is just sad.

Those soldiers have a tough road ahead of them. The ISW map for the area around Robotyne is a little more detailed than their other maps in that it shows Russian fortifications, and the Russians have that area fortified to hell and back:

Of course those are Russian fortifications, so there’s no telling how shitty they are. But I hope those Ukrainian soldiers are getting good weapons for that offensive.

https://lemmynsfw.com/comment/682757

There’s them discussing removing the term in a mod post in that community. It was added after the latest way back machine archive.

Until whenever it was when Ada complained

Edit: Proof: https://lemmynsfw.com/comment/682757

They changed it after Ada complained about the community

Edit: Proof: https://lemmynsfw.com/comment/682757

You guys… the lemmynsfw community had the term “child-like” in its sidebar. Why is everybody conveniently forgetting that? Don’t even try saying that’s not a disgusting request to have in a sidebar too.

The community sidebar used the term “child-like.” That’s pretty disgusting and really disingenuous of the lemmynsfw admins to quietly change that and then pretend like nothing happened. Plus, redditors have already gone through all this with r/jailbait, so it’s not really silly to anybody who remembers that debacle.

Yeah, the repost bots just don’t work. Reading the comments is half the fun of using reddit/lemmy, but lemmy has a very small userbase still, so the comments are a little bit slow moving. Having a ton of reposts suddenly spammed in splits that small comment activity up to the point where comments basically don’t exist and you’re viewing a slideshow of empty threads.

I don’t know what to tell you. This change was more appropriate for Fedora and developers are bad at PR is basically the simplest way to put it.

They do have a robust testing process, but their main focus at the CentOS Stream stage is more about preparing for the stable RHEL build than it is about adding a ton of new features and bug fixes. Testing takes time so it would be physically impossible for them to test everything if they didn’t have a limit on the type of contributions they accept. For bug fixes, their limit is that the bug has to be critical. For bugs lesser than that, the correct place to contribute those fixes is in Fedora.

That has been adequately explained in the merge request at this point, if you click in that link at the top of this thread amd read through it to get the latest info. The Red Hat devs have also made no indication that they’re not welcome to contributors. Anyone who’s saying that is blowing this merge request issue out of proportion.

I’m getting downvoted because I’m not conceding that the miscommunication was a legitimate excuse for that blowup. And I’m going to continue to not concede that. I found this whole situation to be embarrassing, and I think instead of getting mad at the miscommunication, you should all be getting mad at the moron who took that screenshot and whipped up the mob frenzy to swarm that merge request, because ultimately Red Hat was 100% justified in not accepting that merge request, and it made you all look like morons.

It’s fine to get mad on social media, but if you’re contributing to GitLab or someplace else, then you need to slow your roll. There’s always a process involved when contributing to a project, and you have to learn that process in order to contribute effectively. You can’t blow up and whip up a social media frenzy at the slightest inconvenience.

Edit: Sorry, @angrymouse@lemmy.world. I should also add that I’m not mad at you personally or anything, or calling you a moron. I’m more talking about the collective response to this situation. And I’m pretty bad at words, so I feel like I accidentally made it too angry.

I’m still getting downvoted, so I’m just going to put this here and be done with this:

RTFM about DevOps

I’m getting downvoted on my comment about not making a comment on CentOS, so now I feel obligated to reply to this.

I don’t know, dude. I don’t really care about the miscommunication. I was just focusing solely on the merits of the merge request’s code changes.

For the miscommunication, it seems like a two way street to me. That was GitLab, so the Red Hat dev was probably operating under the assumption that people there already understood everything about their testing process. But obviously that’s not the case, so Red Hat should create better boilerplate responses for these scenarios. But on the other side of the coin, whoever took this screenshot and posted it to reddit or wherever did so prematurely, imo. They should’ve asked around a bit to make sure it was a legitimate thing to blow up about before they sent a lynch mob to the merge request.

CentOS Stream is the staging ground for RHEL. It isn’t a bleeding edge distro that can accept any merge request willy-nilly. For the reason why, reread my original comment about the nature of enterprise support.

Fedora is the distro that is more bleeding edge in the RHEL realm. This merge request was more suited for Fedora, and the fix was successfully applied to Fedora. So, I fail to see any irrational actions from Red Hat here.

I’m making no comment on CentOS being absorbed and repurposed by Red Hat. I’m just saying it makes sense why Red Hat would rather have this fix in Fedora than CentOS Stream.

CentOS Stream is midstream of RHEL and Fedora. That sounds like it’s like a cert type of environment for RHEL. The same logic would apply there. You don’t want to be introducing a bunch of new changes to code once it’s in the cert environment unless they’re critical.

I haven’t been really keeping up with this RHEL drama, so I’m probably going to regret making this comment. But about this bug merge request in particular, you have to remember that RHEL’s main target audience is paying enterprise customers. It’s the “E” right there in RHEL. So stability is a high priority for their developers, since if they accidentally introduce a bug to their code, then they’ll have a lot of unhappy paying customers.

The next comment that was cropped out of that screenshot basically explains exactly that. While the Red Hat developers probably appreciate the bug fix, the reality is that the bug was listed as non-critical, and the Red Hat teams didn’t have the capacity to adequately regression test and QA the merge request. But the patch was successfully merged into Fedora, so it will eventually end up in RHEL through that path, which is exactly what the Fedora path is for.

The blowup about this particulat bug doesn’t seem justified to me. Red Hat obviously can’t fix and regression test every single bug that’s listed in their bug tracker. So why arbitrarily focus on this one medium priority bug? if it were listed as a critical bug, then yes, the blowup would be justified.

What is this referring to?