unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Nils Gillmann <niasterisk@grrlz.net>
Cc: guix-devel@gnu.org
Subject: Re: proposal for more options in gnu/services/networking.scm for blocklist
Date: Thu, 04 Feb 2016 17:54:46 +0100	[thread overview]
Message-ID: <87wpqka015.fsf@gnu.org> (raw)
In-Reply-To: <87h9hqzz8k.fsf@grrlz.net> (Nils Gillmann's message of "Tue, 02 Feb 2016 20:30:35 +0100")

Nils Gillmann <niasterisk@grrlz.net> skribis:

> ludo@gnu.org (Ludovic Courtès) writes:
>
>> Nils Gillmann <niasterisk@grrlz.net> skribis:
>>
>>> A first version for google I just came up with starts like the attached
>>> code.
>>>
>>> What do you think?
>>
>> I would use it!  (Although I use Tor + Privoxy for most of my web
>> browsing, so I would also need the black list there.)
>>
>> The only downside I see it having to maintain it.  Do you know if anyone
>> maintains a list of these hosts somewhere?  If yes, we should put the
>> URL as a comment and have a somewhat streamlined process to update the
>> list.
>
> There are many lists out there which are not limited to google.
> The downside I see with this is external authorities and the trust you
> have to put into them, plus unnecessary downloads.
> If it should be moved into a file, I would put it into the Guix system
> source. (-> maybe mirrors of those listed below?)
> I could try and see if I can find a blacklist which is not very long and
> does not need extensive checking.

OK.

>> If there’s no publicly-maintained list of hosts, I think we won’t go
>> beyond Google, because that would easily become unmaintained, and people
>> would be disappointed to get an incomplete/outdated host list.
>>
>> What do people think?
>
> Ublock Origin uses the following sources:
> https://easylist.adblockplus.org/en/policy#easylist
> http://pgl.yoyo.org/adservers/policy.php
> http://www.malwaredomainlist.com
> http://www.malwaredomains.com
> https://github.com/gorhil/uBlock/tree/master/assets/ublock
>
> Pro: Other people and collections of people maintain these lists. less
> work for us
> Pro: widely accepted and maintained
>
> Con: see section above (other authorities, traffic)

Yeah.  OTOH I don’t see us (Guix) claim maintenance of such lists.

Another option would be for you to publish such lists, signed and
versioned, on a hosting site you have access to?  The advantage would be
less churn in Guix proper, and the responsibility would be moved to you
(or the collective that maintains the list) rather than Guix.  We could
refer to it in the manual.

WDYT?

Thanks,
Ludo’.

  reply	other threads:[~2016-02-04 16:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-31 21:09 proposal for more options in gnu/services/networking.scm for blocklist Nils Gillmann
2016-02-02 13:21 ` Ludovic Courtès
2016-02-02 19:30   ` Nils Gillmann
2016-02-04 16:54     ` Ludovic Courtès [this message]
2016-02-06 17:46       ` Nils Gillmann

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=87wpqka015.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=niasterisk@grrlz.net \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).