This is spot on. I feel like it’s also important to not misunderstand meditation. Nobody is forcing you into a lotus position. Open the windows wide, get naked under 2 blankets, close your eyes as if you were going to sleep, listen to the wind, feel every single sensation on your body, try to focus on YOU and your body. You don’t have to try to force yourself to not think, just don’t try to solve problems. Try to let these thoughts go. This doesn’t mean the problem goes away, but this is not the time. Right now we let it go and try to think of how we’re actually on a beach and the wind rushing through the leaves of the trees outside is actually the sound of waves… Or, you know, whatever works for you to ground yourself and have absolutely pure “me time”.

If you’re asking yourself how that does anything, the idea is that it should help you to detach yourself from coping mechanisms and behavioral patterns that are motivated by external factors, instead of what you truly feel you need. You might start to really crave these relaxation sessions that you designed for yourself. When you are in deep relaxation, you will easily be able to divide the thoughts that are forced onto you from those truly driven by your own internal desire for the happiness that exclusively you imagine to be right, just like the relaxation environment itself.

Absolutely spot on. If you’ve already delayed a lot, then reduce the pressure on yourself. You already made a huge leap by even accepting that you might need additional support. You don’t have to force yourself to now make up for potentially lost time or anything. Take your time to progress at your own pace. If you feel like you’re pressuring yourself towards a potential goal, you might set yourself up for failure. Be kind to yourself and don’t demand too much.

When you hear people talking openly about emotional challenging situations in their daily life, which you can relate to, but most people in your regular surroundings can not, that can be extremely emotionally relieving to a degree that is impossible to anticipate. It’s really worth it. But you want to feel comfortable on your way there. Slow pace is fine as long as you are moving towards your own goals.

Maybe it can also help you if you think differently about your goals. It’s not like a sprint in sports. Even if you might think you have to reach certain goals to function in society, and reaching them faster would obviously be better. This is not a competition. You set your own goals for yourself and nobody else sets the rules on how to get there. Your goals are more like a beacon. Even if there are strong headwinds every once in a while, or you take a break and just relax in the sun, you can still clearly see them and continue to steer in their direction, as long as you consider it to be right. You are in control

Maybe I’m just old, but I thought a distribution is literally just a package delivery basically, just like you speculated. Making software work together nicely is actually already hard enough IMO. I don’t think anything is wrong. Valid question though

Lower the barrier. Ask if you can join briefly with a video call to get to know the group. Some people will delay reaching out for decades, making their life harder. You can bet that people in the group will even share exactly this feeling and situation with you. If you really believe it might help to reach out, but you’re standing in your way, try a smaller step in the direction

How do you sell what you did as “it just worked”? Rightaway? You lied to them. You have your coworkers on an unmanaged machine with a foreign OS on the guest WiFi with custom networking. Don’t oversell a workaround as a solution.

Simplifying the problem to “Windows” seems unfair, given how many problems you found. All of them still require a long-term solution for regular operation.

Especially after the GOP literally pulled her into the spotlight over the subject https://newrepublic.com/post/177990/fox-news-conspiracy-theory-taylor-swift-psyop

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

Buy a gun

Sharing the network space with another container is the way to go IMHO. I use podman and just run the main application in one container, and then another VPN-enabling container in the same pod, which is essentially what you’re achieving with with the network_mode: container:foo directive.

Ideally, exposing ports on the host node is not part of your design, so don’t have any --port directives at all. Your host should allow routing to the hosted containers and, thus, their exposed ports. If you run your workloads in a dedicated network, like 10.0.1.0/24, then those addresses assigned to your containers need to be addressable. Then you just reach all of their exposed ports directly. Ultimately, you then want to control port exposure through services like firewalld, but that can usually be delayed. Just remember that port forwarding is not a security mechanism, it’s a convenience mechanism.

If you want DLNA, forget about running that workload in a “proper” container. For DLNA, you need the ability to open random UDP ports for communication with consuming devices on the LAN. This will always require host networking.

Your DLNA-enabled workloads, like Plex, or Jellyfin, need a host networking container. Your services that require internet privacy, like qBittorrent, need their own, dedicated pod, on a dedicated network, with another container that controls their networking plane to redirect communication to the VPN. Ideally, all your manual configuration then ends up with a directive in the Wireguard config like:

PostUp = ip route add 192.168.1.0/24 via 192.168.19.1 dev eth0

Wireguard will likely, by default, route all traffic through the wg0 device. You just then tell it that the LAN CIDR is reachable through eth0 directly. This enables your communication path to the VPN-secured container after the VPN is up.