Enhancements to SusiDNS

[Reportage]

Some ideas for improvement, some more involved than others:

• expose log in UI to allow easy review of newly added domains
• allow searching/filtering by added date/subscription list
• implement site ping to allow optional display (and uptime stats?) of only alive hosts (with the caveat that non-http hosts will likely report as dead)
• allow manual editing of the notes field for individual hosts (or remove field?)
• offer simple dropdown with preconfigured selection of host lists to minimize pain for new users
• convert useful settings in configuration section to UI options (checkboxes etc)
• blacklist subscription list support
• add preference to configure list page size
• add tools page with conversion from b32 ↔ b64, advanced lookup including searching for domain with b32/64 input, search based on list subscription, search based on date added (earlier/later/match), ping test for domain (and advanced probe to determine service type?), aggregate jump link search (which addresses have the queried domain?)
• optional log of addresses visited by date/hit count
• option to purge all addresses from a nominated subscription service
• migrate add/import and search to separate pages with dropdowns/radios to limit scope, and in the case of search, allow global search

[zzz]

Notes is #1433

I believe the others are new

[Reportage]

See also: #2228

[zzz]

Which of the OP items if any would be useful to the typical user?

Most appear to be targetting a power-user or developer.

SusiDNS not a current priority and unlikely to be anytime soon.

[Reportage]

In terms of usability and usefulness for the typical user, an automated, scheduled ping of addressbook domains that exposes uptime and stability of hosts, in similar vein to identiguy, would go some way to addressing the perennial complaint of dead domains. Presenting active hosts on a separate page would further enhance this feature, and the option to either manually export all alive hosts to a hosts.txt file, in addition to only publishing alive hosts to a nominated hosts.txt file, would further consolidate.

In terms of b32/b64 conversion, the option to add .b32 addresses to the addressbook would satisfy the needs of the typical user, and is a feature that's been requested before.

Support for a local blacklist, with optional subscriptions, is also something a typical user would likely find useful. Currently there is no way to blacklist domains, nor permanently remove domains from the addressbook if they're featured in a subscription.. any deleted domains will be reacquired when a subscription is polled, which makes removal of domains from the addressbook mostly redundant.

[zzz]

Add a subticket #2447.

[Reportage]

Add a subticket #2495.

[Reportage]

Some notes on the attached subscription management ui mockup:

• Purge entries: this would permit the removal of all addresses derived from a subscription, either as a precursor to deleting or disabling the subscription, or to ensure that obsolete addresses no longer present in a subscription are removed before updating.
• Enable / Disable subscription: This would permit the inclusion of multiple subscriptions with a default installation, allowing the user to enable desired subscriptions without the extra step of adding them manually. It also allows retrieving a hosts.txt file and then disabling to permit manual updates only (when the subscription is re-enabled).
• Priority: In the event that an address conflicts with another address from a different subscription (same name, different dest), priority would determine which subscription takes precedence.

[Reportage]

Mockup of subscriptions management UI