block-list-formats - Revision history

Kevin Marks: /* Block Chain list */

2016-12-14T01:09:43Z

Block Chain list

← Older revision		Revision as of 01:09, 14 December 2016
Line 171:		Line 171:

	See [http://slrn.sourceforge.net/docs/slrn-FAQ-4.html slrn FAQ] and [http://en.wikipedia.org/wiki/Scorefile Scorefile on Wikipedia].		See [http://slrn.sourceforge.net/docs/slrn-FAQ-4.html slrn FAQ] and [http://en.wikipedia.org/wiki/Scorefile Scorefile on Wikipedia].

			=== Block Chain list ===

			The [https://chrome.google.com/webstore/detail/twitter-block-chain/dkkfampndkdnjffkleokegfnibnnjfah browser plugin Block Chain] exports Twitter [https://github.com/satsukitv/twitter-block-chain/blob/master/js/blockchain.js#L179 followers] in a JSON list of
			<blockquote><pre>{id: user_id, name: user_name}</pre></blockquote>

	== see also ==		== see also ==

TomMorris at 12:22, 15 November 2008

2008-11-15T12:22:14Z

← Older revision		Revision as of 12:22, 15 November 2008
Line 163:		Line 163:
	The rules have the following features:		The rules have the following features:
	* the first line (with the '*') is where the rule applies - the asterisk refers to it being applicable to all newsgroups		* the first line (with the '*') is where the rule applies - the asterisk refers to it being applicable to all newsgroups
	* the Expires: line allows you to specify a yyyy-mm-dd expiry date for the rule. In slrn, you ~~can specify this in a restricted natural language syntax like~~ "~~one month~~" ~~(I think~~)		* the Expires: line allows you to specify a yyyy-mm-dd expiry date for the rule. In slrn, you are prompted with:
			:: "Expires (MM/DD/YYYY, DD-MM-YYYY, +NN (days) or leave blank):"
			:which is, of course, not ISO 8601 and needs to be rejiggled. ;)
	* all the headers can be marked using wildcards. If you just want to filter one conversation, the References: allows you to do so. You can also filter messages originating with particular servers (googlegroups being one that is particularly spammy) by using a filter like "References: googlegroups"		* all the headers can be marked using wildcards. If you just want to filter one conversation, the References: allows you to do so. You can also filter messages originating with particular servers (googlegroups being one that is particularly spammy) by using a filter like "References: googlegroups"

TomMorris: extended section on USENET scorefiles

2008-11-15T12:11:27Z

extended section on USENET scorefiles

@@ Line 135: / Line 135: @@
 </nowiki></pre></blockquote>
-=== Gnus score file ===
+=== Score file ===
 [http://gnus.org/ Gnus], the Emacs newsreader, supports scoring posts both positively and negatively -- as such, its [http://gnus.org/manual/gnus_234.html#SEC234 scoring functionality] is a superset of just killing. The file format is an emacs lisp expression, described in the [http://gnus.org/manual/gnus_238.html#SEC238 score file format] section of the Gnus manual.
 == see also ==

EdwardOConnor: Gnus score file format

2007-10-30T23:15:29Z

Gnus score file format

← Older revision		Revision as of 23:15, 30 October 2007
Line 134:		Line 134:
	/noone@anywhere\.all/Hfrom:m		/noone@anywhere\.all/Hfrom:m
	</nowiki></pre></blockquote>		</nowiki></pre></blockquote>

			=== Gnus score file ===

			[http://gnus.org/ Gnus], the Emacs newsreader, supports scoring posts both positively and negatively -- as such, its [http://gnus.org/manual/gnus_234.html#SEC234 scoring functionality] is a superset of just killing. The file format is an emacs lisp expression, described in the [http://gnus.org/manual/gnus_238.html#SEC238 score file format] section of the Gnus manual.

	== see also ==		== see also ==

Tantek: added trn kill file features

2007-10-30T23:06:20Z

added trn kill file features

@@ Line 100: / Line 100: @@
 		/^Subject: Re:/:j
 </nowiki></pre></blockquote>
@@ Line 108: / Line 140: @@
 * [[block-list-brainstorming]]
 * [[social-network-portability]]

Tantek: drafted

2007-10-28T01:43:32Z

drafted

New page

<h1>block list formats</h1>
{{TOC-right}}
Previous attempts at [[block list]] formats. Part of the effort to enable greater [[social network portability]].

== formats ==
=== rn kill file ===
Usenet/netnews [http://en.wikipedia.org/wiki/Kill_file kill files]. For details of the kill file implemented by the "rn" news reading program, see the [http://www.faqs.org/faqs/killfile-faq/ killfile faq].
<blockquote><pre><nowiki>
Rn and trn
==========
5. What is the general syntax of a KILL file entry?
The general style for building a kill line is:

/pattern/modifiers:command

The <pattern> is the pattern to use to pick articles. This is a regular
expression, like those used in grep. You can use any case in the pattern;
t won't matter, unless you use a modifier to make rn case-sensitive.
The <modifiers> tell rn where to look for the pattern - the subject
(default), one of the other header lines, or the entire article, as examples
of the usual modifiers used.
The command tells what to do with the article once it's been selected.
This is usually either to kill it or to mark it unread.

If no modifier appears before the colon, only the subject line of the
article is searched. More than one command can be performed by using
the style:

/pattern/modifier:command:command

Thus, for instance, you can use j and = together to see the exact subject
lines being killed. (See below for the explanation of j and =.)

6. What are the available modifiers and commands?

The modifiers and commands are all explained in the rn man page, but here
are some of them:
Modifiers:
a: all, look through the entire article for the pattern
h: look through the header of the article for the pattern
f: look at only the 'From:' header (trn 3.0)
c: Make the pattern case sensitive
H: added in trn 3.1, this expands the f: above to any header
Commands:
m mark as unread
j mark as read
= show subject line

...
7. How do I kill a specific subject?

The easiest way to kill a subject line is to kill it from within the
newsgroup. When the subject line comes up that you want to kill, instead
of using 'n' to skip that article or 'k' to kill the subject for that
session, type 'K'. The subject line will then be entered into your KILL
file for that group. If you want to put that line into your global KILL
file, you'll have to do that yourself.

To kill a general subject, ie any 'test' messages, put in the pattern:

/test/:j

This will kill anything with the word 'test' in the subject line.

8. How do I kill postings from a specific person?

To kill articles from a single poster, you need to know the userid and
nodename of the poster; for this example we'll use noone@anywhere.all.

/^From:.*noone@anywhere\.all/h:j

This searches the entire header for any line starting with 'From:', anything
at all, and then 'noone@anywhere.all' in it. This is faster than if the
beginning-of-line character (^) had been left out:

/From:.*noone@anywhere\.all/h:j

If this were used, something like 'Subject: Re: Articles from:
noone@anywhere.all' would also get killed.

9. How do I kill articles from a specific site?

For articles from a particular site, just remove the 'noone' from the
previous lines, and articles from the machine 'anywhere.all' will be killed.
So, the line would be:

/^From:.*@anywhere\.all/h:j

10. How do I kill followups?

To kill anything that is a followup to any article, use this pattern:

/Re:/:j

This kills anything with 'Re:' in it. (This includes articles of the form
'Subject: X (Was Re: Y)'.)

If you just want to kill the direct followups, without the changes in
subject, you have to make it clear where the Re: is in the line:

/^Subject: Re:/:j

</nowiki></pre></blockquote>

== see also ==
* [[block-list]]
* [[block-list-examples]]
* [[block-list-brainstorming]]
* [[social-network-portability]]