public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Tom Rymes <trymes@rymes.com>
To: development@lists.ipfire.org
Subject: Re: [PATCH 0/5] ipblacklist: IP Address Blacklists
Date: Mon, 16 Dec 2019 18:05:14 -0500	[thread overview]
Message-ID: <93d92d4d-c46f-5e13-0965-8a359f80f30a@rymes.com> (raw)
In-Reply-To: <C23B88EC-05D8-4C3E-82DC-01E852928CA3@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1065 bytes --]

On 12/16/2019 5:20 PM, Michael Tremer wrote:> Hi,
 >
 >> On 16 Dec 2019, at 20:06, Tim FitzGeorge <lists(a)tfitzgeorge.me.uk> 
wrote:
 >>
 >> Hi,
 >>
 >> I've attached the current GUI screenshot.
 >
 > Thanks for that.
 >
 > I have a couple of suggestions/concerns about it:

[snip]

 > c) I would suggest to remove the “safe” column because that is a very 
hard summary of what the lists do. We should explain that on the wiki. I 
guess this is too complicated to explain to our users in one sentence 
and it needs at least a page of text. People who do not read that have 
you just lost out.

[snip]

May I opine that the "Safe" information would be helpful to me in the 
WUI. Perhaps we can be more explicit, or better explain, such as is 
often done with RBLs in mail server settings, where lists are sometimes 
described in terms of their likelihood to cause false-positives.

It's all well and good in the documentation, but a quick 
"Safe|Moderate|Risky" listing in the WUI will prove handy, IMHO.

Just my $0.02 as more of a user than a developer,

Tom

  reply	other threads:[~2019-12-16 23:05 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <c0c3b48a-f773-8002-a004-82ff150ea1bb@tfitzgeorge.me.uk>
2019-12-16 22:20 ` Michael Tremer
2019-12-16 23:05   ` Tom Rymes [this message]
2019-12-18 12:10     ` Michael Tremer
2019-12-28 21:17       ` Tim FitzGeorge
2020-01-06 11:21         ` Michael Tremer
2020-01-22 20:35           ` Tim FitzGeorge
2020-01-23 10:53             ` Michael Tremer
     [not found] <aeb93668-a4b6-5735-1f68-fd53cafa2210@tfitzgeorge.me.uk>
2020-01-06 11:27 ` Michael Tremer
2020-01-24 19:40   ` Tim FitzGeorge
2020-01-28 17:14     ` Michael Tremer
2020-01-29 20:40       ` Tim FitzGeorge
2020-01-30 12:54         ` Michael Tremer
2020-01-30 20:24           ` Tim FitzGeorge
2020-01-30 21:26             ` Michael Tremer
     [not found] <6583305a-cd0d-94a5-aa8e-5456622de824@tfitzgeorge.me.uk>
2019-12-18 12:07 ` Michael Tremer
2019-12-21 18:34   ` Tim FitzGeorge
2019-12-24 10:29     ` Michael Tremer
2019-12-28 20:59     ` Tim FitzGeorge
2019-11-25 20:13 Tim FitzGeorge
2019-11-25 21:09 ` Peter Müller
2019-11-27 21:34   ` Tim FitzGeorge
2019-11-28 12:03 ` Michael Tremer
2019-11-28 21:39   ` Peter Müller
2019-11-29 23:25     ` Tim FitzGeorge
2019-12-02 11:17       ` Michael Tremer
2019-12-04 17:05         ` Peter Müller
2019-12-05 22:25           ` Michael Tremer
2019-12-08 20:50             ` Tim FitzGeorge
2019-12-13 23:11               ` Michael Tremer
2019-12-02 11:06     ` Michael Tremer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=93d92d4d-c46f-5e13-0965-8a359f80f30a@rymes.com \
    --to=trymes@rymes.com \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox