Skip Navigation

Posts
0
Comments
288
Joined
3 yr. ago

  • +1 to caddy. There are some services that set safe headers following the recommendations outlined by Mozilla but others don't control headers as strictly. Caddy is the only web server that I found that supports loose default header values. These values will be selected unless the upstream application specifies their own values.

    You can do something similar in nginx but it requires playing with maps and has a little more indirection than I'd like.

    Just wish caddy was capable of starting as root and stepping down permissions like Nginx. I have certs being managed by other tools and have to make sure they are installed and chowned for caddy's use when they are cycled.

  • I assumed from the start that they were purposefully holding back promo codes, or scraping them from users and holding the affected sites ransom (in a sense). "We'll stop serving this cupon if you become a member." Scummy, but ultimately still slightly beneficial to the end user, a Robbin Hood crime. (Ignoring the people who work with genuinely good companies to get discount codes for things like student projects. Unrecognized casualties.)

    It's the affiliate link stealing that's become the source of outcry. That was more stealthy and essentially flipped the script. Now everyone publicly in support of it is being burned.

    If you were never involved in it, it really is just funny to see how quickly a corporate Robin Hood figure can flip sides. It's not like we haven't seen numerous examples before, some of them literally taking the namesake.

  • Rice is not a good idea. It barely wicks the water away and normally just adds other odd things that'll interact with the water and cause additional corrosion.

  • This isn't the new generation of devs. This is just new devs. Some people refuse to grow out of this stage.

  • Yeah, that thing is honestly impressive. If I didn't already have a full network manager wg setup I'd just use that.

  • Reformatting that compose for people:

     yaml
        
    version: "2.1"                                                services:
      wireguard:
        image: linuxserver/wireguard
        container_name: wireguard
        cap_add:
          - NET_ADMIN
          - SYS_MODULE
        environment:
          - PUID=1000
          - PGID=1000
          - TZ=Asia/Singapore
          - SERVERURL=auto #optional
          - SERVERPORT=51820 #optional
          - PEERS=1 #optional
          - PEERDNS=auto #optional
          - INTERNAL_SUBNET=10.13.13.0 #optional
        volumes:
          - ./config:/config
          - /lib/modules:/lib/modules
        ports:
          - 51820:51820/udp
        sysctls:
          - net.ipv4.ip_forward=1
          - net.ipv4.conf.all.src_valid_mark=1
        restart: unless-stopped
    
      

    Sounds like you didn't read the extended manual: https://github.com/linuxserver/docker-wireguard

    There are a lot of other configs for that container that must be provided before startup. It's just a generic runner. If you want it to run as a server you need to follow this section: https://github.com/linuxserver/docker-wireguard?tab=readme-ov-file#server-mode

    Are you at getting the handshake in the app? If so, you're probably just missing the dispatch commands for traffic masquerading.

  • GitHub - ad-on-is/stowman: stowman.sh lets you easily manage your dotfiles using git and GNU stow.

    Jump
  • Yeah, there are a lot of bells and whistles and a fundamental difference between the way they intend to manage dotfiles and the way stow does. Makes it difficult to get started.

    One thing that helped me when I was first getting into it: Chezmoi doesn't like compartmentalization like stow. It supports it, but it want's you to lean into the config langue a bit before you start doing that.

    If you do that you can get away with only touching the add, cd, and update commands.

  • GitHub - ad-on-is/stowman: stowman.sh lets you easily manage your dotfiles using git and GNU stow.

    Jump
  • I liked stow, and used it for quite some time. That being said, it has issues. Issues community members have attempted to solve. Issues the sole maintainer wasn't addressing for quite a few years.

    I use chezmoi now. I've still got mixed feelings, but the templating system is neat. Stow seems to have gotten out of it's slump while I was gone. That's good news! Anyone know if they addressed the tree specific folding/unfolding config feature? Not seeing anything in the docs...

  • Been replaying Watch_Dogs recently. Works surprisingly well. Probably going to play Gestalt next.

  • I like phoronix.com but don't bother reading the article comments.

  • What am I missing here?

    That shoddy code rots when you update the compiler. (And occasionally good code, depending on what rules the compiler wants to start enforcing)

    These types of changes are inevitable.

  • Well, that diagram brings up an interesting point. In fediverse if the host dies the federated content can still live on (theoretically, I haven't checked to see if they cull content from dead hosts) but ATProto would dictate that the host is missing and therefore all content associated with the host is now immediately 404.

    Edit: I stand corrected https://social.coop/@cwebber/113527531906508036

  • I could appreciate a client certification that is optional, like a list of approved clients on their website or something along those lines.

    It should not be enforced by killing the client. I like security, but I enjoy software freedom more.

  • Llvmpipe is enabled in mesa at compilation time and actually modifies the swrast_*.so the last time I checked. Not runtime configurable. Also, I know at one point it had issues running on 32 bit machines. Not sure if that's still the case.

  • Just add a new user

  • Not sure about the Eco tank line, but the smart tank line botched the IPP interface. Ink level reporting is always wrong and printer status is regularly wrong. Exposed settings are limited to push people to the app.

  • To be fair, C predates dependency hell. It was either there or it wasn't. C++ has less of an excuse, but it was just object oriented concepts taped to C so it's no surprise it was also missing dependency management.

    Now with cmake, gnu-make, meson, gradel, and the world of metabuild systems that wrap those, nothing will change. It it does, it might as well kick start world war 3.