Changes between Version 158 and Version 159 of ViewTickets

Timestamp:

2010-12-16T01:05:53Z (14 years ago)

Author:

davidsarah

Comment:

fix anti-censorship query syntax

ViewTickets

@@ -26 +26 @@
  * [query:status!=closed&keywords~=availability availability] ([[TicketQuery(status!=closed&keywords~=availability, count)]]): could lead to a temporary condition of being unable to read or write to the filesystem
  * [query:status!=closed&keywords~=reliability reliability] ([[TicketQuery(status!=closed&keywords~=reliability, count)]]): could lead to unpredictable failure of functionality
- * [query:status!=closed&keywords~=anti-censorship] ([[TicketQuery(status!=closed&keywords~=anti-censorship, count)]]): could help with resistance to censorship or denial of service
+ * [query:status!=closed&keywords~=anti-censorship anti-censorship] ([[TicketQuery(status!=closed&keywords~=anti-censorship, count)]]): could help with resistance to censorship or denial of service
  * [query:status!=closed&keywords~=scalability scalability] ([[TicketQuery(status!=closed&keywords~=scalability, count)]]): scaling to large and/or geographically dispersed storage grids, or to high traffic volumes or numbers of clients
  * [query:status!=closed&keywords~=location location] ([[TicketQuery(status!=closed&keywords~=location, count)]]): concerned with location awareness -- placement of shares according to topographical, geographical, bandwidth, etc. constraints