MediaWiki API result

{
    "batchcomplete": "",
    "continue": {
        "gapcontinue": "UDPMSG3_Protocol",
        "continue": "gapcontinue||"
    },
    "warnings": {
        "main": {
            "*": "Subscribe to the mediawiki-api-announce mailing list at <https://lists.wikimedia.org/postorius/lists/mediawiki-api-announce.lists.wikimedia.org/> for notice of API deprecations and breaking changes."
        },
        "revisions": {
            "*": "Because \"rvslots\" was not specified, a legacy format has been used for the output. This format is deprecated, and in the future the new format will always be used."
        }
    },
    "query": {
        "pages": {
            "61": {
                "pageid": 61,
                "ns": 0,
                "title": "Receiver assessment",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "== Why is an assessment needed? ==\nUsers should have an easy way to find out what nodes fit their needs. The receiver assessment is a potential approach based on points as known from Spamassassin and Weight Watchers. This assessment could either be done by admins or as part of an online survey, by the users.\n\n== How many points for what? ==\n'''Receiver type'''\n\nThe average rating at eham.net could be a worthy source to have our assessment based on it.\n\n''Desktops:''\n\nTen-tec RX-340 5.0\n\nAOR AR-8600 4.8\n\nIC-775 4.8\n\nKenwood TS-480 4.8\n\nKenwood TS-850 4.8\n\nIcom PCR-2500 4.8\n\nIcom IC-756ProIII 4.7\n\nIcom IC-R8500 4.7\n\nIcom IC-R9000 4.6\n\nAOR AR-7030 4.6\n\nIcom IC-718 4.6\n\nJRC NRD 545 4.5\n\nIcom IC-R75 4.5\n\nIcom IC-7000 4.4\n\n[[Icom IC-706]]Mk2 4.4\n\nIcom PCR-1500 4.2\n\nIcom PCR-100 4.0\n\nIcom PCR-1000 3.9\n\nIcom (other)\n\n\n''SDRs:''\n\nSDR-1000 compatible 4.8\n\nPerseus SDR (CI-V) 4.7\n\n\n''Hand-helds:''\n\nAOR AR-8000 5.0\n\nAOR AR-8200 4.3\n\nIcom IC-R10 3.9\n\n\n''Special purpose:''\n\nSONY XDR-F1HD\n\nKenwood KT-6040\n\nAudio only\n\nDummy\n\nFanfare FT1A\n\nFM/TV capture card (FMIO)\n\nHamSphere\n\nHauppauge WinTV\n\n\n'''Location'''\n\nMetropolitan area\n\nCountry site\n\nHard to tell which is best as it depends on the users needs. A metropolitan area usually gets more stuff on VHF/UHF while the QRM on HF is usually lower if the node is located in the woods.\n\n'''Antenna'''\n\nDiscone\n\nLongwire\n\nVertical\n\nLoop\n\nDipole\n\nBeam\n\nTurnable beam\n\nAntenna height does matter too, of course.\n\n\n'''Availability'''\n\n24/7\n\nmore than 48 hrs a week\n\nmore than 24 hrs a week\n\nsporadically\n\n[[Category:GlobalTuners]]"
                    }
                ]
            },
            "62": {
                "pageid": 62,
                "ns": 0,
                "title": "UDPMSG3",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "UDPMSG3 started as a simple protocol for real-time distribution of structured messages through a cloud of interested systems. It has quickly evolved into a suite of compatible applications to distribute textual conversations (chatboxes / IRC channels).\n\n== UDPMSG3 Protocol ==\nUDPMSG3 started as a simple protocol for real-time distribution of structured messages through a cloud of interested systems. It provides a simple way to encode key-value pairs, as well as a mechanism to broadcast arbitrary messages over a mesh network of unicast links. The UDPMSG3 Protocol does not guarantee that messages are delivered, but it tries very hard to deliver a message to all nodes.\n\nMore information on the protocol can be found in the [[UDPMSG3 Protocol]] article.\n\n== UDPMSG3 Applications ==\nSourcecode to the 'official' implementation is available at http://oss.ucis.nl/hg/udpmsg3/ or http://oss.ucis.ano/hg/udpmsg3/ (inside [[Anonet]]). There are various different applications.\n\n=== Hub ===\nThe hub distributes messages among it's 'peers': links to other hubs, gateways, clients, etc. It can be found in the 'hub' subdirectory. All configuration is inside the sourcecode.\n\n=== IRCd ===\nThe IRCd provides a simple IRC server, using UDPMSG3 as it's server-link protocol. Other parties on the UDPMSG3 cloud are presented as real users to the IRC client. The source code can be found in the 'ircd' subdirectory.\n\n=== IRC Relay ===\nThe IRC Relay provides a a 'client bot', which forwards messages among several channels on several IRC servers, and the UDPMSG3 cloud.\n\n=== Simple IRC server ===\nThe Simple IRC server provides a single client UDPMSG3 to IRC translator. It should be run from inetd, xinetd or similar.\n\n=== UnrealIRCd server link ===\nConnects to an UnrealIRCd network using the UnrealIRCd link protocol and presents UDPMSG3 parties to the IRC network as real users. Users are introduced as they speak and disappear after a time-out."
                    }
                ]
            }
        }
    }
}