[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: FilterProxy and DFSG-compliancy?



Kenneth Vestergaard Schmidt forwarded:
> I am quite serious about this.  In case that wasn't clear, you may not
> do the following things with FilterProxy:
>     Remove naughty words
>     Remove pornography
>     Remove "harmful ideas" in any form
>     Enforce access policies.
> *UNLESS* you have the express knowledge and consent of the person whose
> web content is being filtered.  Said person must know exactly what is
> being filtered.  This is just so that unscrupulous individuals don't
> install FilterProxy as a netnanny-type filtering system, and force their
> views on others using it.

I actually find this copyright somewhat humerous.  I have not seen the
software, it's sourcecode, or how it operates, but if the author was
so adament about keeping the recipients of filtered content informed,
why not make it an integral part of the program.

    "The content of this page has been filtered by _FilterProxy_ on
    192.168.1.253.  Follow the link above to get details about the
    changes made."

The link brings you to:

    "FilterProxy (_official site_): http://...b.b.b.laaahh
     FilterAdministrator: _administrator@nework.tld_
     Original Page: http://target.websitenet.tld/page.html (_unfiltered_)

     Content Filtered Summary (_Detail_)
        20 Offensive words replaced with *'s (_Detail_)
        1 Offensively named image file (_Detail_)
        14 Links to offensively named URI's (_Detail_)
        32 Links considered to be ads (_Detail_)
        32 Images considered to be ad banners (_Detail_)
        3 Javascript blocks (_Detail_)
        2 Large images (_Detail_)

     Filters used:
        offensive (_view_)
        ads (_view_)
        large images (_view_)
        javascript (_view_)

     Do you disagree with the filters used? (*) Yes ( ) No
     If yes, why?
     _________________...
     Enter your email address or 'anonymous':
     ________________ 
     Do you want to be contacted by the administrator? ( ) Yes (*) No
     
     [submit]"

Trying to enforce EULA (a wonderful acronym given to us by the
Micro$oft monster), is laughable. ;-)  Making it difficult to remove
end-user information is a much better solution.  The people who
install the software would have to work to remove the 'info' code.

-- 
Chad Walstrom <chewie@wookimus.net>                 | a.k.a. ^chewie
http://www.wookimus.net/                            | s.k.a. gunnarr
Key fingerprint = B4AB D627 9CBD 687E 7A31  1950 0CC7 0B18 206C 5AFD

Attachment: pgpl5bTLCxf4v.pgp
Description: PGP signature


Reply to: