<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>KirinDave</author><text>&amp;gt; Who in their right minds realistically expects any organisation to respond to some random journalistic enquiry on a Sunday?&lt;p&gt;My company did it. Heck, we did it when it was just me and my cofounder answering email. I&amp;#x27;ve worked for multiple companies that had folks who specifically had weekend comms duty, actually. When you reach a certain size this is as normal as having an operations expert on call.&lt;p&gt;It&amp;#x27;s... Weird to suggest that it&amp;#x27;s abnormal to be responsive to press within 24 hours for a company as big as Tesla.</text><parent_chain><item><author>mikro2nd</author><text>A trend that&amp;#x27;s been growing for quite a (long!) while now is exemplified by this article: &amp;quot;&lt;i&gt;Tesla did not respond to Ars’ request for comment on Sunday.&lt;/i&gt;&amp;quot;&lt;p&gt;Who in their right minds realistically expects &lt;i&gt;any&lt;/i&gt; organisation to respond to some random journalistic enquiry &lt;i&gt;on a Sunday&lt;/i&gt;?&lt;p&gt;The other major variant of this shyster tactic is along the lines of, &amp;quot;Company X failed to respond &lt;i&gt;immediately&lt;/i&gt; when asked for comment.&amp;quot; No company is able to respond &lt;i&gt;immediately&lt;/i&gt;, particularly not on an issue that&amp;#x27;s likely contentious. Any response would need to be run by their PR and legal people at the very least.&lt;p&gt;It&amp;#x27;s a cheap and nasty way to make companies look&amp;#x2F;feel uncaring about the issue being reported, but imho it does nothing but reflect poorly on the reporter and publication using these smelly tactics, and leaves me wondering what other agendas they may have running.</text></item></parent_chain></comment><story><title>Ex-SolarCity employees: We were fired after reporting millions in fake sales</title><url>https://arstechnica.com/tech-policy/2018/07/3-ex-solarcity-employees-claim-company-oversaw-bogus-sales-to-inflate-valuation</url></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>princekolt</author><text>&amp;gt; Who in their right minds realistically expects any organisation to respond to some random journalistic enquiry on a Sunday?&lt;p&gt;Jeez. Considering the story was posted today, what this probably means is that they requested commentary &lt;i&gt;on&lt;/i&gt; Sunday, waited for the entirety of Monday, and didn&amp;#x27;t hear back until today, when they decided to post it.</text><parent_chain><item><author>mikro2nd</author><text>A trend that&amp;#x27;s been growing for quite a (long!) while now is exemplified by this article: &amp;quot;&lt;i&gt;Tesla did not respond to Ars’ request for comment on Sunday.&lt;/i&gt;&amp;quot;&lt;p&gt;Who in their right minds realistically expects &lt;i&gt;any&lt;/i&gt; organisation to respond to some random journalistic enquiry &lt;i&gt;on a Sunday&lt;/i&gt;?&lt;p&gt;The other major variant of this shyster tactic is along the lines of, &amp;quot;Company X failed to respond &lt;i&gt;immediately&lt;/i&gt; when asked for comment.&amp;quot; No company is able to respond &lt;i&gt;immediately&lt;/i&gt;, particularly not on an issue that&amp;#x27;s likely contentious. Any response would need to be run by their PR and legal people at the very least.&lt;p&gt;It&amp;#x27;s a cheap and nasty way to make companies look&amp;#x2F;feel uncaring about the issue being reported, but imho it does nothing but reflect poorly on the reporter and publication using these smelly tactics, and leaves me wondering what other agendas they may have running.</text></item></parent_chain></comment><story><title>Ex-SolarCity employees: We were fired after reporting millions in fake sales</title><url>https://arstechnica.com/tech-policy/2018/07/3-ex-solarcity-employees-claim-company-oversaw-bogus-sales-to-inflate-valuation</url></story>