<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: phineyes</title><link>https://news.ycombinator.com/user?id=phineyes</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Mon, 24 Aug 2026 02:26:58 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=phineyes" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[How to build a 30M RPS CDN in 30 days with Rust and WASM]]></title><description><![CDATA[
<p>Article URL: <a href="https://blog.railway.com/p/railway-cdn">https://blog.railway.com/p/railway-cdn</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=48412357">https://news.ycombinator.com/item?id=48412357</a></p>
<p>Points: 4</p>
<p># Comments: 0</p>
]]></description><pubDate>Fri, 05 Jun 2026 13:35:35 +0000</pubDate><link>https://blog.railway.com/p/railway-cdn</link><dc:creator>phineyes</dc:creator><comments>https://news.ycombinator.com/item?id=48412357</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48412357</guid></item><item><title><![CDATA[New comment by phineyes in "Vodafone Germany is changing the open internet, one peering connection at a time"]]></title><description><![CDATA[
<p>This isn't unique to Vodafone. Google has also been slowly withdrawing from IXes globally in favor of PNIs and "VPPs" (verified peering providers). This only makes it harder for smaller networks to establish presence on the internet and feels pretty anti-competitive.<p>On the flip side, IXes are becoming harder and less desirable to participate in: port fees are going up, useful networks are withdrawing, low quality network participants are joining and widening blast radius. I'm not sure what the answer to this is, but this has not been a great year for the "open" internet.</p>
]]></description><pubDate>Fri, 07 Nov 2025 18:25:35 +0000</pubDate><link>https://news.ycombinator.com/item?id=45849318</link><dc:creator>phineyes</dc:creator><comments>https://news.ycombinator.com/item?id=45849318</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45849318</guid></item><item><title><![CDATA[New comment by phineyes in "An eBPF loophole: Using XDP for egress traffic"]]></title><description><![CDATA[
<p>21G on tc egress is slightly surprising to me. I'd like to see the program used for the benchmark. Was GSO accounted for? If you pop/pull headers by hand, you'll often kill GSO which will result in a massive loss in throughput like this.</p>
]]></description><pubDate>Wed, 05 Nov 2025 16:38:48 +0000</pubDate><link>https://news.ycombinator.com/item?id=45824930</link><dc:creator>phineyes</dc:creator><comments>https://news.ycombinator.com/item?id=45824930</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45824930</guid></item><item><title><![CDATA[New comment by phineyes in "Broadband Consumer Labels"]]></title><description><![CDATA[
<p>According to the FCC doc [1], the measurements may be conducted "between two defined
points on a network, such as between a user’s interface device and the ISP’s network core or between the user
interface device and the nearest internet exchange point where the ISP exchanges traffic with other networks". They require these measurements to be an average. I think this makes sense - it at least guarantees your speeds within the service provider's network.<p>[1] <a href="https://docs.fcc.gov/public/attachments/FCC-22-86A1.pdf" rel="nofollow">https://docs.fcc.gov/public/attachments/FCC-22-86A1.pdf</a></p>
]]></description><pubDate>Wed, 19 Apr 2023 03:30:05 +0000</pubDate><link>https://news.ycombinator.com/item?id=35623954</link><dc:creator>phineyes</dc:creator><comments>https://news.ycombinator.com/item?id=35623954</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=35623954</guid></item><item><title><![CDATA[New comment by phineyes in "Employees are feeding sensitive data to ChatGPT, raising security fears"]]></title><description><![CDATA[
<p>Let’s not forget that we’re also feeding in all our code into OpenAI Codex.</p>
]]></description><pubDate>Mon, 27 Mar 2023 19:42:29 +0000</pubDate><link>https://news.ycombinator.com/item?id=35331352</link><dc:creator>phineyes</dc:creator><comments>https://news.ycombinator.com/item?id=35331352</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=35331352</guid></item><item><title><![CDATA[How Discord Stores Trillions of Messages]]></title><description><![CDATA[
<p>Article URL: <a href="https://discord.com/blog/how-discord-stores-trillions-of-messages">https://discord.com/blog/how-discord-stores-trillions-of-messages</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=35048410">https://news.ycombinator.com/item?id=35048410</a></p>
<p>Points: 111</p>
<p># Comments: 10</p>
]]></description><pubDate>Mon, 06 Mar 2023 22:07:31 +0000</pubDate><link>https://discord.com/blog/how-discord-stores-trillions-of-messages</link><dc:creator>phineyes</dc:creator><comments>https://news.ycombinator.com/item?id=35048410</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=35048410</guid></item><item><title><![CDATA[New comment by phineyes in "Hampstead Heath"]]></title><description><![CDATA[
<p>Parliament Hill has great views of the city - probably the most elevated viewpoint in North London. Went there yesterday - gets super quiet after 10pm unlike Primrose.</p>
]]></description><pubDate>Sun, 22 Jan 2023 21:48:49 +0000</pubDate><link>https://news.ycombinator.com/item?id=34482584</link><dc:creator>phineyes</dc:creator><comments>https://news.ycombinator.com/item?id=34482584</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=34482584</guid></item><item><title><![CDATA[Notable Magic Numbers]]></title><description><![CDATA[
<p>Article URL: <a href="https://en.wikipedia.org/wiki/Hexspeak">https://en.wikipedia.org/wiki/Hexspeak</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=33631575">https://news.ycombinator.com/item?id=33631575</a></p>
<p>Points: 2</p>
<p># Comments: 0</p>
]]></description><pubDate>Wed, 16 Nov 2022 22:12:55 +0000</pubDate><link>https://en.wikipedia.org/wiki/Hexspeak</link><dc:creator>phineyes</dc:creator><comments>https://news.ycombinator.com/item?id=33631575</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=33631575</guid></item><item><title><![CDATA[New comment by phineyes in "https://16777217/"]]></title><description><![CDATA[
<p>I mentioned “routed” address, e.g. an address that actually appears on the DFZ. 0.0.0.0/8 is not a range that’s assigned to any RIRs by IANA - it’s reserved for special use.</p>
]]></description><pubDate>Mon, 19 Sep 2022 16:10:32 +0000</pubDate><link>https://news.ycombinator.com/item?id=32900256</link><dc:creator>phineyes</dc:creator><comments>https://news.ycombinator.com/item?id=32900256</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=32900256</guid></item><item><title><![CDATA[New comment by phineyes in "https://16777217/"]]></title><description><![CDATA[
<p>I had to add the trailing period for HN to accept it as a valid URL. However, for me (using Chrome on macOS Monterey), Chrome ignores the period and renders it as "<a href="https://16777217/" rel="nofollow">https://16777217/</a>". I thought it would be the same on other browsers. Interesting.</p>
]]></description><pubDate>Mon, 19 Sep 2022 07:24:16 +0000</pubDate><link>https://news.ycombinator.com/item?id=32895326</link><dc:creator>phineyes</dc:creator><comments>https://news.ycombinator.com/item?id=32895326</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=32895326</guid></item><item><title><![CDATA[New comment by phineyes in "https://16777217/"]]></title><description><![CDATA[
<p>Was more pointing out the numbered hostname, not the service its-self.<p>16777217 is just the lowest number that corresponds with a routed IP address :)</p>
]]></description><pubDate>Mon, 19 Sep 2022 06:21:32 +0000</pubDate><link>https://news.ycombinator.com/item?id=32894906</link><dc:creator>phineyes</dc:creator><comments>https://news.ycombinator.com/item?id=32894906</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=32894906</guid></item><item><title><![CDATA[https://16777217/]]></title><description><![CDATA[
<p>Article URL: <a href="https://16777217./">https://16777217./</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=32894168">https://news.ycombinator.com/item?id=32894168</a></p>
<p>Points: 130</p>
<p># Comments: 86</p>
]]></description><pubDate>Mon, 19 Sep 2022 04:04:01 +0000</pubDate><link>https://16777217./</link><dc:creator>phineyes</dc:creator><comments>https://news.ycombinator.com/item?id=32894168</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=32894168</guid></item><item><title><![CDATA[Nielsen Ratings]]></title><description><![CDATA[
<p>Article URL: <a href="https://en.wikipedia.org/wiki/Nielsen_ratings">https://en.wikipedia.org/wiki/Nielsen_ratings</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=31843710">https://news.ycombinator.com/item?id=31843710</a></p>
<p>Points: 2</p>
<p># Comments: 0</p>
]]></description><pubDate>Thu, 23 Jun 2022 00:34:12 +0000</pubDate><link>https://en.wikipedia.org/wiki/Nielsen_ratings</link><dc:creator>phineyes</dc:creator><comments>https://news.ycombinator.com/item?id=31843710</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=31843710</guid></item><item><title><![CDATA[Three-Digit ASNs Returned to ARIN by the Ontario Government]]></title><description><![CDATA[
<p>Article URL: <a href="https://lists.arin.net/pipermail/arin-issued/2022-June/004925.html">https://lists.arin.net/pipermail/arin-issued/2022-June/004925.html</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=31842067">https://news.ycombinator.com/item?id=31842067</a></p>
<p>Points: 1</p>
<p># Comments: 0</p>
]]></description><pubDate>Wed, 22 Jun 2022 21:25:59 +0000</pubDate><link>https://lists.arin.net/pipermail/arin-issued/2022-June/004925.html</link><dc:creator>phineyes</dc:creator><comments>https://news.ycombinator.com/item?id=31842067</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=31842067</guid></item><item><title><![CDATA[New comment by phineyes in "Apple Maps location scan spikes WiFi latency every 60 seconds"]]></title><description><![CDATA[
<p>It's not just Apple Maps either! Even with location services disabled, try opening AirDrop (even on another device you own) while running a ping and you'll see your en0 device's latency spike, while Apple tries to divide traffic between awdl0 and en0.</p>
]]></description><pubDate>Fri, 13 May 2022 02:31:16 +0000</pubDate><link>https://news.ycombinator.com/item?id=31362601</link><dc:creator>phineyes</dc:creator><comments>https://news.ycombinator.com/item?id=31362601</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=31362601</guid></item><item><title><![CDATA[New comment by phineyes in "Show HN: Prefixed, dual-token, base58 encoded API Keys"]]></title><description><![CDATA[
<p>I don't agree. Your examples (UUID1, UUID4) are <i>much</i> longer strings and contain no useful information. UUID1 contains the device's MAC ID, UUID4 is just random bits.. vs a functional ID system like pika or Snowflakes which make use of those random bits by embedding a timestamp - something which might actually come in useful for some.</p>
]]></description><pubDate>Wed, 11 May 2022 05:05:58 +0000</pubDate><link>https://news.ycombinator.com/item?id=31336016</link><dc:creator>phineyes</dc:creator><comments>https://news.ycombinator.com/item?id=31336016</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=31336016</guid></item><item><title><![CDATA[New comment by phineyes in "Show HN: Prefixed, dual-token, base58 encoded API Keys"]]></title><description><![CDATA[
<p>Yeah, pika is more of an ID system vs. prefixed-api-key which seems to be more oriented around <i>just</i> API keys, which makes sense. However, advantages of timestamps in IDs are that you can create unique IDs based on the current timestamp; bits which, in other ID systems, are usually just random - which feels like a waste imo. Also, knowing when a resource was created when debugging is very helpful.</p>
]]></description><pubDate>Wed, 11 May 2022 02:42:09 +0000</pubDate><link>https://news.ycombinator.com/item?id=31335294</link><dc:creator>phineyes</dc:creator><comments>https://news.ycombinator.com/item?id=31335294</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=31335294</guid></item><item><title><![CDATA[New comment by phineyes in "Show HN: Pika – pragmatic, functional, prefixed IDs"]]></title><description><![CDATA[
<p>Hey HN - I created this new ID system which combines Stripe-style (developer friendly) IDs with Snowflakes (proven, scalable and timestamped) IDs. I believe it combines the best of both worlds and allows for functionality to be added (e.g. secure, signed tokens) while still remaining short and identifiable. Main disadvantage (when compared to Snowflakes, for example) is that they're not sequenceable in a db, which is a trade off we were happy to make.<p>Let me know your thoughts. :)</p>
]]></description><pubDate>Wed, 11 May 2022 02:27:53 +0000</pubDate><link>https://news.ycombinator.com/item?id=31335192</link><dc:creator>phineyes</dc:creator><comments>https://news.ycombinator.com/item?id=31335192</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=31335192</guid></item><item><title><![CDATA[Show HN: Pika – pragmatic, functional, prefixed IDs]]></title><description><![CDATA[
<p>Article URL: <a href="https://github.com/hopinc/pika">https://github.com/hopinc/pika</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=31335168">https://news.ycombinator.com/item?id=31335168</a></p>
<p>Points: 9</p>
<p># Comments: 1</p>
]]></description><pubDate>Wed, 11 May 2022 02:24:20 +0000</pubDate><link>https://github.com/hopinc/pika</link><dc:creator>phineyes</dc:creator><comments>https://news.ycombinator.com/item?id=31335168</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=31335168</guid></item><item><title><![CDATA[New comment by phineyes in "Show HN: Prefixed, dual-token, base58 encoded API Keys"]]></title><description><![CDATA[
<p>I created a similar project recently! Main difference is that I use base64 to encode unique Snowflake IDs, which are timestamped: <a href="https://github.com/hopinc/pika" rel="nofollow">https://github.com/hopinc/pika</a> :)</p>
]]></description><pubDate>Wed, 11 May 2022 02:07:59 +0000</pubDate><link>https://news.ycombinator.com/item?id=31335071</link><dc:creator>phineyes</dc:creator><comments>https://news.ycombinator.com/item?id=31335071</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=31335071</guid></item></channel></rss>