text stringlengths 0 937 |
|---|
MIT License |
Copyright (c) 2022 Frans Bouma |
Permission is hereby granted, free of charge, to any person obtaining a copy |
of this software and associated documentation files (the "Software"), to deal |
in the Software without restriction, including without limitation the rights |
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell |
copies of the Software, and to permit persons to whom the Software is |
furnished to do so, subject to the following conditions: |
The above copyright notice and this permission notice shall be included in all |
copies or substantial portions of the Software. |
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR |
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, |
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE |
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER |
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, |
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE |
SOFTWARE. |
GNU GENERAL PUBLIC LICENSE |
Version 3, 29 June 2007 |
Copyright © 2007 Free Software Foundation, Inc. <https://fsf.org/> |
Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. |
Preamble |
The GNU General Public License is a free, copyleft license for software and other kinds of works. |
The licenses for most software and other practical works are designed to take away your freedom to share and change the works. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change all versions of a program--to make sure it remains free software for all its users. We, the... |
When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for them if you wish), that you receive source code or can get it if you want it, that you can change the software or ... |
To protect your rights, we need to prevent others from denying you these rights or asking you to surrender the rights. Therefore, you have certain responsibilities if you distribute copies of the software, or if you modify it: responsibilities to respect the freedom of others. |
For example, if you distribute copies of such a program, whether gratis or for a fee, you must pass on to the recipients the same freedoms that you received. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights. |
Developers that use the GNU GPL protect your rights with two steps: (1) assert copyright on the software, and (2) offer you this License giving you legal permission to copy, distribute and/or modify it. |
For the developers' and authors' protection, the GPL clearly explains that there is no warranty for this free software. For both users' and authors' sake, the GPL requires that modified versions be marked as changed, so that their problems will not be attributed erroneously to authors of previous versions. |
Some devices are designed to deny users access to install or run modified versions of the software inside them, although the manufacturer can do so. This is fundamentally incompatible with the aim of protecting users' freedom to change the software. The systematic pattern of such abuse occurs in the area of products fo... |
Finally, every program is threatened constantly by software patents. States should not allow patents to restrict development and use of software on general-purpose computers, but in those that do, we wish to avoid the special danger that patents applied to a free program could make it effectively proprietary. To preven... |
The precise terms and conditions for copying, distribution and modification follow. |
TERMS AND CONDITIONS |
0. Definitions. |
“This License” refers to version 3 of the GNU General Public License. |
“Copyright” also means copyright-like laws that apply to other kinds of works, such as semiconductor masks. |
“The Program” refers to any copyrightable work licensed under this License. Each licensee is addressed as “you”. “Licensees” and “recipients” may be individuals or organizations. |
To “modify” a work means to copy from or adapt all or part of the work in a fashion requiring copyright permission, other than the making of an exact copy. The resulting work is called a “modified version” of the earlier work or a work “based on” the earlier work. |
A “covered work” means either the unmodified Program or a work based on the Program. |
To “propagate” a work means to do anything with it that, without permission, would make you directly or secondarily liable for infringement under applicable copyright law, except executing it on a computer or modifying a private copy. Propagation includes copying, distribution (with or without modification), making ava... |
To “convey” a work means any kind of propagation that enables other parties to make or receive copies. Mere interaction with a user through a computer network, with no transfer of a copy, is not conveying. |
An interactive user interface displays “Appropriate Legal Notices” to the extent that it includes a convenient and prominently visible feature that (1) displays an appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to the extent that warranties are provided), that licens... |
1. Source Code. |
The “source code” for a work means the preferred form of the work for making modifications to it. “Object code” means any non-source form of a work. |
A “Standard Interface” means an interface that either is an official standard defined by a recognized standards body, or, in the case of interfaces specified for a particular programming language, one that is widely used among developers working in that language. |
The “System Libraries” of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that Major Component, and (b) serves only to enable use of the work with that Major Component, or to implement a Standard Interf... |
The “Corresponding Source” for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities. However, it does not include the work's System Libraries, or general-purpose tools or g... |
The Corresponding Source need not include anything that users can regenerate automatically from other parts of the Corresponding Source. |
The Corresponding Source for a work in source code form is that same work. |
2. Basic Permissions. |
All rights granted under this License are granted for the term of copyright on the Program, and are irrevocable provided the stated conditions are met. This License explicitly affirms your unlimited permission to run the unmodified Program. The output from running a covered work is covered by this License only if the o... |
You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force. You may convey covered works to others for the sole purpose of having them make modifications exclusively for you, or provide you with facilities for running those works, provided... |
Conveying under any other circumstances is permitted solely under the conditions stated below. Sublicensing is not allowed; section 10 makes it unnecessary. |
3. Protecting Users' Legal Rights From Anti-Circumvention Law. |
No covered work shall be deemed part of an effective technological measure under any applicable law fulfilling obligations under article 11 of the WIPO copyright treaty adopted on 20 December 1996, or similar laws prohibiting or restricting circumvention of such measures. |
When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License with respect to the covered work, and you disclaim any intention to limit operation or modification of the work as a means of e... |
4. Conveying Verbatim Copies. |
You may convey verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice; keep intact all notices stating that this License and any non-permissive terms added in accord with section 7 apply to the... |
You may charge any price or no price for each copy that you convey, and you may offer support or warranty protection for a fee. |
Diogenes GTA Evidence and Handoffs Archive v01
The project has closed. This archive preserves 14 GTA story-mode evidence and handoff ZIPs / 1,433,440,325 public bytes from the beach-demo and multi-camera development lineage. Both tar shards have been archived and verified. ARCHIVE_INDEX.json gives their fixed revisions, paths and hashes, and MANIFEST.jsonl locates every ZIP within its shard.
Ten ZIPs preserve their original bytes. Four are explicit publication copies: three redact private local paths or host labels in text members; one omits four compiled executable/plugin members while preserving source, logs and build evidence. Each changed ZIP carries PUBLICATION-COPY.json describing the original ZIP hash and member-level changes. Private originals are retained in the closeout audit. Unchanged member bytes are verified, while compression and the ZIP container hash necessarily change.
Historical metadata, hashes, signatures, calibration notes, failed-QC results, rejected experiments and non-trainable or uncertified status remain historical. A hash or signature of original bytes does not certify a sanitized copy. The new public manifest identifies published bytes; archived source manifests and evidence must not be interpreted as new validation or training approval.
Contents and review
The ZIPs contain capture provenance, JSON/action/camera metadata, manual-review pages, source deltas, logs, 64 rendered images, five rendered or preview MP4s, four native numeric camera tapes, recorded audio and seven native Rockstar Editor replay members (including historical duplicates). All 817 metadata/text review entries and 49 additional source/HTML entries were decoded and inspected. All embedded images were visually inspected; each MP4 was sampled at the beginning, middle and end. The camera tapes were fully parsed as numeric DMGTAT1 records, and each original adjacent JSON digest matched its binary header. This is not a geometric or playback certification.
Native replay headers were checked for readable private paths/credentials against the reviewed story-mode capture lineage. The proprietary replay payloads were not fully semantically decoded. A replay header check and representative video review cannot certify every internal field or every rendered frame. Archived failures and limits remain visible rather than being repaired or promoted.
Reconstruction
Two tar shards keep every ZIP intact. MANIFEST.jsonl lists the public relative ZIP path and byte count, with exact SHA-256 and fixed-revision archive locations verified during transfer. Each tar also appends a member hash/size manifest. Four publication-copy ZIPs are explicitly marked; the others are byte-preserved originals. Pinned destination integrity and anonymous availability were verified before cloud-source cleanup; the four complete private originals remain retained.
This collection complements the GTA image archive, replay/audio/camera archive and public source snapshot. It does not include the commercial game, SDK installers or the omitted compiled tools. Read NOTICE.md for rights and unchanged use limits.
- Downloads last month
- -