Web site enhancement requests (or: pops head above trench and then ducks!)

18 posts / 0 new
Last post
G3ZOD
Offline
Last seen: 3 years 1 month ago
Joined: 2009/04/18 - 12:39
Web site enhancement requests (or: pops head above trench and then ducks!)
  1. Please include DT values in the Database page displays http://wsprnet.org/drupal/wsprnet/spots . This will be of particular value when trying to help diagnose newcomers who are having tx/rx problems.
  2. Please can we have additional criteria on the "Spot Query Database" page http://wsprnet.org/drupal/wsprnet/spotqueryDatabase ?

    A dropdown list labelled "Limit to:"
    with:
        "Maximum power (W)"
        "Minimum distance"
    and an associated box to to type in a numeric value.

    The value would need to accept decimals, e.g. for Watts 0.1, or alternatively it might be easier to use dBm instead i.e. "Maximum power (dBm)"

    (Other possibilities with numeric values are there too, e.g. min/max SNR, km/Watt)

  3. On the activity page, please can the max. number of lines per band in the tables be increased from 10? This is because when there are high numbers of stations (e.g. 70+), the page becomes excessively wide. I guess some people would say that it would make the page too long, but my take on it is that people look in detail at one band at a time so the page length is not as great an issue (and see [4] below).
  4. Please can the Activity page have hyperlinks at the top, one for each band, to speed up navigation?
  5. Please add 4m (USB dial 70.0286) to the "Frequencies" list in the left hand web page panels.
  6. Please add 4m to the Activity page (dial 70.0286, tx 70.0300 - 70.0302)
  7. The "My Account" / "Edit" page http://wsprnet.org/drupal/user/<nnnn>/edit says:

    "The e-mail address is not made public and will only be used if you wish to receive a new password or wish to receive certain news or notifications by e-mail."

    This used to be true but now email addresses are exposed automatically in the Chat page. At a minimum, this statement needs to be corrected. Ideally, the original promise should be honoured with users' email address only exposed in chat if they "opt in" since people gave email addresses based on the (now) false promise.

    This could be done on the Chat page itself e.g.
        "Allow others to see your email address [  ]"
    to make it easy to do.