<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Arnica on Medium]]></title>
        <description><![CDATA[Stories by Arnica on Medium]]></description>
        <link>https://medium.com/@arnica-io?source=rss-78a87b4c2aa8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*L4oHMgcmE4OcaTnaVBY3wg.png</url>
            <title>Stories by Arnica on Medium</title>
            <link>https://medium.com/@arnica-io?source=rss-78a87b4c2aa8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 01:38:23 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@arnica-io/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Hacking Hacker News for Fun and Profit — Part 1]]></title>
            <link>https://medium.com/@arnica-io/hacking-hacker-news-for-fun-and-profit-part-1-41bd6a48a2c2?source=rss-78a87b4c2aa8------2</link>
            <guid isPermaLink="false">https://medium.com/p/41bd6a48a2c2</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[hacker-news]]></category>
            <category><![CDATA[plg]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[devsecops]]></category>
            <dc:creator><![CDATA[Arnica]]></dc:creator>
            <pubDate>Tue, 26 Oct 2021 16:02:10 GMT</pubDate>
            <atom:updated>2021-10-26T18:24:01.227Z</atom:updated>
            <content:encoded><![CDATA[<h3>Hacking Hacker News for fun and profit — Part 1</h3><h3>Start with the WHY</h3><p>Online traction and product-market fit are the holy grail for SaaS businesses. The summary of startup advice out there is to create a <strong>great product that people like, and to get people to know about it.</strong></p><p>For young companies like Arnica, it boils down to delivering a <a href="https://www.aha.io/blog/minimum-viable-product-vs-minimum-lovable-product">Minimum Lovable Product</a> that is derived from this research. In order to <strong>know what our customers would consider lovable</strong>, we want to hear them out, and while we had multiple validation calls with security, DevOps and engineering leaders, <strong>it doesn’t scale</strong>. Nothing replaces direct interactions with potential customers, but in order to <strong>“validate our validation calls” </strong>we must <strong>detach from our own bias</strong> towards our concepts<strong> </strong>and ensure we are data driven. This is the why we decided to embark on this path with this research.</p><p>Traffic alone can’t make a bad product sell, but if you have a great conversion metric, <strong>a great post can save months of organic growth and give you that much needed bump of early adopters</strong>.</p><p>Part 1 of this research is solely focused on the fundamental data, while the next part will include more advanced analytics.</p><h3>Data extraction and graph construction</h3><p>Thankfully, Hacker News published a <a href="https://hackernews.api-docs.io/v0/overview/introduction">public API</a> to make our job easy… to some extent. We decided to query a relatively small portion of the ~30M records and ended up extracting total 2,252,719 nodes and 4,028,273 relationships from the last 6 months into a Graph database, which is comprised of 110,801 users, 199,052 stories and 1,942,866 comments. Here is how the database is structured in this research:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bcKtL7aLgjYMFbv6n0Kljw.png" /><figcaption>Hacker News Research Graph</figcaption></figure><p>The graph is pretty much self-explanatory except for one detail… what is “links_to”? Well, it is quite popular to link from stories or comments to others, so we decided to parse all titles and texts and link them to the relevant stories and comments. <strong>We found 13,126 links that helped us in this research.</strong></p><h3>Qualitative percentiles</h3><p>Data segmentation and qualitative measures allow better classification of user and post popularity. Below is the approach we took in this research:</p><p><strong>User Karma Classification</strong></p><ul><li>Top = 75th percentile. Karma score is greater or equal to 7,386.</li><li>Median = 50th percentile. Karma score is between 969 and 7,385.</li><li>Low = 55th percentile. Karma score is between 30 and 968.</li><li>Immaterial = All other karma scores (How the heck did someone manage to get to a negative karma of -206 ?!)</li></ul><p><strong>Story Popularity Classification</strong></p><ul><li>Top = 99th percentile. Story score is 397 or above.</li><li>High = 90th percentile. Story score is between 33 and 396.</li><li>Nice = 80th percentile. Story score is between 6 and 32.</li><li>Discredited = All other story scores.</li></ul><p><strong>Story Comments Classification</strong></p><ul><li>Top Commented = 99th percentile. Total comments in the story thread is 54 or above.</li><li>Commented = 90th percentile. Total comments in the story thread is between 16 and 53.</li><li>Immaterial= All other comments count.</li></ul><p><strong>Link Referrals Classification</strong></p><ul><li>Top Linked = 99th percentile. Total link referrals count is 6 or above.</li><li>Linked = 90th percentile. Total link referrals count is between 2 and 5.</li><li>Unlinked = No referral links or only one.</li></ul><h3>Does the week day matter?</h3><p>Let’s look at the chart below. With the premise of Monday being the first day of the week, hence it is represented by the number 1 and so on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SgaH3db902sfn0_UjTJe_g.png" /><figcaption>Story Score by Weekday</figcaption></figure><p>Based on the data above, you<strong> </strong>get the <strong>biggest bang for your buck when posting a story on Tuesday and Thursday</strong>. These days are followed closely by Wednesday and Monday. Traction is low on weekends and relatively low on Fridays, which is typically a shorter day for many people.</p><p>With that said, the ratio between the top to high story scores, top to nice story scores, top to discredited story scores , and top to the total story scores represent the same popularity results. <strong>It means that posting on a specific day of week does not have an impact on the popularity of the story.</strong></p><h3>Does the hour matter?</h3><p>Let’s look at the chart below to understand how Top Story Popularity (defined above) is reflected based on the time the story was posted on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RDzfsmV_ADlcsLfzQC0DqQ.png" /><figcaption>Top Popular Stories by Posted Hour (Eastern Time)</figcaption></figure><p>From the chart above, we can clearly see that the <strong>top posts are published between 12–1 PM </strong>Eastern Time. The chart above is slightly different than the chart below with all story scores:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NNWBuNzTTPDsOQJtJWczqg.png" /><figcaption>All Stories by Posted Hour (Eastern Time)</figcaption></figure><p>While there is some differentiation between the top posts and all posts, <strong>it seems like the general trend is to post between 10 AM and 1 PM </strong>Eastern Time. A couple of obvious conclusions we can derive from this comparison are:</p><ol><li><strong>The chance to post a popular story between 12–1 PM Eastern Time is 38% higher than posting between 11–12 PM and 28% higher than posting between 10–11 PM Eastern Time.</strong></li><li>Note that in case this recommendation is implemented by enough people, this <strong>could change the stats over time</strong>.</li></ol><h3>Does user’s karma matter?</h3><p>Below is a table with a breakdown of the observed users’ karma vs. story popularity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3pRAquIwH-Jt_4hKTxND5w.png" /><figcaption>Story Score vs. User Karma</figcaption></figure><p>The highlighted values represent the top scored stories and the relevant user karma for the authors. <strong>The conclusion on this front is that users with karma above 30 have an equal chance to post a top scored story.</strong></p><h3>Do links to stories matter?</h3><p>Before the data is explained, it is important to mention that links to a story are added after the story is posted. It means that the question in this case is <strong>how links to a given story impact on the popularity of it? </strong>Let’s observe the data below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dXF8pDIouAT1qnajXP-dZA.png" /><figcaption>Links to Story vs. Story Score</figcaption></figure><p>Based on this data, <strong>adding links to a story contribute to its score, but it cannot ensure a Top or High story score</strong>. As a matter of fact, <strong>Top ranked stories have a 5.25X higher ratio of links to story compared to High ranked stories</strong>.</p><p>The caveat is that <strong>linking to a story should not occur immediately</strong>. The average times between a Top story sharing and the link posting ranges between 5.5-13.5 hours (the 25th and 75th percentiles). By examining less popular stories and the links to them, the average time is ~10 hours. In other words,<strong> links to a story are typically impacting its popularity if posted within 5.5–13.5 hours after the story was posted.</strong></p><h3>The bottom line</h3><p>Based on the data shared thus far, several tweaks can be made to increase the chances of a story popularity on Hacker News. With that said, <strong>good content is key to gaining more traction</strong>.</p><p>Follow us on <a href="https://www.linkedin.com/company/arnica-io/">LinkedIn</a> to be notified when we post Part 2.</p><p><strong>EDIT:</strong> thanks for the great feedback on Hacker News. <a href="https://news.ycombinator.com/item?id=29002669">Follow the discussion here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=41bd6a48a2c2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Afraid of your source code leaking? I can tell by the Twitch in your eye…!]]></title>
            <link>https://medium.com/@arnica-io/afraid-of-your-source-code-leaking-i-can-tell-by-the-twitch-in-your-eye-693b71a67eac?source=rss-78a87b4c2aa8------2</link>
            <guid isPermaLink="false">https://medium.com/p/693b71a67eac</guid>
            <category><![CDATA[security-breach]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[twitch]]></category>
            <category><![CDATA[devsecops]]></category>
            <category><![CDATA[source-code-management]]></category>
            <dc:creator><![CDATA[Arnica]]></dc:creator>
            <pubDate>Thu, 07 Oct 2021 01:59:50 GMT</pubDate>
            <atom:updated>2021-10-07T11:36:25.482Z</atom:updated>
            <content:encoded><![CDATA[<p>The publication about the Twitch source code leak represents yet another instance of a repetitive problem — excessive permissions to Source Code Management. Code exfiltration is easy to exploit, but what are the reasons for it?</p><h3>Default Access to Source Code</h3><p>Source Code Management tools are designed to enable collaboration with minimal impact on development velocity. For example, when a user is invited to collaborate on GitHub, there are generally 2 access levels:</p><ol><li><strong>Owner:</strong> full administrative rights to the organization and have complete access to all repositories and teams.</li><li><strong>Member:</strong> can see all other members, and can be granted access to repositories. A member can also create new teams and repositories.</li></ol><p>In addition to these levels, there is an option to add membership in specific teams, which have more specific permissions. Below is an illustration of a user invitation to an organization with specific group membership.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/537/1*uuKwQzPemMfDCBTQm4zVVQ.png" /><figcaption>Example of a User invitation on GitHub</figcaption></figure><p>By looking into this group membership, it can be determined what is the additional permission beyond the default access granted to members:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/993/1*3QrS_FzTTfZcXyEQXnomNg.png" /><figcaption>Example of a Team-specific permission to a GitHub Repository</figcaption></figure><p>Permission management appears to be simple, but the challenge is that<br>permissions are derived from the most common denominator — having a READ access permission to all repositories. Below is a screenshot representing this default setting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/992/1*dQohRfReuRF2jmjeq2llEQ.png" /><figcaption>Default Read Permission on GitHub</figcaption></figure><h3>Ease of Exploitation</h3><p>From adversarial perspective, an access to source code can be exploited by any of the following:</p><p><strong>1. Leverage the git client on the developer’s workstation</strong></p><p>Given access to a developer workstation, especially in the post COVID world with developers working from home in a less secure environment, it is simple to exploit as the access token already stored in the <a href="https://git-scm.com/book/en/v2/Git-Tools-Credential-Storage">Git Credential Storage</a>, which “serves” the token to the git client.</p><p><strong>2. Leverage the browser’s context</strong></p><p>In many cases, project and product management tasks are managed in the Version Control tool. It means that additional roles beyond developers typically have access to source code, such as project managers, which don’t use a git client. An adversary with a malware accessing the browser context can download the zip file containing the archive of the source code. It is harder to exploit but has much broader outreach.</p><p><strong>3. Get an access token</strong></p><p>Any access to private source code requires an access token or SSH key, regardless the source of the request. For example, a build system uses a short-lived token to clone repositories, a developer may use a long-lived token on the git client, and the project manager has a cookie with the token. There are many ways to get the access to these type of tokens, for example:</p><ul><li>Bribing an employee to share the access token with the adversary, as we’ve seen in the past with a <a href="https://www.bbc.com/news/world-us-canada-56469475">Russian criminal who tried to convince a Tesla employee to plant a malware</a>.</li><li>Compromising developer tools with <a href="https://thehackernews.com/2021/05/newly-discovered-bugs-in-vscode.html">malicious extensions</a> to enable remote code execution and even implanting a backdoor in your code.</li></ul><h3>What can you do to minimize the risk?</h3><ol><li>Modify the base permissions in your Source Control Management to be <strong>less permissive</strong> or <strong>manage micro-organizations</strong> within the enterprise.</li><li>Use SSH keys <strong>with a passphrase</strong> to authenticate into the Source Control Management tool. Worth knowing that if the user stores the passphrase in the built-in key storage (such as keychain), it beats the purpose.</li><li>User entitlements review is common practice for regulated companies. The challenge is that these reviews tend to be rubber stamped by the employee managers or repository owners. To minimize the risk, <strong>measure the user entitlements over time</strong> and expect to see a trend of decreasing user entitlements from time to time.</li><li>Educate yourself about how permissions are constructed by playing with them in a sandbox. For this purpose, we created <a href="https://github.com/arnica-ext/GitGoat"><strong>GitGoat</strong></a>, which is an open source tool that was built to enable DevOps and Engineering teams the opportunity to design and implement a sustainable misconfiguration prevention strategy. It can be used to test products (such as <a href="http://openssf.org/">OpenSSF</a>) with access to GitHub repositories without risking your production environment.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=693b71a67eac" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>