Re: Bug#513626: Improved configuration for DynDNS users

[Dan McCombs <dmccombs@dyndns.com>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Torsten Landschoff wrote:
> Right. Without already knowing what that template was about, I'd have 
> a hard time to decipher the message as well. Also the question seems 
> to be a bit indirect, asking the user if he wants the system to fetch 
> a list of hosts, while he actually decides between entering the hosts
> manually and have the system show the possible selections.
> 
> How about (rough, brainstorming-mode draft):
> 
> Template: ddclient/fetchhosts
> Type: select
> Default: from list
> Choices: from list, manually
> _Description: Selection method for updated names?
>  You'll have to select the names to update using ddclient below. You 
>  can select names to update from a list (taken from your DynDNS account) 
>  or enter them dynamically.
> 
> Rationale:
> - Concentrates on "names" as we are talking about the "dynamic domain 
>   naming service". Not sure if this is better than "host names".
> - Makes it more clear that the system can help the user by showing the 
>   available (host) names.
> 

I like the idea of using a select between from list and manually, that
solves the issue of what happens if you don't choose to get the hosts
from the account.

As far as "names" vs. "host names" I'd prefer to keep the later, as they
are referred to as "host names" on www.dyndns.com and in the account
settings there.

>>>> +Template: ddclient/hostslist
>>>> +Type: multiselect
>>>> +Choices: ${choices}
>>>> +_Description: Please select the hostnames you would like to keep updated
>>>> + Select one or more hosts to update using ddclient
>>> _Description: Host names to update:
>>>  Please choose, among the list of host names managed under your
>>>  account, the ones that should be updated with ddclient.
>> AIUI ddclient doesn't update hosts, or even hostnames, and it won't
>> do it just once; it maintains the online server's DNS records so
>> that the selected name is always assigned to your current address.
>> How about:
>>
>>   _Description: Host names to keep updated:
>>    The list of host names managed via your DynDNS account has been
>>    downloaded. Please choose the the one(s) that ddclient should
>>    take care of.
>>
>> (Any ideas for a clear and concise way of expressing exactly what it
>> is that's kept updated?)
> 
> I think we should emphasize that all selected names will be updated 
> from the address pointing to the local node (or that is the intent 
> of running ddclient). Therefore I would expect that most users select
> exactly one host.

My draft as far as emphasizing that ddclient will try to keep these up
to date, and that they are updated using the interface (or web
detection) that was selected in a previous question.


_Description: Host names to keep updated:
 The list of host names managed via your DynDNS account has been
 downloaded.  Please choose which one(s) that ddclient should keep
 up to date with the detected IP address of the selected interface
 or network.


I'll start to merge the changes that have been discussed so far into the
patch and post it here to make it a little easier to follow where we are
currently at.

Thanks for all the input so far,

- --
Dan McCombs
Dynamic Network Services, Inc.
http://www.dyndns.com/

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkmQNXIACgkQSTakzmXY5/hTTACfRjeIxB3+ZLmc7r6i+AFS3zlX
FGsAn34UIUbx4/84VvKYKQ4XRVPLa5vu
=xpTd
-----END PGP SIGNATURE-----