Two cows
Dan Tobias (Talk | contribs) m |
Kayvon2008 (Talk | contribs) (→Limitations) |
||
Line 15: | Line 15: | ||
A higher-bandwidth means of animal-based data transmission is outlined via avian carriers in RFC 1149 and RFC 2549. | A higher-bandwidth means of animal-based data transmission is outlined via avian carriers in RFC 1149 and RFC 2549. | ||
+ | |||
+ | The cows will soon die and it’s skin will either rot, or get eaten by a detrivore, like a wolf. | ||
== See also == | == See also == |
Revision as of 00:24, 31 October 2021
You have two cows. One of them encodes 0, the other encodes 1.
(No connection to Tucows. And the Cowculator probably won't help.)
Limitations
With only two cows, this will not suffice as a data storage method, but merely a transitory data transmission method; the cows might be sent through a gate in the proper sequence to encode the particular bits of the data being transmitted, but no permanent record is kept (unless the cows can be trained to produce excrement in fixed patterns; if this is done, one might prefer male bovines for the excremental encoding of the sorts of data often found on the Internet).
With a larger supply of cows, of two different colors, one might attempt to store data by arranging them in sequence with, for instance, brown cows representing "1" bits and spotted black and white cows representing "0" bits, though getting them to stay in sequence rather than wandering off randomly might be difficult.
A higher-bandwidth means of animal-based data transmission is outlined via avian carriers in RFC 1149 and RFC 2549.
The cows will soon die and it’s skin will either rot, or get eaten by a detrivore, like a wolf.