<story><title>Awless: A Mighty CLI for AWS</title><url>https://github.com/wallix/awless</url></story><parent_chain><item><author>hbbio</author><text>Project creator here (but obviously not the OP).&lt;p&gt;Yes, we do collect minimal anonymised statistics in the sole goal of improving awless. All the statistics code is here: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;wallix&amp;#x2F;awless&amp;#x2F;blob&amp;#x2F;master&amp;#x2F;stats&amp;#x2F;stats.go&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;wallix&amp;#x2F;awless&amp;#x2F;blob&amp;#x2F;master&amp;#x2F;stats&amp;#x2F;stats.go&lt;/a&gt;&lt;p&gt;As the project is Apache licensed, you&amp;#x27;re free to modify it if you don&amp;#x27;t want this. Also, if you&amp;#x27;re conscious about privacy you should use application firewalls on your client side like Little Snitch etc. since many software that you install on your machine also do this.</text></item><item><author>heartsucker</author><text>&amp;gt; We also collect a few anonymous data (CLI errors, most frequently used commands and count of resources).&lt;p&gt;Looks cool, but this is an instant no for me. Sorry guys.</text></item></parent_chain><comment><author>the_duke</author><text>You should at least provide a prompt on first start that asks if participating in analytics collection is acceptable.</text></comment>
<story><title>Awless: A Mighty CLI for AWS</title><url>https://github.com/wallix/awless</url></story><parent_chain><item><author>hbbio</author><text>Project creator here (but obviously not the OP).&lt;p&gt;Yes, we do collect minimal anonymised statistics in the sole goal of improving awless. All the statistics code is here: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;wallix&amp;#x2F;awless&amp;#x2F;blob&amp;#x2F;master&amp;#x2F;stats&amp;#x2F;stats.go&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;wallix&amp;#x2F;awless&amp;#x2F;blob&amp;#x2F;master&amp;#x2F;stats&amp;#x2F;stats.go&lt;/a&gt;&lt;p&gt;As the project is Apache licensed, you&amp;#x27;re free to modify it if you don&amp;#x27;t want this. Also, if you&amp;#x27;re conscious about privacy you should use application firewalls on your client side like Little Snitch etc. since many software that you install on your machine also do this.</text></item><item><author>heartsucker</author><text>&amp;gt; We also collect a few anonymous data (CLI errors, most frequently used commands and count of resources).&lt;p&gt;Looks cool, but this is an instant no for me. Sorry guys.</text></item></parent_chain><comment><author>scaryclam</author><text>I like the look of this, so on the software side it&amp;#x27;s a thumbs up.&lt;p&gt;However, the fact that the code is active at all will rule it out for some companies (firewall or not).&lt;p&gt;Perhaps make it something users can turn off in a config file? Not everyone can code in go, especially if their job is as a sysadmin, which isn&amp;#x27;t unlikely given that this is an infrastructure tool, so it might not be as simple as forking and editing the code for them.</text></comment>