Onboarding with mandatory @everyone channel makes it unusable

Kommentare

8 Kommentare

  • Lettuce

    Not sure exactly what you mean by "can't put the security we want" but here's a tip.

    With any good general-purpose moderation bot, you can have it auto-assign a role to new joins, say, for example an "Unverified" role. So if you have channels that @ everyone can see, you can change the perms for that auto-assigned Unverified role so it can't see any of those channels. Then have a verfication method, something like Wick, and when they complete the verification it replaces the Unverified role with your generic Member/Verified role. That way you can keep onboarding, but still keep your server safe. And if someone joins with an older version of DC, they'll still be assigned that Unverified role until they Verify themselves. Hope that helps

    0
  • SimonB

    Lettuce the problem is I don't have 5 channels where everyone can read and write. 

    I was using the onboarding and was enforcing people to take a role for no one to have only the @everyone role but still some people managed to bypass it and managed to get only the @everyone role so it was messing everything up. 

    Since then I added Double Counter (so people get unverified role when they join). 
    I also have a verification channel for users who were on the server before I installed Double counter so they can verify and to make sure and people only see this, nothing more until they verify.

    After that most of my server is for members only (we give them a proper role) so basically I have no channel at all in read/write for the role @everyone so I can't use the onboarding.

    Tried to put onboarding again and it mess with Double counter people manage to join server without getting the role Unverified so they can see and chat in those infamous @everyone channels ... 

    0
  • icedqueen

    Pretty sure "Switch to Advanced Mode" bypasses those requirements.

    1
  • SimonB

    Well I spent 3 hours talking with DC and we came up to the conclusion that onboarding in his actual state is making things bug no matter what you try to do. 

    Preventing DC to give the unverified role while allowing people to bypass the onboarding making them roleless on the server is just not possible. I reverted back to the good old welcome screen. 
    My community will not benefit from the onboarding good features due to that. Sad but security comes first.

    Advanced mode still asks you to have those stupid channel for everyone.

    0
  • icedqueen

    Not sure I understand. Have you tried enabling Advanced Mode? That should bypass the requirement to have the amount of channels @everyone can chat in iirc. That way you can still use the Onboarding features, but do not need to make major adjustments to your channels / server.

    I didn't see your edit until I sent this lol.
    That does suck, but you could try to have 5 channels that @everyone can read and send messages in?

    0
  • SimonB

    Well we have a verification process to prevent nobodies to read and chat for security reasons and our service is based on being a member gives you access to the discord hidden community channels so no I can't have such channels. 

    Anyway like I said talking with Double Counter staff just like they did, we decided to turn onboarding off until (if ever) Discord do something good enough for closed and secure servers. 

    0
  • icedqueen

    Understandable. Personally I think the requirements of channels are fine. However, I think the Advanced Mode should bypass it entirely as many communities, including your own, has this issue.

    0
  • SimonB

    I totally agree. My needs are not the needs of everyone but we are a lot of server in my case, and not small servers. Just like you said Advanced Mode should totally bypass this requirement and allow you to do what you want since you are in the advanced mode. 

    Let's hope Discord will do something at some point. 

    0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.