> We will never sell your data.
I can/want to host my own data.
> We will empower you to make your own choices about what content you are served
I decide myself what sites I visit. Although in recent years I mostly use HN for discovery.
There is only one problem though: Web authorization/id. When I publish family photos I don't want the whole world to see, only our relatives.
I've setup basic HTTP auth and sent out username+password to all relatives.
That however doesn't scale! And it's impractical.
What we need is a public/private key that is generated by the browser, and which can be shared between many devices. You can have many keys, one for work, one for personal business, another one for gaming or what not, as many identities/keys as you want.
When you visit a web page that wants to know your identity, like any websites that right now asks for a username/password. You get a dialog asking if you want to identify on that website, and what meta-data the website request and what you info you want to give it. Kinda like installing an app on Android or iPhone where you need to confirm the app permissions.
Upon accepting the identify request, you pick an appropriate ID, then your browser sends the public key to the web server, and answers a challenge to make sure you are the owner of that ID. No more username/passwords to remember.
As for me who is a content hoster, I simply chose from a GUI, depending on what server/app i'm using, which group or individual id/public key I want to give access.
If an unknown id/key authenticates, depending on what server/app I'm using, I get a notification, asking me to add that ID/key to contacts or what not. Kinda like with social messenger apps.
At this day and age, we need something better then usernames and passwords!