229:
that the passwords were now likely to be in the hands of criminals"; "Vicente
Silveira, a director at LinkedIn, confirmed the hack on the company's blog on Wednesday afternoon and said that LinkedIn was taking steps to deal with the situation. He wrote that those with compromised passwords will notice that their LinkedIn account password is no longer valid" vs "Vicente Silveira, Director at LinkedIn, confirmed the hack on the company's blog Wednesday afternoon and outlined steps that LinkedIn is taking to deal with the situation. He wrote that those with compromised passwords will notice that their LinkedIn account password is no longer valid."; "LinkedIn said it sent emails to members whose passwords were affected, explaining how to reset them since they were no longer valid on the site" vs "LinkedIn said it sent emails to members whose passwords were affected, explaining how to reset them since they were no longer valid on the site."
262:
the breach was genuine and warned that the passwords were now likely to be in the hands of criminals"; "Vicente
Silveira, a LinkedIn director, confirmed the hack on the company's blog on Wednesday afternoon and said that LinkedIn was taking steps to deal with the situation. He said that those with compromised passwords will notice that their LinkedIn account password is no longer valid" vs "Vicente Silveira, Director at LinkedIn, confirmed the hack on the company's blog Wednesday afternoon and outlined steps that LinkedIn is taking to deal with the situation. He wrote that those with compromised passwords will notice that their LinkedIn account password is no longer valid."
244:
322:
258:
225:
97:
459:
411:
198:
180:
434:
418:
441:
put a tick on an article you created, expanded, or nominated. That's the definition of conflict of interest. Let's let
Nikkimaria, who has identified the problems, say whether they've been settled to her satisfaction. I've found that she's quite happy to do so once the paraphrasing has been fixed.
261:
Yes, it was, but no, it hasn't. Compare: "Graham Cluley, one of the members of internet security firm Sophos, said he believed the breach was genuine and warned that the passwords were now likely to be in the hands of criminals" vs "Graham Cluley, of internet security firm Sophos, said he believed
228:
Copyvio. Compare: "Graham Cluley, member of internet security firm Sophos, said he believed the breach was genuine and warned that the passwords were now likely to be in the hands of criminals" vs "Graham Cluley, of internet security firm Sophos, said he believed the breach was genuine and warned
345:
Better, though there's still a bit of close paraphrasing - for example, current FN10. Also, I don't think "the website was hacked on behalf of the company" is really what you wanted to say.
370:
A side note: now that you've added yourself as an expander, Muboshgu, you've put yourself in line for a QPQ as well, I'm afraid. No good deed goes unpunished, or something like that...
402:
488:
283:"Even inserting text copied with some changes can be a copyright violation if there's substantial linguistic similarity in creative language or structure"
36:
357:
330:
326:
17:
325:
I just put every source in the article through the duplication detector and rephrased a few close paraphrasings that remained.
286:
191:
44:
81:
40:
209:
447:
375:
144:
65:
467:
350:
294:
267:
234:
184:
189:
386:
364:
338:
305:
168:
160:
112:
96:
356:
Yeah, that was bad rephrasing there. I took care of the rest of it from FN 10. Should be fine.
29:
The following discussion is an archived discussion of the DYK nomination of the article below.
204:
152:
273:
I had modified it and therefore they longer hold copyright. Read it up: "I had modified it".
443:
422:
371:
274:
248:
140:
61:
463:
346:
290:
263:
230:
321:
243:
482:
382:
360:
334:
301:
164:
156:
282:
148:
257:
224:
458:
410:
197:
179:
35:
Subsequent comments should be made on the appropriate discussion page (such as
433:
381:
Yep, you're right. And all I was looking for was a simple nom... –
116:
on June 7, 2012, resulting in the release of over 6 million user passwords?
104:
300:
Don't close this just yet. I'll take over and rewrite it. –
414:
The problems are fixed and this can now be promoted. Thanks
Muboshgu!
201:
Hook is good and interesting..article is long enough...good to go..:)
47:), unless there is consensus to re-open the discussion at this page.
442:
Muboshgu, thanks for the QPQ. I very much appreciate it.
86:
183:
Both the article and the hook seems okay. Good to go.
132:: Pending at ITN, but appears likely to fail there.
126:: Not applicable, as I'm not the creator/expander
8:
403:Template:Did you know nominations/Dr. O'Dowd
49:No further edits should be made to this page
333:is due to attributed quotes. –
489:Passed DYK nominations from June 2012
7:
415:
247:, sorry, it was my mistake. Fixed.
24:
18:Template:Did you know nominations
457:
432:
416:
409:
320:
256:
242:
223:
196:
178:
95:
462:Thanks all, looks alright now.
32:Please do not modify this page.
1:
171:) at 17:15, 7 June 2012 (UTC)
378:) 05:58, 19 June 2012 (UTC)
367:) 17:00, 18 June 2012 (UTC)
353:) 16:08, 18 June 2012 (UTC)
341:) 18:10, 14 June 2012 (UTC)
297:) 13:26, 11 June 2012 (UTC)
270:) 13:04, 11 June 2012 (UTC)
470:) 21:48, 19 June 2012 (UTC)
450:) 21:08, 19 June 2012 (UTC)
389:) 15:26, 19 June 2012 (UTC)
308:) 17:52, 14 June 2012 (UTC)
237:) 02:34, 11 June 2012 (UTC)
68:) 23:45, 19 June 2012 (UTC)
45:Knowledge talk:Did you know
37:this nomination's talk page
505:
279:13:13, 11 June 2012 (UTC)
253:05:56, 11 June 2012 (UTC)
427:16:05, 19 June 2012 (UTC)
216:08:02, 8 June 2012 (UTC)
193:07:45, 8 June 2012 (UTC)
41:the article's talk page
437:Dipankan, you cannot
287:WP:Close paraphrasing
139:Created/expanded by
186:♛♚★Vaibhav Jain★♚♛
73:2012 LinkedIn hack
172:
163:). Nominated by
496:
461:
436:
425:
421:
420:
419:
413:
324:
277:
260:
251:
246:
227:
214:
212:
207:
200:
187:
182:
138:
99:
56:The result was:
34:
504:
503:
499:
498:
497:
495:
494:
493:
479:
478:
477:
423:
417:
275:
249:
210:
205:
203:
185:
108:(logo pictured)
100:
93:
91:
87:Article history
75:
69:
30:
22:
21:
20:
12:
11:
5:
502:
500:
492:
491:
481:
480:
476:
475:
474:
473:
472:
471:
452:
451:
429:
428:
406:
405:
395:
394:
393:
392:
391:
390:
318:
317:
316:
315:
314:
313:
312:
311:
310:
309:
239:
238:
220:
219:
218:
217:
194:
136:
135:
134:
133:
127:
118:
117:
94:
90:
89:
84:
82:Back to T:TDYK
78:
76:
74:
71:
54:
53:
25:
23:
15:
14:
13:
10:
9:
6:
4:
3:
2:
501:
490:
487:
486:
484:
469:
465:
460:
456:
455:
454:
453:
449:
445:
440:
435:
431:
430:
426:
412:
408:
407:
404:
400:
397:
396:
388:
384:
380:
379:
377:
373:
369:
368:
366:
362:
359:–
358:
355:
354:
352:
348:
344:
343:
342:
340:
336:
332:
328:
323:
307:
303:
299:
298:
296:
292:
288:
284:
281:
280:
278:
272:
271:
269:
265:
259:
255:
254:
252:
245:
241:
240:
236:
232:
226:
222:
221:
215:
213:
208:
199:
195:
192:
190:
188:
181:
177:
176:
175:
174:
173:
170:
166:
162:
158:
154:
150:
146:
142:
131:
128:
125:
122:
121:
120:
119:
115:
114:
109:
106:
102:
101:
98:
88:
85:
83:
80:
79:
72:
70:
67:
63:
59:
52:
50:
46:
42:
38:
33:
27:
26:
19:
438:
398:
319:
202:
137:
129:
123:
111:
107:
57:
55:
48:
31:
28:
444:BlueMoonset
372:BlueMoonset
285:. See also
141:Dipankan001
62:BlueMoonset
464:Nikkimaria
347:Nikkimaria
291:Nikkimaria
264:Nikkimaria
231:Nikkimaria
206:ƬheⱾtrike
103:... that
483:Category
424:Dipankan
399:Reviewed
383:Muboshgu
361:Muboshgu
335:Muboshgu
302:Muboshgu
276:Dipankan
250:Dipankan
165:Muboshgu
157:Muboshgu
124:Reviewed
105:LinkedIn
58:promoted
149:Jenks24
130:Comment
113:hacked
211:Ҿagle
16:<
468:talk
448:talk
439:ever
387:talk
376:talk
365:talk
351:talk
339:talk
331:this
329:and
327:This
306:talk
295:talk
268:talk
235:talk
169:talk
161:talk
153:talk
145:talk
110:was
66:talk
155:),
147:),
60:by
43:or
485::
401::
289:.
77:(
39:,
466:(
446:(
385:(
374:(
363:(
349:(
337:(
304:(
293:(
266:(
233:(
167:(
159:(
151:(
143:(
92:)
64:(
51:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
