Conversation

Notices

Embed this notice
Andy (pixel@desu.social)'s status on Tuesday, 17-Sep-2024 08:05:09 JST Andy

"hoster prohibits nsfw so we add age verification" to change what about that exactly?
if the adult users post adult content you are still getting booted?
age verification is a spicy topic, but, once again:
keep your instances small, only allow registrations by request, and if you doubt someone's age, don't let them in, or ban them later.
on fedi it wouldn't even change much, they'd register elsewhere or self-host to get access to content.
RE: https://transfem.social/notes/9y9572m036ju0k4f
In conversation about 2 months ago from desu.social permalink
Attachments
1. Untitled attachment
2. Domain not in remote thumbnail source whitelist: transfem.social
  
  Amber (@puppygirlhornypost2)
  
  Disclaimer: I am not part of the sharkey project's leadership or management but I work closely with them... What in the fuck is happening with the "meta" in regards to PR number 611? (https://activitypub.software/TransFem-org/Sharkey/-/merge_requests/611). Let me explain some things to help clear up some issues... Misskey/Sharkey has a lot of optional services by default. These are not self hosted or managed by the instance administrator apart from an api token. Some examples: 1) hCaptcha/recaptcha/mcaptcha/turnstile Not every misskey/sharkey instance utilizes the hCaptcha service but some do in order to prevent bots. If you have followed me for a bit (on my old account i still need to migrate the clip itself) you'll be aware I have a collection of *horrible* inaccessible captchas. I use the clip to highlight the issue with modern captchas (showcasing how they can be inaccessible). 2) SMTP/Email There is an integration with third party email providers (I don't remember this particular email configuration for the instance I'll have to check with kio because he set it up for me). This is a completely optional service that relies on third parties for processing things (such as noreply@transfem.org). 3) DeepL translation I use the free tier of DeepL translation on this instance (I don't manage this, it is an api key i fed into sharkey that makes requests using that token on my behalf). It's an optional service that I had disabled prior because the previous api key was revoked. Now, with that out of the way... What is the PR actually doing? Well, a while ago we had this issue with hetzner. One of the things that Germany requires is that if you are hosting pornographic content that you must verify the age of all your users. This is why woem.men (when they considered specific images and the instance as a whole) was threatened by hetzner. To hetzner's perspective woem.men was operating as an adult website without proper verification in place and therefore a liability. Now, woem.men isn't strictly for that but lewd.lgbt is and so is kitsunes.gay. These are two instances that I have been involved with that are focused on adult only content. I want to talk about how kitsuverify works and how that led into this PR... Kitsuverify is what Kio has named a service that he made himself. What it does is that if there is reasonable suspicion someone is a minor we can put in the moderation notes "ADM/ID" to request additional verification through stripe. Most of the time, people who have 18+ in bio and who don't specify "I am a minor" do not ever go through the ID/Age verification process. This is reserved for people who have stated they are a minor, or for instance administrators (it was a bit insulting to go through age verification for my boyfriend's instance but i did). All the PR is doing is trying to add that same sort of functionality with stripe into sharkey as an *OPTIONAL* service that is disabled by default (you have to provide your own api tokens, it's also a billable thing kio gets billed every id that is processed). This is not "normalizing ID verification" this is trying to host adult only spaces in a legally compliant manner (at least back when they were on hetzner). You are free to keep this disabled on your instance, and I am not going to enable it for transfem.social because this is not an adult content orientated instance. We allow adult content sure, but it's a general purpose instance and not locked down to an adult only space like kitsunes.gay and lewd.lgbt are. Please stop harassing the lead maintainer of sharkey over this, it was a group decision that we thought would be a good idea to help server operators run adult instances in Europe and places that require ID verification. EDIT: To be clear, Hetzner does not allow adult content period. It doesn't change the fact Germany requires ID verification for adult websites. It is probably *why* they do not want to allow adult content on their platform as ensuring everyone is compliant would be a headache for a service provider.
- :blobcathug: likes this.

Public

Conversation

Notices

Feeds