The official rule is that you are offside if you are closer to the goal line than both the ball and second-to-last defender when the ball is passed by your own team. It is only a violation if you then make a play toward the ball after being offside. If the other team makes an intentional play on the ball before you do, then you are no longer offside.

Anyway, this is not practically readable and takes much longer to compose.

(I spent way too long trying to read this, and ended up cheating on the last word.)

This feels like you should still be able to require them to replace or fix it. It would be like them coming into your home, accidentally stepping on it and then saying, “oops, too bad it’s out of warranty.” It’s too bad that small claims is probably more expensive than just paying to replace it.

It doesn’t mention you can take stuff with you. You might end up in Tirana Terminator-style.

When running as root, I did not need to add the firewall rule.

I haven’t tried rootful since I haven’t had issues with rootless. I’ll have to check on that and get back to you.

Philosophically I agree with you. I was just discussing a technological way to accomplish age verification without giving up users’ identities to a service provider, or the government knowing what service you’re using. Unfortunately, too many governments want to know what you’re doing inside your pants.

Oh, I was thinking the certificate would only be needed for signups - once the account is created, it absolutely should be on the account holder, not the service provider.

The service provider could even generate a certificate request that the age verification entity signs (again, with no identifying information, other than “I need an age verification signature, please”). That certificate would only be valid for that specific service provider and can’t be re-used.

I still need to allow the ports in my firewall when using podman, even when I bind to 0.0.0.0.

I had this exact issue with both my desktop and server. Anytime I put any sort of load on the outbound connection, the wifi would cut out. After switching to the iwd backend, I haven’t had any issues.

You could try switching your wifi backend to iwd instead of wpa_supplicant.

If you’re using NetworkManager, then create the file /etc/NetworkManager/conf.d/wifi_backend.conf, and add the following configuration:

[device]
wifi.backend=iwd

I think he meant that party leadership hasn’t learned their lesson.

I think I’m a—LLM now.

I prefer the way Slack groups threaded conversations within a channel. Teams channels are clunky enough that we just end up using group chats instead.

They could use loginctl enable-persist if they want a user service to run at boot. I use it for my home nas server, just to make it slightly easier to manage my non-root services.

VPN software can easily configure your DNS settings without doing MitM trickery on websites’ certificates.

This just looks like a standard orthographic projection with Canada near the center.

Close, Coordinated Universal Time. And for those wondering: Why is UTC used instead of CUT?

It was a reference to a Reddit post.