<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: 7bees</title><link>https://news.ycombinator.com/user?id=7bees</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Fri, 24 Apr 2026 20:18:18 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=7bees" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by 7bees in "UK Biobank health data keeps ending up on GitHub"]]></title><description><![CDATA[
<p>The people involved are volunteers.  The rules for getting access are readily available, and clearly don't include "some random university student": <a href="https://www.ukbiobank.ac.uk/about-us/how-we-work/access-to-uk-biobank-data/" rel="nofollow">https://www.ukbiobank.ac.uk/about-us/how-we-work/access-to-u...</a></p>
]]></description><pubDate>Fri, 24 Apr 2026 03:57:42 +0000</pubDate><link>https://news.ycombinator.com/item?id=47885338</link><dc:creator>7bees</dc:creator><comments>https://news.ycombinator.com/item?id=47885338</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47885338</guid></item><item><title><![CDATA[New comment by 7bees in "CadQuery is an open-source Python library for building 3D CAD models"]]></title><description><![CDATA[
<p>I'm not sure I understand your comment; OpenSCAD has functions like sphere(), cylinder(), etc.  Most OpenSCAD models I have seen are built up primarily from solid primitives combined using boolean operations, just as you describe for the other tools.<p><a href="https://en.wikibooks.org/w/index.php?title=OpenSCAD_User_Manual/Primitive_Solids&stable=1" rel="nofollow">https://en.wikibooks.org/w/index.php?title=OpenSCAD_User_Man...</a></p>
]]></description><pubDate>Fri, 17 Apr 2026 05:38:26 +0000</pubDate><link>https://news.ycombinator.com/item?id=47802743</link><dc:creator>7bees</dc:creator><comments>https://news.ycombinator.com/item?id=47802743</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47802743</guid></item><item><title><![CDATA[New comment by 7bees in "An AI Agent Published a Hit Piece on Me – The Operator Came Forward"]]></title><description><![CDATA[
<p>Yes, it is.  The article includes a link to a comparison between the default file and the one allegedly used here.  The default starts with:<p>_You're not a chatbot. You're becoming someone._</p>
]]></description><pubDate>Fri, 20 Feb 2026 06:30:34 +0000</pubDate><link>https://news.ycombinator.com/item?id=47084486</link><dc:creator>7bees</dc:creator><comments>https://news.ycombinator.com/item?id=47084486</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47084486</guid></item><item><title><![CDATA[New comment by 7bees in "Data centers in space makes no sense"]]></title><description><![CDATA[
<p>xAI acquired twitter in 2025 as part of Musk's financial shell game (probably the same game he is playing with SpaceX/xAI now).</p>
]]></description><pubDate>Wed, 04 Feb 2026 05:59:24 +0000</pubDate><link>https://news.ycombinator.com/item?id=46881999</link><dc:creator>7bees</dc:creator><comments>https://news.ycombinator.com/item?id=46881999</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46881999</guid></item><item><title><![CDATA[New comment by 7bees in "People who know the formula for WD-40"]]></title><description><![CDATA[
<p>> The actual ingredients are literally on the safety data sheet<p>This is an oversimplification, in a way that is likely not obvious to a lot of people on this (software-focused) forum.  An SDS does not have to list exact amounts, does not have to disclose some details of how an ingredient or mix of ingredients was processed, and (depending on jurisdiction) may not have to identify some "safe" ingredients at all.  Some ingredients may be identified in relatively vague ways, that are sufficient for safety purposes but do not reveal the exact product.  As the SDS you linked to says "The specific chemical identity and exact percentages are a trade secret".  An SDS is certainly very helpful to reverse-engineering a product, but it doesn't tell you everything.<p>All that said, yes, the main strength of WD-40 is its marketing and ubiquity, and claims about its secrecy have more to do with marketing than anything practical.</p>
]]></description><pubDate>Mon, 26 Jan 2026 23:51:54 +0000</pubDate><link>https://news.ycombinator.com/item?id=46773446</link><dc:creator>7bees</dc:creator><comments>https://news.ycombinator.com/item?id=46773446</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46773446</guid></item><item><title><![CDATA[New comment by 7bees in "Getting bitten by Intel's poor naming schemes"]]></title><description><![CDATA[
<p>You can correlate microarchitecture to product SKUs using the Intel site that the article links.  AMD has a similar site with similar functionality (except that AFAIK it won't let you easily get a list of products with a given uarch).  These both have their faults, but I'd certainly pick them over an LLM.<p>But you're correct that for anything buried in the guts of CPUID, your life is pain.  And Intel's product branding has been a disaster for years.</p>
]]></description><pubDate>Fri, 19 Dec 2025 07:45:03 +0000</pubDate><link>https://news.ycombinator.com/item?id=46323280</link><dc:creator>7bees</dc:creator><comments>https://news.ycombinator.com/item?id=46323280</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46323280</guid></item><item><title><![CDATA[New comment by 7bees in "Getting bitten by Intel's poor naming schemes"]]></title><description><![CDATA[
<p>Intel doesn't like to officially use codenames for products once they have shipped, but those codenames are used widely to delineate different families (even by them!), so they compromise with the awkward "products formerly x" wording.  Have done for a long time.</p>
]]></description><pubDate>Fri, 19 Dec 2025 07:26:20 +0000</pubDate><link>https://news.ycombinator.com/item?id=46323136</link><dc:creator>7bees</dc:creator><comments>https://news.ycombinator.com/item?id=46323136</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46323136</guid></item><item><title><![CDATA[New comment by 7bees in "Getting bitten by Intel's poor naming schemes"]]></title><description><![CDATA[
<p>It has pretty much always been the case that you need to make sure the motherboard supports the specific chip you want to use, and that you can't rely on just the physical socket as an indicator of compatibility (true for AMD as well).  For motherboards sold at retail the manufacturer's site will normally have a list, and they may provide some BIOS updates over time that extend compatibility to newer chips.  OEM stuff like this can be more of a crapshoot.<p>All things considered I actually kind of respect the relatively straightforward naming of this and several of Intel's other sockets.  LGA to indicate it's land grid array (CPU has flat "lands" on it, pins are on the motherboard), 2011 because it has 2011 pins.  FC because it's flip chip packaging.</p>
]]></description><pubDate>Fri, 19 Dec 2025 07:22:43 +0000</pubDate><link>https://news.ycombinator.com/item?id=46323115</link><dc:creator>7bees</dc:creator><comments>https://news.ycombinator.com/item?id=46323115</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46323115</guid></item></channel></rss>