@Charlotte158918 How the hell do they not know about drill stops? This has been a thing in construction for a long time. You set the depth and drill. Like wtf?
@X, I'm always getting the login overlay with poor UI position popping over my feed. I'm already logged in. I can close it and stay logged in. Some rogue trigger is happening when X is the last active app, my screen locks for 3+ minutes, then I unlock it and X is still active. That usually causes it. Quite annoying. Been happening for about 3 weeks.
Android. OxygenOS.
All great points you have. I do need to do some more research. However, I do think there was some intent on human readability. There are other forms of recording address data that are more system native, even at the time of its creation.
To this day a very common and useful question in IT is "which network?" "10.30". Is much easier than "2001:0db8:85a3". Just giving it a human liable still doesn't help in many cases.
This is why I still see Ipv6 as a forces solution, but very difficult to adopt by its intended users.
So @geerlingguy caused a stir with his IPV6 post, and my post brought on very polar reactions.
I'm realizing that I think network guys, like IPV6 from a technical perspective but the average user of it hates using and are forced to.
The solution(s) being offered is not the ones desired by the users/implementers of it.
@geerlingguy I still don't understand why we can't just take IPV4 and create IPV4.1. Literally just add another dot to the address and the masks.
127.0.0.0.1
@solisvogel@geerlingguy Do you know your own lan ipv6 address by heart?
The number of times that has been helpful is massive. That's my main argument. It's a solid argument if you've ever had to set up a network without a whole team and with the thousands of dollars of equipment that abstracts it away.
@PipingJam@geerlingguy Maybe it's not and just feels that way..... Ha.
From the parsing standpoint and mask application it appears trivial to do one or the other.