Eh, that’s just most large tech companies.

It deserves to be destroyed.

I know we all hate our jobs but there has to be a story behind this…

I’m the same way. Honestly I just like the built in terminal emulator for those few times I forget to open tmux first. Not a fan of the lua integration. Makes the initial startup slower for my config.

I use the linuxserver images for Nextcloud. Have worked pretty well for me over the past few years.

https://hub.docker.com/r/linuxserver/nextcloud

Or servo. Literally anything but chrome man.

Sorry, it was, just not for exploring all of those instances at once. Should have called out the tiling function. Screen also built in a serial terminal emulator and started playing with a few other things.

Executing a command, capturing all terminal formatting and escape codes so I can do some light manipulation on leading whitespace before dumping it back to the terminal.

Tmux was purpose built for terminal multiplexing. You can assign session names for organizing and manipulating multiple instances. Send keys to and read output from detached sessions. It’s easy to script.

People always sleep on script. It’s badass and let’s you do goofy things like this while keeping standard terminal formatting: https://github.com/StaticRocket/dotfiles/blob/043e9a56cc9515060188ec4642e4048c0dd6c000/dot_bashrc#L79-L94

I’d recommend tmux for that particular use. Screen has a lot of extras that are interesting but don’t really follow the GNU mentality of “do one thing and do it well.”

+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.

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:

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.

Eaton is your best bet for compatibility in the consumer market.

https://networkupstools.org/stable-hcl.html

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

https://man.archlinux.org/man/extra/xdotool/xdotool.1.en

https://man.archlinux.org/man/extra/wtype/wtype.1.en

Pipe your clipboard contents through either of those depending on your windowing system. I’d recommend putting that in a script and binding it to a keyboard shortcut.

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.