Hi all! As promised, here is the proposed text of the newest version of the rules. The staff has gone through like eight drafts and literally thousands and thousands of matrix posts to get here, so please be kind. You can see @limeey’s comment on the transparency post if you want more insight into how this sausage was made.

We are opening these rules to commentary from the community before they go into effect. To be clear, this isn’t a vote, but we will take all community feedback into account and answer whatever questions we can before finalizing anything.

Please keep in mind that we are not Reddit, we do not have Reddit’s resources, and safety and consent are our priorities.

I’ll post the draft in two parts in two comments: The new sidebar, and the FAQ/clarifications page.

  • @[email protected]English
    10•1 year ago

    For OC posts in c/gonewild and similar communities, mods of that forum must comply with our verification requirements. For OC, verification counts as sourcing which means it is not strictly necessary but strongly encouraged. We plan to implement a sitewide verification procedure soon, but until we do it’s down to each community’s mods.

    I assume “we plan to implement a sitewide verification procedure” doesn’t mean it will be needed to use the instance, but just for any posting or mod work.

    • @[email protected]MEnglish
      10•1 year ago

      Correct. It won’t be for using the site in general, rather for those posting OC so they can be sourced and vouched for. It’ll be the same as others where we won’t outward require all to be verified before posting always, but more so in the same instance we don’t outright require sourcing but strongly suggest it. If it’s not sourced, and issues is raised and it seems to be probable/sourcing isnt there and we cant really verify beyond that, it’ll be removed and its on the user to appeal that. It’ll be a means of “sourcing” OC creators basically. We plan on trying to hash it out more but it will likely work similarly to reddit sub specific verification (but sitewide) with an OC verification and an age verification when in question. More info will be available as we hash it out more. Think the way gonewild does, like holding a sign. We want to have more control over it than reddit did and also make sure the people we are placing in the specific community responsible for doing verifications are fully vouched for by site staff instead of having a bunch of communities making up their own procedure and that own mess.

      • Kelly SunshineEnglish
        16•1 year ago

        Could something like how Mastodon handles verification be implemented here?

        I like how that method retains our privacy (and our sanity, from having to take dozens of verification photos in various angles for picky subreddit mods.)

        Even without a website to paste html into, something like, adding a user specific verification code into their public profile on an 18+ site where their ID has already been checked (if the user is selling on an adult platform, for example.)

        Of course, this would not work for users without these pre-verified profiles, but I think it’s a good start.

        • @[email protected]MEnglish
          7•1 year ago

          We are hoping to incorporate that in some way, potentially adding your lemmy account link temporarily to an existing adult platform that we know has age verification checks. We want to avoid having to check government IDs if we can, or at the very least have options for those who don’t want to.