• 0 Posts
  • 48 Comments
Joined 10 months ago
cake
Cake day: June 8th, 2025

help-circle



  • I think it comes from the fact that a lot of communities and projects use Discord basically like they would with IRC, with voice chats often not even existing in some servers. I have to assume the people who recommend Matrix are only ever in that kind of server.

    I’m in 2 or 3 servers with different friend groups and of course each one is full of friends of friends of friends. Even the smallest is over 30 people, but I only regularly join VC with 3-4. If I had to call all of them to be in a voice call I would literally never do it.

    Same goes for chats, in Matrix the closest things to channels and servers is rooms and spaces. The difference is that you don’t join a space, you just view rooms in the space and join them. Most of my servers have a ton of different channels for different things, I want to be able to see what happens in all of them without having to join each one, announcing to them that I’ve joined.

    I like Matrix for FOSS project discussions, but I don’t think it’ll ever be the right pick for just hanging out with friends.





  • priapus@piefed.socialtoLinux@lemmy.mlSystemd-sysext Help Needed
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    2 months ago

    I’m not super familiar with sysext, but from my understanding, you’d need to create an additional sysext to include, or find an existing one for DMS (I couldn’t find one).

    Your other options would be using rpmtree or a custom image. Theres already a few images out there that are based on Bluefin with Niri + DMS added.

    Tbh I’m recalling struggling to find good documentation for sysext. Asking in the ublue discord will probably get you better answers.


  • “read the changes before installing a major update”

    Obviously I dont think people need to read every change log for every piece of software. I do think its a good idea to read the release notes for a major update of your DE thought, since its the piece of software that is going to effect you the most.

    And once it is no longer on and has become a setting, they can just remove the setting and force people to drop gsettings and then remove it completely.

    What reason do they possibly have to do this? The setting already exists and is feature complete. It doesnt require maintenance. They also noted in the merge request that many RHEL users use it, so RedHat has a financial incentive not to remove it.

    They could also instead ask people on first launch. Some people enable telemetry, so they will find out how many people prefer to keep it, which I bet will be most.

    They could also just make it a setting. I really dont think it makes a big difference. They can also still use telemetry to see how many users enable it. Based on this thread, I really doubt it will be most.

    The first time startup wizard should be kept relatively short and minimal. This just seems like a very unnecessary thing to include.