Change Instance

HTTP 200 OK
Allow: GET, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "unit": "https://weblate.info.ucl.ac.be/api/units/37490/?format=api",
    "component": "https://weblate.info.ucl.ac.be/api/components/cnp3-ebook/exercisessockets/?format=api",
    "translation": "https://weblate.info.ucl.ac.be/api/translations/cnp3-ebook/exercisessockets/en/?format=api",
    "user": null,
    "author": null,
    "timestamp": "2022-09-17T01:14:26.148329+02:00",
    "action": 59,
    "target": "The first possibility was named  `big-endian` in a note written by Cohen [Cohen1980]_ while the second was named `little-endian`. Vendors of CPUs that used `big-endian` in memory insisted on using `big-endian` encoding in networked applications while vendors of CPUs that used `little-endian` recommended the opposite. Several studies were written on the relative merits of each type of encoding, but the discussion became almost a religious issue [Cohen1980]_. Eventually, the Internet chose the `big-endian` encoding, i.e. multi-byte fields are always transmitted by sending the most significant byte first, :rfc:`791` refers to this encoding as the :term:`network-byte order`. Most libraries [#fhtonl]_ used to write networked applications contain functions to convert multi-byte fields from memory to the network byte order and the reverse.",
    "id": 14702,
    "action_name": "String updated in the repository",
    "url": "https://weblate.info.ucl.ac.be/api/changes/14702/?format=api"
}