Tillbaka till svenska Fidonet
English   Information   Debug  
FIDONEWS_OLD4   0/37224
FIDO_SYSOP   12852
FIDO_UTIL   0/180
FILEFIND   0/209
FILEGATE   0/212
FILM   0/18
FNEWS_PUBLISH   4393
FN_SYSOP   41678
FN_SYSOP_OLD1   71952
FTP_FIDO   0/2
FTSC_PUBLIC   1472/13598
FUNNY   0/4886
GENEALOGY.EUR   0/71
GET_INFO   105
GOLDED   0/408
HAM   0/16069
HOLYSMOKE   0/6791
HOT_SITES   0/1
HTMLEDIT   0/71
HUB203   466
HUB_100   264
HUB_400   39
HUMOR   0/29
IC   0/2851
INTERNET   0/424
INTERUSER   0/3
IP_CONNECT   719
JAMNNTPD   0/233
JAMTLAND   0/47
KATTY_KORNER   0/41
LAN   0/16
LINUX-USER   0/19
LINUXHELP   0/1155
LINUX   0/22090
LINUX_BBS   0/957
mail   18.68
mail_fore_ok   249
MENSA   0/341
MODERATOR   0/102
MONTE   0/992
MOSCOW_OKLAHOMA   0/1245
MUFFIN   0/783
MUSIC   0/321
N203_STAT   924
N203_SYSCHAT   313
NET203   321
NET204   69
NET_DEV   0/10
NORD.ADMIN   0/101
NORD.CHAT   0/2572
NORD.FIDONET   189
NORD.HARDWARE   0/28
NORD.KULTUR   0/114
NORD.PROG   0/32
NORD.SOFTWARE   0/88
NORD.TEKNIK   0/58
NORD   0/453
OCCULT_CHAT   0/93
OS2BBS   0/787
OS2DOSBBS   0/580
OS2HW   0/42
OS2INET   0/37
OS2LAN   0/134
OS2PROG   0/36
OS2REXX   0/113
OS2USER-L   207
OS2   0/4786
OSDEBATE   0/18996
PASCAL   0/490
PERL   0/457
PHP   0/45
POINTS   0/405
POLITICS   0/29554
POL_INC   0/14731
PSION   103
R20_ADMIN   1121
R20_AMATORRADIO   0/2
R20_BEST_OF_FIDONET   13
R20_CHAT   0/893
R20_DEPP   0/3
R20_DEV   399
R20_ECHO2   1379
R20_ECHOPRES   0/35
R20_ESTAT   0/719
R20_FIDONETPROG...
...RAM.MYPOINT
  0/2
R20_FIDONETPROGRAM   0/22
R20_FIDONET   0/248
R20_FILEFIND   0/24
R20_FILEFOUND   0/22
R20_HIFI   0/3
R20_INFO2   3207
R20_INTERNET   0/12940
R20_INTRESSE   0/60
R20_INTR_KOM   0/99
R20_KANDIDAT.CHAT   42
R20_KANDIDAT   28
R20_KOM_DEV   112
R20_KONTROLL   0/13259
R20_KORSET   0/18
R20_LOKALTRAFIK   0/24
R20_MODERATOR   0/1852
R20_NC   76
R20_NET200   245
R20_NETWORK.OTH...
...ERNETS
  0/13
R20_OPERATIVSYS...
...TEM.LINUX
  0/44
R20_PROGRAMVAROR   0/1
R20_REC2NEC   534
R20_SFOSM   0/340
R20_SF   0/108
R20_SPRAK.ENGLISH   0/1
R20_SQUISH   107
R20_TEST   2
R20_WORST_OF_FIDONET   12
RAR   0/9
RA_MULTI   106
RA_UTIL   0/162
REGCON.EUR   0/2056
REGCON   0/13
SCIENCE   0/1206
SF   0/239
SHAREWARE_SUPPORT   0/5146
SHAREWRE   0/14
SIMPSONS   0/169
STATS_OLD1   0/2539.065
STATS_OLD2   0/2530
STATS_OLD3   0/2395.095
STATS_OLD4   0/1692.25
SURVIVOR   0/495
SYSOPS_CORNER   0/3
SYSOP   0/84
TAGLINES   0/112
TEAMOS2   0/4530
TECH   0/2617
TEST.444   0/105
TRAPDOOR   0/19
TREK   0/755
TUB   0/290
UFO   0/40
UNIX   0/1316
USA_EURLINK   0/102
USR_MODEMS   0/1
VATICAN   0/2740
VIETNAM_VETS   0/14
VIRUS   0/378
VIRUS_INFO   0/201
VISUAL_BASIC   0/473
WHITEHOUSE   0/5187
WIN2000   0/101
WIN32   0/30
WIN95   0/4288
WIN95_OLD1   0/70272
WINDOWS   0/1517
WWB_SYSOP   0/419
WWB_TECH   0/810
ZCC-PUBLIC   0/1
ZEC   4

 
4DOS   0/134
ABORTION   0/7
ALASKA_CHAT   0/506
ALLFIX_FILE   0/1313
ALLFIX_FILE_OLD1   0/7997
ALT_DOS   0/152
AMATEUR_RADIO   0/1039
AMIGASALE   0/14
AMIGA   0/331
AMIGA_INT   0/1
AMIGA_PROG   0/20
AMIGA_SYSOP   0/26
ANIME   0/15
ARGUS   0/924
ASCII_ART   0/340
ASIAN_LINK   0/651
ASTRONOMY   0/417
AUDIO   0/92
AUTOMOBILE_RACING   0/105
BABYLON5   0/17862
BAG   135
BATPOWER   0/361
BBBS.ENGLISH   0/382
BBSLAW   0/109
BBS_ADS   0/5290
BBS_INTERNET   0/507
BIBLE   0/3563
BINKD   0/1119
BINKLEY   0/215
BLUEWAVE   0/2173
CABLE_MODEMS   0/25
CBM   0/46
CDRECORD   0/66
CDROM   0/20
CLASSIC_COMPUTER   0/378
COMICS   0/15
CONSPRCY   0/899
COOKING   32712
COOKING_OLD1   0/24719
COOKING_OLD2   0/40862
COOKING_OLD3   0/37489
COOKING_OLD4   0/35496
COOKING_OLD5   9370
C_ECHO   0/189
C_PLUSPLUS   0/31
DIRTY_DOZEN   0/201
DOORGAMES   0/2053
DOS_INTERNET   0/196
duplikat   6002
ECHOLIST   0/18295
EC_SUPPORT   0/318
ELECTRONICS   0/359
ELEKTRONIK.GER   1534
ENET.LINGUISTIC   0/13
ENET.POLITICS   0/4
ENET.SOFT   0/11701
ENET.SYSOP   33888
ENET.TALKS   0/32
ENGLISH_TUTOR   0/2000
EVOLUTION   0/1335
FDECHO   0/217
FDN_ANNOUNCE   0/7068
FIDONEWS   24099
FIDONEWS_OLD1   0/49742
FIDONEWS_OLD2   0/35949
FIDONEWS_OLD3   0/30874
Möte FTSC_PUBLIC, 13598 texter
 lista första sista föregående nästa
Text 1055, 327 rader
Skriven 2007-10-14 00:34:04 av Mithgol the Webmaster (2:5063/88)
Ärende: [6/11] FidoURL.txt
==========================
* originally in FTSC_Public
* also sent to GanjaNet.Local
* also sent to Ru.Fido.WWW
* also sent to Ru.FTN.Develop
* also sent to SU.FidoTech
* also sent to Titanic.Best

textsection 6 of 11 of file FidoURL.txt
textbegin.section

          7.2.1.2.1.1. Empty values
          -+-----------------------

            Any of the six values (year, month, day, hour, minute
            and/or second) MAY be empty in this form of the filter;
            it means that the corresponding part of the DateTime of
            the message is not checked. The adjacent separators ("/",
            "T", ":") MAY also be skipped; however, to maintain some
            difference between the appearance of two-digit values of
            <Month>, <Day>, <Hour>, <Minute> and <Second>, the
            following rules are established.

            Each of the separators between the two non-empty adjacent
            values MUST be present. (It's obvious, but still worth
            mentioning anyway.)

            If the <Second> value is not empty, the preceding colons
            (":") MUST be present.

            Example:

               area://Ru.FTN.Develop/?time=::54

            If the <Minute> value is not empty, the preceding colon
            (":") MUST be present.

            Example:

               area://Ru.FTN.Develop/?time=:56

            If the <Hour> value is not empty, then either the
            succeeding colon (":") or the preceding time separator
            ("T") MUST be present.

            Examples:

               area://Ru.FTN.Develop/?time=T15
               area://Ru.FTN.Develop/?time=15:

            If the <Day> value is not empty, then either the preceding
            slashes ("/") or the succeeding time separator ("T") MUST
            be present.

            Examples:

               area://Ru.FTN.Develop/?time=18T
               area://Ru.FTN.Develop/?time=2007//18

            If the <Month> value is not empty, then either the
            preceding slash ("/") or the succeeding slash MUST be
            present.

            Examples:

               area://Ru.FTN.Develop/?time=2007/08
               area://Ru.FTN.Develop/?time=08/

        7.2.1.2.2. Upper limit
        -+--------------------

          This variant of a "time" filter's value has the following
          form:

          -<Year>/<Month>/<Day>T<Hour>:<Minute>:<Second>

          (Notice the "-" character before the values.)

          Example:

             area://Ru.FTN.Develop/?time=-2007/08/18T15:56:54

          The number of digits and the meaning of the six values are
          the same as for the single moment (see section 7.2.1.2.1).

          A message from the initial message set appears in the
          filtered set (defined by the given upper limit) if
          and only if the message's date and time value is not greater
          than the date and time value given by the filter. All the
          six values of message's date and time (year, month, day,
          hour, minute and second) are checked in the following order:

          1) Message's year is compared with filter's year.
             If message's year is greater than filter's year,
             the message MUST NOT appear in the filtered set.
             If message's year is lesser than filter's year,
             the message MUST appear in the filtered set.
             If message's year is equal to the filter's year,
             proceed to the next step.

          2) Message's month is compared with filter's month.
             If message's month is greater than filter's month,
             the message MUST NOT appear in the filtered set.
             If message's month is lesser than filter's month,
             the message MUST appear in the filtered set.
             If message's month is equal to the filter's month,
             proceed to the next step.

          3) Message's day is compared with filter's day.
             If message's day is greater than filter's day,
             the message MUST NOT appear in the filtered set.
             If message's day is lesser than filter's day,
             the message MUST appear in the filtered set.
             If message's day is equal to the filter's day,
             proceed to the next step.

          4) Message's hour is compared with filter's hour.
             If message's hour is greater than filter's hour,
             the message MUST NOT appear in the filtered set.
             If message's hour is lesser than filter's hour,
             the message MUST appear in the filtered set.
             If message's hour is equal to the filter's hour,
             proceed to the next step.

          5) Message's minute is compared with filter's minute.
             If message's minute is greater than filter's minute,
             the message MUST NOT appear in the filtered set.
             If message's minute is lesser than filter's minute,
             the message MUST appear in the filtered set.
             If message's minute is equal to the filter's minute,
             proceed to the next step.

          6) Message's second is compared with filter's second.
             If message's second is greater than filter's second,
             the message MUST NOT appear in the filtered set.
             If message's second is lesser or equal to the filter's
             second, the message MUST appear in the filtered set.

          The first step of the check, as well as several next steps,
          MAY be skipped if the corresponding leftmost values are
          empty (see the next subsection).

          Unlike in the single moment form, the values of the upper
          limit form of a "time" filter MAY NOT be empty in arbitrary
          order; however, the leftmost values MAY be emptied from left
          to right, and the rightmost values MAY be emptied from right
          to left.

          7.2.1.2.2.1. Empty leftmost values
          -+--------------------------------

            The <Year> value MAY be empty, and in that case the first
            step of the above checking MUST be skipped, as if
            message's year and filter's year were equal.

            If the <Year> value is empty, the <Month> value MAY also
            be empty, and in that case the second step of the above
            checking MUST also be skipped, as if message's month and
            filter's month were equal.

            If the <Year> and <Month> values are empty, the <Day>
            value MAY also be empty, and in that case the third step
            of the above checking MUST also be skipped, as if
            message's day and filter's day were equal.

            If the <Year> and <Month> and <Day> values are empty, the
            <Hour> value MAY also be empty, and in that case the
            fourth step of the above checking MUST also be skipped,
            as if message's hour and filter's hour were equal.

            If the <Year> and <Month> and <Day> and <Hour> values are
            empty, the <Minute> value MAY also be empty, and in that
            case the fifth step of the above checking MUST also be
            skipped, as if message's minute and filter's minute were
            equal.

            To find out whether a separator ("/", or "T", or ":") MAY
            be skipped, consult the subsection 7.2.1.2.1.1: the rules
            on that matter are the same here.

            Example:

               area://Ru.FTN.Develop/?time=-18T15:56:54

                  This URL designates the messages that were written
                  (in Ru.FTN.Develop echomail area) either before
                  the 18th day of any month in any year, or not after
                  15:56:54 of the 18th day.

          7.2.1.2.2.2. Empty rightmost values
          -+---------------------------------

            The <Second> value MAY be empty, and in that case
            the <Second> value is assumed to be 60.

            If the <Second> value is empty, the <Minute> value MAY
            also be empty, and in that case the <Minute>:<Second>
            value is assumed to be 59:60.

            If the <Second> and <Minute> values are empty, the <Hour>
            value MAY also be empty, and in that case
            the <Hour>:<Minute>:<Second> value is assumed to be
            23:59:60.

            If the <Second> and <Minute> and <Hour> values are empty,
            the <Day> value MAY also be empty, and in that case
            the <Day>T<Hour>:<Minute>:<Second> value is assumed to be
            31T23:59:60.

            If the <Second> and <Minute> and <Hour> and <Day> values
            are empty, the <Month> value MAY also be empty, and
            in that case the <Month>/<Day>T<Hour>:<Minute>:<Second>
            value is assumed to be 12/31T23:59:60.

            None of the above assumed values fail the corresponding
            steps of the checking described above; the corresponding
            steps SHOULD be just skipped if the rightmost values are
            empty: if such a step is reached after the previous steps,
            then the tested message MUST appear is the filtered set.

            The leftmost values and the rightmost values MAY be empty
            simultaneously; however, some non-empty values (just one,
            or more) MUST appear in this form of the filter.

            To find out whether a separator ("/", or "T", or ":") MAY
            be skipped, consult the subsection 7.2.1.2.1.1: the rules
            on that matter are the same here.

            Example:

               area://Ru.FTN.Develop/?time=-05/31

                  This URL designates the messages that were written
                  (in Ru.FTN.Develop echomail area) before the summer
                  in any year. It is equivalent to the following form:

               area://Ru.FTN.Develop/?time=-05/31T23:59:60

        7.2.1.2.3. Lower limit
        -+--------------------

          This variant of a "time" filter's value has the following
          form:

          <Year>/<Month>/<Day>T<Hour>:<Minute>:<Second>-

          (Notice the "-" character after the values.)

          Example:

             area://Ru.FTN.Develop/?time=2007/08/18T15:56:54-

          The number of digits and the meaning of the six values are
          the same as for the single moment (see section 7.2.1.2.1).

          A message from the initial message set appears in the
          filtered set (defined by the given lower limit) if
          and only if the message's date and time value is not lesser
          than the date and time value given by the filter. All the
          six values of message's date and time (year, month, day,
          hour, minute and second) are checked in the following order:

          1) Message's year is compared with filter's year.
             If message's year is greater than filter's year,
             the message MUST appear in the filtered set.
             If message's year is lesser than filter's year,
             the message MUST NOT appear in the filtered set.
             If message's year is equal to the filter's year,
             proceed to the next step.

          2) Message's month is compared with filter's month.
             If message's month is greater than filter's month,
             the message MUST appear in the filtered set.
             If message's month is lesser than filter's month,
             the message MUST NOT appear in the filtered set.
             If message's month is equal to the filter's month,
             proceed to the next step.

          3) Message's day is compared with filter's day.
             If message's day is greater than filter's day,
             the message MUST appear in the filtered set.
             If message's day is lesser than filter's day,
             the message MUST NOT appear in the filtered set.
             If message's day is equal to the filter's day,
             proceed to the next step.

          4) Message's hour is compared with filter's hour.
             If message's hour is greater than filter's hour,
             the message MUST appear in the filtered set.
             If message's hour is lesser than filter's hour,
             the message MUST NOT appear in the filtered set.
             If message's hour is equal to the filter's hour,
             proceed to the next step.

          5) Message's minute is compared with filter's minute.
             If message's minute is greater than filter's minute,
             the message MUST appear in the filtered set.
             If message's minute is lesser than filter's minute,
             the message MUST NOT appear in the filtered set.
             If message's minute is equal to the filter's minute,
             proceed to the next step.

          6) Message's second is compared with filter's second.
             If message's second is lesser than filter's second,
             the message MUST NOT appear in the filtered set.
             If message's second is greater or equal to the filter's
             second, the message MUST appear in the filtered set.

          The first step of the check, as well as several next steps,
          MAY be skipped if the corresponding leftmost values are
          empty (see the next subsection).

          Unlike in the single moment form, the values of the lower
          limit form of a "time" filter MAY NOT be empty in arbitrary
          order; however, the leftmost values MAY be emptied from left
          to right, and the rightmost values MAY be emptied from right
          to left.

textend.section



With best Fidonet 2.0 regards,
Mithgol the Webmaster.                 [Real nodelisted name: Sergey Sokoloff]

... 2. My ventilation ducts will be too small to crawl through.
--- Come with me in the twilight of a summer night for a while...  .hack//SIGN
 * Origin: Be careful, the paranoid ones are always wathing you!.. (2:5063/88)