The shrines were a giant sticking point for me, because they totally missed the purpose of dungeons in previous Zelda games. I was a big fan of the “puzzle box” style dungeons in previous games, where changes you make in one room can affect things across the entire dungeon. And the shrines completely erased that, by being totally separate entities.

And sure, you could argue that the divine beasts were puzzle boxes, but that actually brings up my second complaint; All of the previous Zelda dungeons felt different. The forest temple felt dark and gloomy, like you were lost in a forest. The water temple was obviously made by the Zora and had distinct architecture. In BOTW, every single divine beast had the exact same architecture, the exact same theme, the exact same enemies. They didn’t feel like products of their environment, which made them feel very sterile.

Even the statement he released at the time sounded more like “I’m sorry he said it out loud, please don’t send neo-cons to shoot up our concerts.”

The app has already been inactive for a while now. There hasn’t been any active development in several years. They clearly have no interest in continuing it, and just want to move on to other projects.

1. This hasn’t been a notable issue in a while. That’s why Plex’s https-by-default was such a big deal. With https, even your ISP can’t see what you’re streaming. They can see that something is being streamed, but not what specifically.

Also, you totally glossed over the fact that Plex is simply easier for non-savvy people to set up. Plex provides a unified login experience similar to major streaming services, which Jellyfin simply can’t provide; If your mother-in-law can figure out how to log into Netflix on her TV, she can figure out how to log into Plex too.

And the unfortunate truth is that Plex’s remote access is much easier for 90% of users to figure out. It doesn’t require VPNs or reverse proxies at all. You just forward a port and anyone with access can easily see your server. But my MIL’s TV doesn’t even have access to a Jellyfin app without sideloading. Not to mention the fact that I’d need to walk her through actually setting the app up once it is installed, because there is no unified system for logging in. And if I’m not using a reverse proxy for my Jellyfin server, then I also need to walk her through setting up Tailscale, assuming her TV is even capable of using it at all.

Any single one of those hurdles would make Jellyfin a non-starter if I want to walk my MIL through the setup over the phone, and they’re all currently present. And some of them will never be fixed, by design. For instance, the lack of a unified login page is by design, because a unified login would require a centralized server for the app to phone home too. That centralization is exactly what Jellyfin was made to rebel against, so it’s a problem that will never be “solved”; It is seen by the devs and FOSS enthusiasts as a feature, not an issue.

From a FOSS perspective, Jellyfin is a modern marvel. But it’s definitely not at the same level as Plex when you compare ease of setup or remote access. Jellyfin is fine if you’re just using it locally, or are willing to run Tailscale to connect back to your home network. But if you’re looking for true seamless remote access and need to consider the mother-in-law factor, then Plex is hard to beat.

In America, the reason is basically “religion”. There are architectural standards which designers refer to for guidance, and the dude who did the architectural standard for restrooms was super hardcore religious. His standard called for big gaps in all the seams, to prevent people from masturbating in the stalls. Basically, he wanted people to be able to peek into stalls, as a sort of modesty check. And eventually, it just became accepted as normal, even though everyone (including Americans who were born and raised with them as the standard) hates the huge gaps.

In modern day, they’re mostly done to deter drug use. I guess the reasoning is similar, with the large gaps intended to allow people to peek into the stalls and see if someone is doing drugs.

Yeah, newer generations have been raised on tech that “just worked” consistently. They never had to do any deep troubleshooting, because they never encountered any major issues. They grew up in a world where the hard problems were already figured out, so they were insulated from a lot of the issues that allowed millennials to learn.

They never got a BSOD from a faulty USB driver. They never had to reinstall an OS after using Limewire to download “Linkin_Park-Numb.mp3.exe” on the family computer. Or hell, even if they did get tricked by a malicious download, the computer’s anti-virus automatically killed it before they were even able to open it. They never had to manually install OS updates. They never had to figure out how to get their sound card working with a new game. They never had to manually configure their network settings.

All of these things were chances for millennials to learn. But since the younger generations never encountered any issues, they never had to figure their own shit out.

Basically, Trump’s war team accidentally added the lead editor for The Atlantic to a Signal group chat where they were discussing detailed war plans.

It immediately raised a lot of questions with uncomfortable answers. Why are they using Signal, which doesn’t comply with federal records keeping requirements? Why didn’t anyone notice the massive security breach immediately? What was discussed, and how would it impact national security? Did anyone besides the editor have access to the chat? Was Pete Hegseth (current Secretary of Defense, and a known alcoholic who has been caught drunk at work numerous times) drunk when he added the editor to the chat? Why does one of the chat members’ flight logs show them in Russia during the time that all of the sensitive messages were being sent? Along with a lot of other questions, that are honestly too numerous to list…