{"id":5191,"date":"2024-06-13T07:00:00","date_gmt":"2024-06-13T07:00:00","guid":{"rendered":"http:\/\/localhost:10196\/?post_type=articles&p=5191"},"modified":"2024-06-07T15:46:11","modified_gmt":"2024-06-07T15:46:11","slug":"learning-to-program-copy-files","status":"publish","type":"articles","link":"https:\/\/allthingsopen.org\/articles\/learning-to-program-copy-files","title":{"rendered":"Learning to program: 2 ways to copy files in C"},"content":{"rendered":"\n

Whenever I introduce someone to programming, whether that’s in an article or in a “teach yourself” video, I like to use methods that are easy for a beginner to understand. But the way you teach<\/em> programming isn’t always the way you’d actually<\/em> implement it in real life. There are always trade-offs, like performance or security, to balance with “making it easy to learn.” But the first time you learn something, it helps to keep things simple and build up to the other stuff once you understand the basics.<\/p>\n\n\n\n

From simple to more complex examples<\/h2>\n\n\n\n

For example, if I were teaching someone about how to write their own version of the cat<\/code> command in C, I would use obvious variable names and make the program as straightforward as possible. One simple implementation might look like this:<\/p>\n\n\n\n

#include <stdio.h>\n\nint main(int arg_count, char *arg_list[])\n{\n   int item;\n   FILE *text_file;\n   char letter;\n\n   for (item = 1; item < arg_count; item = item + 1) {\n       text_file = fopen(arg_list[item], "r");\n\n       if (text_file != NULL) {\n           do {\n               letter = fgetc(text_file);\n\n               if (letter != EOF) {\n                   putchar(letter);\n               }\n           } while (letter != EOF);\n\n           fclose(text_file);\n       }\n   }\n\n   return 0;\n}<\/code><\/pre>\n\n\n\n
This is a very simple version of cat<\/code> that reads a list of files from the command line, which are stored in the arg_list<\/code> array. The program opens each file using a file pointer<\/em> called text_file<\/code> then reads the file one letter at a time using fgetc<\/code> and prints the letter using putchar<\/code>.<\/p>\n\n\n\n
But while this version is very easy to read, it’s also very monolithic; everything happens inside the main<\/code> program. That’s okay for a short program like this to teach the basics, but a better way to write the cat<\/code> program is to break out the “read a file and print its contents” part into a function<\/em> that is a bit more flexible. For example, we could rewrite this cat<\/code> program like this:<\/p>\n\n\n\n
#include <stdio.h>\n\nvoid cat(FILE *in, FILE *out)\n{\n   int ch;\n\n   while ((ch = fgetc(in)) != EOF) {\n       fputc(ch, out);\n   }\n}\n\nint main(int argc, char **argv)\n{\n   int i;\n   FILE *pfile;\n\n   for (i = 1; i < argc; i++) {\n       pfile = fopen(argv[i], "r");\n\n       if (pfile) {\n           cat(pfile, stdout);\n           fclose(pfile);\n       }\n   }\n\n   return 0;\n}<\/code><\/pre>\n\n\n\n
This puts the important stuff in a function called cat<\/code> that reads from a file pointer called in<\/code> and prints to a different file pointer called out<\/code>. When we call the cat<\/code> function, we can specify a different input and output. In this case, the main<\/code> program only uses stdout<\/code> or the standard output<\/em> when calling the cat<\/code> function – but in theory, this way of writing the cat<\/code> function to write to a file pointer instead of using putchar<\/code> makes it more flexible in case we ever decide to write directly to a different file later on.<\/p>\n\n\n\n
This other version of cat<\/code> also uses different variable names like i<\/code> and pfile<\/code>, which is more common for very short programs that don’t need very descriptive variable names. Experienced programmers typically use i<\/code> as a counter or index<\/em> variable, and pfile<\/code> as a pointer<\/em> to a file<\/em>. Otherwise, the program remains the same as the first simple version of cat<\/code>.<\/p>\n\n\n\n
But reading and writing one letter at a time isn’t the best way to do it. On modern systems with very fast CPUs and solid state drives, you might not notice the difference, but the performance impact of reading one letter then printing one letter will become more noticeable on slower systems.<\/p>\n\n\n\n
To make this run a bit faster on these slower systems, you might instead read part of the file into memory (called a buffer<\/em>) then write that buffer to the output. This is still the same basic algorithm of “read something, then write something,” but it’s able to do more at once, so it’s much faster even on slow systems. For example, we might update the cat<\/code> function one more time to read a file into a buffer using fread<\/code>, then write it back out using fwrite<\/code>:<\/p>\n\n\n\n
void cat(FILE *in, FILE *out)\n{\n   unsigned char buf[128];\n   size_t numread;\n\n   while (!feof(in)) {\n       numread = fread(buf, sizeof(unsigned char), 128, in);\n       fwrite(buf, sizeof(unsigned char), numread, out);\n   }\n}<\/code><\/pre>\n\n\n\n
Since the core functionality is in the cat<\/code> function, we only need to update that part of the program; the main<\/code> program can stay the same. This function creates a buffer<\/em> of 128 bytes; an unsigned char<\/code> is exactly one byte<\/em> long. The while<\/code> loop continues until it reaches the end of the file. Within the loop, it reads a bunch of data (up to 128 bytes) into the buffer using fread<\/code>, and keeps track of how much it read using the numread<\/code> variable. Then it writes that data back out using fwrite<\/code>.<\/p>\n\n\n\n
This is basically the same cat<\/code> program that we wrote above, but it runs much faster even on slow systems because it reads a bunch of data at once. That way, the operating system can just read some data without having to keep going back to the file to read one letter at a time.<\/p>\n\n\n\n
However, I wouldn’t use the “buffer” version of the program to teach someone about programming\u2014at least, not right away. It’s more complicated and difficult to understand. Instead, I’d start with the “one letter” version, and move up to the “buffer” method once we’d learned the basics about programming. The trade-off here is “easy to learn” with “runs fast.”<\/p>\n\n\n\n
Running on slow systems<\/h2>\n\n\n\n
It can be hard to imagine what I mean by a “slow” system. Today’s computers are very fast; my computer at home has a 4-core 8th Generation Intel Core i3-8100T running at 3.10 GHz, with NVMe M.2 storage, and my system is already a few years old. On a system that fast, reading and writing one letter at a time runs at basically the same speed as reading and writing a bunch of data at once using a buffer.<\/p>\n\n\n\n
But not every system is that fast. For example, what we recognize as the personal computing era started in the late 1970s with the Commodore PET, TRS-80, and Apple II computers. In 1981, IBM released the IBM Personal Computer 5150, which became the basis for “PC” computers built after that. My 2019 PC can trace its lineage back to the original 1981 IBM PC.<\/p>\n\n\n\n
In 1981, IBM used a very simple operating system called DOS, the Disk Operating System<\/em>, provided by Microsoft. And DOS is still around, as the open source FreeDOS Project<\/a>. FreeDOS is a more modern version of DOS, but it’s still DOS.<\/p>\n\n\n\n
Because DOS has certain assumptions about the hardware it’s running on, you aren’t likely to run DOS directly<\/em> on very new computers. Instead, most people run FreeDOS in a virtual machine<\/em> or a PC emulator of some kind. And that provides an excellent opportunity to demonstrate running a slow system, because we can artificially slow down a virtual machine.<\/p>\n\n\n\n
For this demonstration, I’ll use the QEMU virtual machine. QEMU supports Linux KVM, or kernel virtual machine<\/em>, which makes the “guest” operating system run at almost native speeds. Without KVM, the “guest” runs through software emulation, which is much slower. So we can simulate a much slower system by running QEMU without KVM support.<\/p>\n\n\n\n
A program to copy files<\/h2>\n\n\n\n
Let’s write a simple FreeDOS program that reads data from one file and writes it to another file. This is basically the same as the Linux cp<\/code> command, or the COPY<\/code> command on DOS.<\/p>\n\n\n\n
As with the cat<\/code> sample program, one way to write this program is to break out the core behavior into a function called cpy<\/code> which reads from one file pointer and writes to another file pointer. In the simplest case, this function reads just one character at a time using fgetc<\/code> and writes each character one at a time with fputc<\/code>:<\/p>\n\n\n\n
#include <stdio.h>\n\nvoid cpy(FILE *in, FILE *out)\n{\n   int ch;\n\n   while ((ch = fgetc(in)) != EOF) {\n       fputc(ch, out);\n   }\n}<\/code><\/pre>\n\n\n\n
This is the same as the cat<\/code> function we wrote above, and is easy to explain to a new programmer: the function reads a character, then writes that character, and again, until it reaches the end of the file.<\/p>\n\n\n\n
But while that’s easy to explain, it isn’t very fast to run. So a better way to write this function is to read a bunch of data at once, then write that to the output:<\/p>\n\n\n\n
#include <stdio.h>\n\n#define BUFSIZE 128\n\ntypedef unsigned char byte_t;\n\nvoid cpy(FILE *in, FILE *out)\n{\n   byte_t buf[BUFSIZE];\n   size_t numread, numwrite;\n\n   while (!feof(in)) {\n       numread = fread(buf, sizeof(byte_t), BUFSIZE, in);\n\n       if (numread > 0) {\n           numwrite = fwrite(buf, sizeof(byte_t), numread, out);\n\n           if (numwrite != numread) {\n               fputs("mismatch!\\n", stderr);\n               return;\n           }\n       }\n   }\n}\n<\/code><\/pre>\n\n\n\n
This uses a typedef<\/code> statement so we don’t need to keep typing unsigned char<\/code> everywhere, but it’s otherwise the same as the “buffer” version of the cat function from above. I’ve also added some extra features here, because we know we’ll be copying files, and it’s very important to know that things work along the way. For example, the function has a little extra code to detect if the amount of data it wrote differs from the amount of data it read, and aborts with an error message if that happens. <\/p>\n\n\n\n
Because both of the functions take the same function arguments<\/em>, we can write just one main<\/code> program that uses either version of cpy<\/code> function:<\/p>\n\n\n\n
#include <stdio.h>\n\nvoid cpy(FILE * in, FILE * out);\n\nint main(int argc, char **argv)\n{\n   FILE *src, *dest;\n\n   \/* check command line *\/\n\n   if (argc != 3) {\n       fprintf(stderr, "usage: cpy src dest\\n");\n       return 1;\n   }\n\n   \/* open files *\/\n\n   src = fopen(argv[1], "rb");\n   if (src == NULL) {\n       fprintf(stderr, "cannot open %s for reading\\n", argv[1]);\n       return 2;\n   }\n\n   dest = fopen(argv[2], "wb");\n   if (dest == NULL) {\n       fprintf(stderr, "cannot open %s for writing\\n", argv[2]);\n       fclose(src);\n       return 3;\n   }\n\n   \/* copy *\/\n\n   cpy(src, dest);\n   fclose(src);\n   fclose(dest);\n\n   return 0;\n}<\/code><\/pre>\n\n\n\n
That’s a longer main<\/code> program than the cat<\/code> program used, but it also includes some extra code to detect errors when opening files, or if the user didn’t provide the right number of options on the command line. The basic outline is:<\/p>\n\n\n\n
    \n
  1. Open the input file as src<\/code><\/li>\n\n\n\n
  2. Open the output file as dest<\/code><\/li>\n\n\n\n
  3. Use the cpy<\/code> function to copy from src<\/code> to dest<\/code><\/li>\n\n\n\n
  4. Close both files<\/li>\n<\/ol>\n\n\n\n
    If we save the “one character at a time” version of the cpy<\/code> function as cpy1.c<\/code> and the “buffer” version as cpybuf.c<\/code>, and the main program as cpy.c<\/code>, we can compile two separate programs. I’ll use the open source OpenWatcom C compiler, which we include in the FreeDOS distribution:<\/p>\n\n\n\n
    wcl -q cpy1.c cpy.c\nwcl -q cpybuf.c cpy.c<\/code><\/pre>\n\n\n\n
    Testing on a slow system<\/h2>\n\n\n\n
    With these two versions of the cpy<\/code> program, we can see how fast or slow these run on FreeDOS, when running QEMU with and without KVM support. To run this test more consistently, I wrote a DOS “batch” file to copy a 9 MB zip file, then use the COMP<\/code> command to compare the original zip file with the copy. This also uses RUNTIME<\/code> (which you can install from the FreeDOS distribution) to tell me how long it takes to run each command. My TEST.BAT<\/code> file looks like this:<\/p>\n\n\n\n
    @ECHO off\n\nset SRC=C:\\TEMP\\FILE.ZIP\nset DEST=C:\\TEMP\\FILE.OUT\n\necho using CPY1 ..\nruntime CPY1 %SRC% %DEST%\nCOMP %SRC% %DEST%\n\necho using CPYBUF ..\nruntime CPYBUF %SRC% %DEST%\nCOMP %SRC% %DEST%<\/code><\/pre>\n\n\n\n
    On Linux, I started a new instance of FreeDOS running in QEMU, with KVM. Running TEST.BAT<\/code> gives this output:<\/p>\n\n\n\n
    using CPY1 ..\nRun time was 29.615385 seconds\nFiles compare OK.\nusing CPYBUF ..\nRun time was 29.285714 seconds\nFiles compare OK.<\/code><\/pre>\n\n\n\n
    KVM is the Linux kernel’s virtual machine accelerator, and it does a great job of helping the “guest” operating system run really fast inside QEMU. In this case, copying a 9 MB file one character at a time (with cpy1<\/code>) and by using a buffer (with cpybuf<\/code>) both take about 29 seconds.<\/p>\n\n\n\n
    But if I restart the virtual machine and don’t enable KVM support, then QEMU has to process all machine instructions through software. That slows down most operations. For this example, running QEMU without KVM is probably closer to running FreeDOS on real hardware from the late 1990s era. You can see it takes much longer to copy the 9 MB file with these settings:<\/p>\n\n\n\n
    using CPY1 ..\nRun time was 105.879121 seconds\nFiles compare OK.\nusing CPYBUF ..\nRun time was 23.846154 seconds\nFiles compare OK.<\/code><\/pre>\n\n\n\n
    Copying the file by reading a bunch of data at once (using a buffer) takes the same amount of time as before, about 24 seconds. But reading and writing files one character at a time is much<\/em> slower on this system, about 105 seconds (that’s 1 minute, 45 seconds).<\/p>\n\n\n\n
    Teach simple methods first<\/h2>\n\n\n\n
    The simplest methods can be much easier for beginner programmers to learn, but the trade-off is these basic implementations aren’t always the best in the real world. But I still like to use the more simple methods when I teach programming. My approach to teaching programming is “learn the basics first” then “use that to learn the more complex stuff.” And I still think that’s the right approach. Just keep in mind that the simplest version isn’t always the best version, even though it does the same thing.<\/p>\n","protected":false},"template":"","class_list":["post-5191","articles","type-articles","status-publish","hentry"],"acf":[],"yoast_head":"\nLearning to program: 2 ways to copy files in C | We Love Open Source • All Things Open<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/allthingsopen.org\/articles\/learning-to-program-copy-files\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Learning to program: 2 ways to copy files in C | We Love Open Source • All Things Open\" \/>\n<meta property=\"og:description\" content=\"Whenever I introduce someone to programming, whether that’s in an article or in a “teach yourself” video, I like to use methods that are easy for a beginner to understand.... Read More\" \/>\n<meta property=\"og:url\" content=\"https:\/\/allthingsopen.org\/articles\/learning-to-program-copy-files\" \/>\n<meta property=\"og:site_name\" content=\"All Things Open\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/facebook.com\/AllThingsOpen\" \/>\n<meta property=\"og:image\" content=\"https:\/\/allthingsopen.org\/wp-content\/uploads\/2024\/05\/pair-pears-program-e1716932126263.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"1920\" \/>\n\t<meta property=\"og:image:height\" content=\"1081\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:site\" content=\"@AllThingsOpen\" \/>\n<meta name=\"twitter:label1\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data1\" content=\"8 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/allthingsopen.org\\\/articles\\\/learning-to-program-copy-files\",\"url\":\"https:\\\/\\\/allthingsopen.org\\\/articles\\\/learning-to-program-copy-files\",\"name\":\"Learning to program: 2 ways to copy files in C | We Love Open Source • All Things Open\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/allthingsopen.org\\\/#website\"},\"datePublished\":\"2024-06-13T07:00:00+00:00\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/allthingsopen.org\\\/articles\\\/learning-to-program-copy-files#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/allthingsopen.org\\\/articles\\\/learning-to-program-copy-files\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/allthingsopen.org\\\/articles\\\/learning-to-program-copy-files#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/allthingsopen.org\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Articles\",\"item\":\"https:\\\/\\\/allthingsopen.org\\\/articles\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Learning to program: 2 ways to copy files in C\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/allthingsopen.org\\\/#website\",\"url\":\"https:\\\/\\\/allthingsopen.org\\\/\",\"name\":\"All Things Open\",\"description\":\"A universe of events and platforms focused on open source, open tech and the open web.\",\"publisher\":{\"@id\":\"https:\\\/\\\/allthingsopen.org\\\/#organization\"},\"alternateName\":\"ATO\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/allthingsopen.org\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/allthingsopen.org\\\/#organization\",\"name\":\"All Things Open\",\"url\":\"https:\\\/\\\/allthingsopen.org\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/allthingsopen.org\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"http:\\\/\\\/allthingsopen.org\\\/wp-content\\\/uploads\\\/2021\\\/10\\\/2022_ATO_Logo_Red_NoDate.svg\",\"contentUrl\":\"http:\\\/\\\/allthingsopen.org\\\/wp-content\\\/uploads\\\/2021\\\/10\\\/2022_ATO_Logo_Red_NoDate.svg\",\"width\":\"1024\",\"height\":\"1024\",\"caption\":\"All Things Open\"},\"image\":{\"@id\":\"https:\\\/\\\/allthingsopen.org\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/facebook.com\\\/AllThingsOpen\",\"https:\\\/\\\/x.com\\\/AllThingsOpen\",\"https:\\\/\\\/www.linkedin.com\\\/company\\\/all-things-open\\\/\",\"https:\\\/\\\/www.instagram.com\\\/allthingsopen\",\"https:\\\/\\\/www.youtube.com\\\/allthingsopen\"]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Learning to program: 2 ways to copy files in C | We Love Open Source • All Things Open","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/allthingsopen.org\/articles\/learning-to-program-copy-files","og_locale":"en_US","og_type":"article","og_title":"Learning to program: 2 ways to copy files in C | We Love Open Source • All Things Open","og_description":"Whenever I introduce someone to programming, whether that’s in an article or in a “teach yourself” video, I like to use methods that are easy for a beginner to understand.... Read More","og_url":"https:\/\/allthingsopen.org\/articles\/learning-to-program-copy-files","og_site_name":"All Things Open","article_publisher":"https:\/\/facebook.com\/AllThingsOpen","og_image":[{"width":1920,"height":1081,"url":"https:\/\/allthingsopen.org\/wp-content\/uploads\/2024\/05\/pair-pears-program-e1716932126263.jpg","type":"image\/jpeg"}],"twitter_card":"summary_large_image","twitter_site":"@AllThingsOpen","twitter_misc":{"Est. reading time":"8 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/allthingsopen.org\/articles\/learning-to-program-copy-files","url":"https:\/\/allthingsopen.org\/articles\/learning-to-program-copy-files","name":"Learning to program: 2 ways to copy files in C | We Love Open Source • All Things Open","isPartOf":{"@id":"https:\/\/allthingsopen.org\/#website"},"datePublished":"2024-06-13T07:00:00+00:00","breadcrumb":{"@id":"https:\/\/allthingsopen.org\/articles\/learning-to-program-copy-files#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/allthingsopen.org\/articles\/learning-to-program-copy-files"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/allthingsopen.org\/articles\/learning-to-program-copy-files#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/allthingsopen.org\/"},{"@type":"ListItem","position":2,"name":"Articles","item":"https:\/\/allthingsopen.org\/articles"},{"@type":"ListItem","position":3,"name":"Learning to program: 2 ways to copy files in C"}]},{"@type":"WebSite","@id":"https:\/\/allthingsopen.org\/#website","url":"https:\/\/allthingsopen.org\/","name":"All Things Open","description":"A universe of events and platforms focused on open source, open tech and the open web.","publisher":{"@id":"https:\/\/allthingsopen.org\/#organization"},"alternateName":"ATO","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/allthingsopen.org\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/allthingsopen.org\/#organization","name":"All Things Open","url":"https:\/\/allthingsopen.org\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/allthingsopen.org\/#\/schema\/logo\/image\/","url":"http:\/\/allthingsopen.org\/wp-content\/uploads\/2021\/10\/2022_ATO_Logo_Red_NoDate.svg","contentUrl":"http:\/\/allthingsopen.org\/wp-content\/uploads\/2021\/10\/2022_ATO_Logo_Red_NoDate.svg","width":"1024","height":"1024","caption":"All Things Open"},"image":{"@id":"https:\/\/allthingsopen.org\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/facebook.com\/AllThingsOpen","https:\/\/x.com\/AllThingsOpen","https:\/\/www.linkedin.com\/company\/all-things-open\/","https:\/\/www.instagram.com\/allthingsopen","https:\/\/www.youtube.com\/allthingsopen"]}]}},"_links":{"self":[{"href":"https:\/\/allthingsopen.org\/wp-json\/wp\/v2\/articles\/5191","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/allthingsopen.org\/wp-json\/wp\/v2\/articles"}],"about":[{"href":"https:\/\/allthingsopen.org\/wp-json\/wp\/v2\/types\/articles"}],"wp:attachment":[{"href":"https:\/\/allthingsopen.org\/wp-json\/wp\/v2\/media?parent=5191"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}