• 0 Posts
  • 116 Comments
Joined 11 months ago
cake
Cake day: February 1st, 2024

help-circle
  • Pick your favorite tech company, pick a small team with a “nerdy” engineering mandate, and I’m confident you’ll find the academic, geeky science and engineering types you’re talking about.

    They probably aren’t very vocal though, because 1) there’s a huge PR/marketing budget which is responsible for being the face of the company, and 2) well…these are nerdy STEM folks who probably like their job because they get very well compensated to be nerdy STEM types, and not because they’re fanboys/girls.








  • It’s completely context dependent; you’re right that using male/female is appropriate for humans in certain contexts, e.g., medical usage (“Patient, a 47yo female, presented with…”). But it is — for cultural and historical reasons — generally considered inappropriate to refer to our fellow humans that way in conversation.

    Re: mutt, fair enough. Bitch/stud are examples of how animal terms, when applied to humans, take on very different meanings. Purebred is afaik not specific to species, but it is wildly inappropriate to refer to people as such.

    At the end of the day, the logic behind what is and is not appropriate has history behind it; animal terms have been used extensively to refer to subjugated peoples; it may be scientifically accurate but that doesn’t mean that it’s inoffensive.


  • Of course we’re animals, but let’s use some common sense wrt cultural norms here. A dog of mixed lineage is mutt, but it’s completely inappropriate to refer to a multiracial person as such. A female dog is a bitch, a male is a stud; the sexism is pretty obvious when applied to humans. It’s fine to talk about owning a dog; it’s not ok to talk about owning another human (except perhaps children, in certain contexts).

    Yes, we are animals too, but that doesn’t mean we should talk about each other in the same way. (And I say this as a vegetarian who thinks we should treat all animals with significantly more respect than we currently do.)












  • My method:

    VPS with reverse proxy to my public facing services. This holds SSL certs, and communicates with home network through WireGuard link configured on my router.

    Local computer with reverse proxy for all services. This also has SSL certs, and handles the same services as the VPS, so I can have local/LAN speeds. Additionally, it serves as a reverse proxy for all my private services, such as my router/switches/access point config pages, Jellyfin, etc.

    No complaints, it mostly just works. I also have my router override DNS entries for my FQDN to resolve locally, so I use the same URL for accessing public services on my LAN.