{"id":531,"date":"2024-03-20T18:01:24","date_gmt":"2024-03-20T17:01:24","guid":{"rendered":"https:\/\/sp4thk.elfro.pl\/?page_id=531"},"modified":"2026-01-04T08:10:47","modified_gmt":"2026-01-04T07:10:47","slug":"logbook-2","status":"publish","type":"page","link":"https:\/\/sp4thk.elfro.pl\/index.php\/en\/logbook-2\/","title":{"rendered":"LogBook"},"content":{"rendered":"\n

The second main module of the program, and in many cases the first one, is the LogBook, which allows you to record communications. It may or may not work in conjunction with a transceiver.<\/p>\n\n\n\n

You can also set it as the main program window if you want to use only logs without connecting to the radio.<\/p>\n\n\n\n

The idea behind the creation of the log was field activations in various programs. For now, I have experience with the POTA program, so other programs may still require testing and corrections.<\/p>\n\n\n\n

Log does not need databases, the files are saved in text form in the CSV format and can be easily opened in Excel, for example.<\/p>\n\n\n\n

This is a simple and quick way to save data that does not require filtering or various types of queries. It is good practice to save each activation in a separate log created for a specific activation. This protects against failure and speeds up the program’s operation.<\/p>\n\n\n\n

We run the logbook from Menu->Log Book with the POTA\/SOTA cluster\u2026.<\/p>\n\n\n\n

Other startup and configuration methods are described in the Installation<\/a> section.<\/p>\n\n\n\n

You can easily move between the necessary fields, i.e. sign, reports, frequency, etc., using the Tab or Enter key.<\/p>\n\n\n\n

Required fields are highlighted in „blue”<\/p>\n\n\n\n

The program marks required fields in „red” if they are not completed.<\/p>\n\n\n\n

When working with a cluster, clicking on a cluster element will fill the fields with data from the cluster. We start a conversation (if we succeed). We press enter several times to accept, correct the RST reports if necessary, and the log is saved. You can also immediately click on Save to logbook. If the date is empty, it will be filled in automatically.<\/p>\n\n\n\n

When not saving, click on another record in the cluster or the Clr button. \u2013 data cleaner. There are two Clr buttons. At the sign, he cleans as much as he can. For a band, it only clears the frequency, band and mode.<\/p>\n\n\n\n

\ud83d\uddfa\ufe0fLogBook main window:<\/strong><\/p>\n\n\n

\n
\"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button><\/figure>\n<\/div>\n\n\n

Next to the date and time, one or two icons are displayed.
The date and time are updated automatically, but this behavior can be paused.<\/p>\n\n\n\n

Updating the time is stopped by entering edit mode (clicking on the time) or by clicking the icon.<\/p>\n\n\n\n

Icon meanings:<\/strong><\/p>\n\n\n\n

\"\"

 Time updating is disabled<\/p><\/div>\n

<\/div>\n
\"\"

 Time updating is enabled<\/p><\/div>\n

<\/div>\n
\"\"

 Inserts the current time (does not start automatic updating)<\/p><\/div>\n

<\/div>\n\n\n\n

At first, the multitude of options may be overwhelming, but after a while everything will become clear.<\/p>\n\n\n\n

I suggest you set the configuration first. To do this, click on the Settings icon:<\/p>\n\n\n

\n
\"\"<\/figure>\n<\/div>\n\n\n

A window with options will appear:<\/p>\n\n\n\n

\u2699\ufe0f Logbook Configuration<\/strong><\/p>\n\n\n\n

Most options are intuitive, so the description focuses on the more advanced or less obvious settings.<\/p>\n\n\n\n

\"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button><\/figure>\n\n\n\n

Logbook configuration is divided into the following sections:<\/p>\n\n\n\n

    \n
  • Logbook<\/b> \u2013 logbook name and template, user data, behavior, appearance<\/li>\n
  • QRZ<\/b> \u2013 login credentials for QRZ and how the program interacts with QRZ.<\/li>\n
  • LoTW<\/b> \u2013 configuration for cooperation with the TQSL application used by LoTW.<\/li>\n
  • eQSL<\/b> \u2013 configuration for sending QSL cards via e-mail.<\/li>\n
  • Clusters \/ Telnet<\/b> \u2013 as the name suggests, configuration of DX cluster connections.<\/li>\n
  • WSJTX \/ NTP<\/b> \u2013 support for digital mode applications (e.g. FT8) and time synchronization.<\/li>\n
  • Scheduler<\/b> \u2013 settings for automatic tasks, e.g. sending logs to QRZ or LoTW.<\/li>\n
  • Misc<\/b> \u2013 other program options: language, backups, and additional settings.<\/li>\n
  • Appearance<\/b> \u2013 program appearance: visual styles, color scheme, and font sizes.<\/li>\n
  • Map<\/b> \u2013 options for map display and QSO visualizations.<\/li>\n
  • Audio Recorder<\/b> \u2013 audio configuration and recording options.<\/li>\n
  • Wine<\/b> \u2013 visible only on Linux, used to configure the program in the Wine environment.<\/li>\n<\/ul>\n\n\n\n

    The main Logbook Configuration<\/strong> window contains the primary appearance and functionality options.<\/p>\n\n\n\n

    \ud83d\udcd8 Logbook Name<\/strong> \u2013 you can select an existing logbook from the list or enter a new name.<\/p>\n\n\n\n

    Logbooks are stored in the program\u2019s LOGBOOKS<\/strong> folder. Each logbook is kept in a separate folder named after the logbook.
    For this reason, special characters such as ? * & % * \\ \/<\/code> are not allowed in the name.
    Inside the logbook folder, there is a logbook.csv<\/code> file along with its backups (the last 11 changes<\/strong>, excluding the addition of a new QSO).<\/p>\n\n\n\n

    Logbook Template<\/strong> \u2013 the following templates are available: Standard<\/strong>, POTA<\/strong>, SOTA<\/strong>, WWFF<\/strong>, Field Day<\/strong>.
    The Logbook works essentially the same in all cases; the difference lies in the required fields<\/strong>.
    For example, for POTA<\/strong> you must enter your park reference, for SOTA<\/strong> the summit reference, etc.<\/p>\n\n\n\n

    Default Window<\/strong> \u2013 as mentioned during installation, the program can operate either as a Logbook-only<\/strong> application or with transceiver control<\/strong> enabled.<\/p>\n\n\n\n

      \n
    • If this option is enabled, the program behaves as a classic logging application.<\/li>\n\n\n\n
    • If it is disabled, the default main window is the radio control window<\/strong>, which can cooperate with the Logbook.<\/li>\n<\/ul>\n\n\n\n

      In practice, this results in three different views<\/strong>.<\/p>\n\n\n\n

      When the option is enabled:<\/strong><\/p>\n\n\n\n

        \n
      1. Only the Logbook<\/strong> window is visible.<\/li>\n<\/ol>\n\n\n\n

        When the option is disabled:<\/strong>
        2. The Radio Control<\/strong> window
        3. The Radio Control<\/strong> window together with the Logbook<\/strong> window<\/p>\n\n\n\n

        Why this somewhat unusual approach?<\/h3>\n\n\n\n
          \n
        • Radio control is not always required.<\/li>\n\n\n\n
        • Enabling radio control initializes additional libraries, which may temporarily pause the application.
          It is more efficient to perform this initialization once at startup<\/strong> rather than every time the TRX controller window is opened.<\/li>\n<\/ul>\n\n\n\n

          <\/p>\n\n\n\n

          Configuration at first startup each day<\/strong><\/h3>\n\n\n\n

          This option is especially useful for portable and field activations<\/strong>.
          When starting a laptop in the field, the program immediately enters the configuration mode, allowing you to quickly create a new Logbook for a specific activation<\/strong>.<\/p>\n\n\n\n

          In this scenario, the option \u201cStart with Logbook selection only\u201d<\/strong> is particularly useful.<\/p>\n\n\n\n

          Hide POTA \/ SOTA fields and show statistics<\/strong><\/h3>\n\n\n\n

          To allow entering additional data required by various award programs \u2014 and because activators often participate in multiple programs at the same time \u2014 the application provides a number of dedicated input fields.<\/p>\n\n\n\n

          However, not every user participates in POTA or similar programs and may never use these fields.
          They can be hidden, and the freed space will instead display simple log statistics<\/strong>.<\/p>\n\n\n\n

          \n
          \"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button><\/figure>\n\n\n\n
          \"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button><\/figure>\n<\/figure>\n\n\n\n

          Disable clusters \u2013 offline mode<\/strong><\/p>\n\n\n\n

          When this option is enabled, the program does not attempt to connect to the internet.<\/p>\n\n\n\n

          During field activations with poor network coverage, downloading data from services such as QRZ<\/strong> or map providers may be very slow.
          With a single click, all online connections can be disabled, allowing you to perform activations without interruptions<\/strong>.<\/p>\n\n\n\n

          The next few tabs are intentionally skipped here and will be described separately.<\/p>\n\n\n\n

          \n\n\n\n

          Changing the logbook<\/strong><\/p>\n\n\n\n

          There may be situations where one logbook is already open and you want to open another one.<\/p>\n\n\n\n

          What should be done with the existing records?
          Save them, discard them, or perhaps append them to the logbook being opened?<\/p>\n\n\n\n

          When changing the logbook folder or name and clicking OK<\/strong>, the program will ask:<\/p>\n\n\n

          \n
          \"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button><\/figure>\n<\/div>\n\n\n
          \n\n\n\n

          After completing the configuration, we return to the main window.
          Its upper section contains the current QSO data<\/strong> that will be recorded.<\/p>\n\n\n\n

          There are many input fields, but only some of them are required.
          This depends on the selected award program (POTA, SOTA<\/strong>, etc.).
          Required fields are highlighted<\/strong>.<\/p>\n\n\n\n

          Why aren\u2019t unnecessary fields hidden to simplify the interface?<\/h3>\n\n\n\n

          This design allows multiple programs to be combined \u2014 for example POTA and SOTA<\/strong> \u2014 by simply filling in additional fields.<\/p>\n\n\n\n

          Close the configuration window.<\/p>\n\n\n\n

          \n\n\n\n

          \ud83d\uddfa\ufe0f Logbook Operation<\/strong><\/p>\n\n\n\n

          After entering your data in the My\u2026<\/strong> fields and adding the first log entry, these values will be saved as defaults<\/strong> for subsequent QSOs.<\/p>\n\n\n\n

          If no QSO has been added yet, the entered data can still be saved by clicking Save defaults<\/strong>, or cleared using Clear defaults<\/strong>.<\/p>\n\n\n\n

          If the logbook is connected to a radio, frequencies can also be updated directly from the radio<\/strong>.<\/p>\n\n\n

          \n
          \"\"<\/figure>\n<\/div>\n\n\n

          The lower part of the logbook window contains a list view<\/strong>.
          This list can display different types of data.<\/p>\n\n\n\n

          It can show:<\/p>\n\n\n\n

            \n
          • the list of saved QSOs from My Logbook<\/strong>, and<\/li>\n\n\n\n
          • data from POTA, SOTA, WWFF, and DX clusters<\/strong>.<\/li>\n<\/ul>\n\n\n\n

            The POTA cluster<\/strong> is additionally divided into SPOTS<\/strong> and ACTIVATIONS<\/strong>.<\/p>\n\n\n\n

            The SOTA cluster<\/strong> is divided into SPOTS<\/strong> and ALERTS<\/strong>.<\/p>\n\n\n\n

            Filtering is enabled by entering a fragment of the region or text you are interested in, for example SP<\/strong>.
            The filter is case-sensitive<\/strong>.<\/p>\n\n\n\n

            Depending on the selected display mode (Logbook or Cluster), the filter searches specific fields and checks whether they contain the entered text fragment \u2014 for example:
            SP4THK<\/strong>, SPAIN<\/strong>, ISLAND<\/strong>, SP-1234<\/strong>, or anything else containing SP<\/strong>.<\/p>\n\n\n\n

            Note:<\/strong> In some search fields, the program distinguishes between uppercase and lowercase letters.
            SP<\/strong>, sp<\/strong>, Sp<\/strong>, and sP<\/strong> are treated as different queries.<\/p>\n\n\n\n

            When a filter is active, the filtered list in the main Logbook window is displayed with a red background<\/strong>.
            This makes it immediately obvious \u2014 especially in moments of panic \u2014 where the rest of your QSOs went \ud83d\ude09
            They are not gone, they are just filtered out<\/strong>.<\/p>\n\n\n\n

            \n
            \n<\/div>\n
            Info. <\/strong><\/div>\n<\/div>
            <\/div>\n\n\n\n

            Clicking on an entry from any cluster will automatically populate the corresponding fields in the log entry area at the top of the window.<\/p>\n\n\n\n

            If the Rig (TRX) control module<\/strong> is enabled, the radio frequency will also be set automatically.<\/p>\n\n\n\n

            Depending on the configuration settings, this action may require either a single click<\/strong> or a double click<\/strong>.<\/p>\n\n\n\n

            \n
            \n<\/div>\n
            Info. <\/strong><\/div>\n<\/div>
            <\/div>\n\n\n\n

            There is no problem \u2014 it will still be treated as a single record<\/strong>.
            If you operate from multiple parks or had a contact with multiple parks, enter them separated by commas<\/strong>.
            During export, the data will be processed accordingly \u2014 split, duplicated where necessary, and divided into the appropriate output files.<\/p>\n\n\n\n

            \ud83d\udcdd QSO Editing<\/strong><\/p>\n\n\n\n

            After adding a QSO, it often turns out that something needs to be corrected \u2014 for example, a missing grid locator.<\/p>\n\n\n\n

            Simply double-click<\/strong> the selected record, and the edit window will appear:<\/p>\n\n\n\n

            \"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button><\/figure>\n\n\n\n

            All fields of the record can be edited here.
            Use the arrow buttons to move to the next<\/strong> or previous<\/strong> QSO.<\/p>\n\n\n\n

            Advanced<\/strong><\/p>\n\n\n\n

            What if all records in the log need to be changed?
            For example, if the park reference was entered incorrectly?
            Click Advanced<\/strong>:<\/p>\n\n\n\n

            \"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button><\/figure>\n\n\n\n

            Using the appropriate buttons, the value of the current field can be copied to all records<\/strong> (all remaining QSOs) in the log.<\/p>\n\n\n\n

            It is also possible to perform a bulk query to QRZ<\/strong> and automatically fill in data for all QSOs with a single click.
            This requires that QRZ login credentials have been entered beforehand.<\/p>\n\n\n\n

            You can click Settings<\/strong> to open the same configuration window that is available from the main logbook window.<\/p>\n\n\n\n

            Proceed with caution<\/strong> \u2014 the program does not verify what data is being overwritten.<\/p>\n\n\n\n

            Keep in mind that downloading data for all records from QRZ can be very time-consuming<\/strong>.<\/p>\n\n\n\n

            A backup copy of the logbook<\/strong> is created automatically \u2014 just in case.<\/p>\n\n\n\n

            \n\n\n\n

            Filtering<\/strong><\/p>\n\n\n\n

            The Logbook provides the ability to filter entries.
            This is done using the following buttons:<\/p>\n\n\n

            \n
            \"\"<\/figure>\n<\/div>\n\n\n

            Previous QSO<\/strong><\/h3>\n\n\n\n

            The first simple filter is Previous QSO<\/strong>.<\/p>\n\n\n\n

            If you enter the callsign of the correspondent, the date of the last contact<\/strong> will appear next to the Previous QSO<\/em> label.
            Clicking the Previous QSO<\/strong> button quickly enables a filter that displays all contacts with the selected station<\/strong>.<\/p>\n\n\n\n

            Set Filter<\/strong><\/h3>\n\n\n\n

            This is an advanced filtering option that allows filtering by most logbook parameters<\/strong>:<\/p>\n\n\n\n

            \"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button><\/figure>\n\n\n\n

            The number of available fields and their descriptions depend on the type of log currently in use \u2014 for example, Logbook<\/strong>, POTA Cluster<\/strong>, Telnet<\/strong>, etc.
            Different logs contain different data, which results in different filtering parameters.<\/p>\n\n\n\n

            Warning!<\/strong>
            When switching between logs and using filters specific to a given cluster type, filtering may be applied to different fields<\/strong>.<\/p>\n\n\n\n

            Warning!<\/strong>
            If more than one filter parameter is selected (for example band<\/strong> and mode<\/strong>), special attention must be paid to the filter logic<\/strong> being used.<\/p>\n\n\n

            \n
            \"\"<\/figure>\n<\/div>\n\n\n

            OR filter<\/strong><\/h3>\n\n\n\n

            The OR<\/strong> filter works as a logical OR<\/em>.
            For example, if you select 40 m band<\/strong> and SSB mode<\/strong>, the filter will display:<\/p>\n\n\n\n

              \n
            • all entries from the 40 m band<\/strong> (SSB, CW, DIGI, etc.), and<\/li>\n\n\n\n
            • all SSB<\/strong> entries from all bands<\/strong>, for example also from 20 m<\/strong>.<\/li>\n<\/ul>\n\n\n\n
              \n\n\n\n

              AND filter<\/strong><\/h3>\n\n\n\n

              The AND<\/strong> filter works as a logical AND<\/em>.
              For example, if you select 40 m band<\/strong> and SSB mode<\/strong>, only entries from the 40 m band in SSB mode<\/strong> will be displayed.
              All other entries will be excluded.<\/p>\n\n\n\n

              \n\n\n\n

              Case sensitivity<\/strong><\/h3>\n\n\n\n

              The filter can be case-sensitive<\/strong> or case-insensitive<\/strong>.<\/p>\n\n\n\n

              When case sensitivity is enabled, for example:
              Poland<\/strong>, POLAND<\/strong>, and POland<\/strong> are treated as different values<\/strong>.<\/p>\n\n\n\n

              \n\n\n\n

              Default matching<\/strong><\/h3>\n\n\n\n

              Exact match<\/strong>
              The field must match the value exactly.
              For example, SSB<\/strong> is different from SSB USB<\/strong>.<\/p>\n\n\n\n

              Starts with<\/strong>
              The field must start with the specified value.
              For example, Pol<\/strong> will match Pol<\/em>, Polska<\/em>, Poland<\/em>, Pologne<\/em>.<\/p>\n\n\n\n

              Ends with<\/strong>
              The field must end with the specified value.
              For example, land<\/strong> will match Poland<\/em>, Holland<\/em>, England<\/em>, land<\/em>.<\/p>\n\n\n\n

              Contains text<\/strong>
              The field must contain the specified text.
              For example, la<\/strong> will match Poland<\/em>, Alaska<\/em>, la<\/em>.<\/p>\n\n\n\n

              Control characters<\/strong><\/h3>\n\n\n\n

              In addition to the default matching modes, you can use control characters<\/strong> in filter fields.
              For example, by entering patterns with *<\/code> in the Country<\/em> field:<\/p>\n\n\n\n

                \n
              • Pol*<\/code><\/li>\n\n\n\n
              • *land<\/code><\/li>\n\n\n\n
              • *la*<\/code><\/li>\n<\/ul>\n\n\n\n

                Using !<\/code> as the first character<\/strong> applies negation<\/strong> to the filter.
                For example, !Poland<\/code> will display all countries except Poland<\/strong>.<\/p>\n\n\n\n

                You can also use &<\/code> or |<\/code> for logical AND<\/strong> \/ OR<\/strong> combinations (evaluated in the order they appear).<\/p>\n\n\n\n

                Examples:<\/strong><\/p>\n\n\n\n

                  \n
                • Polska|Nor*<\/code> \u2013 select countries named Polska<\/em> and all countries starting with Nor<\/em> (e.g. Norwegia<\/em>, Norway<\/em>).<\/li>\n\n\n\n
                • !Polska|!Nor*<\/code> \u2013 select countries other than Polska<\/em> and all countries not<\/strong> starting with Nor<\/em>.<\/li>\n\n\n\n
                • SP4*|SP5*<\/code> \u2013 all callsigns starting with SP4<\/strong> or SP5<\/strong>.<\/li>\n\n\n\n
                • SP4*&!*ABC<\/code> \u2013 all callsigns starting with SP4<\/strong> and not<\/strong> ending with ABC<\/strong>.<\/li>\n<\/ul>\n\n\n\n

                  The characters &<\/code>, |<\/code>, *<\/code>, and !<\/code> cannot be used in frequency filters<\/strong>,
                  with the exception of !<\/code> at the beginning, which negates the entire value (e.g. !DIGI<\/code>).<\/p>\n\n\n\n

                  In frequency fields, you can use a comma as a separator<\/strong>, for example:
                  DIGI FT8, DIGI FT4, 7100<\/code>.<\/p>\n\n\n\n

                  Frequency filtering<\/strong><\/h3>\n\n\n\n

                  Frequency can be filtered in additional ways.
                  You can enter a single frequency<\/strong>, for example 7100<\/code>, or a range<\/strong>, such as 7100\u20137200<\/code>.
                  Multiple ranges can be specified using commas, for example:
                  7100\u20137200, 14000\u201314100<\/code>.<\/p>\n\n\n\n

                  Among logical operators, only the !<\/code> (NOT)<\/strong> operator is supported here.
                  For example, !7100\u20137200<\/code> will display all entries outside<\/strong> the specified range.<\/p>\n\n\n\n

                  You can also specify a frequency with an offset<\/strong>, for example:
                  7100+100<\/code>, which is equivalent to 7100\u20137200<\/code>.<\/p>\n\n\n\n

                  To avoid having to manually enter frequency ranges each time, you can create macros<\/strong>.
                  To do this, click Advanced<\/strong>.<\/p>\n\n\n\n

                  Frequency macros<\/strong><\/h3>\n\n\n\n
                  \"\"<\/figure>\n\n\n\n

                  This is where macros<\/strong> are defined.
                  As shown in the attached image, for example, there is a macro that covers all FT8 frequencies<\/strong>.<\/p>\n\n\n\n

                  At the top, there is a text field containing the current frequency filter<\/strong> from the previous window.
                  As mentioned earlier, you can use frequency ranges<\/strong>, for example 7074\u20137077.5<\/code> or 7074+3.5<\/code>.<\/p>\n\n\n\n

                  The characters ,<\/code> or ;<\/code> are used to separate ranges, for example:
                  7074\u20137077.5, 14074+3.5<\/code>.<\/p>\n\n\n\n

                  You can also use user-defined macros<\/strong>, for example DIGI<\/code>.
                  Multiple macros and frequencies can be combined, for example:
                  DIGI, 7100+10, 28500\u201328600<\/code>.<\/p>\n\n\n\n

                  Text characters as well as !<\/code> and *<\/code> are not allowed<\/strong> in this field.<\/p>\n\n\n\n

                  Below is the list of macros<\/strong>. Each macro can be edited here, as shown in the attached image.<\/p>\n\n\n\n

                  Warning!<\/strong>
                  Do not confuse the upper frequency filter field<\/strong> with the macro list<\/strong> below.
                  The upper field represents your query<\/strong>, while the macro list is defined separately.<\/p>\n\n\n\n

                  Editing a macro does not<\/strong> automatically insert it into the filter query.
                  A macro must be manually entered<\/strong> into the filter field.<\/p>\n","protected":false},"excerpt":{"rendered":"

                  The second main module of the program, and in many cases the first one, is the LogBook, which allows you to record communications. It may or may not work in conjunction with a transceiver. You can also set it as the main program window if you want to use only logs without connecting to the […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-531","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/sp4thk.elfro.pl\/index.php\/wp-json\/wp\/v2\/pages\/531","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/sp4thk.elfro.pl\/index.php\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/sp4thk.elfro.pl\/index.php\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/sp4thk.elfro.pl\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/sp4thk.elfro.pl\/index.php\/wp-json\/wp\/v2\/comments?post=531"}],"version-history":[{"count":15,"href":"https:\/\/sp4thk.elfro.pl\/index.php\/wp-json\/wp\/v2\/pages\/531\/revisions"}],"predecessor-version":[{"id":1838,"href":"https:\/\/sp4thk.elfro.pl\/index.php\/wp-json\/wp\/v2\/pages\/531\/revisions\/1838"}],"wp:attachment":[{"href":"https:\/\/sp4thk.elfro.pl\/index.php\/wp-json\/wp\/v2\/media?parent=531"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}