I am trying to figure out how, or if there is a way, to restrict only New andãWWW (i.e. they meet both requirements) from being able to post in message areasãuntil they are upgraded. I was hoping to figure out that maybe I could set theãnew user level for those users to a separate value than for telnet/SSH/etc.ãusers.ã ãI have read here before that some people don't allow WWW users to post at allãeven after they are not new (which I don't want to do). I currently have itãset where all new users cannot post (or even see the message areas) by settingãone new user level that is lower than the access level for all the areas.ã ãIs there a way to set the new-user access level for WWW new users to a lowerãvalue than the others, or restrict their posting abilities while they areã"new"?ã ãI checked the wiki and the docs but couldn't find what I was looking for.ã ãThanks!ãã---ã þ Synchronet þ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTPã

Re: Prevent New Web users from postingã By: Dumas Walker to All on Fri Dec 30 2022 10:44 amãã > I am trying to figure out how, or if there is a way, to restrict only Newã > and WWW (i.e. they meet both requirements) from being able to post inã > message areas until they are upgraded. I was hoping to figure out thatã > maybe I could set the new user level for those users to a separate valueã > than for telnet/SSH/etc. users.ããBetter yet, just check the protocol in the posting requirements string:ã LEVEL <upgraded> OR PROT != HTTP*ããWhere <upgraded> is your upgraded-user level. That should do what you're wanting. "HTTP*" should match either "HTTP" or "HTTPS".ãã > I have read here before that some people don't allow WWW users to post atã > all even after they are not new (which I don't want to do). I currentlyã > have it set where all new users cannot post (or even see the message areas)ã > by setting one new user level that is lower than the access level for allã > the areas.ã >ã > Is there a way to set the new-user access level for WWW new users to a lowerã > value than the others, or restrict their posting abilities while they areã > "new"?ã >ã > I checked the wiki and the docs but couldn't find what I was looking for.ããhttps://wiki.synchro.net/access:requirementsã-- ã digital man (rob)ããRush quote #28:ãThe future pre-decided, detached and subdivided in the mass production zoneãNorco, CA WX: 55.5øF, 86.0% humidity, 0 mph E wind, 0.00 inches rain/24hrsã---ã þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.netã

I am trying to figure out how, or if there is a way, to restrict only Newã> > and WWW (i.e. they meet both requirements) from being able to post inã> > message areas until they are upgraded. I was hoping to figure out thatã> > maybe I could set the new user level for those users to a separate valueã> > than for telnet/SSH/etc. users.ãã> Better yet, just check the protocol in the posting requirements string:ã> LEVEL <upgraded> OR PROT != HTTP*ãã> Where <upgraded> is your upgraded-user level. That should do what you'reãantiã> . "HTTP*" should match either "HTTP" or "HTTPS".ããI don't this fixes it, unless I am misunderstanding the conditionãstatement.ããI want to limit *only* *new* web users from being able to post until they areãupgraded. I think your way would still limit everyone until they areãupgraded (first half of statement satisfied), but would never allow web usersãto post (second half satisfied), which is what I am trying to avoid.ããI think that would require something like this:ããIF PROT = HTTP*ã LEVEL <upgraded WWW>ãELSEã LEVEL <that it used to be before WWW spammer problems>ãEND-IFããI think I can phrase that in a synchronet conditional statement like this:ããLEVEL <upgraded WWW> OR (LEVEL <something lower> AND PROT != HTTP*)ããFrom the wiki page, Nested example 2, it does look like I can nestãstatements that way, and SCFG (under linux) will just BARELY let me getãthat typed in. :)ããNow, is there a way to set that globally for all message areas? I thoughtãI could set a global requirement under SCFG -> Message Options but Iãdon't see it there.ããThanks!ããã * SLMR 2.1a * Basic Flying Rule #1: Keep the pointy end forward.ãã---ã þ Synchronet þ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTPã

Re: Prevent New Web users froã By: Dumas Walker to DIGITAL MAN on Sat Dec 31 2022 11:04 amãã > > > I am trying to figure out how, or if there is a way, to restrict onlyã > > > New and WWW (i.e. they meet both requirements) from being able to postã > > > in message areas until they are upgraded. I was hoping to figure outã > > > that maybe I could set the new user level for those users to a separateã > > > value than for telnet/SSH/etc. users.ã >ã > > Better yet, just check the protocol in the posting requirements string:ã > > LEVEL <upgraded> OR PROT != HTTP*ã >ã > > Where <upgraded> is your upgraded-user level. That should do what you'reã > antiã > > . "HTTP*" should match either "HTTP" or "HTTPS".ã >ã > I don't this fixes it, unless I am misunderstanding the conditionã > statement.ã >ã > I want to limit *only* *new* web users from being able to post until theyã > are upgraded. I think your way would still limit everyone until they areã > upgraded (first half of statement satisfied), but would never allow webã > users to post (second half satisfied), which is what I am trying to avoid.ããThat's exactly what the requirements string I provided does:ããSecurity level must be greater than or equal to the <upgraded> level, ORãtheir protocol must not be HTTP*. If their protocol is not HTTP*, then the security level doesn't matter.ãã > I think that would require something like this:ã >ã > IF PROT = HTTP*ã > LEVEL <upgraded WWW>ã > ELSEã > LEVEL <that it used to be before WWW spammer problems>ã > END-IFããNope.ãã > I think I can phrase that in a synchronet conditional statement like this:ã >ã > LEVEL <upgraded WWW> OR (LEVEL <something lower> AND PROT != HTTP*)ã >ã > From the wiki page, Nested example 2, it does look like I can nestã > statements that way, and SCFG (under linux) will just BARELY let me getã > that typed in. :)ããYou don't need a nested example because there are only 2 conditions.ãã > Now, is there a way to set that globally for all message areas?ããIf you're running v3.20a, doing a search/replace of the "post_ars" key values should be easy with most text editors.ãã > I thoughtã > I could set a global requirement under SCFG -> Message Options but Iã > don't see it there.ããNo, the closest thing is the template sub-board that you clone to the rest of the message group with a single operation in SCFG.ããAlso, ecWeb supports its own set of newuser values:ãhttps://wiki.synchro.net/config:webv4#new_user_valuesããSo you could just give new users via web the 'P' restriction and then remove it when they're validated.ã-- ã digital man (rob)ããSynchronet/BBS Terminology Definition #85:ãTTY = Teletype (dumb terminal)ãNorco, CA WX: 56.5øF, 95.0% humidity, 0 mph E wind, 0.04 inches rain/24hrsã---ã þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.netã

That's exactly what the requirements string I provided does:ãã> Security level must be greater than or equal to the <upgraded> level, ORã> their protocol must not be HTTP*. If their protocol is not HTTP*, then theãecã> ity level doesn't matter.ããIf the default new user level is 50, and I don't want anyone under 50 to beãable to post, then it does matter.ãã> > Now, is there a way to set that globally for all message areas?ãã> If you're running v3.20a, doing a search/replace of the "post_ars" key valuesã> ould be easy with most text editors.ããI am running 3.19 for now. Will keep this in mind when I upgrade. Forãreference, what text file would I be doing a search/replace on?ããã * SLMR 2.1a * The 4 major food groups: fast, frozen, junk, & spoiled.ãã---ã þ Synchronet þ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTPã

Re: Prevent New Web users froã By: Dumas Walker to DIGITAL MAN on Sun Jan 01 2023 10:09 amãã > > That's exactly what the requirements string I provided does:ã >ã > > Security level must be greater than or equal to the <upgraded> level, ORã > > their protocol must not be HTTP*. If their protocol is not HTTP*, then theã > ecã > > ity level doesn't matter.ã >ã > If the default new user level is 50, and I don't want anyone under 50 to beã > able to post, then it does matter.ããIf the default level is 50, and you don't want the user to post, give the user the 'P' restriction.ãã > > > Now, is there a way to set that globally for all message areas?ã >ã > > If you're running v3.20a, doing a search/replace of the "post_ars" keyã > > values ould be easy with most text editors.ã >ã > I am running 3.19 for now. Will keep this in mind when I upgrade. Forã > reference, what text file would I be doing a search/replace on?ããctrl/msgs.iniã-- ã digital man (rob)ããSling Blade quote #23:ãKarl: I reckon I'm gonna have to get used to looking at pretty people.ãNorco, CA WX: 52.9øF, 95.0% humidity, 0 mph ENE wind, 0.12 inches rain/24hrsã---ã þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.netã