Followup: We have published a post concerning the upcoming defed from woem.men.
Basically: we've noticed a pattern of behavior, been alerted to specific posts, and have overall determined that the reactions by admins have made us determine that it would be safer for our community to defed.
https://info.tech.lgbt/2025/01/12/defederating-from-woem-men.html
=> More informations about this toot | View the thread
tech.lgbt will be defederating from woem.men in two weeks time, on 15 January 2025.
While we have many connections of accounts between servers, we have received multiple credible reports of misconduct from the instance, including grooming and predation.
The scope goes beyond a single admin, and we feel that it is in the best interest of our members to block the entire instance, as opposed to a few individual accounts.
=> More informations about this toot | View the thread
Instance cost breakdown for November 2024:
Digital Ocean - $740.71
Mailgun - $13.60
DeepL Translate - $32.48
tech.lgbt Domain Registration - $6.10 (updated .lgbt TLD registration is $73.16/year, paid in November)
Total: 792.89
We want to thank our instance supporters on our Patreon and Liberapay for keeping the instance running!
https://www.patreon.com/techlgbt
https://liberapay.com/techlgbt/
=> More informations about this toot | View the thread
While we do not ask you to take our word on this incident, we do ask for understanding and sympathy that transparency - especially when previous opinion exists on a subject - has a cost of friction against preconceived notions, and sometimes these become too great for us to handle.
We try to do our best when we can, and we try to make sure that the woes of our instance do not become a subject of burnout for us. Otherwise we cannot put motivation towards our ideal of making this server a safe and welcoming fedi experience. We wish to persevere.
We have multiple ideas and efforts to improve our transparency, while avoiding these points of burnout, and we intend on sharing some of them soon.
=> More informations about this toot | View the thread
The user in question posted screenshots of DMs and these emails on their account, which then triggered our moderation rule on posting private conversation publicly (which is in place to prevent harassment). Subsequently, these posts were reported and removed under that rule by another moderator online at the time.
Since then, this incident has been the subject of much misunderstanding, reframing, and perspective that does not allow us to insert any statement of our own without it becoming subject to scrutiny as the incident is interpreted above. We know from many incidents - including a large and prominent one from 1 year ago - that public posting would not resolve the discussion. Instead, it would only serve as fuel for the discourse, and ultimately would put stress on us that we are not able to resolve, and would result in further proliferation of this perspective.
=> More informations about this toot | View the thread
During a particular heightened point in a discussion with one of our users, when emotions ran high, a user was contacted using their account email. Note that this happened during a time where many of us were under pressure due to the backlash of the moderation decision, and thus - to communicate to our users - this wasn't seen as a huge issue. We have since then - in discussion - decided that this isn't an acceptable approach in any moderation (and non-moderation) discussion with our own users, yet the fact this happened that way is unfortunate.
The admin in question (@david) also immediately realised and regretted this action, which was caused by high-running emotions. (See their reflection thread: https://tech.lgbt/@david/113526867417950887, and apology post: https://tech.lgbt/@david/113527795130206241)
=> More informations about this toot | View the thread
For those of you who are aware of the current meta of this server:
We're sorry that we haven't been able to respond to this, but the truth of the matter is is that this has blown up to such a degree that anything we'll communicate publicly will be used as fuel for further debate.
Last week, we had to make a difficult decision of blocking nano.lgbt due to then-unrevealed concerns of pedophilia, adding to a substantial number of previous suspensions of the owner. This caused a ton of debate, which we could not clear up easily.
The bind:
=> More informations about this toot | View the thread
We have both a Patreon and Liberapay that we are very thankful to have covered server expenses since November 2022 when it became too expensive to maintain privately.
If you feel so compelled to help support the instance, you can utilize either of those for a subscription, or for a one-time payment.
If you are unable to support, please do not feel the need to do so. We're glad to have you here!
https://www.patreon.com/techlgbt
https://liberapay.com/techlgbt/
=> More informations about this toot | View the thread
This is something that we've been meaning to post for a while. As the first attempt at posting some instance costs, this may not be complete or in a finalized format.
This covers costs for October 2024 approximately, as some services are billed partway through the month, and domain registration is annual.
$729.43 - Server and Storage on Digital Ocean
$28.09 - DeepL integration for automated translations
$7.74 - Mailgun for instance email delivery
$2.38 - Fastmail for instance email accounts
$4.76 - tech.lgbt domain registration ($57.16 for the year)
Total - $772.40
=> More informations about this toot | View the thread
=> This profile with reblog | Go to mods@tech.lgbt account This content has been proxied by September (ba2dc).Proxy Information
text/gemini