JRaccoon

Obviously I’m not a lawyer but I don’t see what law they could use to shut it down. All it’s doing is accessing publicly available data via a proxy. It’s not like it’s exploiting Instagram somehow.

If they wanna stop it, they can do what Twitter did and start requiring an account to see almost anything. Personally I suspect Meta is slowly going towards that.

Awesome! Got it running and seems to work well. Also I love the CLAUDE.md file you got there in the repo 🐈

Most browser compatibility issues come from JavaScript, not HTML/CSS. Unless you want to support ancient/dead browsers (like Internet Explorer or non-HTML5 browsers), it’s very likely there won’t be any issues.

MDN has a compatibility table for every HTML tag and CSS property. For a simple static site I would just manually check there.

Original source: https://blog.joinmastodon.org/2025/10/our-ideas-about-packs/

Reading this thread, I’m so glad I live in a country where government procedures at least somewhat make sense. I don’t think there’s any other place where the government failing to pass a budget wouldn’t mean that government collapsing, new elections being called, and civil servants keeping the lights on until a new government is formed. It’s crazy that the biggest economy in the world can just stop paying its employees because two political parties can grind the whole system to a halt.

https://okm.fi/en/finnish-matriculation-examination

Everyone takes the same test with the same questions at the same time. It’s very strict. If you’re sick that day or show up even one minute late, you need to wait half a year for the next chance.

Yes, but everyone taking the test needs to take it exactly the same time. I think in most schools there wouldn’t be enough computers for everyone.

I see everyone in this thread recommending a VPN or reverse proxy for accessing Jellyfin from outside the LAN. While I generally agree, I don’t see a realistic risk in exposing Jellyfin directly to the internet. It supports HTTPS and certificates nowadays, so there’s no need for outside SSL termination anymore. (See Edit 2)

In my setup, which I’ve been running for some time, I’ve port-forwarded only Jellyfin’s HTTPS port to eliminate the possibility of someone ending up on pure HTTP and sending credentials unencrypted. I’ve also changed the Jellyfin’s default port to a non-standard one to avoid basic port-scanning bots spamming login attempts. I fully understand that this falls into the security through obscurity category, but no harm in it either.

Anyone wanna yell at me for being an idiot and doing everything wrong? I’m genuinely curious, as the sentiment online seems to be that at least a reverse proxy is almost mandatory for this kind of setup, and I’m not entirely sure why.

Edit: Thank you everyone for your responses. While I don’t agree with everything, the new insight is appreciated.

Edit 2: I’ve been informed that infact the support for HTTPS will be removed in a future version. From v10.11 release notes:

Deprecation Notice: Jellyfin’s internal handling of TLS/SSL certificates and configuration in the web server will be removed in a future version. No changes to the current system have been made in 10.11, however future versions will remove the current system and instead will provide advanced instructions to configure the Kestrel webserver directly for this relatively niche usecase. We strongly advise anyone using the current TLS options to use a Reverse Proxy for TLS termination instead if at all possible, as this provides a number of benefits