User Terms Engineering Layer for IEEE (The Institute of Electrical and Electronics Engineers)

Oh, okay. We're ready to go, doc. Okay. All right. All thank you everybody. I wish I was there in person. I normally am. So is Joyce's a last, so we had commitments here and couldn't make it this time. We will be in Berlin.

However, so that'll be great. The, and I'm substituting for Mary hotter and she and I are both on involved with the I E in a meeting. That's going out exactly now. And they may not have a quorum because Joyce is in it too. She just went downstairs to give us a core of anyhow. So this is the name of the, the, the, the thing we're doing right now, it's too complicated. It's about the IEE and which is a nonprofit with a zillion members began in 1884, emerged with radio engineers. When radio was a hot thing in 1952 became the I E in 1963, still the same organization.

And it has 39 technical societies. One of which is this one, and I'm not gonna read it, cuz we don't have enough time, but here's what matters. They approached us, meaning Joyce, myself, and a few other people, including Mary to come up with this, this one P as a working group called P 7 0 1, 2 standard for machine readable, personal privacy terms. This is a very, very new and different thing that we've ever seen before.

It's par, which is a project authorization request is to make a standard that addresses. And this is the language, the manner in which personal privacy terms are proffered and how they can be read and agreed to by machines now, because it's personal. It means that we do the proffering as you know, on the web right now, it's the other way around. We're always agreeing to somebody else's terms and we do it with every single freaking website that we go to. Every service that we engage, this is broken and it's terribly broken.

And I'll go into that next, you know, and it started because we, which is mostly, I wrote that it's time for them to agree to our terms rather than the other way around. We should be. They should agree to ours at scale. And so let me put that in context in the physical world and the internet, both of those came without privacy, but we fixed one of those. We fixed it with clothing and shelter right now, all of us are sitting here, me with my pre shirt, with privacy technology, we're wearing privacy technology.

It isn't absolutely protection, but it does give a signal to other people in the world that we'd rather not have somebody come into our private space. And we understand what each other's private spaces are. And this works really well in the physical world is worked this way for a very long time. It is thus far almost inconceivable except to a few of us and the IEE that we can also do this in the online world, which is born without privacy as well.

You know, we were born naked in the physical world. We're kind of naked in the, in the online world. And so in the absence of that, you know, we've got this, we've got every advertiser and every publisher in the world craving personal data. And because we're, Hey, we live in a digital world now.

Well, all this personal data's out there for us to grab up, we can harvest it. It's like blueberries on the forest floor. It's free. Let's just go get it right. And it's turned to companies of the world into data vampires. That's what's actually happened and have set out that dogs to sniff us, is it where we call 'em cookies? But basically they're looking for us at all times. So they could target us with advertising. That's the idea and is a multi-trillion dollar business now. And it isn't just Google and Facebook, which are the easy targets of regulation and interest.

It's every freaking website on the net that isn't supported in some other way. And it's way out of control. And we call this now surveillance capitalism. Thank you. So Shaana ZBA for creating that term.

It's it, it's very helpful. But anyway, we're kind of stuck in this and in the absence of that, we came up with regulation, the GDPR, I, I created this graphic in 19 20 17 or 18 before the GDPR came along, which by the way was in on the 25th of, of, of may in 2018, just a few, a few days after the, the 2018 EIC, which is an eventful for one for us, which for reason we will go into, but, but we had high high hopes. The GDPR GDPR is gonna like blow this stuff up. It didn't do it.

You know, instead what gave us is this cookie hell. I mean, we have every single website. It's the GDPR said is, Hey, you, you, me, all of us individuals, we are nothing more than data subjects. We are natural persons. That's the term they use in English, but we are data subjects and data controllers and data processors are these other parties. And we have to go to them.

And we, our privacy is entirely at the grace of these freaking companies and it's an awful thing for them. And it's an awful thing for us. And that's where we're stuck. So here's where P 7 0 1, 2 fits on the right here is, is an image from creative commons, creative comments fixed a lot of copyright in a really simple way.

It said, you know what? We can, we can just divide this up into legal code, human readable code, you know, what are you asking for and make it machine readable. And so that's where we can get privacy is that we will make it machine readable. We can have ways of expressing it and have it be machine readable. So one example is just give me as not based on tracking me. And in fact, we at project VM and customer comments, which is the nonprofit that Joyce and I, and a few other people, including Mary started, it's a, a worldwide nonprofit, but it's, it's based in the us.

And this is a term, it's an example of a term. And it's one that should be agreeable to publishers online, which is just give me ads, not based on tracking me. I I'm fine with that said, don't track me, right? That would keep them in business. It would work for us. And that is called P P two B one. And that's at the customer comment site at that long URL, you can navigate to it if you just go to customer comments.org. So that's one example, and that's the only thing that's missing right now is the machine readable part, which is why we need this standard.

Another one is this one called the buy way. The, and that's a customer comments itself, and this is a new thing. And the idea behind the buy way is that, you know what, we can't get this done on the web. The web is lost. It's too late.

We're, we're too screwed up there. We it's, it. We already had something like the no stalking thing that I showed back up here. That's no stalking. It says no stalking. That's the name of that, that term. But we already had, do not track do not track was a polite request in a, in a browser header to every website in the world that says exactly what your pants do, which is don't track me. It don't get into my private space and it was mocked and ignored completely. And this stuff might also be mocked and ignored, even if it's a standard.

So, and that's because the way the web is built is top down. It is, it is a master slave system and we're stuck in it for now. So maybe we can fix it.

Maybe not, who knows, maybe if the GDPR becomes infinitely enforced, and everybody other country actually enforces that and makes it too difficult and expensive, but it's still a top down master slave relationship called client server. That's been around since the mainframe age and it's too hard to fix. The byway is a new thing outside of that, based on open standards. And we're working on it right now, Joyce and I have both moved to Bloomington Indiana in the us so we can work on it with the Ostrom workshop at Indiana university.

And if you wanna help with that, you know, write me at, you know, at my first name, at my last name, docket soles.com. So that's basically it.