And a quick search turns up this for Chrome:
https://github.com/GoogleChrome/chrome-app-samples/tree/master/samples/mdns-browser
Apparently writing an extension is as easy as writing html and
javascript in chrome. I vaguely think that
Firefox is the same, but not for sure.
Mike
On 05/31/2018 04:27 PM, Michael Thomas wrote:
On 05/31/2018 04:00 PM, Ted Lemon wrote:
That's one way of doing the renaming, sure. It's not that simple
though. You'd probably have to populate both names and mark one of
them as deprecated. The problem is that this creates a bit of a mess.
With a CNAME, you wouldn't need to deprecate the other... it's just an
alias that you have control of.
From the UI perspective, whatever is presenting names to the user can
prefer the human-given name over
the auto-generated name, right? We wouldn't need to standardize
anything then.
Regarding specifying a UI, I think that is it of scope, but it's an
interesting problem that would be worth talking about.
I'm not an expert on browser plugins, but it seems to me that they
could probably go a very long
way if one were created to simplify things like naming. And the one
thing we can take for granted
is that people know how to push bits around using a web browser :)
Mike
On Thu, May 31, 2018, 15:06 Michael Thomas <[email protected]> wrote:
On 05/31/2018 02:32 PM, Ted Lemon wrote:
> In practice, you just change the device's name in its web ui. Then
> it's starts advertising the new name, and the old name stops
working.
> If you have enough of a model of this to change the name, you also
> know enough to select the printer under it's new name. Of
course it
> would be nice if we could have it publish some kind of
announcement
> about the name change.
On the subject of naming, it's not really necessary to change the
name
to give it a pretty display name in DNS... you can just give it a
CNAME
or something like that. That would at least give me one source of
truth
on naming without having to go to every grotty web interface on
low end
devices (assuming it exists at all).
Mike
_______________________________________________
homenet mailing list
[email protected] <mailto:[email protected]>
https://www.ietf.org/mailman/listinfo/homenet
_______________________________________________
homenet mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/homenet
_______________________________________________
homenet mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/homenet
