Comment by 9dev
1 day ago
Is the p2p problem really still one in our world that is mobile first, but also has ubiquitous internet connectivity pretty much everywhere? I’m almost sure I could host my website from my phone and have at least 99.5% percent of uptime.
Give that it's impossible to even listen on port 443 on a phone, as that would require root privileges, I don't think you can host your website on your phone at all, at least not if you want it to accessible in a normal way. And that's not even going into all of the problems with running background apps on a phone, especially on iOS.
By I could, I meant that my phone has a persistent connection uninterruptedly long enough to be theoretically able to serve a website in the background. There are all sorts of (arbitrary, mind you) technical limitations, from the IPv6 address randomly changing as you roam across networks to iOS killing background processes - but those are software limitations.
The point was that mobile device doesn't equate spotty connectivity anymore for most people.
Even in this idea of "could in principle", the IP address randomly changing as you roam is not an arbitrary technical limitation, it is a fundamental property of how IP networks operate that proved to be too hard to fix for IPv6. The LTE network does a lot of work to try to preserve your IP as seen by the servers you connect to, to preserve your active connections, but this could only be done as a layer on top of IP.
The reason why this is fundamentally quite hard is to do with routing optimization. Routing tables have to reflect physical connectivity - which means packets destined for F2::67 mustn't be routed to LA if that is the IP of a phone that is now resident in SF. However, changing routing tables on all devices along the way as a phone roams would not be an easy feat.