• 0 Posts
  • 59 Comments
Joined 1 year ago
cake
Cake day: June 29th, 2023

help-circle

  • gencha@lemm.eetoSelfhosted@lemmy.worldPaid SSL vs Letsencrypt
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    15
    ·
    21 hours ago

    People who have actually relevant use cases with the need for a reliable partner would never use LE. It’s a gimmick for hobbyists and people who suck at their job.

    If you have never revoked a certificate, you don’t really know what you’re doing. If you have never run into rate-limiting issues with LE that block a rollout, you don’t know what you’re doing.

    LE works until it doesn’t, and then it’s like every other free service on the internet: no guarantees If your setup relies on the goodwill of a single entity handing out shit for free, it’s not a robust setup. If you rely on that entity to keep an OCSP responder alive for free so all your consumers can verify the validity of your certificate, that’s not great. And people do this to save their company $1 a month for the real thing? Even running the shitty certbot in compute has a larger cost. People are so blindly in love with this “free” garbage. The fanboys will never die off



  • https://discord.com/terms#5 is pretty permissive

    Your content is yours, but you give us a license to it when you use Discord. Your content may be protected by certain intellectual property rights. We don’t own those. But by using our services, you grant us a license—which is a form of permission—to do the following with your content, in accordance with applicable legal requirements, in connection with operating, developing, and improving our services:

    Use, copy, store, distribute, and communicate your content in manners consistent with your use of the services. (For example, so we can store and display your content.)
    Publish, publicly perform, or publicly display your content if you’ve chosen to make it visible to others. (For example, so we can display your messages if you post them in certain servers or recommend that content to others.)
    Monitor, modify, translate, and reformat your content. (For example, so we can resize an image you post to fit on a mobile device.)
    Sublicense your content, to allow our services to work as intended. (For example, so we can store your content with our cloud service providers.)
    



  • He’s lying. 42 is a secret code that refers to letters of the alphabet. It’s the fourth and second letter: DB

    DB is a hidden operation in Germany. It’s a large secret society that moves huge metal objects of unknown purpose through the country. Some people have created schedules that indicate where in the country the vessels are expected to be seen - but when you arrive on site, nothing ever happens.

    At this point nobody is sure what goal DB is after, but many people assume it’s to confuse and frustrate Germans to death.

    I’m not making this up. DB is on Wikipedia.






  • Numbers give the wrong impression that one version follows another. Debian release channels exit alongside each other individually. Giving the release channels names helps to make that distinction. It also makes for an easy layout of packages in APT repositories.

    Sid is and always has been Sid. If you were to assign numbers, what number should replace that name? There are perfectly working labels for release channels and there is no reasonable replacement.


  • I feel like most people base their decision on license purely on anecdotes of a handful of cases where the outcome was not how they would have wanted it. Yet, most people will never be in that spot, because they don’t have anything that anyone would want to consume.

    If I had produced something of value I want to protect, I wouldn’t make it open in the first place. Every piece of your code will be used to feed LLMs, regardless of your license.

    It is perfectly fine to slap MIT on your JavaScript widget and let some junior in some shop use it to get their project done. Makes people’s life easier, and you don’t want to sue anyone anyway in case of license violations.

    If you’re building a kernel module for a TCP reimplementation which dramatically outperforms the current implementation, yeah, probably a different story


  • GitHub is a place you can use to easily put a copy of your code online. Many people just want to build a working solution and move on. Building a useful GitHub project, with fancy stuff like releases, is work that isn’t really solving any issues. Many people don’t like doing it. Many people especially don’t want to invest time in proprietary solutions like GitHub. They might not even accept pull requests on GitHub.

    Quality assessment though 😄




  • That makes sense, but my understanding is, what Google considers Family content is not an add-on to regular content. Your content is not also for children, it is catered towards them. This implies using dedicated Google functionality, special SDKs, and so on, to comply with law. So your product needs to be designed in a very specific way to be eligible. I’m not aware of how Google Play restricts children from installing certain apps, but you can always install an app through a parental supervisor account.

    To me, this story seems like a lot of crying over a situation that is not fully explained.


  • I remember this mindset in myself. Today I consider it a waste of time.

    If you rely on any tool for this, the tool will make mistakes you cannot accept. If you do it manually, you will make mistakes as well and that also does not work. Also, the information your consider worthy for removal might be key to understanding the problem.

    Like, you remove your name, but a certain character in your name is what is actually tripping up the program.

    Ultimately, don’t post your logs publicly. In the past years, I was always able to email logs to devs. I have no reason not to trust them with my log. If they want data from me, they could easily exfiltrate it through their actual application.



  • If you are already familiar with one package manager, pick a distro that also uses that package manager.

    When deciding on the release track, the harder it is to recover the system, the more stable the track should be. Stable does not imply secure.

    As you move up through virtualization layers, the less stable the track needs to be, allowing access to more recent features.

    Steer clear of distros that pride themselves on using musl. It’s historically slow and incomplete. Don’t buy into the marketing.

    Think about IaC. Remote management is a lot more comfortable if you can consider your server ephemeral. You’ll appreciate the work on the day you need to upgrade to a new major release of the distro.