<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><br>
</p>
<div class="moz-cite-prefix">On 26/02/2025 21:33, Phillip
Hallam-Baker wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAMm+LwiWpDMqF4A8YxoQJoDVPUtTbSv5KDvLrcreoqU-RvkV7Q@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div dir="ltr"><br>
<div class="gmail_default" style="font-size:small">The user
experience I am aiming for with a webcam is Alice buys the
webcam, gives it a name in the DNS space for her house '<a
href="http://webcam.house.example.com"
moz-do-not-send="true">webcam.house.example.com</a>' and
lists @<a href="http://alice.example.com"
moz-do-not-send="true">alice.example.com</a>, @<a
href="http://bob.example.net" moz-do-not-send="true">bob.example.net</a>, @<a
href="http://carol.example.com" moz-do-not-send="true">carol.example.com</a>
as the list of people authorized to access it. From that
point on, they can go to <a
href="https://webcam.house.example.com/"
moz-do-not-send="true" class="moz-txt-link-freetext">https://webcam.house.example.com/</a>
and log in via OAUTH using a regular browser.</div>
<div class="gmail_default" style="font-size:small"><br>
</div>
<br>
</div>
</div>
</blockquote>
Before moving on with the details of the protocol, it is worth
considering whether it is smart to put handles for users in DNS. DNS
is good a publishing information and a list of authorized users is
typically not something you want to published.<br>
</body>
</html>