<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: aka13_404</title><link>https://news.ycombinator.com/user?id=aka13_404</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Thu, 18 Jun 2026 02:56:04 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=aka13_404" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by aka13_404 in "Volkswagen started blocking GrapheneOS users"]]></title><description><![CDATA[
<p>This is sadly not even the full extent of it. What they did is, they locked their api entirely for anything that is not play protect certified. That means, all the cool stuff that was doable via community-driven projects is now dead in the water.<p>The "app" they provide is 60% advertisement, 30% features, and I unironically preferred using a Home Assistant connection instead of of it for everything. Even for automations like "when to preheat the car", since that was easier and more intuitive outside of their native function.<p>This also means, that charge control from the cars side is not possible to automate anymore.<p>Sure, one could take the position "but it was never officially promised", but for some people, including me, having the api (which is paid btw) was a selling point.<p>Yes, I registered specifically for this comment.</p>
]]></description><pubDate>Wed, 17 Jun 2026 15:57:44 +0000</pubDate><link>https://news.ycombinator.com/item?id=48572286</link><dc:creator>aka13_404</dc:creator><comments>https://news.ycombinator.com/item?id=48572286</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48572286</guid></item></channel></rss>