• 0 Posts
  • 25 Comments
Joined 14 days ago
cake
Cake day: July 21st, 2025

help-circle


  • A TCP session is a unique combination of client IP, client port, server IP, and server port.

    So you can use the same IP and port as long as the destination is a different IP or port.

    This means that in principle you could use the same IP and port to connect to every IP address on the Internet using 65536 concurrent sessions. 😆

    This wouldn’t help going to popular destinations, since they have a lot of people going to the same IP address and port, but for many (most?) of them you probably have some sort of CDN servers in your data centers anyway.


















  • Sorry I replied to the wrong comment in the thread.

    Let me try to explain.

    GPL was designed to give users access to the source code for hardware they control.

    This worked pretty well until TiVo came up with locks that would only allow you to run kernels they signed. This was to prevent people from putting in cheap disks to their hardware.

    So GNU came up with GPLv3, which closes the TiVo hole. It also tried to address the evils of software patents to an extent.

    That works okay, but then people invented SaaS (software as a service). In that case the user doesn’t own the hardware, so companies don’t have to publish the source under GPL. Which meets the letter of the license and gives a big middle finger to the intent.

    So AGPLv3 was developed to close that hole. With AGPL users must have access to any open source run by a service to provide them with that service, restoring the ability of users to see what the code is doing, and possibly forking and making their own version if it doesn’t do what they want.