• 1 Post
  • 22 Comments
Joined 2 years ago
cake
Cake day: June 16th, 2023

help-circle

  • Yeah, I agree with you that, realistically speaking, Rust people would probably complain when C code brakes their code, but I still think that this was not what Hellwig was talking about.

    In my opinion, he was just being unreasonable when he told people that he would be doing everything he can to prevent anything else that’s not C code from being merged into the kernel.

    I mean, I understand his concerns of not wanting to deal with Rust code, but what he said is not contributing AT ALL to the discussion.

    btw, I’m not the one downvoting your comments. I disagree with you but I think you are making some valid points.



  • I think that Linus’ concerns about posting on social media is completely valid, but I was pretty disappointed that he didn’t address Hellwig going full retard. Marcan dealt with this like a spoiled child in the end, but he was 100% right.

    If you want to make Linux impossible to maintain due to a cross-language codebase, do that in your driver so that you have to do it instead of spreading this cancer to core subsystems. (where this cancer explicitly is a cross-language codebase and not Rust itself, just to escape the flameware brigade).

    This should be worth a Linus rant in my honest opinion.





  • I’ve tried a lot of different DAWs already, Cubase/Nuendo, ProTools, Logic, Reaper, FL Studio, Bitwig, Ableton, Studio One, just to name a few. I’ve worked professionally only with Cubase, Pro Tools and Logic. I hated every minute I used Logic. Cubase being the best for composing and Pro Tools for recording and mixing. Studio One is very mature right now and that’s what I’m testing, since they now have a Linux beta. I tried Ardour before and unfortunately it doesn’t come even close to being as good as a “real” professional DAW. Even Logic was more pleasant to use than Ardour. I really wanted to like it, but it was not a very pleasant experience.






  • I think people are missing the point here. The biggest problem was not that the update was bricking the machines, that could’ve happened to Linux/macOS/BSD etc. The problem is that the solution to the problem is to MANUALLY access the machine, get into safe mode and type some commands. This is insane. And you should be able to EASILY disable automatic updates for apps like that on Windows Server.









  • Yep, definitely something wrong with the webserver 😅 Can you try this configuration?

    https://nextcloud.domain.com {
            reverse_proxy 192.168.1.182:443 {
                    header_up Strict-Transport-Security "max-age=31536000; includeSubDomains; preload"
                    header_up X-Forwarded-Proto {scheme}
                    header_up X-Forwarded-For {remote}
                    header_up X-Real-IP {remote}
            }
    }
    

    You said that “originally, the Nextcloud server handled HTTPS with Let’s Encrypt at domain.com” and now you are redirecting to 192.168.1.182 on port 443. Is this Nextcloud server still serving HTTPS with Let’s Encrypt for domain.com?

    I’m asking because if you are using Caddy in front of that HTTPS webserver as a reverse-proxy, you will need to override the Host header with the configured upstream address. Here’s the documentation. I think it would be something like this (?):

    https://nextcloud.domain.com {
            reverse_proxy domain.com:443 {
                    header_up Host {upstream_hostport}
                    header_up Strict-Transport-Security "max-age=31536000; includeSubDomains; preload"
                    header_up X-Forwarded-Proto {scheme}
                    header_up X-Forwarded-For {remote}
                    header_up X-Real-IP {remote}
            }
    }