Добро пожаловать, Гость. Пожалуйста авторизуйтесь здесь.
FGHIGate на GaNJa NeTWoRK ST@Ti0N - Просмотр сообщения в эхоконференции GANJANET.LOCAL
Введите FGHI ссылку:


Присутствуют сообщения из эхоконференции GANJANET.LOCAL с датами от 13 Oct 05 22:03:42 до 05 Aug 17 10:35:42, всего сообщений: 3030
Ответить на сообщение К списку сообщений Предыдущее сообщение Следующее сообщение
= Сообщение: 1940 из 3030 =================================== GANJANET.LOCAL =
От   : Mithgol the Webmaster            2:5063/88          10 Feb 07 13:51:30
Кому : All                                                 10 Feb 07 13:51:30
Тема : [6/11] FidoURL.txt
FGHI : area://GANJANET.LOCAL?msgid=2:5063/88+45cda3ff
На   : area://GANJANET.LOCAL?msgid=2:5063/88+45cd9f43
= Кодировка сообщения определена как: CP866 ==================================
==============================================================================
* изначально написано в эхоконференцию FTSC_PUBLIC
* также было отослано в эхоконференцию CU.TALK
* также было отослано в эхоконференцию GANJANET.LOCAL
* также было отослано в эхоконференцию RU.FIDO.WWW
* также было отослано в эхоконференцию RU.FIDONET.TODAY
* также было отослано в эхоконференцию RU.FTN.DEVELOP
* также было отослано в эхоконференцию SU.FIDOTECH
* также было отослано в эхоконференцию TITANIC.BEST

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

    6.2.4. Relative "areafix:" URLs
    -+-----------------------------

      If an areafix URL is published in the same echomail area that is
      involved in the designated action, then the <echomail-area-name>
      MAY be omitted.

      Examples:

         ...if you don't like this area, areafix:?unsubscribe>https://fido.g0x.ru/?areafix:?unsubscribe>areafix:?unsubscribe from it!

         ...if you feel that some echomail messages is missing, then
         your current uplink is not reliable. You'd better subscribe
         using areafix:?uplink=2:5063/88>https://fido.g0x.ru/?areafix:?uplink=2:5063/88>areafix:?uplink=2:5063/88

      If such a relative "areafix:" URL is encountered outside of Fido
      echomail, then the URL is not valid.

  6.3. "echomail:" scheme
  -+---------------------

    Echomail is an important and powerful force in Fidonet. Echomail
    is, by definition, a broadcast medium. See echomail specifications
    in FTS-0004.

    An echomail area is a shared base of messages that have common
    areatag (area identifier) and are distributed through Fidonet
    via hierarchical and/or p2p-alike connections between individual
    Fidonet systems (nodes and points).

    The "echomail:" scheme is used to designate a Fidonet echomail
    area as a location where echomail can be sent to.

    The character "/" has its literal meaning for this scheme.

    The echomail URLs take the form:

    echomail:<areatag>?<optional-part>

    Examples:

       echomail:Ru.FTN.Develop>https://fido.g0x.ru/?echomail:Ru.FTN.Develop>echomail:Ru.FTN.Develop
       echomail:Ru.FTN.WinSoft>https://fido.g0x.ru/?echomail:Ru.FTN.WinSoft>echomail:Ru.FTN.WinSoft
       echomail:FTSC_Public>https://fido.g0x.ru/?echomail:FTSC_Public>echomail:FTSC_Public

    When an "echomail:" hyperlink is used (clicked, followed),
    an echomail message composer SHOULD be launched.

    6.3.1. Optional parameter "to"
    -+----------------------------

      The "to" optional parameter is used to designate the name of
      echomail addressee. Its default value SHOULD be "All", meaning
      all of the area audience. The default value MAY also be given by
      some user setting of the echomail composer used to process
      the "echomail:" URL.

      Examples:

         echomail:Ru.FTN.Develop?to=Mithgol+the+Webmaster>https://fido.g0x.ru/?echomail:Ru.FTN.Develop?to=Mithgol+the+Webmaster>echomail:Ru.FTN.Develop?to=Mithgol+the+Webmaster
         echomail:Ru.FTN.WinSoft?to=Trooper>https://fido.g0x.ru/?echomail:Ru.FTN.WinSoft?to=Trooper>echomail:Ru.FTN.WinSoft?to=Trooper
         echomail:Ru.Fidonet.Today?to=Alex%20Kocharin>https://fido.g0x.ru/?echomail:Ru.Fidonet.Today?to=Alex%20Kocharin>echomail:Ru.Fidonet.Today?to=Alex%20Kocharin

    6.3.2. Optional parameter "subject"
    -+---------------------------------

      The "subject" optional parameter is used to designate
      the subject line of the echomail message composed. Its default
      value is empty; the default value MAY also be determined by
      some user setting of the echomail composer used to process
      the "echomail:" URL.

      Examples:

         echomail:SU.Chainik?subject=How+do+I+set+up+a+tosser%3F>https://fido.g0x.ru/?echomail:SU.Chainik?subject=How+do+I+set+up+a+tosser%3F>echomail:SU.Chainik?subject=How+do+I+set+up+a+tosser%3F
         echomail:Ru.GoldEd?subject=GoldEd%2b+changelog>https://fido.g0x.ru/?echomail:Ru.GoldEd?subject=GoldEd%2b+changelog>echomail:Ru.GoldEd?subject=GoldEd%2b+changelog
         echomail:R50.Bone?to=R50BM&subject=%D0%AD%D1%85%D0%B8%3F>https://fido.g0x.ru/?echomail:R50.Bone?to=R50BM&subject=%D0%AD%D1%85%D0%B8%3F>echomail:R50.Bone?to=R50BM&subject=%D0%AD%D1%85%D0%B8%3F

    6.3.3. Optional parameter "subj"
    -+------------------------------

      The "subj" optional parameter is used as a shorter equivalent to
      the "subject" parameter. If the optional parameter "subject" is
      not present in a given URL, the value of "subj" parameter MUST
      be taken instead the value of "subject", provided that "subj"
      is present.

      Example:

 echomail:FTSC_Public?subj=Long+subject+may+avoid+line+wrapping+limits>https://fido.g0x.ru/?echomail:FTSC_Public?subj=Long+subject+may+avoid+line+wrapping+limits>echomail:FTSC_Public?subj=Long+subject+may+avoid+line+wrapping+limits

    6.3.4. Optional parameter "from"
    -+------------------------------

      The "from" optional parameter is used to designate the name of
      the echomail letter's author. Its default value is usually
      defined within the echomail composer settings.

      Examples:

         echomail:Ru.Moderator?to=R50EC&from=Moderator+of+XXX.chat>https://fido.g0x.ru/?echomail:Ru.Moderator?to=R50EC&from=Moderator+of+XXX.chat>echomail:Ru.Moderator?to=R50EC&from=Moderator+of+XXX.chat
         echomail:Ru.Fidonet.Yo?from=Moderator&subject>https://fido.g0x.ru/?echomail:Ru.Fidonet.Yo?from=Moderator&subjectechomail:Ru.Fidonet.Yo?from=Moderator&subject color=white>=*+*+*+Rules

    6.3.5. Optional parameter "body"
    -+------------------------------

      The "body" optional parameter is used to designate the body part
      of the echomail message composed. (Its default value is empty.)
      The echomail composer MAY wrap the value of "body" parameter in
      elements of some user-defined message template (user-defined
      signature, greeting, etc.)

      Examples:

         echomail:Ru.FTN.Develop?subj=FGHI&body=Fidonet+2.0+approached>https://fido.g0x.ru/?echomail:Ru.FTN.Develop?subj=FGHI&body=Fidonet+2.0+approached>echomail:Ru.FTN.Develop?subj=FGHI&body=Fidonet+2.0+approached
         echomail:400.Link?subj=Interface&body=A+much+better+option%3F>https://fido.g0x.ru/?echomail:400.Link?subj=Interface&body=A+much+better+option%3F>echomail:400.Link?subj=Interface&body=A+much+better+option%3F
         echomail:GSS.ParToss?body=Will+it+ever+toss+JAM%3F&subj=Hopes>https://fido.g0x.ru/?echomail:GSS.ParToss?body=Will+it+ever+toss+JAM%3F&subj=Hopes>echomail:GSS.ParToss?body=Will+it+ever+toss+JAM%3F&subj=Hopes

7. Fidonet URL schemes designating objects
-+----------------------------------------

  The URL schemes enumerated below designate named objects
  that can be accessed, read, browsed, etc.

  According to the above section of delimiter guidelines,
  the "://" character triplet (and not the ":" character)
  SHOULD be used as the delimiter after <scheme> part of such URLs.

  7.1. The <object-path> part of URL. Possible forms of the path
  -+------------------------------------------------------------

    Sometimes Fidonet is regarded as a text-only network. At least,
    Fidonet is notable for its very few means of transferring binary
    data. File echoes do not enjoy an audience comparable to that
    of traditional echo areas; file requests and attaches are almost
    never routed between nodes. In that somewhat harsh circumstances,
    however, several means of encoding and embedding the binary data
    inside text messages exist. Files (and sometimes whole directories
    of files) are packed to economize traffic; some of the resulting
    archives are encoded in text lines that are sent via text-only
    means of communication -- in echomail, in netmail.

    That's why all the following Fidonet URL schemes must have some
    common method to designate, if necessary, an object inside packed
    (archive) files and/or embedded in some text. The <required-part>
    of their URL always ends with "/<object-path>", and so URLs are
    written as follows:

    <scheme>://<basic-required-part>/<object-path>?<optional-part>

    The character "/" always has its reserved meaning in <object-path>
    part of URL; this character plays the role of delimiter between
    parts of the path.

    The <object-path> part of URL takes one of the following forms:

    <object-name>

       If <object-path> contains just a name of some object, the URL
       designates that object. The object itself is embedded or is
       contained inside the resource specified by the rest of URL:

            <scheme>://<basic-required-part>?<optional-part>

    <object-name>/

        The named object itself is a container (e.g. packed archive).
        The URL designates the root directory of that container.

     <object-name>/<needed-object>

        The <object-name> is a container (e.g. a packed archive),
        and its root directory contains <needed-object>; the URL
        designates that <needed-object>. If <needed-object>
        is a directory (i.e. not a file), the <object-path>
        is equivalent to its following form,
        <object-name>/<needed-object>/

     <object-name>/<needed-object>/

        The <needed-object> inside <object-name> is either a container
        itself (e.g. a packed archive file) or a subdirectory inside
        <object-name> container. The URL designates the contents of
        <needed-object> container or directory. (If <needed-object>
        is a container with subdirectories, the URL designate the
        contents of its root directory.)

     <object-name>/<elem1>/<elem2>/.../<elemN>/<needed-object>
     or
     <object-name>/<elem1>/<elem2>/.../<elemN>/<needed-object>/

        The <object-name> contains a hierarchy as deep as N elements,
        they're either subdirectories or container objects (packed
        archive files, for example). It is necessary to enter those
        containers and browse into directories, one after another,
        in the given order. The innermost element contains the object
        <needed-object>. The URL designates either the object itself
        (if trailing slash is missing and <needed-object> is not
        a subdirectory) or its contents (if <needed-object> is
        a subdirectory, that directory's contents is designated;
        otherwise, <needed-object>/ means the root directory of
        <needed-object>).

textend.section


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

... 78. I will not tell my Legions of Terror "And he must be taken alive!"
--- Orcs are near, All! My Golded 1.1.5-b20060515 is gleaming!..
* Origin: And the Soviets ── waist-deep in the snow ── marched in (2:5063/88)

К главной странице гейта
Powered by NoSFeRaTU`s FGHIGate
Открытие страницы: 0.027537 секунды