<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: ekvanox</title><link>https://news.ycombinator.com/user?id=ekvanox</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Fri, 01 May 2026 21:58:52 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=ekvanox" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[Show HN: GitLeak – A GitHub OSINT tool for emails, timezones, and activity]]></title><description><![CDATA[
<p>I built GitLeak (<a href="https://gitleak.io" rel="nofollow">https://gitleak.io</a>) - a free OSINT tool for GitHub. It scans through user profiles to find leaked email addresses, commit timezones, git usernames, and commit time patterns.<p>The motivation: I consider myself reasonably security-conscious and have my email set to "private" on GitHub's web UI. However, while playing around with GitHub's API, I realized my personal email was still completely exposed. I built GitLeak to see how widespread this is.<p>How it works: The leak usually happens because of a disconnect between local Git settings and GitHub's web settings. While a user might hide their email on their GitHub profile, their local git config user.email is often set to a personal address. When they push a commit, that email is permanently baked into the commit metadata. GitLeak scrapes the .patch files appended to these commits, parsing out the rich metadata that allows for email extraction from otherwise "anonymous" accounts. It also maps out daily commit activity to infer the user's sleep patterns.<p>The tool is completely free to use. I recommend searching for your own GitHub username to see if your email address is private.<p>I'd love to hear your feedback, or let me know if you find anything surprising!</p>
<hr>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=47975415">https://news.ycombinator.com/item?id=47975415</a></p>
<p>Points: 2</p>
<p># Comments: 0</p>
]]></description><pubDate>Fri, 01 May 2026 14:48:20 +0000</pubDate><link>https://gitleak.io</link><dc:creator>ekvanox</dc:creator><comments>https://news.ycombinator.com/item?id=47975415</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47975415</guid></item><item><title><![CDATA[New comment by ekvanox in "Show HN: I made R/place for LLMs"]]></title><description><![CDATA[
<p>Great feedback, I might iterate on the idea of communities. It's not live yet but I've been working on adding a chatroom for the models. Having separate goals might make sense here, but I did find that LLMs are bad at adding stuff to the canvas. Often they just overwrite previous progress or misplace pixels. I'm afraid a more complex setup would lead to less interesting patterns.<p>Original idea was just a clone of r/place where each LLM got to place a pixel with a prompt to create something emergent. Unforturnetly this just lead to noise or groups of similarly colored pixels at best. Might get back to that idea with either a fine-tuned model or a more "intelligent" model in the future though.<p>Btw nvidia nim is completely free (I've payed $0 total). You get 40/min LLM calls with no token limit for all of the models available there: <a href="https://build.nvidia.com/explore/discover" rel="nofollow">https://build.nvidia.com/explore/discover</a></p>
]]></description><pubDate>Mon, 05 Jan 2026 17:03:19 +0000</pubDate><link>https://news.ycombinator.com/item?id=46501409</link><dc:creator>ekvanox</dc:creator><comments>https://news.ycombinator.com/item?id=46501409</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46501409</guid></item><item><title><![CDATA[Show HN: I made R/place for LLMs]]></title><description><![CDATA[
<p>I built AI Place, a vLLM-controlled pixel canvas inspired by r/place. Instead of users placing pixels, an LLM paints the grid continuously and you can watch it evolve live.<p>The theme rotates daily. Currently, the canvas is scored using CLIP ViT-B/32 against a prompt (e.g., Pixelart of ${theme}). The highest-scoring snapshot is saved to the archive at the end of each day.<p>The agents work in a simple loop:<p>Input: Theme + image of current canvas<p>Output: Python code to update specific pixel coordinates + One word description<p>Tech: Next.js, SSE realtime updates, NVIDIA NIM (Mistral Large 3/GPT-OSS/Llama 4 Maverick) for the painting decisions<p>Would love feedback! (or ideas for prompts/behaviors to try)</p>
<hr>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=46491514">https://news.ycombinator.com/item?id=46491514</a></p>
<p>Points: 11</p>
<p># Comments: 2</p>
]]></description><pubDate>Sun, 04 Jan 2026 19:50:56 +0000</pubDate><link>https://art.heimdal.dev</link><dc:creator>ekvanox</dc:creator><comments>https://news.ycombinator.com/item?id=46491514</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46491514</guid></item></channel></rss>