• 3 Posts
  • 32 Comments
Joined 1 year ago
cake
Cake day: July 6th, 2023

help-circle

  • yarn@sopuli.xyztoFediverse@lemmy.worldChild Safety on Federated Social Media
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    9
    ·
    edit-2
    1 year ago

    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.




  • Haha yeah, the canned fruit is loaded with sugar from that extra syrup they add. I’ve been rationalizing it as at least I’m not drinking soda anymore, but I need to fix that too.

    This is great info, though. Dried fruit is a good idea about ditching that sugary syrup. Plus, it’s easier than canned fruit anyway. I have been avoiding the premixed canned stuff and I do eat a lot of nuts and seeds, but I don’t do any dried vegetables. I’ll start looking into trying those. They do sound like they’d be a good way to get more variety.






  • Yeah, that’s the type of thing I was wondering about. Some weird chemical type thing or something that does damage over time. I haven’t been worrying about it too much, but figured I should probably at least check before I knock too many canned meals back.

    And yeah, this is metal cans I’m talking about.

    For the microplastics, I guess I’m not too concerned with this if I can’t avoid them anyway.




  • 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 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.




  • 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.




  • Yes, it’s a safe bet that it’s just my current job. I was a lot happier at a previous job with a government contractor that was very low stress. I’m going to start applying for new dev jobs.

    I’ll most likely stay in the dev field because it’s the path of least resistance for me, and because the job security most definitely shields me from a lot of new stressors I’m probably not even aware of. But I still wonder sometimes what it would be like to have a job outside like that one guy who said he became a wildlife ranger. Or to have a job where you solve physical problems with your hands, instead of abstract problems with your brain.