Difference between revisions of "Talk:2369: All-in-One"
Line 13: | Line 13: | ||
Seems like plagiarize would be somehow related to scan and copy. | Seems like plagiarize would be somehow related to scan and copy. | ||
+ | : I imagine the internal sub-functions would be: Scan (or read from prepocessed page data from an original document 'sent to printer'), OCR (as necessary - implied in Translate but not mentioned as a function, despite being an actually popular 'one touch' function with appropriate desktop software involved), Comprehend (natural-language processing), De-Source (remove references that indicate the true source, including headers, watermarks, logos), Re-Arrange (optional shuffling/re-wording in places, maybe even synonyms), Re-Source (personalise back up again, for the plagiarist's benefit), then Print (if scan-for-copy/printed) or Save (if scan-for-storage, maybe even 'print'-to-storage via the device). [[Special:Contributions/141.101.98.52|141.101.98.52]] 00:21, 8 October 2020 (UTC) | ||
shred and scan (or scanf) are also unix and C functions. Shred overwrites a file on disk, deleting it and preventing any subsequent recovery of the lost data. scan reads input according to a format string. Should one take a standard file and scan a string per the format '%s', the program will read in the variable until an end-of-line character is encountered. If the file were shredded first, resulting in a random set of bits, this end of line character might never be read. This seems to be more of a memory problem than a CPU problem, thus might not be the full explanation of the alt-text. --[[Special:Contributions/162.158.126.126|162.158.126.126]] 21:10, 7 October 2020 (UTC) | shred and scan (or scanf) are also unix and C functions. Shred overwrites a file on disk, deleting it and preventing any subsequent recovery of the lost data. scan reads input according to a format string. Should one take a standard file and scan a string per the format '%s', the program will read in the variable until an end-of-line character is encountered. If the file were shredded first, resulting in a random set of bits, this end of line character might never be read. This seems to be more of a memory problem than a CPU problem, thus might not be the full explanation of the alt-text. --[[Special:Contributions/162.158.126.126|162.158.126.126]] 21:10, 7 October 2020 (UTC) |
Revision as of 00:21, 8 October 2020
Is the title text a reference the Librareome project in Rainbow's End (Vernor Vinge)?
See, e.g., [1]
--162.158.79.124 18:06, 7 October 2020 (UTC)
I wonder if Randall took inspiration from [this Dilbert](https://dilbert.com/strip/1994-04-25). Moosenonny10 (talk) 18:52, 7 October 2020 (UTC)
I don't think "eat" and "corrugate" are intended as malfunctions. People sometimes eat paper -- it's a common trope in spy parodies where someone will eat a document to prevent someone from getting access to it. And corrugate just sounds like it's making corrugated cardboard from the input paper. Barmar (talk) 19:22, 7 October 2020 (UTC)
- I changed it. What do you think? welp, i Donthaveusername (talk) 19:37, 7 October 2020 (UTC)
Seems like plagiarize would be somehow related to scan and copy.
- I imagine the internal sub-functions would be: Scan (or read from prepocessed page data from an original document 'sent to printer'), OCR (as necessary - implied in Translate but not mentioned as a function, despite being an actually popular 'one touch' function with appropriate desktop software involved), Comprehend (natural-language processing), De-Source (remove references that indicate the true source, including headers, watermarks, logos), Re-Arrange (optional shuffling/re-wording in places, maybe even synonyms), Re-Source (personalise back up again, for the plagiarist's benefit), then Print (if scan-for-copy/printed) or Save (if scan-for-storage, maybe even 'print'-to-storage via the device). 141.101.98.52 00:21, 8 October 2020 (UTC)
shred and scan (or scanf) are also unix and C functions. Shred overwrites a file on disk, deleting it and preventing any subsequent recovery of the lost data. scan reads input according to a format string. Should one take a standard file and scan a string per the format '%s', the program will read in the variable until an end-of-line character is encountered. If the file were shredded first, resulting in a random set of bits, this end of line character might never be read. This seems to be more of a memory problem than a CPU problem, thus might not be the full explanation of the alt-text. --162.158.126.126 21:10, 7 October 2020 (UTC)
The incomplete template mentions that there might be a reason for Randall making this topic, but I don't think there is other than just making a funny joke. 172.69.34.146 22:42, 7 October 2020 (UTC)
What, it can fold but not spindle or mutilate? :( 162.158.75.114 23:14, 7 October 2020 (UTC)
Is staple removal a real printer feature? BunsenH (talk) 23:17, 7 October 2020 (UTC)
- Doubt it. 172.68.132.243 23:39, 7 October 2020 (UTC)
- Staple-detection is (fairly) trivial, but consistently extracting them 'nicely' while preserving the paper as much as possible might be beyond a device (it's tricky enough for a person, sometimes). 141.101.99.211 23:51, 7 October 2020 (UTC)
I'm disappointed there's no "jam for no particular reason in the most difficult place to access" option. 108.162.216.184 23:18, 7 October 2020 (UTC)
- I thought there should be Paper Cranes in the right-hand column... But your suggestion is also an obvious omission. 141.101.99.211 23:51, 7 October 2020 (UTC)