Intrinsic systems of identification, may end up being part of the features of next generations of the internet provides.
Identity storage has become commonplace on the internet, as well as storage of information, like posts, uploads, and communications, which can essentially be viewed at as and extension of the identity, like a large fingerprint of activity.
Consider the fact that social networking is such a large and integral part of the modern web. Protection of identity is questioned all the time and not always transparent. Control of information is present and not always completely transparent. For instance, if you post something, the transparency of your being able to see who is manipulating your content and have control over censorship is left up to the website developer to articulate and implement, there is not built into the internet itself much control or transparency mechanisms for high level transactions such as posting and deletion or alteration of content. Also protective measures are left to be implemented by site developers and managed by them. A good protective and transparent high level protocol could make this an indestructable feature of the internet itself for all sites.
We could then designate roles and view officers and force them to identify themselves n the case of a breach of information or intrusion within communication channels, keep better track of politicians, who maybe would have to register under stricter transparency measures than regular citizens or free people, to track activity in an easy and useful fashion. Citizen/Free roles may have high support for transparent and highly controllable degrees of privacy and protection, to ensure safety from authoritative bodies or intrusive or malicious traffic.
You may not realize but even nowadays you only have a (limited) number of privacy rights and protection rights built into the internet, and you give up your information each time you access it. The simple patterns of you interaction build up to a likeness which when compared to fragments of identity information that is in actuality captured in pretty large amounts during regular web use. All this builds up to an accurate profile, or choice of a certain number of possible profiles in the case where information is blurry.
Systems intended to more universally and intrinsically handle this type of information may also have the effect of optimizing the web (as well as the process of web development) for these kinds of applications. This means things like collaborative effort can be conducted at a much more fast paced, concentrated and easily configured way. Logging in can be conducted more instantaneously, and maybe log-in information can be more centrally managed by the individual and more well protected across many sites and applications. Like, picture having like five different passwords, and being able to assign them to whatever sites, or switch them between sites you use or services you subscribe to, and being able to see the all the sites one password is used for, in an easily manageable way (instead of having tons of passwords for different sites, and different levels of faith in security in each site. Centralization and focus on the identity as a thing across sites, or site transient, could also more easily prevent breach of multiple sites by the discovery of one identity. Like, the identity could know when one of its site’s security became compromised, and automatically change or mask itself on other sites that identity is used for, thus preventing further security breach. Your passwords, themselves, may also trigger alerts to mobile devices, etc that subscribe to alerts from whichever identity or password…
Things like passwords and security features surrounding remotely stored account information were not really built into the original web. We see nowadays so many instances of the usage of this type of personal identification and profile representation that its use is almost pervasive on the web. Tunneling, like as in virtual private networks (VPNs), is a technology that requires extraneously built and configured clients to operate on protocols which have been built into the web, but these protocols are somewhat basic and low level, lacking definition of higher level activities such as commenting, censorship, profile definition, storage, etc. and still difficult for the average user to configure or become aware of.