amethyst
I mentioned this in another recent thread, but I spent a lot of time looking through reddit threads where transgirls talked about body hair.
What I thought was interesting is that:
- while you do get a lot of responses that say it only somewhat reduces body hair
- there were several folk who said it eventually did pretty much stop growth in many places (especially the torso), but that it took 3-4 years.
- One thing generally agreed on was that no matter what, hair on the legs/forearms will stick around; that’s typical for cis women as well. (There’s a lot of variability where cis women will have noticeable hair, but almost always on the legs/forearms.)
In online spaces you’ll generally see a lot more folk in the 0-2yrs range of HRT (because they’re newer and have more things they want to talk about.) So my guess is that the long term reduction in body hair is larger than you’d think just skimming threads like this one.
I’m at a bit more than 2 years, and it definitely has reduced a lot on my chest/shoulders/back/butt/upper arms, but I still have to shave occasionally (especially chest/butt). For now I’m content to see if the rest goes away on its own.
Will I be able to go more than one day without shaving my body hair without looking at my chest and arms in disgust?
I’ve previously been curious about this, and I waded through a lot of reddit threads looking at all the anecdotal answers.
A pretty fair number of folk said they eventually saw a large reduction in body hair on the torso especially, but that it took 3-4 years.
You’ll also see a lot of folk on 2 years of HRT saying it gives only a little bit of reduction.
Hard to draw a strong conclusion here, but it seems hopeful! (I’m two years in and see some reduction, but I still have plenty of hair. Pretty sure it grows back much more slowly now, but since I didn’t shave my body pre-HRT it’s kind of hard to tell.)
I’ve watched four this season:
- Seven Spellblades: I assumed going in it would be fairly generic, but it’s turned into my overall favorite, mostly on the merits of the story itself. It does a surprisingly good job of maintaining a relatively large ensemble of MCs. (Also, given that the setting is kind of “dark anime harry potter”, I can’t help but appreciate the implied “fuck you” to JKR in one subplot.)
- Helck: not all the humor lands for me, but enough does that I really enjoy the show! The slowly unfolding plot is kind of neat too.
- Undead Girl Murder Farce: I really like the sense of humor and style in this one. At the start it seems like it’s going to be a bit like In/Spectre in terms of slow-paced mystery solving, but the action starts to pick up ~half way through the first cour.
- The vending machine iskei: I wouldn’t say it’s exactly a good show, but it’s been watchable enough I made it to the end of the season!
What I’m pretty sure is the creator’s name is watermarked in the top left – “Sangled”.
That let me find this post: https://www.deviantart.com/sangled/art/I-Made-a-Picrew-805976802
It says it was made private, but that you can still access it via this link: https://picrew.me/ja/secret_image_maker/GWQo0ayzr7bd5eKF. (I checked and it has the sunglasses and lips from your pic, so presumably it’s the right one!)
it seems to kind of match the manga’s art style, though.
You might want to start by looking at common last names for a region you identify with.
e.g. here’s a list of common surnames in England/Wales (Picked because I’m British myself)
If I had to pick from that particular list, I might go with:
- Valentine Yates
- Valentine May
- Valentine Frost
(also several borderline puns such as Valentine Hart, Valentine Rose, Valentine Day)
e: Oh also, I honestly didn’t think my full name flowed very well initially. But I got used to it over time!
Here is some previous discussion on whether to defederate from them due to worries about their moderation capacity (and how it leads to spam/etc): https://lemmy.blahaj.zone/post/1671319
So far, it seems that most of the spam etc isn’t making it through to people, which is great! It means we can keep things going as they are without it impacting people too much. Please use this thread to let me know if that changes though
This is such a shitty way to frame it.
I think folk should default to neutral pronouns, especially in trans safe spaces. But phrasing a failure to do so it as “misgendering trans people” is jumping straight to the most absolute bad-faith interpretation.
Then further, saying that anyone who does it is “a transphobe” is way off base. (It reminds me of Contrapoint’s bit about essentialism)
It’s also notable to me that you’re not asking for e.g. any change of policy here. You’re not trying to improve the way this instance is run to discourage folk from using masculine defaults.
You’re using this incident only to wage war against someone you were already in conflict with, and assuming that anyone who steps in and criticizes your behavior is taking sides in that conflict.
Agreeing with WontonSoup here:
Compartmentalize things so they all handle one thing individually and then you call those things from a main class is generally the way you’d do it.
OP, one common approach here is that code for calling to an external dependency should be split out into its own module that’s called from some central place. That’s a fairly natural way to organize code that tends to provide a good separation of concerns – a lot of the times there’s some sort of messy logic about calling an api or pulling something from the database, and its nice to have all that set aside from the core logic of what your app is actually doing.
As an app grows more complicated, you often end up wanting to add some additional layer. The result is a three-fold division at a high level: One “outer” layer dealing with the triggering context (e.g. an incoming http request), one core layer that handles any business/domain logic, and a third layer for handling all external dependencies. Then in each layer, you’d split things into specific files/modules based on grouped functionality.
There are a lot of specific ways of implementing this arrangement (and a lot of ways it can break down!), but the main point is to prevent certain types of complexity from creeping into places its not necessary. You want a structure that’s easy to test, easy to reason about and navigate, and is easy to modify going forward.
In your case it sounds like you could start pretty simply:
- An outer module/file for dealing with the triggering condition and its environment (which could be handling an http request, an executable invocation, a messaging bus signal, a scheduled job trigger, however you’ve set this up to run once/hour!)
- A core module that orchestrates the details of the process.
- One file/module each per type of external dependency.
Likely #2 could be folded into #1 for a simple project like you have in mind. It is still a good idea to at least separate it into its own method. :) You’ll inevitably want to run it on demand (whether testing manually, or writing some sort of unit/integration test.)
I can’t think of anything less trans-friendly than mandatory pronoun marking.
I quite liked this quote from Isabel Fall (more about identity than pronouns specifically, but still related!)
“We make boxes that seem to enclose a satisfying number of human experiences, and then we put labels on those and argue about them instead,” she says. “The boxes change over time, according to a process which is governed by, as far as I can tell, cycles of human suffering: We realize that forcing people into the last set of boxes was painful and wrong, we wring our hands, we fold up some new boxes and assure ourselves that this time we got it right, or at least right enough for now. Because we need the boxes to argue over. I do not want to be in a box. I want to sift through your fingers, to vanish, to be unseen.”