• 1 Post
  • 67 Comments
Joined 11 days ago
cake
Cake day: March 20th, 2025

help-circle






  • Torture has proven effective, but only before the torture actually starts. Basically, the victim is more likely to divulge good information when they’re anticipating the torture, as an attempt to get out of it. Basically, before the torture, there is still some level of rapport between the victim and the torturer. But once the torture starts, the rapport is gone and the victim will harden themselves and refuse, or intentionally give bad info. Or they will simply say whatever they think the torturer wants to hear to attempt to stop the torture, regardless of whether or not it’s accurate.

    Basically, the only time the torturer has any actual trust in the info is when the victim is trying to delay/avoid the torture. Once it starts, the torturer can’t actually trust anything the victim says. If getting info was actually the goal, the torturer could simply start prepping for the torture and never actually start it. Essentially, keep the victim in that initial “if I keep talking I can avoid the torture” phase.



    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.



  • The way The Sims does it is actually pretty interesting. The individual sims have very little behavioral coding involved. They’re basically just monitoring their individual needs. The vast majority of the objects contain “advertisements” that they broadcast, and the sims can simply look for nearby advertisements to decide on what to do.

    Basically, you have a sim. They are simply listening to advertisements that are being broadcasted by the objects around them. Maybe the kitchen sink says “Clean +3” while the shower says “Clean +7”. If the sim’s cleanliness meter is low, they’ll check for local “clean” advertisements and choose one. As their needs get lower and lower, they’ll be more likely to pick stronger advertisements. So a slightly dirty sim will be likely to choose the sink, but a very dirty sim will choose the shower.

    Then once they get to the chosen object, the object basically goes “okay, here’s how to interact with me”. The sim simply pulls from that pool of interactions for the specific object. There may be flags for specific interactions based on certain conditions, or certain traits that make a sim more likely to choose one object over another. For instance, if your sim is a witch, they may have specific magical interactions available. Or if a sim has the Active trait, they may be more likely to choose fitness-based advertisements.

    This makes adding expansions very easy. You don’t need to do a ton of coding for individual sims, to “teach” them how to use new objects. You simply add new advertisements to the objects you’re adding to the game, and make sure your interactions are properly flagged for the various conditions that can exist. And now those objects can be dropped directly into existing save files without any fuss.

    Worth noting that this advertisement system is what caused the infamous “my sim is using the bathroom sink to wash dishes” complaint that plagued the series for so long; the bathroom sink was nicer than the kitchen sink, so it had a better advertisement. The sim wasn’t looking at advertisements based on why they needed a sink. They just knew they needed a sink to wash dishes, and picked the one with the strongest advertisement.






  • But also, tetanus is commonly misunderstood. Scapes and scratches are extremely unlikely to result in tetanus, regardless of what causes it. Rust isn’t any more likely to transmit tetanus.

    Tetanus is an anaerobic microbe that can only really survive in deep cuts and punctures where air isn’t able to reach the wound. The spores are basically everywhere… But the spores only bloom and become dangerous when they come into contact with blood. Once they bloom, oxygen will kill them. So you don’t need to worry about it for surface-level scratches and scrapes, because the air will kill off any blooms. The only reason it is commonly associated with rust is because one of the more common puncture wounds is from stepping on rusty things.




  • .ml tends to moderate things before they get outrageous. The biggest issue is simply the censorship that happens quietly. It’s less “extremists screaming at each other/into the heavens” and more “Big Brother is ensuring you don’t accidentally post anything that goes against the officially approved narrative.” The heavy censorship ensures the echo chamber remains polite (because they leave very little room for disagreement) but very echo-y.

    So as an outsider looking in, you tend to see a bunch of polite discussion. It isn’t until you dig deeper (and see a bunch of the removed comments, and users who got banned for totally mundane things) that you actually begin to see the whole picture.