<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>matt_wulfeck</author><text>&amp;gt;&lt;i&gt;Randomise your bucket names! There is no need to use company-backup.s3.amazonaws.com&lt;/i&gt;&lt;p&gt;This is really poor advice. It offers no real benefit, especially since any asset you access will betray your bucket name because it&amp;#x27;s part of the DNS resolution. Bucket names are emphatically public as much as a DNS name is public.</text><parent_chain></parent_chain></comment><story><title>Bucket Stream: Finding S3 Buckets by watching certificate transparency logs</title><url>https://github.com/eth0izzle/bucket-stream</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>notyourwork</author><text>&amp;gt; Randomise your bucket names! There is no need to use company-backup.s3.amazonaws.com.&lt;p&gt;I don&amp;#x27;t think this is a globally true statement. Random bucket names are hard, not everyone is using s3 with a code configuration and therefore remembering bucket name is actually important.</text><parent_chain></parent_chain></comment><story><title>Bucket Stream: Finding S3 Buckets by watching certificate transparency logs</title><url>https://github.com/eth0izzle/bucket-stream</url></story>