@sleepybisexual lol.
It works by, for an AMAB, removing the scrotum and tedticles, leaving the penis as is, then crafting a shorter vulva with or without, according to the preference of the person getting it, a standard vaginal canal where the perineum would otherwise be.
So, yes. It would remove the testes, ending major testosterone production (your adrenal gland would still make some--usually enough to meet your needs otherwise).
@snarfed.org @activitypubblueskybridge @fedidevs @fediversenews
Such a service should be opt-in only, for the handful of folks who DO want their content used to generate traffic for Bluesky.
As I'm not one of those people, I am notifying you that I am opting out. It'd be nice if that request was honored, but realistically I know it won't be.
So fuck you.
@narada @Ottovonshitpost @sickburnbro
Also, why would you care?
A definition of a word is by definition (ironically enough) whateverthefuck you decide it to be.
So, even if it was gender == sex 50 years ago, it isn't now, and it can be 10 years from now.
for ages my brain has continually looped around the standard point of how 4D chess is every normal 3D game of chess being played, but since 4am this morning when i woke up ive been realised the fact that 2D chess is the most common form of chess that most chess masters play these days online. So now im stuck trying to conceptualize what 1D chess is, and how absolutely difficult to play that would be.
So in summary 1D chess and 5D chess are where it gets difficult while 2D-4D chess is all the same degree of difficulty.
qemu arm will not successfully load an uncompressed kernel because it hardcodes the load address as 0x40010000, which is not an offset of 0x8000 from a nice round number and apparently that offset is required. It will load a zImage (#liminix doesn’t currently build this target because we use U-boot everywhere else and why ship a self-extracting compressed kernel when that task can/should be performed by the bootloader) because they can relocate while uncompressing, and apparently it will also load a U-boot uimage - but looking at the source code I think it’ll only load the old-style uimage and not the FIT uimages that #liminix is using on arm{32,64}. Or I could use -device loader instead of -kernel and have full control of where it loads into, but then it’s not called with the DTB address in r2 as the linux kernel expects it to be.
So many options, none of them really very good…
Background reading upon which some of these assertions are based: https://people.kernel.org/linusw/how-the-arm32-kernel-starts
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.