MediaWiki API result

{
    "batchcomplete": "",
    "continue": {
        "gapcontinue": "Reverse_Engineering_Tools",
        "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": {
            "511": {
                "pageid": 511,
                "ns": 0,
                "title": "Repository Management",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "Here are instructions and advice for setting up and managing a Cydia repository. For context, Cydia uses an adapted version of Debian APT ([https://en.wikipedia.org/wiki/Advanced_Packaging_Tool Advanced Packaging Tool]) to manage packages.\n\n== saurik's explanation ==\n\nThe authoritative guide to setting up a Cydia APT repository is '''[http://www.saurik.com/id/7 saurik's post on the subject]'''.\n\n=== Share API ===\n\nPublic since July 3rd 2015 in saurik's [https://twitter.com/saurik/status/617138072342282240 tweet], it is possible to link to a repository or package from a url that Cydia can pick up.\n\nTo link to a repository, make an anchor on your site to\n\n    cydia://url/https://cydia.saurik.com/api/share#?source=http://apt.saurik.com/beta/itsamystery/\n\nTo link to a package, make an anchor on your site to\n\n    cydia://url/https://cydia.saurik.com/api/share#?source=http://apt.saurik.com/beta/itsamystery/&package=com.saurik.mystery\n\nReplacing ''http://apt.saurik.com/beta/itsamystery/'' and ''com.saurik.mystery'' to the target repository and package.\n\nIf the repository is not on the list Cydia will ask to add it. It will then take you to the package list (if linked to a repository) or to the specified package (if linked to a package).\n\n== Other explanations ==\n\nPatrick Muff wrote [http://patrickmuff.ch/blog/2013/02/15/create-your-own-cydia-repository-on-ubuntu/ \"Create your own Cydia Repository on Ubuntu in a few minutes\"]\n\nWinneonSword made a [https://github.com/WinneonSword/tutorial-repository Tutorial Repository on Github].\n\n== Quick and dirty summary ==\n\nFirst thing is, you'll need a web host. It could be anything, like [https://pages.github.com/ GitHub pages] (which is what most people do these days).\n\n=== Repository structure ===\n\nThe basic idea is that you have two files in your server, <tt>Packages</tt> and <tt>Release</tt>. <tt>Packages</tt> must be bzipped and named <tt>Packages.bz2</tt>, and optionally <tt>Release</tt> may be also. <tt>Packages</tt> contains all of the information related to the different packages on your server (and where to download them, more on that later) and <tt>Release</tt> contains all of the information related to your server (like the name, description, etc).\n\nIf you want to see examples of <tt>Packages</tt> and <tt>Release</tt> files, you can see the cached files from your installed repos at <tt>/var/lib/apt/lists</tt> (note they can be quite large).\n\n=== .deb files ===\n\nThe <tt>Packages</tt> file mentioned earlier points to .deb files in your server that you can download. These are made with [http://man.he.net/man1/dpkg-deb dpkg-deb]. Read more in the '''[[Packaging]]''' page.\n\n== Custom icon ==\n\nPut the file <tt>CydiaIcon.png</tt> at the root of your repository. It is displayed at 32x32, and it would be best for the file to be at Retina resolution (64x64 for @2x and 96x96 for @3x).\n\n== Private repositories ==\n\n\n<b>NOTE:</b> Static webhosts (like Github Pages) won't work for private repos. You'll need a server that has some way to let you process requests server-side, e.g. PHP, node.js, Go, Django, etc.\n\n=== Payment Provider API ===\n\nAll current package managers (with the exception of Cydia) support Payment Provider API, which can be used for purposes other than payment/checkout systems.\n\n* [https://developer.getsileo.app/payment-providers Payment Provider API specification]\n\n=== Password Protection ===\n\nYou can use a username and password system through Cydia's depiction system, where the user enters their username and password in the depiction page, and then is authorized to download the package.\n\n==== Password Protection Examples ====\n\n* [https://github.com/goeo-/errrr/ PHP]\n\n=== UDID Protection ===\n\nYou can also restrict access based on UDID. Cydia sends the user's UDID via the <tt>X-Unique-ID</tt> HTTP header, so your server could check that against a database in order to ensure that the user has rightful access.\n\n==== Pitfalls of UDID Protection ====\n\nUDID-protected repos are not very secure. UDID's can be easily faked since there is nothing to say whether it's legitimate or spoofed since it's sent as an HTTP header (<code>X-Unique-ID</code>), and these are sent with ''every'' Cydia support email. There have been public UDID leaks that pirate repositories are known to brute-force packages with. An unfortunate number of repositories, and Cydia Store, use it despite its misuse being bad enough that it was [http://www.theverge.com/2013/3/21/4133288/apple-to-finally-stop-accepting-apps-that-use-outdated-udid-device-identifier-may-1st banned from the App Store] in 2012. You should not consider protection by UDID completely secure; while it works and is simple to implement, it's like a fingerprint: if it's compromised by bad guys, it's hard to change it.\n\n==== UDID Protection Examples ====\n\n* [https://github.com/xdb6f/udid-cydia-repo PHP].\n* [https://github.com/Aehmlo/udid-enabled-cydia-repo Node.js].\n\n== See also ==\n\n* About <code>target=_blank</code> links in repositories: https://mathiasbynens.github.io/rel-noopener/ and https://css-tricks.com/use-target_blank/"
                    }
                ]
            },
            "499": {
                "pageid": 499,
                "ns": 0,
                "title": "Retrieving SDKs",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "'''SDKs''' (Software Development Kits) are bundles that contain headers, binaries, and other tools needed to build for a specific version of iOS. These can be found within Xcode at <code>Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs</code>.\n\n== Retrieving without a Mac ==\nThe legal way to download an SDK without access to a Mac is to download a copy of Xcode from Apple. These are available at [https://developer.apple.com/downloads/index.action developer.apple.com] (free developer registration required). Usually the latest SDK is best, but if you want an older version, find the Xcode version containing it from [https://xcodereleases.com/ this table]. \n\nA shareware program, [http://www.acutesystems.com/scrtm.htm TransMac], can extract Xcode DMGs on Windows. Open the DMG in the program, then use the left directory tree to navigate to <code>xcode.dmg/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs</code>. Right-click the SDK directory and choose \"Copy To\".\n\nAlternatively, grab a copy from [http://resources.airnativeextensions.com/ios/ here].\n\n''Expansion needed: How can modern Xcode .xip releases be extracted on Windows/Linux?''\n\n=== Troubleshooting ===\n\nAs of iOS 8, some people found that those instructions didn't work with the latest version of TransMac (version 11), but version 10.6 may work."
                    }
                ]
            }
        }
    }
}