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

help-circle

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


  • yarn@sopuli.xyztoFediverse@lemmy.worldChild Safety on Federated Social Media
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    11
    ·
    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.





  • Well, this is off topic, but c/all for all the popular instances are like 99% the same, save for the occasional obscure community in one of the instances that nobody else is subscribed to. You can confirm that yourself by opening up lemmy.world and sopuli.xyz in private tabs and selecting all with the same sort in both. But I should’ve also mentioned that I sort by the “top” sorts when I browse all. If you browse with hot or active, then it is a significantly different experience from the top sorts.

    But alright, I won’t pester you anymore. I apologize if I sounded angry too. I’ve been having issues with that recently that I’m trying to be more conscious of. I shouldn’t have even made my original comment in here, now that I’m thinking of it. That was kind of poor forum etiquette. It’s easy enough to just ignore the migration notices. So sorry about that haha. I wish you the best of luck with your communities, though.




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