“Evolutionary reason” does not necessarily mean that a feature is an advantage. Mutations are random and then positive or negative selective pressure act on them untill the mutation is either extinct or is adopted by the whole population. For features without selective pressure the same thing still happens it just takes longer and is basically random. So different populations of a species will always develop different features even when given the same environment.

So for most of the features you listed: yeah it just happened.

You didn’t read the article did you? Its not about the inclusion of a character, but about how a specific scene with that character is handled. The author claims it is completely jarring, doesn’t fit into the games setting and doesn’t even use the games existing lore for transgender people but instead uses modern terminology.

I found the article to very informative and not at all “gamergatey”.

Its points are:

• this is the scene
• it is bad
• here is exelent trans representation in a fantasy setting
• “its a BioWare self insert”
• this is how they could have handled it better
• the game is great, but now everybody will just talk about woke, so again the game is good

No. The key looks strange and I hab to reread it a few times. I’m also quite certain I have seen the same joke before in a different comic

The ghost is sad because it locked itself out/forgot the key inside. Second ghost shows up an tells them to just warp through because they are ghosts. But instead of being happy they are inside and never needed the key, they try to move the key outside so they can unlock the door to get inside.

That is the “low tech”; works 100% of the time; will make your live easier in the future solution.

It takes longer than remounting but getting rid of a NTFS drive in a Linux only environment is a good move.

Then OP has to die in international waters. And I think ships usually count as part of the country they are registered in. So if you die on a cruise ship it still counts like dieing in that ships owner country. And its not trivial to move a corpse out of a country, there are laws about that. So the country they plan to die in very mutch matters.

Yes it is technically the diminutive form of Hahn which is german for rooster but “Hähnchen” is mostly just used to refer to the meat of any chicken. Like beef is the meat of a cow, Hähnchen is the meat of a chicken.

Client isolation doesn’t help. That is just the access point not routing traffic between connected devices. The problem with WiFi is it is a radio signal. Everybody in range can receive 100% of all communication on that network. Just by being in range the attacker can do passive sniffing. No wiretap needed like with cabled networks.

WiFi is encryoed if it uses a password. So any public WiFi without a password can be sniffed by literally every device in range (no need to connect to the WiFi for sniffing). On public WiFi with a password, the radio signal is encrypted but everybody knows the encryption key. So everybody connected to the WiFi can still sniff the traffic of everybody else.

That encryption is only on the WiFi level, so encrypted radio signals, not on the actually traffic level (like TLS/HTTPS etc).

.LAN is not an official top level domain. So I assume this is either your home network or work network? In any case your problem has nothing to do with the .LAN doman.

Maybe you have “https everywhere” activated. If so, Firefox will always default to https unless you specify http in the URL. Again, unrelated to .LAN.

For the certificate: what do you mean “when available”? A self signed cert is a self signed cert. There is no “available” or not. You can import the certificate into the Firefox trust store so Firefox will trust that one specific cert but any other self signed cert will cause an error. That is expected and save behaviour (and unrelated to .LAN).

No, why would it? It will run code in the context of the current user which is absolutely enough to start a new process that will run in the background, download more code from a attacker server and allow remote access. The attacker will only have as much permissions as the user executing the code but that is enough to steal their files, run a keyloggers, steal their sessions for other websites etc.

They can try to escalate to the admin user, but when targeting private victims, all the data that is worth stealing is available to the user and does not require admin privs.