Developers of Sympa

[Luc Didry <address@concealed>]

mercredi 21 novembre 2018, 10:29:18 CET IKEDA Soji wrote:
> That's also the case of gmail.fr (honestly I didn't checked
> usability of these domains.  I just wanted to show examples of
> confusion with existing domains).

Whois for gmail.fr contains a lot of google related stuff (contact,
address, e-mail…). The registrar is MARKMONITOR, which is a company
that monitor bad use of marks[1]. I think that Google delegated the
typo-squatting supervision to that company.

> I feel it depends on what sort of corrections you aim to.
> 
> If you want to deal with renaming/moving domains of particular
> services, I think exact (and optionally suffix) matching seem
> suffice.
> 
> If you want to deal with typos by slipping fingers of users,
> matching rules (including wildcard) probably may not suit:
> You may have to register typos as many as you can think out.

Slipping fingers are my target… and stupid mistakes too (when you
write gmail.fr instead of gmail.com, that's not a typo, that's a
stupid mistake).

> The other ways, e.g. checking DNS MX/A RR of domains through
> AJAX calls during input by users, would possiblly be better.

It may not work: some typo-squatters may be well organized
(gmail.ne.jp has a MX which has a RR — not matching the MX though)

I saw some typo-squatters that seems to be well-intentioned: they have
a MX with good RR and they say they forward the mail to the correct
address, but you can only trust their words.

> It depends.  We should have to provide GUI to edit the configuration
> (I think most of recent users will complain, if UI won't be provided).
> Even if UI were not provided, it would be better to have simple format
> which is easy to edit.
>
> From these point of view, my format may look simpler to edit, and it
> may be more or less easier to realize GUI reusing existing codes.

UI can be easily made with something like that:

for my $key (keys %{$corrections->{substitutions}}) {
    var $sub = join('\n', $corrections->{substitutions}->{$key});
    # put $key in an input field and $sub in a textarea
    # use split to transform the sent textarea to array
}
for my $key (keys %{$corrections->{globbing}}) {
    # put $key and value in input fields
}

As for the UI need, I wrote that tool thinking it would be available
only to admin, just as sympa.conf since it's quite dangerous: I don't
think giving such power to users would be a good thing (given the
amount of mistakes they do with the existing tools). I don't see
advanced tools in Sympa WebUI for the listmaster to modify the default
templates: they're just big textarea (I looked at
/sympa/serveradmin/templates, is there any other tool?).

I could do without the globbing if it's considered as dangerous, but
to me, the format of the file needs to be concise.

Racke, David… any opinion?

[1] I know them, I already had contact with them.
-- 
Luc
"La route est longue, mais la voie est libre…" https://framasoft.org

Framasoft ne vit que par vos dons (déductibles des impôts). Merci d'avance 
pour votre soutien https://soutenir.framasoft.org