<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: random_human_</title><link>https://news.ycombinator.com/user?id=random_human_</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Tue, 14 Apr 2026 20:25:46 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=random_human_" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by random_human_ in "WiiFin – Jellyfin Client for Nintendo Wii"]]></title><description><![CDATA[
<p>The absolute worst thing I can see in there is that an third party who <i>somehow</i> managed to get a link to one of your library items (either directly from you or from one of your users--or by spending the next decade bruteforcing it I guess) could stream said item:
<a href="https://github.com/jellyfin/jellyfin/issues/5415#issuecomment-2825240290" rel="nofollow">https://github.com/jellyfin/jellyfin/issues/5415#issuecommen...</a><p>Everything else looks to me like unimportant issues, that would provide someone who's already logged in as a user minor details about your server.</p>
]]></description><pubDate>Tue, 14 Apr 2026 09:21:22 +0000</pubDate><link>https://news.ycombinator.com/item?id=47763209</link><dc:creator>random_human_</dc:creator><comments>https://news.ycombinator.com/item?id=47763209</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47763209</guid></item><item><title><![CDATA[New comment by random_human_ in "WiiFin – Jellyfin Client for Nintendo Wii"]]></title><description><![CDATA[
<p>If you expose Jellyfin on 443, have HTTPS properly set up (which Caddy handles automatically), your admin password is not pswd1234 (or you straight up disable remote admin logins), and use a cheap .com domain rather than your IP--what is the actual attack surface in that case?<p>As far as I can remember that is more or less what is usually suggested by Jellyfin's devs, and I have yet to see something that convinces me about its inadequacy.</p>
]]></description><pubDate>Tue, 14 Apr 2026 06:35:00 +0000</pubDate><link>https://news.ycombinator.com/item?id=47762019</link><dc:creator>random_human_</dc:creator><comments>https://news.ycombinator.com/item?id=47762019</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47762019</guid></item><item><title><![CDATA[New comment by random_human_ in "WiiFin – Jellyfin Client for Nintendo Wii"]]></title><description><![CDATA[
<p>For whatever reason people here and on Reddit will tell you that you need to have Jellyfin pass through five VPNs, otherwise nasty things will happen. Meanwhile the actual devs suggests simply setting up a reverse proxy, which you can do in two lines with Caddy:
<a href="https://jellyfin.org/docs/general/post-install/networking/reverse-proxy/caddy/" rel="nofollow">https://jellyfin.org/docs/general/post-install/networking/re...</a></p>
]]></description><pubDate>Tue, 14 Apr 2026 05:42:52 +0000</pubDate><link>https://news.ycombinator.com/item?id=47761690</link><dc:creator>random_human_</dc:creator><comments>https://news.ycombinator.com/item?id=47761690</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47761690</guid></item></channel></rss>