@arfonzo.eth
Agreed with frenpai @adnum. We tried to make it work with a single, all-encompassing @imgn platform. Traditional organisations didn't like this mix--not just payment providers. Some insight that I can probably now share:
- Payment providers being li'l bitches to Mastercard and Visa, of course did not accept this, given the global sweeping changes from last autumn. That locked out a lot of our userbase from payments.
- Advertisers and marketers did not like this, as SFW was at risk of contagion with NSFW content.
- Surprisingly, NSFW advertisers and marketers also did not like this: they want it all NSFW.
Most importantly for me (PERSONALLY), many users were uncomfortable using @imgn in a work or personal context where it just wasn't that SFW. Imagine trying to use it with your children to generate some colouring sheets, then some massive tits and cocks show up. Or they see other inappropriate disturbing content.
The last point is actually kinda important: I've never let my daughter anywhere near my office when I'm on the IMGN website, for this reason. The risk of content contagion is real, from many perspectives not just payment providers.
The cleanest solution (having tried all other options), was to provide both SFW and NSFW content their own focused platform. It means both sides win, and both platforms can fully focus on each content type without worrying about the other.