diff --git a/sources/tech/20191025 How I used the wget Linux command to recover lost images.md b/sources/tech/20191025 How I used the wget Linux command to recover lost images.md
deleted file mode 100644
index 02cdd087db..0000000000
--- a/sources/tech/20191025 How I used the wget Linux command to recover lost images.md
+++ /dev/null
@@ -1,132 +0,0 @@
-[#]: collector: (lujun9972)
-[#]: translator: (wxy)
-[#]: reviewer: ( )
-[#]: publisher: ( )
-[#]: url: ( )
-[#]: subject: (How I used the wget Linux command to recover lost images)
-[#]: via: (https://opensource.com/article/19/10/how-community-saved-artwork-creative-commons)
-[#]: author: (Seth Kenlon https://opensource.com/users/seth)
-
-How I used the wget Linux command to recover lost images
-======
-The story of the rise and fall of the Open Clip Art Library and the
-birth of FreeSVG.org, a new library of communal artwork.
-![White shoes on top of an orange tribal pattern][1]
-
-In 2004, the Open Clip Art Library (OCAL) was launched as a source of free illustrations for anyone to use, for any purpose, without requiring attribution or anything in return. This site was the open source world’s answer to the big stacks of clip art CDs on the shelf of every home office in the 1990s, and to the art dumps provided by the closed-source office and artistic software titles.
-
-In the beginning, the clip art library consisted mostly of work by a few contributors, but in 2010 it went live with a brand new interactive website, allowing anyone to create and contribute clip art with a vector illustration application. The site immediately garnered contributions from around the globe, and from all manner of free software and free culture projects. A special importer for this library was even included in [Inkscape][2].
-
-However, in early 2019, the website hosting the Open Clip Art Library went offline with no warning or explanation. Its community, which had grown to number in the thousands, assumed at first that this was a temporary glitch. The site remained offline, however, for over six months without any clear explanation of what had happened.
-
-Rumors started to swell. The site was being updated ("There is years of technical debt to pay off," said site developer Jon Philips in an email). The site had fallen to rampant DDOS attacks, claimed a Twitter account. The maintainer had fallen prey to identity theft, another Twitter account claimed. Today, as of this writing, the site’s one and only remaining page declares that it is in "maintenance and protected mode," the meaning of which is unclear, except that users cannot access its content.
-
-### Recovering the commons
-
-Sites appear and disappear over the course of time, but the loss of the Open Clip Art Library was particularly surprising to its community because it was seen as a community project. Few community members understood that the site hosting the library had fallen into the hands of a single maintainer, so while the artwork in the library was owned by everyone due to its [Creative Commons 0 License][3], access to it was functionally owned by a single maintainer. And, because the site’s community kept in touch with one another through the site, that same maintainer effectively owned the community.
-
-When the site failed, the community lost access to its artwork as well as each other. And without the site, there was no community.
-
-Initially, everything on the site was blocked when it went down. After several months, though, users started recognizing that the site’s database was still online, which meant that a user could access an individual art file by entering its exact URL. In other words, you couldn’t navigate to the art file through clicking around a website, but if you already knew the address, then you could bring it up in your browser. Similarly, technical (or lazy) users realized it was also possible to "scrape" the site with an automated web browser like **wget**.
-
-The **wget** Linux command is _technically_ a web browser, although it doesn’t let you browse interactively the way you do with Firefox. Instead, **wget** goes out onto the internet and retrieves a file or a collection of files and downloads them to your hard drive. You can then open those files in Firefox or a text editor, or whatever application is most appropriate, and view the content.
-
-Usually, **wget** needs to know a specific file to fetch. If you’re on Linux or macOS with **wget** installed, you can try this process by downloading the index page for [example.com][4]:
-
-
-```
-$ wget example.org/index.html
-[...]
-$ tail index.html
-
-<body><div>
- <h1>Example Domain</h1>
- <p>This domain is for illustrative examples in documents.
- You may use this domain in examples without permission.</p>
- <p><a href="[http://www.iana.org/domains/example"\>More][5] info</a></p>
-</div></body></html>
-```
-
-To scrape the Open Clip Art Library, I used the **\--mirror** option, so that I could point **wget** to just the directory containing the artwork so it could download everything within that directory. This action resulted in four straight days (96 hours) of constant downloading, ending with an excess of 100,000 SVG files that had been contributed by over 5,000 community members. Unfortunately, the author of any file that did not have proper metadata was irrecoverable because this information was locked in inaccessible files in the database, but the CC0 license meant that this issue _technically_ didn’t matter (because no attribution is required with CC0 files).
-
-A casual analysis of the downloaded files also revealed that nearly 45,000 of them were copies of the same single file (the site’s logo). This was caused by redirects pointing to the site's logo (for reasons unknown), and careful parsing could extract the original destination. Another 96 hours, and all clip art posted on OCAL up to its last day was recovered: **a total of about 156,000 images.**
-
-SVG files tend to be small, but this is still an enormous amount of work that poses a few very real problems. First of all, several gigabytes of online storage would be needed so the artwork could be made available to its former community. Secondly, a means of searching the artwork would be necessary, because it’s just not realistic to browse through 55,000 files manually.
-
-It became apparent that what the community really needed was a platform.
-
-### Building a new platform
-
-For some time, the site [Public Domain Vectors][6] had been publishing vector art that was in the public domain. While it remains a popular site, open source users often used it only as a secondary source of art because most of the files there were in the EPS and AI formats, both of which are associated with Adobe. Both file formats can generally be converted to SVG but at a loss of features.
-
-When the Public Domain Vectors site’s maintainers (Vedran and Boris) heard about the loss of the Open Clip Art Library, they decided to create a site oriented toward the open source community. True to form, they chose the open source [Laravel][7] framework as the backend, which provided the site with an admin dashboard and user access. The framework, being robust and well-developed, also allowed them to respond quickly to bug reports and feature requests, and to upgrade the site as needed. The site they are building is called [FreeSVG.org][8], and is already a robust and thriving library of communal artwork.
-
-Since then they have been uploading all of the clip art from the Open Clip Art Library, and they're even diligently tagging and categorizing the art as they go. As creators of Public Domain Vectors, they are also contributing their own images in SVG format. Their aim is to become the primary resource for SVG images with a CC0 license on the internet.
-
-### Contributing
-
-The maintainers of [FreeSVG.org][8] are aware that they have inherited significant stewardship. They are working to title and describe all images on the site so that users can easily find artwork, and will provide this file to the community once it is ready, believing strongly that the metadata about the art belongs to the people that create and use the art as much as the art itself does. They're also aware that unforeseen circumstances can arise, so they create regular backups of their site and content, and intend to make the most recent backup available to the public, should their site fail.
-
-If you want to add to the Creative Commons content of [FreeSVG.org][9], then download [Inkscape][10] and start drawing. There’s plenty of public domain artwork out there in the world, like [historical advertisements][11], [tarot cards][12], and [storybooks][13] just waiting to be converted to SVG, so you can contribute even if you aren’t confident in your drawing skills. Visit the [FreeSVG forum][14] to connect with and support other contributors.
-
-The concept of the _commons_ is important. [Creative Commons benefits everyone][15], whether you’re a student, teacher, librarian, small business owner, or CEO. If you don’t contribute directly, then you can always help promote it.
-
-That’s a strength of free culture: It doesn’t just scale, it gets better when more people participate.
-
-### Hard lessons learned
-
-From the demise of the Open Clip Art Library to the rise of FreeSVG.org, the open culture community has learned several hard lessons. For posterity, here are the ones that I believe are most important.
-
-#### Maintain your metadata
-
-If you’re a content creator, help the archivists of the future and add metadata to your files. Most image, music, font, and video file formats can have EXIF data embedded into them, and others have metadata entry interfaces in the applications that create them. Be diligent in tagging your work with your name, website or public email, and license.
-
-#### Make copies
-
-Don’t assume that somebody else is doing backups. If you care about communal digital content, then back it up yourself, or else don’t count on having it available forever. The trope that _whatever’s uploaded to the internet is forever_ may be true, but that doesn’t mean it’s _available to you_ forever. If the Open Clip Art Library files hadn’t become secretly available again, it’s unlikely that anyone would have ever successfully uncovered all 55,000 images from random places on the web, or from personal stashes on people’s hard drives around the globe.
-
-#### Create external channels
-
-If a community is defined by a single website or physical location, then that community is as good as dissolved should it lose access to that space. If you’re a member of a community that’s driven by a single organization or site, you owe it to yourselves to share contact information with those you care about and to establish a channel for communication even when that site is not available.
-
-For example, [Opensource.com][16] itself maintains mailing lists and other off-site channels for its authors and correspondents to communicate with one another, with or without the intervention or even existence of the website.
-
-#### Free culture is worth working for
-
-The internet is sometimes seen as a lazy person’s social club. You can log on when you want and turn it off when you’re tired, and you can wander into whatever social circle you want.
-
-But in reality, free culture can be hard work. It’s not hard in the sense that it’s difficult to be a part of, but it’s something you have to work to maintain. If you ignore the community you’re in, then the community may wither and fade before you realize it.
-
-Take a moment to look around you and identify what communities you’re a part of, and if nothing else, tell someone that you appreciate what they bring to your life. And just as importantly, keep in mind that you’re contributing to the lives of your communities, too.
-
-Creative Commons held its Gl obal Summit a few weeks ago in Warsaw, with amazing international...
-
---------------------------------------------------------------------------------
-
-via: https://opensource.com/article/19/10/how-community-saved-artwork-creative-commons
-
-作者：[Seth Kenlon][a]
-选题：[lujun9972][b]
-译者：[译者ID](https://github.com/译者ID)
-校对：[校对者ID](https://github.com/校对者ID)
-
-本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
-
-[a]: https://opensource.com/users/seth
-[b]: https://github.com/lujun9972
-[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/tribal_pattern_shoes.png?itok=e5dSf2hS (White shoes on top of an orange tribal pattern)
-[2]: https://opensource.com/article/18/1/inkscape-absolute-beginners
-[3]: https://creativecommons.org/share-your-work/public-domain/cc0/
-[4]: http://example.com
-[5]: http://www.iana.org/domains/example"\>More
-[6]: http://publicdomainvectors.org
-[7]: https://github.com/viralsolani/laravel-adminpanel
-[8]: https://freesvg.org
-[9]: http://freesvg.org
-[10]: http://inkscape.org
-[11]: https://freesvg.org/drinking-coffee-vector-drawing
-[12]: https://freesvg.org/king-of-swords-tarot-card
-[13]: https://freesvg.org/space-pioneers-135-scene-vector-image
-[14]: http://forum.freesvg.org/
-[15]: https://opensource.com/article/18/1/creative-commons-real-world
-[16]: http://Opensource.com
diff --git a/sources/tech/20191029 What you probably didn-t know about sudo.md b/sources/tech/20191029 What you probably didn-t know about sudo.md
deleted file mode 100644
index e58c092602..0000000000
--- a/sources/tech/20191029 What you probably didn-t know about sudo.md
+++ /dev/null
@@ -1,200 +0,0 @@
-[#]: collector: (lujun9972)
-[#]: translator: ( )
-[#]: reviewer: ( )
-[#]: publisher: ( )
-[#]: url: ( )
-[#]: subject: (What you probably didn’t know about sudo)
-[#]: via: (https://opensource.com/article/19/10/know-about-sudo)
-[#]: author: (Peter Czanik https://opensource.com/users/czanik)
-
-What you probably didn’t know about sudo
-======
-Think you know everything about sudo? Think again.
-![Command line prompt][1]
-
-Everybody knows **sudo**, right? This tool is installed by default on most Linux systems and is available for most BSD and commercial Unix variants. Still, after talking to hundreds of **sudo** users, the most common answer I received was that **sudo** is a tool to complicate life.
-
-There is a root user and there is the **su** command, so why have yet another tool? For many, **sudo** was just a prefix for administrative commands. Only a handful mentioned that when you have multiple administrators for the same system, you can use **sudo** logs to see who did what.
-
-So, what is **sudo**? According to the [**sudo** website][2]:
-
-> _"Sudo allows a system administrator to delegate authority by giving certain users the ability to run some commands as root or another user while providing an audit trail of the commands and their arguments."_
-
-By default, **sudo** comes with a simple configuration, a single rule allowing a user or a group of users to do practically anything (more on the configuration file later in this article):
-
-
-```
-`%wheel ALL=(ALL) ALL`
-```
-
-In this example, the parameters mean the following:
-
- * The first parameter defines the members of the group.
- * The second parameter defines the host(s) the group members can run commands on.
- * The third parameter defines the usernames under which the command can be executed.
- * The last parameter defines the applications that can be run.
-
-
-
-So, in this example, the members of the **wheel** group can run all applications as all users on all hosts. Even this really permissive rule is useful because it results in logs of who did what on your machine.
-
-### Aliases
-
-Of course, once it is not just you and your best friend administering a shared box, you will start to fine-tune permissions. You can replace the items in the above configuration with lists: a list of users, a list of commands, and so on. Most likely, you will copy and paste some of these lists around in your configuration.
-
-This situation is where aliases can come handy. Maintaining the same list in multiple places is error-prone. You define an alias once and then you can use it many times. Therefore, when you lose trust in one of your administrators, you can remove them from the alias and you are done. With multiple lists instead of aliases, it is easy to forget to remove the user from one of the lists with elevated privileges.
-
-### Enable features for a certain group of users
-
-The **sudo** command comes with a huge set of defaults. Still, there are situations when you want to override some of these. This is when you use the **Defaults** statement in the configuration. Usually, these defaults are enforced on every user, but you can narrow the setting down to a subset of users based on host, username, and so on. Here is an example that my generation of sysadmins loves to hear about: insults. These are just some funny messages for when someone mistypes a password:
-
-
-```
-czanik@linux-mewy:~> sudo ls
-[sudo] password for root:
-Hold it up to the light --- not a brain in sight!
-[sudo] password for root:
-My pet ferret can type better than you!
-[sudo] password for root:
-sudo: 3 incorrect password attempts
-czanik@linux-mewy:~>
-```
-
-Because not everyone is a fan of sysadmin humor, these insults are disabled by default. The following example shows how to enable this setting only for your seasoned sysadmins, who are members of the **wheel** group:
-
-
-```
-Defaults !insults
-Defaults:%wheel insults
-```
-
-I do not have enough fingers to count how many people thanked me for bringing these messages back.
-
-### Digest verification
-
-There are, of course, more serious features in **sudo** as well. One of them is digest verification. You can include the digest of applications in your configuration:
-
-
-```
-`peter ALL = sha244:11925141bb22866afdf257ce7790bd6275feda80b3b241c108b79c88 /usr/bin/passwd`
-```
-
-In this case, **sudo** checks and compares the digest of the application to the one stored in the configuration before running the application. If they do not match, **sudo** refuses to run the application. While it is difficult to maintain this information in your configuration—there are no automated tools for this purpose—these digests can provide you with an additional layer of protection.
-
-### Session recording
-
-Session recording is also a lesser-known feature of **sudo**. After my demo, many people leave my talk with plans to implement it on their infrastructure. Why? Because with session recording, you see not just the command name, but also everything that happened in the terminal. You can see what your admins are doing even if they have shell access and logs only show that **bash** is started.
-
-There is one limitation, currently. Records are stored locally, so with enough permissions, users can delete their traces. Stay tuned for upcoming features.
-
-### Plugins
-
-Starting with version 1.8, **sudo** changed to a modular, plugin-based architecture. With most features implemented as plugins, you can easily replace or extend the functionality of **sudo** by writing your own. There are both open source and commercial plugins already available for **sudo**.
-
-In my talk, I demonstrated the **sudo_pair** plugin, which is available [on GitHub][3]. This plugin is developed in Rust, meaning that it is not so easy to compile, and it is even more difficult to distribute the results. On the other hand, the plugin provides interesting functionality, requiring a second admin to approve (or deny) running commands through **sudo**. Not just that, but sessions can be followed on-screen and terminated if there is suspicious activity.
-
-In a demo I did during a recent talk at the All Things Open conference, I had the infamous:
-
-
-```
-`czanik@linux-mewy:~> sudo rm -fr /`
-```
-
-command displayed on the screen. Everybody was holding their breath to see whether my laptop got destroyed, but it survived.
-
-### Logs
-
-As I already mentioned at the beginning, logging and alerting is an important part of **sudo**. If you do not check your **sudo** logs regularly, there is not much worth in using **sudo**. This tool alerts by email on events specified in the configuration and logs all events to **syslog**. Debug logs can be turned on and used to debug rules or report bugs.
-
-### Alerts
-
-Email alerts are kind of old-fashioned now, but if you use **syslog-ng** for collecting your log messages, your **sudo** log messages are automatically parsed. You can easily create custom alerts and send those to a wide variety of destinations, including Slack, Telegram, Splunk, or Elasticsearch. You can learn more about this feature from [my blog on syslong-ng.com][4].
-
-### Configuration
-
-We talked a lot about **sudo** features and even saw a few lines of configuration. Now, let’s take a closer look at how **sudo** is configured. The configuration itself is available in **/etc/sudoers**, which is a simple text file. Still, it is not recommended to edit this file directly. Instead, use **visudo**, as this tool also does syntax checking. If you do not like **vi**, you can change which editor to use by pointing the **EDITOR** environment variable at your preferred option.
-
-Before you start editing the **sudo** configuration, make sure that you know the root password. (Yes, even on Ubuntu, where root does not have a password by default.) While **visudo** checks the syntax, it is easy to create a syntactically correct configuration that locks you out of your system.
-
-When you have a root password at hand in case of an emergency, you can start editing your configuration. When it comes to the **sudoers** file, there is one important thing to remember: This file is read from top to bottom, and the last setting wins. What this fact means for you is that you should start with generic settings and place exceptions at the end, otherwise exceptions are overridden by the generic settings.
-
-You can find a simple **sudoers** file below, based on the one in CentOS, and add a few lines we discussed previously:
-
-
-```
-Defaults !visiblepw
-Defaults always_set_home
-Defaults match_group_by_gid
-Defaults always_query_group_plugin
-Defaults env_reset
-Defaults env_keep = "COLORS DISPLAY HOSTNAME HISTSIZE KDEDIR LS_COLORS"
-Defaults env_keep += "MAIL PS1 PS2 QTDIR USERNAME LANG LC_ADDRESS LC_CTYPE"
-Defaults secure_path = /sbin:/bin:/usr/sbin:/usr/bin
-root ALL=(ALL) ALL
-%wheel ALL=(ALL) ALL
-Defaults:%wheel insults
-Defaults !insults
-Defaults log_output
-```
-
-This file starts by changing a number of defaults. Then come the usual default rules: The **root** user and members of the **wheel** group have full permissions over the machine. Next, we enable insults for the **wheel** group, but disable them for everyone else. The last line enables session recording.
-
-The above configuration is syntactically correct, but can you spot the logical error? Yes, there is one: Insults are disabled for everyone since the last, generic setting overrides the previous, more specific setting. Once you switch the two lines, the setup works as expected: Members of the **wheel** group receive funny messages, but the rest of the users do not receive them.
-
-### Configuration management
-
-Once you have to maintain the **sudoers** file on multiple machines, you will most likely want to manage your configuration centrally. There are two major open source possibilities here. Both have their advantages and drawbacks.
-
-You can use one of the configuration management applications that you also use to configure the rest of your infrastructure. Red Hat Ansible, Puppet, and Chef all have modules to configure **sudo**. The problem with this approach is that updating configurations is far from real-time. Also, users can still edit the **sudoers** file locally and change settings.
-
-The **sudo** tool can also store its configuration in LDAP. In this case, configuration changes are real-time and users cannot mess with the **sudoers** file. On the other hand, this method also has limitations. For example, you cannot use aliases or use **sudo** when the LDAP server is unavailable.
-
-### New features
-
-There is a new version of **sudo** right around the corner. Version 1.9 will include many interesting new features. Here are the most important planned features:
-
- * A recording service to collect session recordings centrally, which offers many advantages compared to local storage:
- * It is more convenient to search in one place.
- * Recordings are available even if the sender machine is down.
- * Recordings cannot be deleted by someone who wants to delete their tracks.
- * The **audit** plugin does not add new features to **sudoers**, but instead provides an API for plugins to easily access any kind of **sudo** logs. This plugin enables creating custom logs from **sudo** events using plugins.
- * The **approval** plugin enables session approvals without using third-party plugins.
- * And my personal favorite: Python support for plugins, which enables you to easily extend **sudo** using Python code instead of coding natively in C.
-
-
-
-### Conclusion
-
-I hope this article proved to you that **sudo** is a lot more than just a simple prefix. There are tons of possibilities to fine-tune permissions on your system. You cannot just fine-tune permissions, but also improve security by checking digests. Session recordings enable you to check what is happening on your systems. You can also extend the functionality of **sudo** using plugins, either using something already available or writing your own. Finally, given the list of upcoming features you can see that even if **sudo** is decades old, it is a living project that is constantly evolving.
-
-If you want to learn more about **sudo**, here are a few resources:
-
- * [The **sudo** website][5]
-
- * [The **sudo** blog][6]
-
- * [Follow us on Twitter][7]
-
-
-
-
---------------------------------------------------------------------------------
-
-via: https://opensource.com/article/19/10/know-about-sudo
-
-作者：[Peter Czanik][a]
-选题：[lujun9972][b]
-译者：[译者ID](https://github.com/译者ID)
-校对：[校对者ID](https://github.com/校对者ID)
-
-本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
-
-[a]: https://opensource.com/users/czanik
-[b]: https://github.com/lujun9972
-[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/command_line_prompt.png?itok=wbGiJ_yg (Command line prompt)
-[2]: https://www.sudo.ws
-[3]: https://github.com/square/sudo_pair/
-[4]: https://www.syslog-ng.com/community/b/blog/posts/alerting-on-sudo-events-using-syslog-ng
-[5]: https://www.sudo.ws/
-[6]: https://blog.sudo.ws/
-[7]: https://twitter.com/sudoproject
diff --git a/translated/tech/20191025 How I used the wget Linux command to recover lost images.md b/translated/tech/20191025 How I used the wget Linux command to recover lost images.md
new file mode 100644
index 0000000000..c7c33f1666
--- /dev/null
+++ b/translated/tech/20191025 How I used the wget Linux command to recover lost images.md
@@ -0,0 +1,132 @@
+[#]: collector: (lujun9972)
+[#]: translator: (wxy)
+[#]: reviewer: ( )
+[#]: publisher: ( )
+[#]: url: ( )
+[#]: subject: (How I used the wget Linux command to recover lost images)
+[#]: via: (https://opensource.com/article/19/10/how-community-saved-artwork-creative-commons)
+[#]: author: (Seth Kenlon https://opensource.com/users/seth)
+
+我是如何使用 wget 命令恢复丢失的图像的
+======
+
+> 开放剪贴画库兴衰的故事以及一个新的公共艺术品图书馆 FreeSVG.org 的诞生。
+
+![White shoes on top of an orange tribal pattern][1]
+
+开放剪贴画库（OCAL）发布于 2004 年，成为了免费插图的来源，任何人都可以出于任何目的使用它们，而无需注明出处或提供任何回报。针对 1990 年代每个家庭办公室书架上的大量剪贴画 CD 以及由闭源公司和艺术品软件提供的艺术品转储，这个网站是开源世界的答复。
+
+最初，这个剪贴画库主要由一些贡献者组成，但是在 2010 年，它重新打造成了一个全新的交互式网站，可以让任何人使用矢量插图应用程序创建和贡献剪贴画。该网站立即获得了来自全球的、各种形式的自由软件和自由文化项目的贡献。[Inkscape][2] 中甚至包含了该库的专用导入器。
+
+但是，在 2019 年初，托管开放剪贴画库的网站离线，没有任何警告或解释。它已经成长为有着成千上万的人的社区，起初以为这是暂时的故障。 但是，这个站点一直离线已超过六个月，而没有任何清楚的解释。
+
+谣言开始膨胀。该网站正在更新中（“要偿还数年的技术债务”，网站开发者 Jon Philips 在一封电子邮件中说）。一个 Twitter 帐户声称，该网站遭受了猖狂的 DDoS 攻击。另一个 Twitter 帐户声称，该网站维护者已经成为身份盗用的牺牲品。今天，在撰写本文时，该网站的一个且唯一的页面声明它处于“维护和保护模式”，其含义不清楚，只是用户无法访问其内容。
+
+### 恢复公地
+
+网站会随着时间的流逝而消失，但是对其社区而言开放剪贴画库的丢失尤其令人惊讶，因为它被视为一个社区项目。很少有社区成员知道托管该库的站点已经落入一个维护者手中，因此，由于 [CC0 许可证][3]，该库中的艺术品归所有人所有，但对它的访问是功能性的由单个维护者执行。而且，由于该站点的社区通过该站点彼此保持联系，因此该维护者实际上拥有该社区。
+
+当站点发生故障时，社区以及彼此之间都无法访问其艺术品。没有该站点，就没有社区。
+
+最初，该网站离线后其上的所有东西都是被封挡的。不过，在几个月之后，用户开始意识到该网站的数据库仍然在线，这意味着用户能够通过输入精确的 URL 访问单个剪贴画。换句话说，你不能通过在网站上到处点击来流量剪贴画文件，但是如果你知道该地址，你就可以在浏览器中访问它。类似的，技术型（或偷懒的）用户意识到能够通过类似 `wget` 的自动 Web 浏览器将网站“抓取”下来。
+
+Linux 的 `wget` 命令技术上是一个 Web 浏览器，虽然它不能让你像用 Firefox 一样交互式地浏览。相反，`wget` 可以连到互联网，获取文件或文件集，并下载到你的本次硬盘。然后，你可以在 Firefox 或文本编辑器或最合适的应用程序中打开这些文件，然后查看内容。
+
+通常，`wget` 需要知道要提取的特定文件。如果你使用的是安装了 `wget` 的 Linux 或 macOS，则可以通过下载 [example.com][4] 的索引页来尝试此过程：
+
+```
+$ wget example.org/index.html
+[...]
+$ tail index.html
+
+
+
Example Domain
+
This domain is for illustrative examples in documents.
+ You may use this domain in examples without permission.