Most addictive would be DoTA. You can probably find 10 million player with atleast 5k hours

I mean he did get 5-10x better reaction from antibodies against covid. Imagine if we could design a course for our immune system to fight every known virus.

Our immune system decays and dies as we age. Maybe keeping it busy can keep it alive a bit longer like exercising a muscle.

Wow. This opens up a possibility that we can keep exercising our immune system and study the long term effects of that. What if there was a weekly schedule of all diseases to practice immune response against!

What usually happens is that you're top 1% in certain skill. There are still other skills where you're not top 1%. Most people always keep learning from other people. A top 1% mathematician may not be top 1% anxiety manager.

I'm curious you'd see it in ls -l Did inode change? I remember making the same mistake. I think everyone sees this sometime during the career

I think that's just because Hindus have been poor in history. Give them power and they'll show they're just a cosmetic difference away from Islam. You remember the murder on live TV? Do you know what the murderers chanted after shooting? Jai Shree Ram is just the new Allah Akbar.

Since I'm already a NixOS user, I thought to check out Series 4. One of the steps was "install flatpak"

My disappointment is immeasurable and my day is ruined.

Unfortunately India will also peak it's population around 2040. My city already has a fertility rate of 1.4 I wish world was comfortable enough for people to be okay having kids

Is it possible to connect docker / podman directly to the router? I'm operating an L2 bridge https://developers.redhat.com/articles/2022/04/06/introduction-linux-bridging-commands-and-features systemd-nspawn containers can connect to my router directly, but how to do it with docker / podman?

Not sure, but I think that designing an internet measurement in a RIPE Atlas network might just fit this task? https://atlas.ripe.net/probes/ You have micro cuts, but are those only to the big name websites or to something local as well? Might help answer that, and give ISP data on where exactly are they hitting the bottleneck and what are they missing monitoring.

How do you organize your notes? I have text files in a folder and was looking for something better.

This worked. Now I can have unlimited lightweight systemd containers, each with it's own globally routable public ipv6 address :)

I hope some GPU manufacturer starts allowing removable RAMs. 4 x 8 GB DDR5 might not be too bad given PCIe speeds aren't a bottleneck. If I could upgrade the RAM to 64 GB later, I'm ready to give $10k at 3080 level perf. Intel ARC people I hope you are already doing this!

Can you go IPv6 only with dynamic dns + recycling ip every day? My raspberry pi doesn't get bot traffic. I have 22, 80, 443 and a few other ports open on public ipv6 address.

• Can give NixOS a try if you want to make things extra hard and get more satisfaction from finishing. The biggest advantage is most of your OS & services config will be in a file, so there's no need to remember a thousand knobs to tune the experience just the way you want - a text file in a git repo will be all your config.
• I'd recommend Namecheap over porkbun. I found porkbun has less features. I specifically needed to wildcard forward email, which works well on namecheap.
• If you're from Africa, India or some other country where $10 / year is a lot I recommend a 111 class B domain https://gen.xyz/1111b for $1 / year.
• Do you have static IPv4 or globally routable public IPv6 address assigned to your device? I'm ipv6 only selfhoster, and I use inadyn and afraid
• Can use wireguard and then later open ssh once you feel more comfortable.

I'll try doing this and update if it works for me.

Chat GPT @ chat.openai.com's answer

Thank you for providing the details. Based on your requirements, you can achieve your goal by utilizing the Linux bridge functionality to create a software-level Layer 2 switch. Here's an outline of the steps involved:

1. Install the necessary software: Ensure that the bridge-utils package is installed on your Linux machine. You can typically install it using the package manager specific to your distribution. For example, on Ubuntu or Debian, you can run sudo apt-get install bridge-utils.

2. Identify your physical network interface: Determine the name of your WiFi network interface that is connected to the ISP router. You can use the ip link command to list the available network interfaces. Look for the interface name associated with your WiFi connection (e.g., wlan0).

3. Disable network management on the physical interface: To prevent network managers from managing the physical interface directly, you'll want to disable their control. This step may vary depending on your specific network manager. For example, if you're using NetworkManager, you can edit the configuration file associated with your WiFi connection (usually located in /etc/NetworkManager/system-connections/) and set managed=false. Alternatively, you can stop or disable the network manager service temporarily.

4. Create a bridge interface: Create a Linux bridge interface using the brctl command. For example, you can run sudo brctl addbr br0 to create a bridge named br0.

5. Add the physical interface to the bridge: Add your WiFi interface to the bridge using the brctl addif command. For example, run sudo brctl addif br0 wlan0 to add wlan0 to the bridge.

6. Configure the bridge interface: Assign an IP address to the bridge interface (br0) by configuring it in the network configuration files. The specific file to edit depends on your Linux distribution. For example, on Ubuntu or Debian, you can edit /etc/network/interfaces and add the following lines:

   auto br0
   iface br0 inet dhcp
   

   Alternatively, you can use network management tools like NetworkManager or systemd-networkd to configure the bridge interface.

7. Configure the virtual machines and containers: Configure your virtual machines, Docker containers, and systemd-containers to use the bridge interface (br0) as their network interface. This configuration varies depending on the specific technology you are using. For example:

   • For Docker: Create a new Docker network of type "bridge" and specify the bridge name as br0. Then, when creating or running Docker containers, connect them to this network.
   • For systemd-containers: Configure the net-attach@.netdev and net-attach@.network units to attach the container to the bridge interface (br0). This can be done using the systemctl command and systemd network configuration files.

With these steps, your virtual machines, Docker containers, and systemd-containers should be able to obtain IP addresses directly from your ISP router via the software-level Layer 2 switch created using the Linux bridge interface.

Please note that the specific commands and configuration files may vary depending on your Linux distribution and network management setup. Make sure to adapt the instructions accordingly. Additionally, be cautious when modifying network configurations as it can potentially impact your network connectivity.