nsnshsuejeb

3 ms·

1. 1.▲
   by nsnshsuejeb 2y ago

   No need. Just convince the king (e.g. Google for HTTP) to make a tweak in the next standard version.
2. 2.▲
   by nsnshsuejeb 2y ago

   Not defending the producer, just making pragmatic choices!
3. 3.▲
   by nsnshsuejeb 2y ago

   The letters after the dot in my filename don't map 1 to 1 with the file format.
4. 4.▲
   by nsnshsuejeb 2y ago

   Yes. We all know how to do this. You know that API version thingy. I agree to drop the carriage return when not needed but do it in future protocols. Obviously IPv6 shows you need to be patient. Your great grandkids may see a useless carria
5. 5.▲
   by nsnshsuejeb 2y ago

   Elephant in the room is the trillions of actual servers and user agents that would need to be tested and patched if you retroactively change a standard. Luckily there are some digits after HTTP that allow the concept of new versions of the