docs: remove mention of #1588 from docs/frontends/FTP-and-SFTP.rst, since it is fixed

[tahoe-lafs/tahoe-lafs.git] / docs / frontends / FTP-and-SFTP.rst

diff --git a/docs/frontends/FTP-and-SFTP.rst b/docs/frontends/FTP-and-SFTP.rst
index a7de32c5d8e0168d776690c6e37c6ac9b1934fc8..be9da9e714d58c6cb1510a434e19256af15aa300 100644 (file)
--- a/docs/frontends/FTP-and-SFTP.rst
+++ b/docs/frontends/FTP-and-SFTP.rst
@@ -55,9 +55,7 @@ implemented in Tahoe-LAFS.)
 
 Tahoe-LAFS provides two mechanisms to perform this user-to-cap mapping. The
 first is a simple flat file with one account per line. The second is an
-HTTP-based login mechanism, backed by simple PHP script and a database. The
-latter form is used by allmydata.com to provide secure access to customer
-caps.
+HTTP-based login mechanism, backed by simple PHP script and a database.
 
 Creating an Account File
 ========================
@@ -272,9 +270,6 @@ listed over FTP.
 
 Non-ASCII filenames are not supported by FTP (`ticket #682`_).
 
-The FTP frontend returns all timestamps as being Jan 1, 1970 (`ticket
-#1688`_).
-
 The FTP frontend sometimes fails to report errors, for example if an upload
 fails because it does meet the "servers of happiness" threshold (`ticket
 #1081`_).