TransBucket.com was created Summer 2009 after the shutdown of Transster.com (2001-2009), a surgery photosharing website exclusively for FTMs. In Fall 2012, the original founders Kit and Ryan moved on from active management of the site, passing on responsibility to Alex.
Our historical origin is why the site is so heavily skewed in content towards FTMs. We've tried to build on the foundation of Transster, but offer a surgery outcomes resource for everyone, from FTMs to MTFs to genderqueers, gender non-confirming individuals, agender individuals, and everyone else who could benefit from exploring the real life experiences collected here. Since the site is for those that have undergone procedures, we don't actually require specific identifications. For that reason, we recognize even individuals that identify as "detrans" or "desisted" or "post-trans" (who may now also identify as "cis") should be welcome to share their medical experiences here with zero harrassment.
When you participate on the site, keep in mind our inclusive tenets, no matter how you identify or how you feel about your outcomes or the outcomes of others. Your outcomes don't predict other people's outcomes, and your feelings don't predict other people's feelings. It's easy to forget you're looking at real bodies, which belong to real human beings with real feelings. What you say has real consequences. Posts and comments are moderated by the community and volunteers, and can be removed at any time with no notice.
In 2021, Alex added ads to the site after paying for hosting costs out of pocket for almost a decade. With these ads, the site is now self-sustaining given the existing hosting costs and traffic level. If Alex is unable to manage the site at some point, another webmaster could take over without needing to contribute significant disposable income. You can still use an adblocker on your desktop to avoid the ads.
If you're interested in volunteering to help work on development efforts, moderation, or alternatives to funding the site, please reach out or feel free to cut us an issue on GitHub!