• 1 Post
  • 10 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle

  • Efwis@lemmy.ziptoAsk Lemmy@lemmy.world*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    5
    ·
    5 months ago

    Unionize. Have companies pay you fairly for what you do.

    The problem with that here I. The states are two fold. First of all if the companies could, at least here in the states, they wouldn’t allow unionization. They don’t want to pay fairly for what you do. All these companies want to do is make as much money as possible, while paying the workers as little as possible.

    Most of the companies here would like us to work until we die on the lines, but pay us nothing to do the work so they could make it all. Companies don’t give a damn about workers rights, or being fair to us. A lot of non-union shops will fire you for trying to bring a union in. They would be extremely happy if the labor boards, OSHA etc would cease to exist.




  • It’s a KWin scrip called Autocompose. Does endeavour ship it by default?

    Endeavour installs a mostly default DE when you make your choice of which one to use, so most of the DE’s come as packaged by the devs. If I’m not mistaken Autocompose is a default script included with KDE.

    I say mostly, because some parts of the DE you use is incompatible with the Arch ecosystem and disabled by default. For example, Discover on KDE is pretty much unusable on arch/EndeavourOS because the repos aren’t adequately designed for such a setup.


  • So do snaps and flatpacks. And they are still consider containerized / sandboxed. Appimages are the predecessors to snap and flatpack. The only difference is unlike Appimages they got it right for the most part.

    Generally speaking the Appimages integrate with KDE better than all the other DE’s. The codes for Appimages are still containerized from the OS in general as defined in my last post.



  • The thing about snaps and app image is they are containerized. The idea behind that is to help keep the apps separate from the main file subsystem by sandboxing them from each other as well as not cluttering your hdd with different versions of the same libraries to make them work.

    Because of the sandboxing, once you close the app it stops running in the background therefore there is nothing to get notifications from.

    IMHO, this is why snap and app image programs are not advisable for programs you may need notifications from on a, generally, required/needed basis.

    As for superconductivity, the only way around that problem is to download from source, compile it and let it run natively on your system in the background, or add it to you auto startup list so it is running at boot time.