remove <LegacyCallout /> tags

cwaring · cwaring · commit 51f10a65ad8e · 2019-12-10T21:22:47.000Z
diff --git a/docs/README.md b/docs/README.md
@@ -34,5 +34,3 @@ Also, check out [ProtoSchool](https://www.proto.school) for interactive tutorial
 ## The IPFS project
 
 [Learn all about the IPFS project](/project/), including its history, current state, specifications, and future trajectory — plus, find everything you need to know in order to join the thousands of IPFS contributors from around the world!
-
-<LegacyCallout />
diff --git a/docs/community/README.md b/docs/community/README.md
@@ -34,5 +34,3 @@ We're in a lot of places. Here's [how to find them all](social-media) for your f
 ## Awesome IPFS
 
 Get inspired by [Awesome IPFS](https://awesome.ipfs.io/), a catalog of community-built projects using IPFS for everything from image sharing to decentralized archiving. Have a project of your own to add to Awesome IPFS? Make a PR [in the repo!](https://github.com/ipfs/awesome-ipfs)
-
-<LegacyCallout />
diff --git a/docs/community/irc.md b/docs/community/irc.md
@@ -22,5 +22,3 @@ If you’re new to IRC, there are _lots_ of mobile and desktop clients for worki
 - [Textual](https://www.codeux.com/textual/) or [Adium](https://adium.im) on macOS
 - [mIRC](http://standaloneinstaller.com/download-mirc) or [HexChat](https://hexchat.github.io) on Windows
 - [XChat](http://xchat.org) or [Irssi](https://irssi.org) on Linux
-
-<LegacyCallout />
diff --git a/docs/community/social-media.md b/docs/community/social-media.md
@@ -23,5 +23,3 @@ Get your IPFS news in tweet-sized bites. Follow these accounts for the latest:
 - [@IPFSbot](https://twitter.com/IPFSbot) for news and other updates
 - [@IPFSevents](https://twitter.com/ipfsevents) for info on IPFS-related events
 - [@ProtoSchool](https://twitter.com/protoschool) for updates on ProtoSchool chapters and tutorials
-
-<LegacyCallout />
diff --git a/docs/concepts/README.md b/docs/concepts/README.md
@@ -56,5 +56,3 @@ IPFS aims to be the future of the internet, but it still needs to play well with
 ## Don't see what you're looking for?
 
 We're adding more documentation all the time and making ongoing revisions to existing docs, but if you don't see what you need, please [file an issue](https://github.com/ipfs/docs/issues/new?assignees=&labels=OKR+3%3A+Content+Improvement%2C+docs-ipfs&template=content-request.md&title=%5BCONTENT+REQUEST%5D+%28add+your+title+here%21%29) to let us know! We also recommend visiting the [IPFS forums](https://discuss.ipfs.io/) for support and discussion with IPFS enthusiasts and experts worldwide.
-
-<LegacyCallout />
diff --git a/docs/concepts/content-addressing.md b/docs/concepts/content-addressing.md
@@ -43,5 +43,3 @@ You can use the first few bytes of the CID to interpret the remainder of the con
 ## CID Inspector
 
 It's easy to explore a CID for yourself. Want to pull apart a specific CID's multibase, multicodec, or multihash info? You can use the [CID Inspector](https://cid.ipfs.io/#QmY7Yh4UquoXHLPFo2XbhXkhBvFoPwmQUSa92pxnxjQuPU) or the [CID Info panel in IPLD Explorer](https://explore.ipld.io/#/explore/QmY7Yh4UquoXHLPFo2XbhXkhBvFoPwmQUSa92pxnxjQuPU) (both links launch using a sample CID) for an interactive breakdown of differently-formatted CIDs.
-
-<LegacyCallout />
diff --git a/docs/concepts/dht.md b/docs/concepts/dht.md
@@ -83,5 +83,3 @@ Adding a blob of data to IPFS is the equivalent of advertising that you have it.
 IPFS will automatically chunk your data and add a mapping on the DHT between the Content ID and your `peerID`. Note that there can be other `peerID`s already mapped to that value, so you will be added to the list. Also note that if the provided data is bigger than 124KB, it will be chunked into "blocks", and both those blocks and the overall data will be mapped.
 
 You can publish an IPNS record using [`ipfs.name.publish`](/concepts/ipns).
-
-<LegacyCallout />
diff --git a/docs/concepts/dnslink.md b/docs/concepts/dnslink.md
@@ -61,5 +61,3 @@ Will get you this block:
 ## Further Resources
 
 For a complete guide to DNSLink — including tutorials, usage examples and FAQs — check out [dnslink.io](http://dnslink.io/).
-
-<LegacyCallout />
diff --git a/docs/concepts/faq.md b/docs/concepts/faq.md
@@ -50,5 +50,3 @@ IPFS is an open source project, with a community of more than four thousand cont
 ## Don't see your question?
 
 We're working on expanding this FAQ with more content, including questions from the original-generation [IPFS forums](https://discuss.ipfs.io/c/help/Old-FAQ), so please watch this space! However, if you don’t see your question, please [ask in the forums](https://discuss.ipfs.io/) so you can get the answers you need and make us aware of new FAQ items.
-
-<LegacyCallout />
diff --git a/docs/concepts/file-systems.md b/docs/concepts/file-systems.md
@@ -35,5 +35,3 @@ A file in IPFS isn’t just content. It might be too big to fit in a single bloc
 UnixFS is a [protocol-buffers](https://developers.google.com/protocol-buffers/)-based format. You can find the definitions for it [here](https://github.com/ipfs/go-unixfs/blob/master/pb/unixfs.proto).
 
 _Note: we are currently designing an updated version of UnixFS that will be [IPLD](https://ipld.io)-compatible. You can follow along or participate [on GitHub](https://github.com/ipfs/unixfs-v2)._
-
-<LegacyCallout />
diff --git a/docs/concepts/hashing.md b/docs/concepts/hashing.md
@@ -51,5 +51,3 @@ Cryptographic hashes come with a couple of very important characteristics:
 It turns out these features also mean we can use a cryptographic hash to identify any piece of data: the hash is unique to the data we calculated it from and it’s not too long (a hash is a fixed length, so the SHA-256 hash of a one-gigabyte video file is still only 32 bytes), so sending it around the network doesn't take up a lot of resources.
 
 That's critical for a distributed system like IPFS, where we want to be able to store and retrieve data from many places. A computer running IPFS can ask all the peers it's connected to whether they have a file with a particular hash and, if one of them does, they send back the whole file. Without a short, unique identifier like a cryptographic hash, that wouldn't be possible. This technique is called [content addressing](/concepts/content-addressing/) — because the content itself is used to form an address, rather than information about the computer and disk location it's stored at.
-
-<LegacyCallout />
diff --git a/docs/concepts/how-ipfs-works.md b/docs/concepts/how-ipfs-works.md
@@ -76,5 +76,3 @@ This is useful because establishing connections is usually hard to set up and ex
 As you may have noticed from this discussion, the IPFS ecosystem is made up of many modular libraries that support specific parts of any distributed system. You can certainly use any part of the stack independently, or combine them in novel ways.
 
 The IPFS ecosystem gives CIDs to content, and links that content together by generating IPLD Merkle DAGs. You can discover content using a DHT that's provided by libp2p, and open a connection to any provider of that content and download it using a multiplexed connection. All of this is held together by the “middle” of the stack, which is linked, unique identifiers; that's the essential part that IPFS is built on.
-
-<LegacyCallout />
diff --git a/docs/concepts/ipns.md b/docs/concepts/ipns.md
@@ -38,5 +38,3 @@ In the same way, you can republish a new version of your website under the same
 ## Alternatives to IPNS
 
 IPNS is not the only way to create mutable addresses on IPFS. You can also use [DNSLink](/concepts/dnslink/), which is currently much faster than IPNS and also uses more readable names. Other community members are exploring ways to use blockchains to store common name records.
-
-<LegacyCallout />
diff --git a/docs/concepts/merkle-dag.md b/docs/concepts/merkle-dag.md
@@ -26,5 +26,3 @@ Merkle DAGs are _self-verified_ structures. The CID of a node is univocally link
 ## Further resources
 
 For more information, you may want to read the full [draft Merkle-CRDTs paper](https://hector.link/presentations/merkle-crdts/merkle-crdts.pdf) by [@hsanjuan](https://www.github.com/hsanuan), [@haadcode](https://www.github.com/haadcode), and [@pgte](https://www.github.com/pgte).
-
-<LegacyCallout />
diff --git a/docs/concepts/persistence.md b/docs/concepts/persistence.md
@@ -26,5 +26,3 @@ To ensure that your important data is retained, you may want to use a pinning se
 - You don’t have a lot of disk space, but you want to ensure some data sticks around.
 - Your computer is a laptop, phone, or tablet that will have intermittent connectivity to the network, but you want to be able to access your data on IPFS from anywhere at any time, even when the device you added it from is offline.
 - You want a backup that ensures your data is always available from another computer on the network in case you accidentally delete or garbage-collect on your own computer.
-
-<LegacyCallout />
diff --git a/docs/concepts/what-is-ipfs.md b/docs/concepts/what-is-ipfs.md
@@ -79,5 +79,3 @@ While there’s lots of complex technology in IPFS, the fundamental ideas are ab
 That means IPFS only works well when people are actively participating. If you use your computer to share files using IPFS, but then you turn your computer off, other people won’t be able to get those files from you anymore. But if you or others make sure that copies of those files are stored on more than one computer that’s powered on and running IPFS, those files will be more reliably available to other IPFS users who want them. This happens to some extent automatically: by default, your computer shares a file with others for a limited time after you’ve downloaded it using IPFS. You can also make content available more permanently by _pinning_ it, which saves it to your computer and makes it available on the IPFS network until you decide to _unpin_ it. (You can learn more about this in our [guide to persistence and pinning](/concepts/persistence).)
 
 If you want to make sure one of your own files is permanently shared on the internet today, you might use a for-pay file-sharing service like Dropbox. Some people have begun offering similar services based on IPFS called _pinning services_. But since IPFS makes this kind of sharing a built-in feature, you can also collaborate with friends or partner with institutions (for example, museums and libraries might work together) to share each others’ files. We hope IPFS can be the low-level tool that allows a rich fabric of communities, business, and cooperative organizations to all form a distributed web that is much more reliable, robust, and equitable than the one we have today.
-
-<LegacyCallout />
diff --git a/docs/how-to/README.md b/docs/how-to/README.md
@@ -24,5 +24,3 @@ See the site navigation menu for all our how-tos, organized by topic area, inclu
 ## Don't see what you're looking for?
 
 We're adding more documentation all the time and making ongoing revisions to existing docs, but if you don't see what you need, please [file an issue](https://github.com/ipfs/docs/issues/new?assignees=&labels=OKR+3%3A+Content+Improvement%2C+docs-ipfs&template=content-request.md&title=%5BCONTENT+REQUEST%5D+%28add+your+title+here%21%29) to let us know! We also recommend visiting the [IPFS forums](https://discuss.ipfs.io/) for support and discussion with IPFS enthusiasts and experts worldwide.
-
-<LegacyCallout />
diff --git a/docs/how-to/address-ipfs-on-web.md b/docs/how-to/address-ipfs-on-web.md
@@ -123,5 +123,3 @@ This concept isn't yet built, but may be explored and experimented with in the f
 
 - `dweb://` protocol handler ([arewedistributedyet/issues/28](https://github.com/arewedistributedyet/arewedistributedyet/issues/28))
 - `.dweb` special-use top-level domain name ([arewedistributedyet/issues/34](https://github.com/arewedistributedyet/arewedistributedyet/issues/34))
-
-<LegacyCallout />
diff --git a/docs/how-to/browser-tools-frameworks.md b/docs/how-to/browser-tools-frameworks.md
@@ -29,5 +29,3 @@ Want to learn how to use IPFS in combination with your favorite framework or bro
 ## Electron
 
 [Minimal example](https://github.com/ipfs/js-ipfs/blob/master/examples/run-in-electron) of how to use js-ipfs in your Electron app.
-
-<LegacyCallout />
diff --git a/docs/how-to/command-line-quick-start.md b/docs/how-to/command-line-quick-start.md
@@ -281,5 +281,3 @@ You need to install and set up FUSE in order to mount the file system. For more
 ### Still need help?
 
 The IPFS community is friendly and able to help! Get support from other IPFS developers in the official [IPFS forums](https://discuss.ipfs.io/), or join the conversation on [IRC](/community/irc/).
-
-<LegacyCallout />
diff --git a/docs/how-to/configure-node.md b/docs/how-to/configure-node.md
@@ -40,5 +40,3 @@ The mounts config values specifies the default mount points for the IPFS and ipn
 ## Bootstrap
 
 The Bootstrap config array specifies the list of IPFS peers that your daemon will connect to on startup. The default values for this are the 'ipfs solarnet' nodes, which are a set of VPS servers distributed around the country.
-
-<LegacyCallout />
diff --git a/docs/how-to/host-git-style-repo.md b/docs/how-to/host-git-style-repo.md
@@ -77,5 +77,3 @@ import (
 And you will be guaranteed to have the same code every time!
 
 Note: Since Go doesn't allow the usage of localhost for import paths, we use the public HTTP gateways. This provides no security guarantees, as a man-in-the-middle attack could ship you bad code. You could use a domain name that redirects to the localhost instead to avoid the issue.
-
-<LegacyCallout />
diff --git a/docs/how-to/host-single-page-site.md b/docs/how-to/host-single-page-site.md
@@ -114,5 +114,3 @@ Alternatively, it is possible to use CNAME records to point at the DNS records o
 However you will need to change the key for the TXT record from `your.domain` to `_dnslink.your.domain`.
 
 So by creating a CNAME for `your.domain` to `gateway.ipfs.io` and adding a `_dnslink.your.domain` record with `dnslink=/ipns/<your peer id>` you can host your website without explicitly referring to IP addresses of the ipfs gateway.
-
-<LegacyCallout />
diff --git a/docs/how-to/make-service.md b/docs/how-to/make-service.md
@@ -161,5 +161,3 @@ Now, you might be asking yourself: "Why would I use this? How is it better than
 1. You dial a specific peerID, no matter what their IP address happens to be at the moment.
 2. You take advantage of the NAT traversal built into our net package.
 3. Instead of a 'port' number, you get a much more meaningful protocol ID string.
-
-<LegacyCallout />
diff --git a/docs/how-to/modify-bootstrap-list.md b/docs/how-to/modify-bootstrap-list.md
@@ -62,5 +62,3 @@ Remove the entire bootstrap list again, and restore our saved one by piping the
 ipfs bootstrap rm --all
 cat save | ipfs bootstrap add
 ```
-
-<LegacyCallout />
diff --git a/docs/how-to/observe-peers.md b/docs/how-to/observe-peers.md
@@ -24,5 +24,3 @@ Search for a given peer on the network:
 ```sh
 ipfs dht findpeer QmSoLnSGccFuZQJzRadHn95W2CrSFmZuTdDWP8HXaHca9z
 ```
-
-<LegacyCallout />
diff --git a/docs/how-to/pin-files.md b/docs/how-to/pin-files.md
@@ -39,5 +39,3 @@ ipfs pin rm -r <foo hash>
 ipfs repo gc
 ipfs cat <foo hash>
 ```
-
-<LegacyCallout />
diff --git a/docs/how-to/store-play-videos.md b/docs/how-to/store-play-videos.md
@@ -30,5 +30,3 @@ Or open it up in a browser tab (in this example, Chrome):
 ```bash
 chromium http://localhost:8080/ipfs/$vidhash
 ```
-
-<LegacyCallout />
diff --git a/docs/how-to/take-snapshot.md b/docs/how-to/take-snapshot.md
@@ -49,5 +49,3 @@ ls
 ```
 
 Through the FUSE interface, you'll be able to access your files exactly as they were when you took the snapshot.
-
-<LegacyCallout />
diff --git a/docs/how-to/work-with-blocks.md b/docs/how-to/work-with-blocks.md
@@ -51,5 +51,3 @@ ipfs block get QmfQ5QAjvg4GtA3wg3adpnDJug8ktA1BxurVqBD8rtgVjM
 ```
 
 Note: When making your own block data, you won't be able to read the data with `ipfs cat`. This is because you are inputting raw data without the unixfs data format. To read raw blocks, use `ipfs block get` as shown in the example.
-
-<LegacyCallout />
diff --git a/docs/install/README.md b/docs/install/README.md
@@ -55,5 +55,3 @@ Go developers, this reference implementation of IPFS is for you. [Install go-ipf
 ### Install js-ipfs
 
 Building for the browser, or for JavaScript-driven frameworks like Electron? Bake in IPFS goodness with the JS implementation. [Install js-ipfs now](https://www.npmjs.com/package/ipfs)
-
-<LegacyCallout />
diff --git a/docs/project/README.md b/docs/project/README.md
@@ -41,5 +41,3 @@ Thousands of people contribute to IPFS from all over the world — and that can
 ## Code of conduct
 
 The IPFS community believes that our mission is best served in an environment that is friendly, safe, and accepting, and free from intimidation or harassment. To that end, we ask that everyone involved in IPFS read and respect our [code of conduct](https://github.com/ipfs/community/blob/master/code-of-conduct.md).
-
-<LegacyCallout />
diff --git a/docs/project/contribute.md b/docs/project/contribute.md
@@ -80,5 +80,3 @@ IPFS is ultimately about building better protocols, and we always welcome ideas
 ## Research
 
 Finally, we see Protocol Labs as a research lab, where YOUR ideas can become technologies that have a real impact on the world. If you're interested in contributing to our research, please reach out to research@ipfs.io or research@protocol.ai for more information. Include what your interests are so we can make sure you get to work on something fun and valuable.
-
-<LegacyCallout />
diff --git a/docs/project/related-projects.md b/docs/project/related-projects.md
@@ -29,5 +29,3 @@ The Multiformats Project is a collection of protocols which aim to future-proof
 ## ProtoSchool
 
 Interactive tutorials on decentralized web protocols, designed to introduce you to decentralized web concepts, protocols, and tools. Complete code challenges right in your web browser and track your progress as you go. Learn more at [https://proto.school/](https://proto.school/).
-
-<LegacyCallout />
diff --git a/docs/reference/README.md b/docs/reference/README.md
@@ -24,5 +24,3 @@ We're currently investigating improved ways to present our API and CLI reference
 ## CLI commands
 
 Working in the terminal? Here's where you'll find the IPFS [command-line interface (CLI) reference](/reference/cli/).
-
-<LegacyCallout />
diff --git a/docs/reference/cli.md b/docs/reference/cli.md
@@ -4479,5 +4479,3 @@ DESCRIPTION
 
 
 ```
-
-<LegacyCallout />
diff --git a/docs/reference/go/api.md b/docs/reference/go/api.md
@@ -45,5 +45,3 @@ If you are running IPFS as a separate process, you should use `go-ipfs-api` to w
 ## Go HTTP clients
 
 [CoreAPI implementation using HTTP API](https://godoc.org/github.com/ipfs/go-ipfs-http-client). **This package is experimental and subject to change.** For an old but stable Go HTTP client, use [CoreAPI interfaces](https://godoc.org/github.com/ipfs/interface-go-ipfs-core).
-
-<LegacyCallout />
diff --git a/docs/reference/http/api.md b/docs/reference/http/api.md
@@ -3629,5 +3629,3 @@ On success, the call to this endpoint will return with 200 and the following bod
 ### cURL Example
 
 `curl "http://localhost:5001/api/v0/version/deps"`
-
-<LegacyCallout />
diff --git a/docs/reference/js/api.md b/docs/reference/js/api.md
@@ -30,5 +30,3 @@ See the [JS core API reference](https://github.com/ipfs/interface-ipfs-core/tree
 ## JS HTTP client library
 
 A [client library](https://github.com/ipfs/js-ipfs-http-client) for the IPFS HTTP API, implemented in JavaScript. This client library implements the interface-ipfs-core enabling applications to change between an embedded js-ipfs node and any remote IPFS node without having to change the code. In addition, this client library implements a set of utility functions.
-
-<LegacyCallout />

-Original file line number
+Diff line change
 ## Research
 Finally, we see Protocol Labs as a research lab, where YOUR ideas can become technologies that have a real impact on the world. If you're interested in contributing to our research, please reach out to [email protected] or [email protected] for more information. Include what your interests are so we can make sure you get to work on something fun and valuable.
+-
 -<LegacyCallout />
Original file line number	Diff line number	Diff line change
`@@ -4479,5 +4479,3 @@ DESCRIPTION`
`4479`	`4479`
`4480`	`4480`
`4481`	`4481`	```
`4482`		`-`
`4483`		`-<LegacyCallout />`