1028:
Horowitz later that year. CipherCloud released its Gmail encryption solution in June 2012. By
September 2012 CipherCloud's platform could also encrypt Force.com, Chatter, Microsoft Office 365. It also launched Connect AnyApp, which allowed users to "simply specify fields on Web pages to be encrypted," and data format and operations would be preserved. CipherCloud closed a $ 30 million funding round led by Andreessen Horowitz and Index Ventures in December 2012. Deutsche Telekom also participated in the funding round through T-Ventures, the telecommunications company's venture capital arm. John M. Jack, a partner at Andreessen Horowitz and former CEO of Fortify Software, joined the CipherCloud board following the investment. The company opened its European headquarters in London, England in the same month. CipherCloud added an Australian headquarters in 2013. In February 2013, CipherCloud joined Box Inc. (formerly Box.net), an online file sharing and cloud-content management service, to bring CipherCloud's encryption to file-sharing and file-hosting services such as Box. In January 2014, CipherCloud acquired CloudUp Networks. CloudUp Networks developed software that helped users track data as it moved through cloud environments and restricted that data from leaving the cloud without authorization. In April 2014 CipherCloud released a new product, CipherCloud for Cloud Discovery. Cloud Discovery analyzes cloud applications, which enterprises use for visibility and determine the risk of applications within the organization. According to Forbes, Cloud Discovery analyzes cloud applications such as "CRM, finance, HR, IT management, file sharing, collaboration, and productivity." In November 2014, the company announced closing its Series B funding round of $ 50 million. Transamerica Ventures led the round, joined by Delta Partners, and existing investors Andreessen Horowitz and T-Ventures, the venture capital arm of Deutsche Telekom. In April 2015, CipherCloud acquired Anicut Systems, a privately held provider of adaptive security as a service. The acquisition was made to incorporate cloud security analytics technology and accelerate enterprise cloud adoption. In November 2017, CipherCloud joined the VMware Mobile Security Alliance to provide end-to-end information protection across cloud, mobile and endpoints. In April 2018, CipherCloud announced the launch of CASB+ platform, that enabled cloud data protection in multi-mode deployment: API mode and Inline mode (reverse and forward proxy). In March 2019, CipherCloud announced the availability of Secure SaaS Workspace solution as part of its CASB+ platform, that extended enterprise security controls to the cloud data and eliminated the need to route access to SaaS applications through enterprise's infrastructure. In 2018-2019, CipherCloud was on the Gartner’s Magic Quadrant List for Cloud Access Security Brokers (CASB) in the “Visionary” category.
909:, I'm not sure that goes far enough to explain the full situation. The whole incident got written up in the mainstream press by large outlets like TechCrunch and WIRED, and the incident did bring scrutiny on their security claims. I believe the primary problem is original research, not nececssarily soapboxing. May I propose this edit? "A StackExchange user posted a question on its Cryptography board asking how CipherCloud does encryption. Several users suggested that CipherCloud was not using homomorphic encryption, based on the information available online (a white paper, a promotional video, and a security conference presentation). Many users suggested that the company was instead using deterministic encryption, a weaker method. CipherCloud sent a DMCA takedown notice and defamation complaint to StackExchange about the dialogue/postings. The takedown complaint was ultimately dismissed, but the incident generated scrutiny of CipherCloud’s security claims and approach." Let me know what you think and hopefully we can find a compromise solution.
990:, I saw that in the last week you reverted a number of edits for this page without any reasonable explanation. It makes impression of non-constructive behavior probably related to your based opinion. I want to inform you that I wrote to the Wikimedia Foundation Arbitrage regarding this company's page to ask for a second unbiased opinion about new suggested edits. I want to remind you that Knowledge pages do not belong to anyone and the tags are removable given the fact that the conditions for removal are met. I proclaim that I'm a neutral curious editor who edits from time to time different pages. Also, I have a strong impression that you over-use your power on the Knowledge and treat many editors with condescending manner of not even being able to spend extra time and justify your reverts also making an impression of using a bot automatically working on reverts. If you decide to participate in the discussion, you are more than welcome to do it. Here are the suggested edits:
1050:
more. The Zero-Trust security model adopted by CASB+ enables a single, consistent platform for all cloud applications, delivering seamless data protection with continuous risk assessment and automatic compliance, allowing businesses to get the most from their cloud applications. CASB+ also includes built-in connectors for all the popular cloud applications, that serve as a cloud encryption gateway and encrypt sensitive data in real-time before sending it to the cloud environment. CipherCloud's industry-first
Searchable Strong Encryption (SSE) technology, built using standard cryptographic modules and validated by FIPS 140-2, preserves the cloud functionality, allowing users to seamlessly perform basic cloud operations on the encrypted data, such as search and sort.
1100:
perspective of the company, it is an opinionated statement. For instance, according to whom does the company "ensure" data security? My point is not that you must list what that is coming from but that the statement shouldn't be included in the article as it is opinionated. I don't know much more information so it's hard to give you advice on what to replace it with, but for example this sentence could essentially be shortened to "a cloud services company" (as all cloud services companies I would think would try to ensure data security). Note that this is just an example and there are other instances of this in your text. Let me know if I should provide some more examples.
488:
213:
396:
365:
464:
891:. Yeah, that was my proposal, but "In April 2013, CipherCloud filed a Digital Millennium Copyright Act takedown notice against Stack Exchange Network for posting a discussion titled "How is CipherCloud doing homomorphic encryption?", which CipherCloud claimed contained copyrighted marketing material to criticize the company. The takedown complaint was dismissed." without going into soap. Let me know.
72:
873:, I agree that my edit may have gone a little overboard. I think your edit is good, but are you proposing to replace the entire section with those two sentences? If so, I think at least there should be a sentence that the claim was ultimately dismissed. Maybe keep "The takedown complaint was ultimately dismissed, but the incident generated renewed scrutiny of CipherCloud’s security claims"?
1129:
length of the quote makes it appear as this is the opinion of the article, while in reality the article shouldn't have an opinion. If you remove the very long quote and just put the text "Gartner described CipherCloud products in its annual research report "Magic
Quadrant for Cloud Access Security Broker, Oct 2019"" in the recognition section, this would merit consideration in the article.
124:
103:
21:
134:
550:
1061:
provides a Zero-Trust security model delivering CASB life-cycle with automated security processes so that organizations can adopt more clouds securely. CASB+ also includes
Searchable Strong Encryption (SSE) technology allowing users to perform operations on encrypted data, such as search, sort and analytics.
1049:
CipherCloud's CASB+ platform provides data protection, deep visibility, adaptive access control, advanced threat protection and centralized compliance capabilities across major SaaS and IaaS clouds, including Office 365, Dropbox, Google Suite, Amazon Web
Services, Microsoft Azure, Adobe Analytics and
1221:
I've just done additional clean up of the page, removing duplicate information in the Lead section and cleaning the
History section from all the buzz and redundant words. I thought the tag could be removed after that. Let me know if you still find any issues with the text - please, be specific while
1128:
Ok. I'm just looking at one of your most recent changes (I presume this is you) under the "products" section. Long quotes are discouraged on
Knowledge. In fact in general, quotes should be used quite sparingly. Although given the presence of the quote it's fairly obvious that this is an opinion, the
1060:
CipherCloud's CASB+ platform provides visibility, adaptive access control, data security, threat protection and compliance capabilities across SaaS and IaaS clouds, including Office 365, Salesforce, ServiceNow, Slack, Box, Dropbox, Google Suite, Amazon Web
Services, Microsoft Azure, etc. CipherCloud
1027:
CipherCloud was founded in 2010 by Pravin
Kothari, who previously co-founded ArcSight. The company launched in February 2011 and worked solely in Salesforce.com environments initially. It added Amazon Web Services integration in 2011. CipherCloud raised $ 1.4 million in seed funding from Andreessen
1009:
CipherCloud is a cloud security software company based in San Jose, California. The company enables businesses to adopt cloud services while ensuring data security and regulatory compliance. CipherCloud platform provides risk visibility, cloud control, threat protection, and global data protection
998:
CipherCloud is a cloud security software company based in San Jose, California. The company enables businesses to adopt cloud services while ensuring data security and regulatory compliance. CipherCloud platform provides risk visibility, cloud control, end-to-end encryption, threat protection, data
790:
Hi there. I'm the one who made the edit. As you can see with my talk page post above, I believed the page was being patrolled by users who were filling the page with language reminiscent of public relations and advertising. When I did some research, I found several sources that dealt with the DCMA
645:
As others have noted on this talk page, this article contains a lot of puffery and reads very much like an advertisement for CipherCloud. As a result, I have added the Advert
Template to this page. In addition, very many publicly available articles on CipherCloud mention the DCMA takedown issue. I
855:): "In April 2013, CipherCloud filed a Digital Millennium Copyright Act takedown notice against Stack Exchange Network for posting a discussion titled "How is CipherCloud doing homomorphic encryption?", which CipherCloud claimed contained copyrighted marketing material to criticize the company."
674:
magazine sentence for the paragraph, as it is used as the source for supporting the section. This was my edit: "In April 2013, CipherCloud filed a Digital Millennium Copyright Act takedown notice against Stack Exchange Network for posting a discussion titled "How is CipherCloud doing homomorphic
1076:
2019. SaaS Security Solution of the Year (in Cloud Security category) (CyberSecurity Breakthrough) 2016. Best Cloud Computing Security Solution (SC Magazine 2016 Awards) 2014. 10th Info Security Global Excellence Awards 2013. "Information Security Product of the Year" (SC Magazine's Excellence
646:
find it very suspicious that this page has consistently been edited to remove that from the page, even though it was a very public and widely documented controversy. For that reason, I am adding a discussion of that issue into a new section, with several publicly available secondary sources.
1099:
Here are my suggestions for making this seem less advertorial. Try to stick to the facts. I would avoid vague statements as much as possible. For instance, "enables businesses to adopt cloud services while ensuring data security and regulatory compliance." While this might be true from the
736:
targeted by the notice might be worth a link as well, since it's the only publicly available analysis of their product I can find. I won't revert that change, since my involvement in the incident constitutes a conflict of interest.
1003:
Hello, I suggest to remove "end-to-end encryption" and "data sovereignty" as they are redundant and a bit promotional. Additionally, Gartner announced in 2019 that the CASB space is evolving to SASE where CipherCloud fits
675:
encryption?", which CipherCloud claimed contained copyrighted marketing material to criticize the company." Does this work and/or should it be in that section? I think it reads better imo. Thanks for your comments!
791:
takedown controversy, and I thought it was sufficient to include in the article. While I'm open to suggestions and/or working with others on how to improve the section, I believe it should remain on the page.
1300:
1054:
please change "platform" to "product and technology"; remove promotional words "deep", "advanced", "centralized", "seamless", etc. Keep either "single" or "consistent", but not both, etc. see the following
1066:
According to Gartner’s recently released 2019 Magic Quadrant Critical Capabilities for CASB report, CipherCloud received the highest ratings of 26.5 out of 30, leading the CASB market in functionality.
817:
for sure. At a quick glance, there's a lot more to comb through, both ott editing and npov. Definitely agree that the page has gotten out of hand on that front. Regarding DCMA.. I proposed this edit
231:
1223:
334:
41:
1083:
999:
sovereignty, and global data protection compliance. CipherCloud is in two categories of security vendors classified by Gartner as cloud access security broker and Cloud Encryption Gateway.
1280:
581:
1295:
502:
1227:
1290:
270:
257:
51:
1265:
454:
444:
190:
1275:
1162:
1114:
Update: I just saw that that is already in the article. It should definitely be deleted, but I will provide some comments on your specific draft now.
478:
1250:
180:
1305:
1260:
1255:
515:
497:
379:
1270:
1245:
420:
244:
156:
264:
1087:
1206:
629:
733:
1195:
1310:
403:
370:
147:
108:
1285:
473:
375:
325:
1015:
238:
225:
83:
830:
668:
I moved the DCMA take-down notice material up to the "History" section in a previous edit. In the move, I removed the
251:
1163:
https://www.brighttalk.com/webcast/17800/395573/a-cloud-first-security-architecture-secure-access-service-edge-sase
761:
775:
Saw this on my WL w/ expansion further than my edit suggestions above. Tagging for pov, will await feedback here.
590:
Create the Project Navigation Box including lists of adopted articles, requested articles, reviewed articles, etc.
27:
564:
71:
952:
The next issue is the excess advertising mentioned above. I cut some, but this needs work. Will circle back.
914:
878:
796:
742:
651:
1173:
416:
297:
757:
625:
277:
89:
738:
621:
715:
617:
1033:
20:
1037:
826:
822:
419:
on Knowledge. If you would like to participate, please visit the project page, where you can join
155:
on Knowledge. If you would like to participate, please visit the project page, where you can join
1207:
https://www.ciphercloud.com/ciphercloud-achieves-highest-gartner-mq-critical-capabilities-scores/
1134:
1119:
1105:
1077:
Awards) 2013. Best Emerging Technology in Information Security (SC Magazine's Excellence Awards)
923:
910:
888:
874:
806:
792:
647:
1184:
559:
1196:
https://blogs.gartner.com/andrew-lerner/2019/12/23/say-hello-sase-secure-access-service-edge/
756:
The most recent edit was a P.R. piece that was planted. I reverted it and seek comment here.
957:
943:
896:
860:
842:
780:
709:
695:
680:
283:
139:
825:
and clarity. The newest controversy section is more expansive than previously and contains
314:
834:
704:
Made edit in section. I think it works higher up on the page in the History. Thoughts?
290:
212:
593:
Find editors who have shown interest in this subject and ask them to take a look here.
1239:
1130:
1115:
1101:
809:. Just checked out the revision history and definitely found some overt advertising
987:
487:
1010:
compliance. CipherCloud is in three categories of security vendors classified by
953:
939:
906:
892:
870:
856:
838:
776:
705:
691:
676:
463:
395:
364:
129:
1032:
please include minor edits of the description I made on the main page today.
412:
30:. Please review the prior discussions if you are considering re-nomination:
930:
article, but agree that this was covered in reputable news. I pulled from
1018:(CASB), Cloud Encryption Gateway, and Secure Access Service Edge(SASE) .
408:
1174:
https://www.gartner.com/it-glossary/cloud-access-security-brokers-casbs/
1011:
152:
123:
102:
549:
1231:
1138:
1123:
1109:
1091:
961:
947:
918:
900:
882:
864:
852:
846:
818:
800:
784:
765:
746:
719:
699:
684:
655:
633:
670:
65:
15:
1185:
https://www.gartner.com/it-glossary/cloud-encryption-gateways
232:
Knowledge:Requested articles/Business and economics/Companies
548:
486:
462:
1301:
Start-Class Computer Security articles of Low-importance
1081:
All the updates are confirmed by existing or new sources
935:
814:
810:
729:
541:
536:
531:
526:
407:, a collaborative effort to improve the coverage of
151:, a collaborative effort to improve the coverage of
571:Review importance and quality of existing articles
732:, presumably by an employee of ciphercloud. The
574:Identify categories related to Computer Security
1281:Start-Class software articles of Low-importance
1064:
1058:
1052:
1030:
1007:
1001:
728:The paragraph about the DMCA notice has been
8:
271:Category:Company articles needing infoboxes
258:Category:Company articles needing attention
69:
580:Identify articles for creation (see also:
510:
359:
220:Here are some tasks awaiting attention:
198:
97:
1296:Low-importance Computer Security articles
562:. Please allow some days for processing.
1155:
361:
99:
1291:Start-Class Computer Security articles
1224:2601:1C0:CB01:2660:ED91:DC4A:596A:50AD
1084:2601:1C0:CB01:2660:A8F3:B5E:FA09:5E2E
296:Help expand stub articles located at
7:
401:This article is within the scope of
245:Category:Unassessed company articles
145:This article is within the scope of
88:It is of interest to the following
14:
1266:Low-importance Computing articles
587:Identify articles for improvement
1276:Low-importance software articles
613:This page is obvious marketing
394:
363:
322:Tag company talk pages with the
211:
132:
122:
101:
70:
19:
1251:Low-importance company articles
982:Suggested edits and discussions
449:This article has been rated as
429:Knowledge:WikiProject Computing
185:This article has been rated as
165:Knowledge:WikiProject Companies
26:This article was nominated for
1306:All Computer Security articles
1261:Start-Class Computing articles
1256:WikiProject Companies articles
432:Template:WikiProject Computing
311:Tag company articles with the
168:Template:WikiProject Companies
1:
1271:Start-Class software articles
919:20:05, 23 November 2015 (UTC)
901:14:30, 11 November 2015 (UTC)
883:20:44, 10 November 2015 (UTC)
656:15:54, 8 September 2015 (UTC)
558:will be generated shortly by
516:WikiProject Computer Security
498:WikiProject Computer Security
495:This article is supported by
471:This article is supported by
423:and see a list of open tasks.
159:and see a list of open tasks.
1246:Start-Class company articles
1040:) 07:25, 26 April 2020 (UTC)
1016:cloud access security broker
962:21:24, 4 December 2015 (UTC)
948:21:18, 4 December 2015 (UTC)
865:19:31, 3 November 2015 (UTC)
847:18:45, 28 October 2015 (UTC)
837:. Welcome suggestions here.
801:21:38, 22 October 2015 (UTC)
785:22:12, 19 October 2015 (UTC)
202:WikiProject Companies To-do:
634:11:54, 7 October 2013 (UTC)
1327:
1139:03:59, 25 April 2020 (UTC)
1124:03:55, 25 April 2020 (UTC)
1110:03:53, 25 April 2020 (UTC)
1092:01:36, 25 April 2020 (UTC)
455:project's importance scale
191:project's importance scale
887:Thanks for reaching out,
805:Thanks for reaching out,
747:17:25, 29 June 2015 (UTC)
509:
494:
470:
448:
389:
197:
184:
117:
96:
1232:22:48, 5 June 2020 (UTC)
1217:Clean up and tag removal
720:23:42, 21 May 2014 (UTC)
700:23:48, 13 May 2014 (UTC)
685:15:31, 10 May 2014 (UTC)
1222:addressing the issues.
766:05:47, 6 May 2015 (UTC)
1311:All Computing articles
1069:
1063:
1057:
1045:Product and technology
1042:
1020:
1006:
752:Watch for P.R. Puffery
553:
491:
467:
417:information technology
298:Category:Company stubs
78:This article is rated
40:, October 7 2013, see
1286:All Software articles
934:/our proposal edits,
552:
490:
466:
404:WikiProject Computing
335:requests for comments
326:WikiProject Companies
148:WikiProject Companies
831:WP:original research
577:Tag related articles
514:Things you can help
474:WikiProject Software
50:, July 15 2013, see
821:based on issues w/
565:More information...
690:Thoughts on edit?
554:
492:
468:
435:Computing articles
84:content assessment
637:
620:comment added by
611:
610:
607:
606:
603:
602:
599:
598:
358:
357:
354:
353:
350:
349:
346:
345:
64:
63:
60:
59:
1318:
1209:
1204:
1198:
1193:
1187:
1182:
1176:
1171:
1165:
1160:
758:BeenAroundAWhile
722:
636:
614:
582:Article requests
567:
511:
437:
436:
433:
430:
427:
398:
391:
390:
385:
382:
367:
360:
329:
318:
284:Portal:Companies
226:Article requests
215:
208:
207:
199:
173:
172:
171:company articles
169:
166:
163:
142:
140:Companies portal
137:
136:
135:
126:
119:
118:
113:
105:
98:
81:
75:
74:
66:
32:
31:
23:
16:
1326:
1325:
1321:
1320:
1319:
1317:
1316:
1315:
1236:
1235:
1219:
1214:
1213:
1212:
1205:
1201:
1194:
1190:
1183:
1179:
1172:
1168:
1161:
1157:
1074:
1072:Industry Awards
1047:
1025:
996:
984:
926:, didn't see a
833:and borderline
773:
754:
713:
663:
643:
615:
568:
563:
546:
434:
431:
428:
425:
424:
383:
373:
342:
339:
323:
312:
170:
167:
164:
161:
160:
138:
133:
131:
111:
82:on Knowledge's
79:
12:
11:
5:
1324:
1322:
1314:
1313:
1308:
1303:
1298:
1293:
1288:
1283:
1278:
1273:
1268:
1263:
1258:
1253:
1248:
1238:
1237:
1218:
1215:
1211:
1210:
1199:
1188:
1177:
1166:
1154:
1153:
1149:
1148:
1147:
1146:
1145:
1144:
1143:
1142:
1141:
1073:
1070:
1046:
1043:
1024:
1021:
995:
992:
983:
980:
979:
978:
977:
976:
975:
974:
973:
972:
971:
970:
969:
968:
967:
966:
965:
964:
851:Proposed (per
772:
771:Contro section
769:
753:
750:
726:
725:
724:
723:
718:comment added
662:
659:
642:
639:
609:
608:
605:
604:
601:
600:
597:
596:
595:
594:
591:
588:
585:
578:
575:
572:
556:Article alerts
547:
545:
544:
539:
534:
529:
523:
520:
519:
507:
506:
503:Low-importance
493:
483:
482:
479:Low-importance
469:
459:
458:
451:Low-importance
447:
441:
440:
438:
421:the discussion
399:
387:
386:
384:Low‑importance
368:
356:
355:
352:
351:
348:
347:
344:
343:
341:
340:
338:
337:
331:
330:project banner
320:
308:
300:
286:
273:
260:
247:
234:
219:
217:
216:
204:
203:
195:
194:
187:Low-importance
183:
177:
176:
174:
157:the discussion
144:
143:
127:
115:
114:
112:Low‑importance
106:
94:
93:
87:
76:
62:
61:
58:
57:
56:
55:
45:
24:
13:
10:
9:
6:
4:
3:
2:
1323:
1312:
1309:
1307:
1304:
1302:
1299:
1297:
1294:
1292:
1289:
1287:
1284:
1282:
1279:
1277:
1274:
1272:
1269:
1267:
1264:
1262:
1259:
1257:
1254:
1252:
1249:
1247:
1244:
1243:
1241:
1234:
1233:
1229:
1225:
1216:
1208:
1203:
1200:
1197:
1192:
1189:
1186:
1181:
1178:
1175:
1170:
1167:
1164:
1159:
1156:
1152:
1140:
1136:
1132:
1127:
1126:
1125:
1121:
1117:
1113:
1112:
1111:
1107:
1103:
1098:
1097:
1096:
1095:
1094:
1093:
1089:
1085:
1082:
1078:
1071:
1068:
1062:
1056:
1051:
1044:
1041:
1039:
1035:
1029:
1022:
1019:
1017:
1013:
1005:
1000:
993:
991:
989:
981:
963:
959:
955:
951:
950:
949:
945:
941:
937:
933:
929:
925:
924:BurritoSlayer
922:
921:
920:
916:
912:
911:BurritoSlayer
908:
904:
903:
902:
898:
894:
890:
889:BurritoSlayer
886:
885:
884:
880:
876:
875:BurritoSlayer
872:
868:
867:
866:
862:
858:
854:
850:
849:
848:
844:
840:
836:
832:
828:
824:
820:
816:
812:
808:
807:BurritoSlayer
804:
803:
802:
798:
794:
793:BurritoSlayer
789:
788:
787:
786:
782:
778:
770:
768:
767:
763:
759:
751:
749:
748:
744:
740:
735:
731:
721:
717:
711:
707:
703:
702:
701:
697:
693:
689:
688:
687:
686:
682:
678:
673:
672:
666:
660:
658:
657:
653:
649:
648:BurritoSlayer
640:
638:
635:
631:
627:
623:
619:
592:
589:
586:
583:
579:
576:
573:
570:
569:
566:
561:
557:
551:
543:
540:
538:
535:
533:
530:
528:
525:
524:
522:
521:
517:
513:
512:
508:
504:
501:(assessed as
500:
499:
489:
485:
484:
480:
477:(assessed as
476:
475:
465:
461:
460:
456:
452:
446:
443:
442:
439:
422:
418:
414:
410:
406:
405:
400:
397:
393:
392:
388:
381:
377:
372:
369:
366:
362:
336:
332:
327:
321:
316:
310:
309:
307:
305:
301:
299:
295:
293:
292:
287:
285:
282:
280:
279:
274:
272:
269:
267:
266:
261:
259:
256:
254:
253:
248:
246:
243:
241:
240:
235:
233:
230:
228:
227:
222:
221:
218:
214:
210:
209:
206:
205:
201:
200:
196:
192:
188:
182:
179:
178:
175:
158:
154:
150:
149:
141:
130:
128:
125:
121:
120:
116:
110:
107:
104:
100:
95:
91:
85:
77:
73:
68:
67:
53:
49:
46:
43:
39:
36:
35:
34:
33:
29:
25:
22:
18:
17:
1220:
1202:
1191:
1180:
1169:
1158:
1150:
1080:
1079:
1075:
1065:
1059:
1053:
1048:
1031:
1026:
1008:
1002:
997:
994:Lead Section
985:
931:
927:
827:WP:synthesis
823:WP:Quotefarm
774:
755:
739:CodesInChaos
727:
714:— Preceding
669:
667:
664:
644:
616:— Preceding
612:
555:
496:
472:
450:
402:
317:|Companies}}
303:
302:
289:
288:
276:
275:
263:
262:
250:
249:
237:
236:
224:
223:
186:
146:
90:WikiProjects
47:
37:
622:Mikefromnyc
80:Start-class
1240:Categories
1151:References
928:TechCrunch
734:discussion
641:PR Puffery
52:discussion
42:discussion
1055:revision:
1034:Peter9970
560:AAlertBot
426:Computing
413:computing
409:computers
371:Computing
162:Companies
153:companies
109:Companies
1131:Sam-2727
1116:Sam-2727
1102:Sam-2727
936:see here
630:contribs
618:unsigned
380:Security
376:Software
319:template
278:Maintain
252:Copyedit
28:deletion
1023:History
1012:Gartner
988:MrOllie
835:WP:soap
730:removed
716:undated
532:history
453:on the
333:Answer
265:Infobox
189:on the
954:Jppcap
940:Jppcap
907:Jppcap
893:Jppcap
871:Jppcap
857:Jppcap
839:Jppcap
777:Jppcap
706:Jppcap
692:Jppcap
677:Jppcap
415:, and
315:portal
239:Assess
86:scale.
48:delete
1004:well.
932:Wired
671:Wired
542:purge
537:watch
518:with:
304:Other
291:Stubs
1228:talk
1135:talk
1120:talk
1106:talk
1088:talk
1038:talk
986:Hi,
958:talk
944:talk
915:talk
897:talk
879:talk
861:talk
853:here
843:talk
819:here
815:here
813:and
811:here
797:talk
781:talk
762:talk
743:talk
710:talk
696:talk
681:talk
665:Hi,
661:DCMA
652:talk
626:talk
527:edit
38:keep
1014:as
905:Hi
869:Hi
712:)
445:Low
181:Low
1242::
1230:)
1137:)
1122:)
1108:)
1090:)
960:)
946:)
938:.
917:)
899:)
881:)
863:)
845:)
829:,
799:)
783:)
764:)
745:)
698:)
683:)
654:)
632:)
628:•
505:).
481:).
411:,
378:/
374::
328:}}
324:{{
313:{{
1226:(
1133:(
1118:(
1104:(
1086:(
1036:(
956:(
942:(
913:(
895:(
877:(
859:(
841:(
795:(
779:(
760:(
741:(
708:(
694:(
679:(
650:(
624:(
584:)
457:.
306::
294::
281::
268::
255::
242::
229::
193:.
92::
54:.
44:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
