@Raeve like yeah it makes sense to not start on a high dose when for all you know less might be enough, but there's no excuse to start at a dose that works for less than one in a thousand people. having E levels be a little higher for a bit isn't a big deal (and endos are too obsessed about only giving as much as strictly necessary, if that). start at a reasonable baseline, dose up or down as needed. unless the patient asks to start lower.
Hot take about HRT providers, at reader
If your levels are bad, it's not your body. Your provider just sucks. There is no argument otherwise. Blaming your body for 'not responding' is deflection, especially with spiro.
Slow titration of HRT in adults is complete and absolute bullshit. Just plainly transphobic "we want to make sure you want this" dogshit fucking nonsense.
Your provider will blame your body for your levels being bad instead of examining the care they're giving.
HRT isn't a fucking SSRI or antipsychotic or anything else with variable responses. Hormone levels will directly correlate with doses taken. No exceptions or weasel words about it. There is no 'ramping up', and anything about breast development especially is somewhere between cargo culting and fucking pseudoscience.
If you are an adult going on HRT, demand adult hormone levels from the start.
In transfems, that means trough levels above 100pgml E2 at absolute minimum. Anything less is a failure of one's provider.
Gonna reiterate this again with slightly less indignance to be outside of a CW because it's very very important:
If one is an adult seeking HRT, demand adult levels from the very start. One likely does not have the luxury of leftover childhood HGH to fill in any gap, nor do any desired effects have any reason at all to be delayed.
Adult HRT should reach adult levels from the start, no exceptions.
okay but what if ELF had a feature where a particular executable page would get mapped from a different offset in the file depending on CPU flags, so you could do CPU capability dispatch with literally zero runtime cost by just having several versions of the same page with different versions of the same function at the same mapped address
#OnThisDay, 24 Aug 1896, an unknown woman cyclist has a beer at the bar in New Jersey - making headlines in the New York Times.
Chapeau!
#WomenInHistory #OTD #History #WomensHistory #Cycling #AmericanHistory #Histodons
i'm the only true transgender woman in the internet because i have equal hatred for all of the programming languages, makig me purer than all of you
oh my fucking god. so i was having a problem when i enabled optimizations when compiling the doom port. memcpy ended up overwriting itself. so i looked into what was happening, and apparently memcpy just kept calling itself over and over. the reason? i was compiling my own version of memcpy, because i wasn't using the standard library, but i also didn't use the "-ffreestanding" flag, so gcc assumed i *did* have the standard library. so gcc, in its infinite wisdom, turned memcpy into another call to memcpy, resulting in a stack overflow.
Why is this the biggest salient? Because browser choice can *end* App Stores. Thoroughly and totally. And that's why Apple continues to fight real choice so damned hard. They're pulling out every stop -- including funding astroturf groups -- and risking every possible fine to keep true choice from emerging through a mechanism they don't control.
Small reversals like this are helpful, but Apple has continues to geofence and degrade the potential of real browser choice. And that's a scandal
The tech press continues to miss the biggest iOS anti-trust thrust: browsers. The press, that is, with the exception of The Register:
https://www.theregister.com/2024/08/24/apple_eu_browser_defaults/
Friend: What do you play games on?
Me: I play games on a switch!
Trans woman, bisexual, someone's fiancée, forever a programmer, poly, and former total mess