<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: ta576248_743568</title><link>https://news.ycombinator.com/user?id=ta576248_743568</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Wed, 29 Apr 2026 09:37:49 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=ta576248_743568" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by ta576248_743568 in "Apple declined to implement 16 Web APIs in Safari due to privacy concerns"]]></title><description><![CDATA[
<p>PWAs run from the browser sandbox which is generally much stricter than restrictions for native apps. Permission systems for native applications seems to be starting to follow browsers (flatpak, snap, .appx, etc.), but don't offer nearly the ability to restrict what a native app can do like the browser does.<p>In theory native apps are "trusted", but I think for the vast majority of users the trust between a companies website and app are equivalent, vetted the same, and probably do an equivalent amount of tracking if not more by the native app (facebook SDKs are pretty common in native mobile apps).</p>
]]></description><pubDate>Mon, 29 Jun 2020 18:27:41 +0000</pubDate><link>https://news.ycombinator.com/item?id=23680656</link><dc:creator>ta576248_743568</dc:creator><comments>https://news.ycombinator.com/item?id=23680656</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=23680656</guid></item><item><title><![CDATA[New comment by ta576248_743568 in "Megadesk"]]></title><description><![CDATA[
<p>It would probably be better to just implement continuous current (proportional to torque which is proportional to force up/down) limiting on the motor, that would prevent the desk from pushing up or down at a force that could injure someone. Not sure if this is directly controlling the motor or just communicating with the actual motor controller. If the motor controller is separate it may already do this.</p>
]]></description><pubDate>Mon, 29 Jun 2020 17:19:05 +0000</pubDate><link>https://news.ycombinator.com/item?id=23679659</link><dc:creator>ta576248_743568</dc:creator><comments>https://news.ycombinator.com/item?id=23679659</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=23679659</guid></item><item><title><![CDATA[New comment by ta576248_743568 in "Comcast, Mozilla strike privacy deal to encrypt DNS lookups in Firefox"]]></title><description><![CDATA[
<p>My understanding is that Comcast signs a legally-binding contract with Mozilla which imposes the requirements on them [0]. This obviously isn't perfect protection, but it substantially increases the risk of failing to adhere to the requirements. Mozilla claims "We intend to publicly document violations of this Policy and take additional actions if necessary." [1]. Presumably the additional actions include suing for damages pursuant to the breach of contract.<p>[0] <a href="https://blog.mozilla.org/netpolicy/2020/02/25/the-facts-mozillas-dns-over-https-doh/" rel="nofollow">https://blog.mozilla.org/netpolicy/2020/02/25/the-facts-mozi...</a>
[1] <a href="https://wiki.mozilla.org/Security/DOH-resolver-policy#Enforcement" rel="nofollow">https://wiki.mozilla.org/Security/DOH-resolver-policy#Enforc...</a></p>
]]></description><pubDate>Thu, 25 Jun 2020 15:16:58 +0000</pubDate><link>https://news.ycombinator.com/item?id=23641690</link><dc:creator>ta576248_743568</dc:creator><comments>https://news.ycombinator.com/item?id=23641690</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=23641690</guid></item></channel></rss>