-With Tahoe, you can store your files in a distributed way across a set
-of computers, such that if some of the computers fail or become
-unavailable, you can still retrieve your data from the remaining
-computers. You can also securely share your files with other users.
-
-This release is targeted at hackers and users who are willing to use a
-text-oriented web user interface, or a command-line user interface.
-(Or a RESTful API. Just telnet to localhost and type HTTP requests to
-get started.)
-
-Because this software is new, it is not yet recommended for storage of
-highly confidential data nor for important data which is not otherwise
-backed up. Given that caveat, this software works and there are no
-known security flaws which would compromise confidentiality or data
-integrity.
-
-This release of Tahoe is suitable for the "friendnet" use case [3].
-It is easy to set up a private grid which is securely shared among a
-specific, limited set of friends. Files uploaded to this shared grid
-will be available to all friends, even when some of the computers are
-unavailable. It is also easy to encrypt individual files and
-directories so that only designated recipients can read them.
+With Tahoe-LAFS, you distribute your data across multiple
+servers. Even if some of the servers fail or are taken over
+by an attacker, the entire file store continues to function
+correctly, preserving your privacy and security. You can
+easily share specific files and directories with other people.
+
+In addition to the core storage system itself, volunteers
+have built other projects on top of Tahoe-LAFS and have
+integrated Tahoe-LAFS with existing systems, including
+Windows, JavaScript, iPhone, Android, Hadoop, Flume, Django,
+Puppet, bzr, mercurial, perforce, duplicity, TiddlyWiki, and
+more. See the Related Projects page on the wiki [3].
+
+We believe that strong cryptography, Free and Open Source
+Software, erasure coding, and principled engineering practices
+make Tahoe-LAFS safer than RAID, removable drive, tape,
+on-line backup or cloud storage.
+
+This software is developed under test-driven development, and
+there are no known bugs or security flaws which would
+compromise confidentiality or data integrity under recommended
+use. (For all important issues that we are currently aware of
+please see the known_issues.rst file [2].)
+
+
+COMPATIBILITY
+
+This release should be compatible with the version 1 series of
+Tahoe-LAFS. Clients from this release can write files and
+directories in the format used by clients of all versions back
+to v1.0 (which was released March 25, 2008). Clients from this
+release can read files and directories produced by clients of
+all versions since v1.0. Servers from this release can serve
+clients of all versions back to v1.0 and clients from this
+release can use servers of all versions back to v1.0.
+
+Except for the new optional MDMF format, we have not made any
+intentional compatibility changes. However we do not yet have
+the test infrastructure to continuously verify that all new
+versions are interoperable with previous versions. We intend
+to build such an infrastructure in the future.
+
+The new Introducer protocol added in v1.10 is backwards
+compatible with older clients and introducer servers, however
+some features will be unavailable when an older node is
+involved. Please see docs/nodekeys.rst [14] for details.
+
+This is the nineteenth release in the version 1 series. This
+series of Tahoe-LAFS will be actively supported and maintained
+for the foreseeable future, and future versions of Tahoe-LAFS
+will retain the ability to read and write files compatible
+with this series.