Gnus development mailing list
 help / color / mirror / Atom feed
From: <yamaoka@jpl.org>
Subject: Re: PATCH: Make nnrss include RSS dc:subject
Date: Thu, 13 Apr 2006 17:59:40 +0900	[thread overview]
Message-ID: <b4mmzeprgub.fsf@jpl.org> (raw)
In-Reply-To: <m3lkua9ffi.fsf@quimbies.gnus.org>

>>>>> In <m3lkua9ffi.fsf@quimbies.gnus.org>
>>>>>	Lars Magne Ingebrigtsen wrote:

> Katsumi Yamaoka <yamaoka@jpl.org> writes:

>> The advantage of nnshimbun is to remove advertisement.  However, the
>> module to deal with it with each news site is needed (e.g.,
>> sb-bbc.el for BBC), and we need to make major changes in those
>> modules periodically.

> Would it be possible to separate out this into something declarative
> that could be downloaded at will?

This is exactly what the emacs-w3m people were considering.  It
has not been achieved yet, though.  In fact, the number of
modules is too large for a few developers to maintain nowadays.

> The main problem with all these web-centred things is the need to
> update the source code whenever the HTML changes, and I don't see any
> general way to fix that.  To parse Slashdot, for instance, you
> probably have to do that programmatically.

Yes, we will not be able to deal with everything using only
regexps.

> But for stuff like ad removal, couldn't a language be defined for
> that?  For instance a set of regexps (or something) that could be
> applied to the article bodies before displaying (on a per-source
> basis).  The user could update these rules with, say,
> `M-x gnus-update-washing-rules' that would download the rules from
> some central repository.

> The important thing being, of course, that there would be no actual
> code being downloaded, because that would be a security problem.

Or there might be a bug causing a serious accident even if it
was made with no malice.

> Heh.  Imagine rules that would remove Yahoo ads from Yahoogroups
> mailing lists, and Sourceforge ads from those lists, and...

> Gnus ad blocker.  :-)

Perhaps we had better concentrate instead on `Gnus spam blocker'.
:-)



  reply	other threads:[~2006-04-13  8:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-17  4:09 Mark Plaksin
2005-12-19  5:19 ` Katsumi Yamaoka
2005-12-20  2:17   ` Katsumi Yamaoka
2005-12-20  6:34     ` Katsumi Yamaoka
2005-12-20 15:46       ` Mark Plaksin
2005-12-21  0:45         ` Katsumi Yamaoka
2006-04-13  6:07           ` Lars Magne Ingebrigtsen
2006-04-13  8:59             ` yamaoka [this message]
2006-04-13  9:11               ` Lars Magne Ingebrigtsen
2006-04-13  9:42                 ` Katsumi Yamaoka
2006-04-13 10:52                   ` Lars Magne Ingebrigtsen

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=b4mmzeprgub.fsf@jpl.org \
    --to=yamaoka@jpl.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;
as well as URLs for NNTP newsgroup(s).