So the idea about a alternative is nice, but totally impossible to get it to the people.
Is it not possible for a team of a few smart people to do develop this? I might be ignorant of what this requires technologically, but please explain.
The adoption problem can be separated into two very interdependent problems: Developer adoption and user adoption.
I think user adoption is much easier than many seem to think. If people really want to use a website, they will also be willing to download and install a program (browser) in order to use it. It is not comparable to people having to install an OS. It is comparable to installing a video game in order to play it, so I don't think it will be that hard to get people to use it. This is of course meaningless if there is no developer adoption.
Developer adoption is probably much harder as you also point out. Primarily because of unsolved state and the perceived hardness of the user adoption problem, but also because the barrier to entry is a lot higher for developers. Thus the tools of course have to be great and developers have to convinced that users will come. Then there will be a positive feedback loop of higher adoption.
Of course the powers that be will fight against it as with most things, so it will not go fast. However, I think the biggest hurdle is probably getting it going in the first place. But maybe the Handmade community is the dry wood that can catch the spark. By that I mean that this community was founded on the hope that we can have nice things if we put in the work, so I would think many people here would be willing to try to be the first developer to adopt if given the option. There might not be enough web developers here though.
Its definitly possible to solve all the technical issues we have right now, if we fully restart from a good base (TCP/IP) - especially done by handmaders ;) We could certainly create a alternative from a technological point of view.
What we need is a few things:
- A new protocol for transferring binary data based on security and stability (Basically a HTTP/HTTPS replacement)
- A isolated low-level language for transforming packets from that new protocol
- A server application for serving in/out packets (HTTP-Server replacement)
- A browser replacement which understands the new protocol
Now here comes the caveat, or rather random ideas i have:
- The protocol packets must be encryted, but decryptable by some sort of a key
- Packets cannot be cloned, every packet is unique
- The server application must be able to decrypt and re-encrypt the packets
- It should not be possible to decrypt the packets before it reaches a server
- Each server/user must have some sort of unique identification
- A packet is for one user and one server only
- User to user (Peer-to-peer) packet serving should be possible as well
- The main problem is how to uniquely and reliably identify a user and a server (Impossible/Unreasonable to hack with current hardware)