<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>thr0wawayf00</author><text>I can&amp;#x27;t believe these idiots tried playing chicken with a hacker, heads need to roll over this one. They have completely and needlessly destroyed their credibility by trying and completely failing to control the narrative.</text><parent_chain></parent_chain></comment><story><title>New Updated Okta Statement on Lapsus$</title><text>New update, but posted on top of the old public post. Now indicates Okta recognizes a breach officially and has started notified affected organizations.&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.okta.com&amp;#x2F;blog&amp;#x2F;2022&amp;#x2F;03&amp;#x2F;updated-okta-statement-on-lapsus&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.okta.com&amp;#x2F;blog&amp;#x2F;2022&amp;#x2F;03&amp;#x2F;updated-okta-statement-on-...&lt;/a&gt;</text></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>hexadec</author><text>I think the flip flopping is hurting them and their users more and more. What was initially a flat denial this morning has resulted in taunts from Lapsus$ on Twitter, Okta was out-scooped by Cloudflare&amp;#x27;s public investigation. Now they admit a breach affecting 2.5% (roughly 250 orgs based on public data).&lt;p&gt;The webinar tomorrow should be fascinating if they allow questions.</text><parent_chain></parent_chain></comment><story><title>New Updated Okta Statement on Lapsus$</title><text>New update, but posted on top of the old public post. Now indicates Okta recognizes a breach officially and has started notified affected organizations.&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.okta.com&amp;#x2F;blog&amp;#x2F;2022&amp;#x2F;03&amp;#x2F;updated-okta-statement-on-lapsus&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.okta.com&amp;#x2F;blog&amp;#x2F;2022&amp;#x2F;03&amp;#x2F;updated-okta-statement-on-...&lt;/a&gt;</text></story>