Telmatherina obscura
Telmatherina obscura is a species of fish in the subfamily Telmatherininae part of the family Melanotaeniidae, the rainbowfishes. It is endemic to Indonesia.[2] The species was described in 1991 by Maurice Kottelat with a type locality of Mengonuwai on Lake Matano on the island of Sulawesi.[3]
| Telmatherina obscura | |
|---|---|
Scientific classification  | |
| Kingdom: | Animalia |
| Phylum: | Chordata |
| Class: | Actinopterygii |
| Order: | Atheriniformes |
| Family: | Melanotaeniidae |
| Genus: | Telmatherina |
| Species: | T. obscura |
| Binomial name | |
| Telmatherina obscura Kottelat, 1991 | |
Sources
- Lumbantobing, D. 2019. Telmatherina obscura. The IUCN Red List of Threatened Species 2019: e.T21576A90980108. https://doi.org/10.2305/IUCN.UK.2019-2.RLTS.T21576A90980108.en. Downloaded on 25 July 2019.
- Froese, Rainer and Pauly, Daniel, eds. (2019). "Tematherina obscura" in FishBase. February 2019 version.
- Eschmeyer, W. N.; R. Fricke & R. van der Laan (eds.). "Telmatherina obscura". Catalog of Fishes. California Academy of Sciences. Retrieved 13 July 2019.
gollark: It does NOT allow random access.
gollark: Hmm, so, designoidal idea:- files have the following metadata: filename, last modified time, maybe permissions (I may not actually need this), size, checksum, flags (in case I need this later; probably just compression format?)- each version of a file in an archive has this metadata in front of it- when all the files in some set of data are archived, a header gets written to the end with all the file metadata plus positions- when backup is rerun, the system™️ just checks the last modified time of everything and sees if its local copies are newer, and if so appends them to the end; when it is done a new header is added containing all the files- when a backup needs to be extracted, it just reads the end, finds the latest versions and decompresses stuff at the right offsetThere are some important considerations here: it should be able to deal with damaged/partial files, encryption would be nice to have (it would probably work to just run it through authenticated AES-whatever when writing), adding new files shouldn't require tons of seeking, and it might be necessary to store backups on FAT32 disks so maybe it needs to be able of using multiple files somehow.
gollark: I have been pondering an osmarksarchiveformat™ because I dislike the existing ones somewhat. Specifically for backups and append-only-ish access. Thusly, thoughts on the design (crossposted from old esolangs)?
gollark: If you run too much current through beans they may vaporise/burn/etc.
gollark: You could make a mechanical computer from solidified beans.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.