• 1 Post
  • 23 Comments
Joined 1 year ago
cake
Cake day: March 10th, 2024

help-circle


  • If it works for you, there is no reason to switch.

    The benefit for me is mostly the systemd integration (e.g. do a simple DB backup before running the container using StartExecPre) & the corresponding unified logging with journalctl. Then there is auto update and boot persistence without having to run an additional process.






  • but then you’d still have to have your mobile mail client go and download all this mail you said is a battery drain, so you’re sort of negating yourself.

    That is precisely my point. I do not want a mobile or desktop client anymore. Just a client which is running on a system which is always running anyway to send me a notification and I can then decide if I will check it out now or if it can wait.

    Proprietary mobile clients often work similarly, they do the “heavy lifting” on the server side, send a notification, but only temporarily load the mails you explicitly view temporarily on the device. And thus, they use less battery and storage of the device. Another benefit for the unified client would be faster sync of mail status (e.g. read/unread) as it is only one client on the IMAP server instead of one on each device. And another benefit would be not having to migrate email clients when replacing devices.











  • First: IANAL, EU law is complicated. This is my understanding as of now:

    TL;DR: The EU Cyber Resilience Act (CRA) aims to enhance cybersecurity standards for products with digital elements. It introduces mandatory requirements for manufacturers and retailers to ensure cybersecurity throughout a product’s lifecycle. The CRA excludes open-source software developers unless their software is used commercially as part of a “product with digital elements”.

    would lemmy be regulated by CRA?

    Lemmy, as an open-source project, would likely not be directly regulated by the CRA. The Act specifically excludes open-source developers from its scope unless their software is used commercially.

    Whaz about lemmy instances?

    Lemmy instances might be regulated by the CRA if they are operated commercially as part of a “product with digital Elements”. (Is there a pay for access instance or hosting as a service for lemmy? I am not aware of one.) However, since most instances are run non-commercially or for personal use, they would likely fall outside the CRA’s scope.

    Is there a difference if there is a fee or a recurrent donations?

    Yes:

    • A fee is typically a mandatory payment for a service or product, e.g. a feature locked behind a paywall.
    • A recurring donation is a voluntary, regular contribution to support an organization or cause, often without receiving goods or services in return.

    The key distinction lies in the obligation attached to the payment. Fees come with an expectation of receiving something in return, while donations are given freely without such expectations.




    • monitors CPU, memory and disk space
    • can accept multiple hosts to watch
    • has some sort of alerting system
    • can be deployed as a single docker container
    • can be configured using a text file
    • configs can be imported and exported inside the docker compose file

    https://github.com/henrygd/beszel

    There is no really config to speak of. You setup the hub. Then you click on add system and write in the IP. Then you click on “Copy compose”. That is the agent you can then deploy with a compose file on any system. Click on add and it is there.

    The only thing you might want to configure is alerting, but only once on the hub.