Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)ST
Posts
0
Comments
637
Joined
2 yr. ago

  • Not necessarily traffic. Often download sites use mirrors to serve you the download. Sometimes those links are provided via a CDN which can be forced to comply to LEA or some other static hosted mirrors which are often hosted by others. The second part is more likely on community managed software.

    So either traffic or the server/CDN behind the link. Happened before.

  • You have basically two options.

    1. Symmetric Encryption. That means you use the same password/key for writing the Backup and for reading the backup. Here you have to write the password somewhere, depending on the OS there are options like keychains or similar that can hold the password so that the password is only available once you are loged in or have unlocked the keychain.
    2. Asymmetric Encryption. That means you have different passwords/keys to read and write the backup. PGP is an example here. Here you can just simply use one key to write the backup, this key can become public and you do not have to worry about your backup since it will only be readable with the 2. key.

    I personally use Restic with a password that is only readable by the system root user stored on the filesystem. Since I use Full Disk Encryption i do not have to worry too much about when the secret is available in clear text at runtime.

  • Not really how patents work. It does not matter if the code is open or not, others are still not allowed to use patented code elsewhere or at least not commercially. (Not talking about the legitimacy of software patents)

  • OC stated those things 'should be worked on'. What else is it than blaming ppl?

    Yes things could be better, but saying things should be better while sitting on their ass and doing nothing is just not correct to say. If you say it should be better then you should take part in it getting better.

  • Yes thats why i said in theory. I doubt that many residential IPs are blacklisted, but still not optimal.

    IPv6 only works but there are probably many Mail Servers that are IPv4 only, so you will not receive mails from them.

    If you are serious about it, rent a VPS or get a static IP on your residential connection.

  • It would be more reliable to use a 'clean' not blacklisted static IP.

    But in theory you could just use ddns and update the IP. But I actually never tried it.

    Mailcow comes ready out of the box. Just change the DNS entries according to Mailcow and you are good to go.

  • This has been said over and over again. I have been hosting Mail now for over 2 years and have yet to encounter any problems. Although, i would not recommend to set it up manually and rather advise to use one of the 'all in one' suggested solutions here in the thread.

  • A project ending as abandonware is always a possibility. One reason projects get abandoned is losing funding, which can be secured by using dual licensing and selling some features to businesses.

    That is not my point.

    Having a CE or OS version and an Enterprise Version can lead to conflict of interest. Do you add a feature to the OS Version or do you spend time on the Enterprise feature? There are a lot of examples, Emby is one, others are escaping me right now.

    There are other models that work well like paid support etc. Nonetheless i will stay away.

  • I encountered it now multiple times that new TLD are discriminated against. They are more likely to get blocked. This applies not only to Mails also to any more controlled network like free wifi networks or business networks.

    Go with a classic .com .net .org or a country TLD if you can.

    Btw, also applies to registrations on online services.

  • I absolutely disagree with you. If a manufacturer does not care about Linux support, it's on the manufacturer. Do not blame the thousands of unpaid volunteers and a few paid ppl for not supporting a specific BT chip or controller or whatever.

    The signing issue is so on OP cause disabling secure boot or using a supported distro like ubuntu could have fixed that, and yes you can run Windows 11 with Linux dual boot without secure boot.

  • Basically everything you stated, Bluetooth, Controller and GPU is hardware.

    Your experience is probably different since you still think and act like you use windows. This is normal. When you are used to something and then switch to something that works differently you will run into problems.

  • Looks like you used hardware that was designed for windows and are blaming it now on Linux.

    I am not understanding the issue you have that requires signing of drivers.

    Yes some Bluetooth devices lack the support from the manufacturer's for Linux, the Controllers i have used work great, at least for my needs.

    Controllers have better support Linux for ages. Not understanding the issue here either.

    Troubleshooting on Windows sucks at least to the same degree. The same non specific error message gets you 50 possible solutions.

    No need to announce your departure.