<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: himata4113</title><link>https://news.ycombinator.com/user?id=himata4113</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Sat, 13 Jun 2026 12:47:43 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=himata4113" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by himata4113 in "CRISPR tech selectively shreds cancer cells, including "undruggable" cancers"]]></title><description><![CDATA[
<p>Oh wow, not as impressive as I thought, but I guess we are looking at broad categories rather than specific types and variants. But overall the trend is down on ever cancer since around a decade ago. Was expecting a sharper drop around 1-2 decades ago, but things just take time when it comes to experimenting with human lives. Will be interesting to revisit this in another decade when a lot of the treatments finally leave the experimental stage.</p>
]]></description><pubDate>Fri, 12 Jun 2026 21:47:22 +0000</pubDate><link>https://news.ycombinator.com/item?id=48509826</link><dc:creator>himata4113</dc:creator><comments>https://news.ycombinator.com/item?id=48509826</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48509826</guid></item><item><title><![CDATA[New comment by himata4113 in "CRISPR tech selectively shreds cancer cells, including "undruggable" cancers"]]></title><description><![CDATA[
<p>I guess then a graph of deaths from disagnosed cancer at various stages would be just as awe inspiring. I'd settle for that as well.</p>
]]></description><pubDate>Fri, 12 Jun 2026 21:30:40 +0000</pubDate><link>https://news.ycombinator.com/item?id=48509653</link><dc:creator>himata4113</dc:creator><comments>https://news.ycombinator.com/item?id=48509653</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48509653</guid></item><item><title><![CDATA[New comment by himata4113 in "WASI 0.3"]]></title><description><![CDATA[
<p>I do specifically that and abandoned WASI in favor of freestanding with shared memory regions + PIC memory region. It works today and is easily extensible as well as increadibly fast, sandboxing is not as strong since modules can read code they don't own and modify data they do not own, but splitting modules into "trusted" and "untrusted" largely mitigated those issues as memory has write bit stripped for execution during untrusted modules, only allowing data they own to be modified. Sensitive data lives outside the runtime and has to be fetched with (slower) host methods.<p>Point being, if you rely on a non standard specification of developer defined wasi api subspec you might as well just go with freestanding.</p>
]]></description><pubDate>Fri, 12 Jun 2026 21:06:40 +0000</pubDate><link>https://news.ycombinator.com/item?id=48509430</link><dc:creator>himata4113</dc:creator><comments>https://news.ycombinator.com/item?id=48509430</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48509430</guid></item><item><title><![CDATA[New comment by himata4113 in "CRISPR tech selectively shreds cancer cells, including "undruggable" cancers"]]></title><description><![CDATA[
<p>Does anyone know a website where I can see/read of how many cancers (and their variants) we've effectively solved, have drugs to negate their effects, have experimental drugs for and uncurable cancers? I think that graph would be awe inspiring looking at the past decade of advancements.<p>What's more crazy is that we're slowly going from millenia, to decades, to likely years in the near future from being presented a biological problem and achieving the next milestone in solving it. We might have "AI", but we also have brilliant minds right now that are speeding up development to a pace that would be unimaginable just few years ago.</p>
]]></description><pubDate>Fri, 12 Jun 2026 20:18:32 +0000</pubDate><link>https://news.ycombinator.com/item?id=48508993</link><dc:creator>himata4113</dc:creator><comments>https://news.ycombinator.com/item?id=48508993</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48508993</guid></item><item><title><![CDATA[New comment by himata4113 in "macOS 27 Beta breaks the ability to boot Asahi Linux"]]></title><description><![CDATA[
<p>404</p>
]]></description><pubDate>Thu, 11 Jun 2026 20:08:18 +0000</pubDate><link>https://news.ycombinator.com/item?id=48495749</link><dc:creator>himata4113</dc:creator><comments>https://news.ycombinator.com/item?id=48495749</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48495749</guid></item><item><title><![CDATA[New comment by himata4113 in "Amazon Says Its Data Centers Use 2.5B Gallons of Water"]]></title><description><![CDATA[
<p>Roughly 736* of US households assuming it's 2.5B per year, 100 gal per person. I can't read the article because I got what it feels like 17 popups that nearly gave me epilepsy.<p>edit: corrected to 736, its per year.</p>
]]></description><pubDate>Thu, 11 Jun 2026 15:08:48 +0000</pubDate><link>https://news.ycombinator.com/item?id=48491409</link><dc:creator>himata4113</dc:creator><comments>https://news.ycombinator.com/item?id=48491409</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48491409</guid></item><item><title><![CDATA[New comment by himata4113 in "Cybersecurity researchers aren't happy about the guardrails on Anthropic's Fable"]]></title><description><![CDATA[
<p>some static words in AGENTS.md trigger it as well as some mcp servers.</p>
]]></description><pubDate>Wed, 10 Jun 2026 22:48:59 +0000</pubDate><link>https://news.ycombinator.com/item?id=48483855</link><dc:creator>himata4113</dc:creator><comments>https://news.ycombinator.com/item?id=48483855</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48483855</guid></item><item><title><![CDATA[New comment by himata4113 in "Cybersecurity researchers aren't happy about the guardrails on Anthropic's Fable"]]></title><description><![CDATA[
<p>I've done this, including the hardcoded refusal strings that already exist in claude code. It won't stop a real attacker, but I still find it really funny when you're trying to use one of the AI tools and it gives you a random refusal and you don't know why, wastes a little bit of time.</p>
]]></description><pubDate>Wed, 10 Jun 2026 22:48:16 +0000</pubDate><link>https://news.ycombinator.com/item?id=48483845</link><dc:creator>himata4113</dc:creator><comments>https://news.ycombinator.com/item?id=48483845</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48483845</guid></item><item><title><![CDATA[New comment by himata4113 in "Who Runs Your Rust Future? Hands-On Intro to Async Rust"]]></title><description><![CDATA[
<p>async gives you a few other advantages, it allows you to handle bi-streams much easier than two sync threads especially when it comes to synchronization.</p>
]]></description><pubDate>Wed, 10 Jun 2026 22:12:40 +0000</pubDate><link>https://news.ycombinator.com/item?id=48483442</link><dc:creator>himata4113</dc:creator><comments>https://news.ycombinator.com/item?id=48483442</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48483442</guid></item><item><title><![CDATA[New comment by himata4113 in "Who Runs Your Rust Future? Hands-On Intro to Async Rust"]]></title><description><![CDATA[
<p>You use async to preserve system resources. For example you can easily exhaust the host with ~20k connections running a thread-per-connection schema where each thread simply waits for epoll event, async prevents this by having a threadpool of ~16 threads that handle all the connections instead of polling the scheduler wakes it up, asks "do you haev work to do" if not continues to next task. (This heavily varied by the async runtime implementation, each async runtime can and will act differently to maximize efficiency over throughput)</p>
]]></description><pubDate>Wed, 10 Jun 2026 16:03:23 +0000</pubDate><link>https://news.ycombinator.com/item?id=48478383</link><dc:creator>himata4113</dc:creator><comments>https://news.ycombinator.com/item?id=48478383</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48478383</guid></item><item><title><![CDATA[Claude Fable 5 Launches at #1 on the Artificial Analysis Intelligence Index]]></title><description><![CDATA[
<p>Article URL: <a href="https://artificialanalysis.ai/articles/claude-fable-5-mythos-intelligence-index">https://artificialanalysis.ai/articles/claude-fable-5-mythos-intelligence-index</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=48477562">https://news.ycombinator.com/item?id=48477562</a></p>
<p>Points: 4</p>
<p># Comments: 0</p>
]]></description><pubDate>Wed, 10 Jun 2026 15:11:06 +0000</pubDate><link>https://artificialanalysis.ai/articles/claude-fable-5-mythos-intelligence-index</link><dc:creator>himata4113</dc:creator><comments>https://news.ycombinator.com/item?id=48477562</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48477562</guid></item><item><title><![CDATA[New comment by himata4113 in "CEOs who think AI replaces their employees are just bad CEOs"]]></title><description><![CDATA[
<p>now it's closer to 95% of work can be done by AI and requires 5% mental effort, but 5% of the work requires 95% of the mental effort to finish because of all the unoptimial decisions AI has taken. I find that AI works best in small micro-service type architecture where each component has a clear goal and doesn't have interconnected parts within the same application that can break. But you do run into an issue where changes in microservice a need changes in microservice b and updating it is not ideal since it usually cascades thru the entire system or requires stacks of legacy support.</p>
]]></description><pubDate>Tue, 09 Jun 2026 21:37:04 +0000</pubDate><link>https://news.ycombinator.com/item?id=48468112</link><dc:creator>himata4113</dc:creator><comments>https://news.ycombinator.com/item?id=48468112</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48468112</guid></item><item><title><![CDATA[New comment by himata4113 in "Claude Fable 5"]]></title><description><![CDATA[
<p><p><pre><code>  > virtualization
  switching to opus 4.8
</code></pre>
ok fair<p><pre><code>  > embedded-allocator
  switching to opus 4.8
</code></pre>
urgh fine<p><pre><code>  > chrome
  switching to opus 4.8
</code></pre>
are you kidding me?</p>
]]></description><pubDate>Tue, 09 Jun 2026 18:05:22 +0000</pubDate><link>https://news.ycombinator.com/item?id=48465015</link><dc:creator>himata4113</dc:creator><comments>https://news.ycombinator.com/item?id=48465015</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48465015</guid></item><item><title><![CDATA[New comment by himata4113 in "Claude Fable 5"]]></title><description><![CDATA[
<p>concept is similar to how it works in inference, instead of performing regressive writes to the entire model you run the whole model, but part of the model can live in system memory and get swapped in/out on demand. So only XB parameters are active in training.<p>edit: I am not really sure if it works like that. I haven't looked too deep into deepseek v4 pro specifically.</p>
]]></description><pubDate>Tue, 09 Jun 2026 18:01:54 +0000</pubDate><link>https://news.ycombinator.com/item?id=48464959</link><dc:creator>himata4113</dc:creator><comments>https://news.ycombinator.com/item?id=48464959</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48464959</guid></item><item><title><![CDATA[New comment by himata4113 in "Claude Fable 5"]]></title><description><![CDATA[
<p>MoE experts were likely trained independently / in a sparse format. Training anything beyond 2t on typical systems would be infuriantingly slow, you could do 4t on nvidias room-scale solution, but for a reasonable training speed / batch size it caps around 3t.</p>
]]></description><pubDate>Tue, 09 Jun 2026 17:37:23 +0000</pubDate><link>https://news.ycombinator.com/item?id=48464490</link><dc:creator>himata4113</dc:creator><comments>https://news.ycombinator.com/item?id=48464490</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48464490</guid></item><item><title><![CDATA[New comment by himata4113 in "Claude Fable 5"]]></title><description><![CDATA[
<p>They're trained in a model class likely in 2t to 3t range. It's very unlikely that chinese labs have access to gpu systems capable of training models like that, let alone serving them. This requires proprietary room-scale systems which fetch a huge premium over typical 10 slot systems.<p>I am sure that they can develop their own equivlient version of such clusters in around 1 year though. Distilling fabel 5 will also go a long way.</p>
]]></description><pubDate>Tue, 09 Jun 2026 17:27:33 +0000</pubDate><link>https://news.ycombinator.com/item?id=48464309</link><dc:creator>himata4113</dc:creator><comments>https://news.ycombinator.com/item?id=48464309</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48464309</guid></item><item><title><![CDATA[New comment by himata4113 in "Siri AI"]]></title><description><![CDATA[
<p>Apple could have the same kind of permission dialogues with their own models (and they actually should). Each and every (first-time) use of a feature should:<p><pre><code>  1) ask for permission explaining the scope
  2) warn you about the dangers with a confirmation / nevermind option
</code></pre>
Putting this in practice:<p><pre><code>  1) Acme AI requires access to your email provider in order to execute this request. Grant / Deny
  2) You're about to let Acme AI read and send emails on your behalf, this might be dangerous due to X and Y. Do you want to continue? / Nevermind.
</code></pre>
In this case:<p><pre><code>  1) Asks for access to a service
  2) Asks for a specific use-case of the service
</code></pre>
1 is access to data, you might want to give broad access to some applications and input data<p>2 is permission to act, but you might want to deny access to some parts such as sending email and scope to summarization</p>
]]></description><pubDate>Mon, 08 Jun 2026 23:46:08 +0000</pubDate><link>https://news.ycombinator.com/item?id=48454063</link><dc:creator>himata4113</dc:creator><comments>https://news.ycombinator.com/item?id=48454063</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48454063</guid></item><item><title><![CDATA[New comment by himata4113 in "Siri AI"]]></title><description><![CDATA[
<p>"Trusted System Agent" imo sounds like an apple approved agent which would only be available to companies that accept apples (likely unreasonable) demands and would completely lock smaller companies out of the ecosystem.</p>
]]></description><pubDate>Mon, 08 Jun 2026 21:47:20 +0000</pubDate><link>https://news.ycombinator.com/item?id=48452677</link><dc:creator>himata4113</dc:creator><comments>https://news.ycombinator.com/item?id=48452677</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48452677</guid></item><item><title><![CDATA[New comment by himata4113 in "Siri AI"]]></title><description><![CDATA[
<p>I read through the entire DMA rant that apple has here: <a href="https://www.apple.com/newsroom/2026/06/due-to-dma-siri-ai-delayed-in-eu-for-ios-27-and-ipados-27/" rel="nofollow">https://www.apple.com/newsroom/2026/06/due-to-dma-siri-ai-de...</a><p>This feels like it could be solved with a list of permissions that the user has to turn on when using 3rd party AI.<p>Apple already:<p><pre><code>    1) requires developers to submit ID to publish an app on the appstore (at least I had to after ~1000 downloads to be able to publish an update)
    2) has strong kernel enforced memory integrity and disallowes arbitrary code execution (unless explicitely approved for games like roblox, jitting not allowed tho has to be interpreted).
    3) reviews every app update.
</code></pre>
I feel like this is nothing more than Apple being angry that they have to allow people to actually choose what AI they want on their phone. This is particulary interesting if anthropic and openai decided they want to add siri ai override to their apps allowing them to take advantage of the apple ecosystem without signing some kind of deal like they had to with Google. I assume behind closed doors Google had to make some sacrifices for them to be the model powering siri.</p>
]]></description><pubDate>Mon, 08 Jun 2026 20:59:36 +0000</pubDate><link>https://news.ycombinator.com/item?id=48451954</link><dc:creator>himata4113</dc:creator><comments>https://news.ycombinator.com/item?id=48451954</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48451954</guid></item><item><title><![CDATA[New comment by himata4113 in "Siri AI"]]></title><description><![CDATA[
<p>Change your region. I've done so and haven't particulary noticed anything off, all the EU specific apps are weirdly still available in US appstore.</p>
]]></description><pubDate>Mon, 08 Jun 2026 19:05:31 +0000</pubDate><link>https://news.ycombinator.com/item?id=48449974</link><dc:creator>himata4113</dc:creator><comments>https://news.ycombinator.com/item?id=48449974</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48449974</guid></item></channel></rss>